Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
cleanup the msg handler interface a bit

was: 5db608d124c98fb288077f3db378d86c594886e4

    • -4
    • +3
    ./org/jboss/as/protocol/ProtocolMessages.java
  1. … 13 more files in changeset.
switch to a new channel when receiving a close message

was: 1b80975248003de7060f491c2de6acd9d129998a

  1. … 5 more files in changeset.
Mark operation future as failed if channel is closed

was: 351380586c8c556ebfed63757aed3b95fd9c1161

[AS7-1387] Minor modification to now supply an XnioSsl instance and enable SSL if the realm is configured with a SSL identity, also initial clean up of SSL settings for clients.

was: 4f9b5cc678b7985137a92178ce427098a1b02e31

  1. … 10 more files in changeset.
reuse connection and channel until closed

was: 933f1a866ddf25ddd205ea8a66ee0e2cde5e7265

    • -0
    • +295
    ./org/jboss/as/protocol/ProtocolChannelSetup.java
  1. … 3 more files in changeset.
use ProtocolMessages

was: 144e06d1c4f3173bf9af9d4244ae08231f4e0fb2

    • -0
    • +18
    ./org/jboss/as/protocol/ProtocolMessages.java
    • -16
    • +20
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
  1. … 3 more files in changeset.
[AS7-1457] Remove all manual SASL provider registrations.

was: fddfac1b3bf0e217d15907d294ae0b6374a1b3b9

  1. … 5 more files in changeset.
[AS7-2657] Disable the JBOSS-LOCAL-USER mechanism on clients that already know this is a remote call.

was: 302f12430551c33b9642ba9748b385b72db53bf3

[AS7-2719] Update RealmAuthenticationProvider to enable and configure the JBOSS-LOCAL-USER mechanism. [AS7-2730] CLI needs to verify that a username was actually entered when prompted.

was: 54e2444630e20164cffd72533efef99072824d7f

  1. … 2 more files in changeset.
[AS7-2658] Better error message to indicate authentication failure.

was: 4a2d981a2c13cfa6d401465e613c99bc56727153

  1. … 3 more files in changeset.
management protocol handling cleanup

was: e6eb03132958473d0784fd2832fb092a6bd03be2

    • -42
    • +11
    ./org/jboss/as/protocol/ProtocolChannel.java
    • -0
    • +6
    ./org/jboss/as/protocol/ProtocolLogger.java
    • -3
    • +3
    ./org/jboss/as/protocol/ProtocolMessages.java
    • -1
    • +19
    ./org/jboss/as/protocol/StreamUtils.java
    • -0
    • +75
    ./org/jboss/as/protocol/mgmt/AbstractManagementRequest.java
    • -0
    • +109
    ./org/jboss/as/protocol/mgmt/ActiveOperation.java
    • -0
    • +284
    ./org/jboss/as/protocol/mgmt/ActiveOperationSupport.java
    • -0
    • +122
    ./org/jboss/as/protocol/mgmt/FlushableDataOutputImpl2.java
    • -327
    • +17
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
  1. … 49 more files in changeset.
[AS7-809] Add id's to @MessageBundles where they were previously not added.

was: f89658cbfe9a6ccc9bbea8dab5147c7c018b246c

    • -32
    • +32
    ./org/jboss/as/protocol/ProtocolMessages.java
  1. … 2 more files in changeset.
[AS7-2396] The timeouts are no longer needed, better error message

was: 015a74c83142162339e02e16f24d02783483d0c5

    • -0
    • +8
    ./org/jboss/as/protocol/ProtocolLogger.java
    • -13
    • +5
    ./org/jboss/as/protocol/ProtocolMessages.java
Reintroduce ProtocolChannelClient.setExecutor() which is needed for backwards compatibility

was: f176d4627ffcda0a7c7b7332ebcf07e75575b015

    • -5
    • +9
    ./org/jboss/as/protocol/ProtocolLogger.java
    • -22
    • +6
    ./org/jboss/as/protocol/ProtocolMessages.java
[AS7-2084] Get rid of unneeded executor

was: bbb46b2c92d14c6f70f250040ace9aa22883fb76

  1. … 5 more files in changeset.
Update Remoting to fix close issues

was: 5f269946f78ebeabdb92456d69f8c9f626528d6e

    • -0
    • +6
    ./org/jboss/as/protocol/ProtocolChannel.java
  1. … 14 more files in changeset.
