• Changes to Client that require connect() be called

    This topic is in reference to http://jira.jboss.com/jira/browse/JBREM-366 The remoting code has been changed to use reference counting for client invokers created instead of re-creating new instances if the current o...
    Profile Photo
    last modified by tom.elrod
  • Broken connection listener test due to JBREM-382

    Test case org.jboss.test.remoting.lease.LocalLeaseTestCase within remoting test suite fails due to the changes for http://jira.jboss.com/jira/browse/JBREM-382 (also more info in http://www.jboss.com/index.html?module=...
    Profile Photo
    created by tom.elrod
  • local invoker behavior

    While working on JBREM-382, I realized might be good to get feedback on the behavior of the local invokers in general. To start, if a client and server are running within the same VM, the client will use a local invok...
    Profile Photo
    last modified by tom.elrod
  • remoting configuration semantics

    Currently the rules for configuration the Client and Connector is fairly loose. The problem is that the projects is getting too big to not have better constraints on when/where configurations can be set. Therefore, wo...
    Profile Photo
    created by tom.elrod
  • JBAS-2267 - PooledInvokers missing Version Information

    I'm looking at this issue, and it's not possible to fix Optimized*Stream without break binary compatibility. I could try adding some exception handling, but it doesn't seem possible. regular ObjectOutputStream will ...
    Profile Photo
    last modified by clebert.suconic
  • Important bug in thread pool management

    Hi, while testing JBoss Remoting I limited the maxPoolSize to 2 on the Connector on the server side. Also I added an InvocationHandler which simply waits for 5 seconds and returns a response. Then I created 5 client t...
    Profile Photo
    last modified by bulenterdemir
  • Removing remoting from JBossAS 3.2 branch

    Since 3.2 branch is in maintenance mode and no other parts within 3.2 branch depend on remoting, would like to remove it (especially since the version in 3.2 branch is very old). Remoting will be maintained and update...
    Profile Photo
    created by tom.elrod
  • PooledInvokerProxy proposition

    Hi All! I have encountered a problem with the current way of opening connection by PooledInvokerProxy - server supplies its host name as server address - the problem is that some client can't resolve the host name. S...
    Profile Photo
    last modified by olegnitz
  • remove remoting tests with proprietary license, in 3.2.x ?

    There are some leftover tests in jbas 3.2.x with a proprietary license. If there are no objections I'll remove them for the next 3.2.x release. http://jira.jboss.com/jira/browse/JBAS-2466
    Profile Photo
    last modified by dimitris
  • Potential problem with thread usage in pingers and lease

    Looking at the code - I can see that connection pinger is implemented by creating a new java.util.Timer instance per Client on the client side, and using another java.util.Timer instance per connection on the server s...
    Profile Photo
    last modified by timfox
  • JBAS-3102 - UnifiedInvoker configuration into JBoss4.0 tests

    I'm going to create a target into the testsuite using UnifiedInvokers as the distribution layer. I don't know yet what tests to include. Probably I'm going to add a few ejb tests, and play around with JBossSerializat...
    Profile Photo
    last modified by clebert.suconic
  • JBAS-3089, JBAS-2500 PooledInvokerProxy issues

    The change to the PooledInvokerProxy for JBAS-2500 essentially broke pooling: http://jira.jboss.com/jira/browse/JBAS-3089 There is also no testcase for the JBAS-2500 issue. Every ejb create now results in a PooledInv...
    Profile Photo
    last modified by starksm64
  • Refactoring org.jboss.invocation.* into a remoting project

    While I'm refactoring the org.jboss.naming.* package to pull it out of the server package, and a related task is pulling out the detached invoker code from the NamingService into a jmx interceptor. This is just boiler...
    Profile Photo
    last modified by starksm64
  • Remoting and JCA

    I just reassigned some JCA issues to the remoting project. These relate to this issue which I've left in the JCA module but we need a remoting task to deal with most of the issue: http://jira.jboss.com/jira/browse/JB...
    Profile Photo
    last modified by adrian.brock
  • Version exception on connection close

    Tom et al, as you know we are getting a lot of the following exception: java.io.IOException: Can not read data for version -1. Supported versions: 1,2 with the latest remoting in CVS. This seems to occur if a...
    Profile Photo
    last modified by timfox
  • HTTPClientInvoker - Client Lease Feature

    http://jira.jboss.com/jira/browse/JBREM-317 The client lease feature causes an extra 0-length HTTP post to be sent on connection start, and then periodic "$PING$" posts afterwords. The problem with this approach is ...
    Profile Photo
    last modified by jason.greene
  • Race condition in Client invocations

    I get the following exception intermittently under high load with multiple clients using the same invoker: org.jboss.remoting.ConnectionFailedException: org.jboss.remoting.transport.local .LocalClientInvoker@95068...
    Profile Photo
    last modified by timfox
  • Remoting version compatibility

    Messaging requires full forward and server backward compatibility, between clients and servers (and in the future between servers and servers) We are building placeholders for this into 1.0 so as not to get caught ou...
    Profile Photo
    last modified by timfox
  • ConcurrentModificationException in InvokerRegistry

    I'm getting a ConcurrentModificationException in InvokerRegistry.java. It only occurs with log level of debug or finer. Looking at the code: public static void destroyClientInvoker(InvokerLocator locator) { Cl...
    Profile Photo
    last modified by timfox
  • Exception when connection is terminated

    When socket connections are terminated "hard". E.g. when the remote client dies, we get the following exceptions on the server: at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) 11:57...
    Profile Photo
    last modified by timfox