re ERROR [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] received new control socket for unrecognized listenerId

[digidew]

re environment { jboss AS 4.3.2 GA, jboss messaging 1.4.5 GA, jboss remoting 2.2.3 SP1 GA }

re ERROR [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] received new control socket for unrecognized listenerId

hi guys,

My log file is flooded with the specified above error message, where listenerID is always something unique

I was to blame jboss remoting for this error to occur (https://jira.jboss.com/jira/browse/JBREM-1165) though unfortunatly

I was unable to upgrade  jboss remoting 2.2.3 SP1 GA to  jboss remoting 2.5.0 GA...

if you have any idea on how to make the error message go away or how to upgrade the jboss remoting from 2.2.3 to 2.5.0 please let me know and I am sure this day will bring in this world one more happy person :-)

Any input is highly appreciated

Have a great day

Sergii

[digidew]

P.S. Isn't it something we can tweak at server/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml ?

P.P.S. is remoting 2.5.0 GA compatible with my configuration?

Thanks

[ron_sigal]

Hi Sergii,

The change for JBREM-1165 "Reduce log level of "received new control socket for unrecognized listenerId" message" has been made for future releases 2.2.3.SP2 and 2.5.2.SP1.  I believe that people have been using Remoting versions 2.4/2.5 with AS 4.3.2 GA and jboss messaging 1.4, but I don't know that the combination has ever been tested, at least by JBoss people.

I plan to release 2.5.2.SP1 in the next couple of days, so you could try it if you like.  2.2.3.SP2 probably won't be released until around the beginning of next February, but you could always build it yourself.

-Ron

[ron_sigal]

I forgot to mention that the 2.4 / 2.5 versions of Remoting might have additional features and some improvements under the covers, but should be compatible with and substitutable for the 2.2 versions.