AS7-2110 Don't create multiple remoting Endpoints; clean up remoting resources

was: 5724d5dd2dd22c8ae0529658a728308aa2114735

  1. … 2 more files in changeset.
move the 'old' protocol into the process-controller module

was: dd88235097e602d14959983f1780169c6685fcef

    • -162
    • +0
    ./org/jboss/as/protocol/old/ChunkyByteInput.java
    • -130
    • +0
    ./org/jboss/as/protocol/old/ChunkyByteOutput.java
    • -42
    • +0
    ./org/jboss/as/protocol/old/ConnectionHandler.java
    • -403
    • +0
    ./org/jboss/as/protocol/old/ConnectionImpl.java
    • -262
    • +0
    ./org/jboss/as/protocol/old/Pipe.java
    • -185
    • +0
    ./org/jboss/as/protocol/old/ProtocolClient.java
    • -34
    • +0
    ./org/jboss/as/protocol/old/ProtocolConstants.java
    • -250
    • +0
    ./org/jboss/as/protocol/old/ProtocolServer.java
    • -0
    • +88
    ./org/jboss/as/protocol/StreamUtils.java
  1. … 55 more files in changeset.
Only send bye bye from the side initiating the shutdown

was: aaedb37262982761368733f989df3b39c7bd25a7

[AS7-809] Converted the protocol subsystem to use i18n loggers and messages.

was: fa76a317deaaab85303291fd62597ef3506db770

    • -9
    • +9
    ./org/jboss/as/protocol/ProtocolChannel.java
    • -0
    • +192
    ./org/jboss/as/protocol/ProtocolLogger.java
    • -0
    • +376
    ./org/jboss/as/protocol/ProtocolMessages.java
    • -34
    • +33
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
    • -24
    • +21
    ./org/jboss/as/protocol/old/ConnectionImpl.java
    • -10
    • +11
    ./org/jboss/as/protocol/old/ProtocolClient.java
    • -12
    • +12
    ./org/jboss/as/protocol/old/ProtocolServer.java
  1. … 1 more file in changeset.
[AS7-1650] Enable PLAIN mechanism for the Native interface.

was: c3272e9ff48db5281b5d1f492b324a584c85b5ae

  1. … 3 more files in changeset.
[AS7-1104] Wrap all JBossSaslProvider registrations in a PrivilegedAction.

Conflicts:

arquillian/container-managed/src/main/java/org/jboss/as/arquillian/container/managed/ManagedDeployableContainer.java

was: 1f09ce9d99970a2a7288fa92324d76109faf9a4b

  1. … 6 more files in changeset.
[AS7-1225] Call System.exit() no matter how the cli is run

was: 0dd4f078481485fc6f694c3c233978bba0bb3408

  1. … 1 more file in changeset.
Tidy up logging

was: 1b502d1d1fedf82bcf5efd85198fa508dcb3dee2

    • -1
    • +10
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
  1. … 1 more file in changeset.
Don't try to connect when creating the management client channel strategy

was: 11980e90896d5a513bb3cd4f08f6873d952daa05

Better message for when communication problems happen

was: 9db8c511bac8a7e66aab85e542591778beec6c27

  1. … 1 more file in changeset.
Add pings in protocol to detect things that go down ungracefully, since remoting does not do that for us in all cases

was: 4bf5542a2a249f15e9739f4d4c9de1acfe51c571

    • -0
    • +53
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
    • -0
    • +102
    ./org/jboss/as/protocol/mgmt/ManagementChannelPinger.java
    • -0
    • +39
    ./org/jboss/as/protocol/mgmt/ManagementPingHeader.java
    • -0
    • +39
    ./org/jboss/as/protocol/mgmt/ManagementPongHeader.java
  1. … 1 more file in changeset.
Clean up the bye bye shutdown stuff, and get ready for pings

was: 815720cb7072ff81d5646e9019aab2bc4fdfa028

    • -11
    • +18
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java
Implement shutdown in management protocol

was: c85640e627778afdf09c3a2e893c9566c258970e

  1. … 3 more files in changeset.
Handle channel close at management protocol level

was: f482dd23d645c9541ac2ff8ad3f3a3ab6b839a74

    • -3
    • +6
    ./org/jboss/as/protocol/ProtocolChannel.java
    • -0
    • +30
    ./org/jboss/as/protocol/mgmt/ByeByeException.java
    • -2
    • +47
    ./org/jboss/as/protocol/mgmt/ManagementChannel.java