Actually, that number, strange as it seems, is fine. Normally, that number would be the port where the bisocket://10.33.32.22:1810191292/callback? ... callback server (on the client side) would be listening, but the bisocket transport doesn't open a port on the client, so this number is just a unique value to distinguish this InvokerLocator from any other InvokerLocators.
When a callback client (on the server side), which JBossMessaging uses to sends messages to a consumer, wants a new socket, it writes a message to the client, and the exception you're seeing means that that process failed. It could be a problem with the connection over which that message is written, but it's more likely that there's a problem on the client side. Take a look at your client side logs. If you see a complaint from ConnectionValidator about a failed connection, try increasing the values of | <attribute name="validatorPingPeriod" isParam="true">10000</attribute> | <attribute name="validatorPingTimeout" isParam="true">5000</attribute> | in your $JBOSS_HOME/server/$CONFIG/jboss-messaging.sar/remoting-bisocket-service.xml. That will reduce the likelihood of spurious connection failures on a busy network or between busy hosts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253689#4253689 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253689 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
