[JBoss Messaging Development] - why JMS server connection can not recover when the socket, which JMS server uses to delivery messages to client, is broken
by yong deng
yong deng [http://community.jboss.org/people/dengyong] created the discussion
"why JMS server connection can not recover when the socket, which JMS server uses to delivery messages to client, is broken"
To view the discussion, visit: http://community.jboss.org/message/544953#544953
--------------------------------------------------------------
My environment:
JBoss messaging 1.4.0.SP3-CP05 + JBoss remoting 2.2.2.SP10
My case is like below:
I have a JMS client which will subscribe messages from a JMS topic. On the JMS connection, I set an ExceptionListener so that I can detect the connection broken.
I did following testing and found some situation JMS connection exception listener can not dectect connection broken.
By default, JMS bisocket will listen on port 4457. For every JMS connection, I can find two TCP connection connecting to the port 4457. Besides that, I can find the other two TCP connection which I guess server will use to delivery messages to the clients.
1. when I [only] close TCP connection connecting to the port 4457 use some tools, indeed the ExceptionListener can detect the broken connection
2. but when I [only] close the other two TCP connection, I find:
1) JMS server will log an exception on ServerInvokerCallbackHandler. After that, it seems will never recover to delivery messages to the clients agains.
On the same handle, the session will still be live in server side, I find this from MBean [jboss.messaging:service=ServerPeer showActiveClientsAsHTML] from JMX console.
2) JMS client then can never get message from server side again and also the JMS ExceptionListener on connection can never detect connection failure
Now my questions here is:
1. for my case 2, should not the JMS server try to recovery from broken sockets to delivery messages to the JMS client again?
2. for my case 2, if expected behavior can not be implemented, at least JMS connection ExceptionListener should be able to detect failure and reconnect?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544953#544953]
Start a new discussion in JBoss Messaging Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 11 months
[JBoss Web Services Development] - WS-Policy, SOAP 1.2 and the Standard client config
by Riccardo Serafin
Riccardo Serafin [http://community.jboss.org/people/barakka] created the discussion
"WS-Policy, SOAP 1.2 and the Standard client config"
To view the discussion, visit: http://community.jboss.org/message/544747#544747
--------------------------------------------------------------
Hi,
I'm using JBossWS 3.1.1.GA, and I've discovered a possible problem when mixing the support for WS-Policy, WS-Security and a web service with SOAP1.2 binding.
The problem is that by default, if no specific client configuration is provided, the client wsdl parser will parse the provided policy, detect that WS-Security is required and load the "Standard WSSecurity Client" configuration from the embedded standard-jaxws-client-confix.xml, which correcly adds the WS-Security handler, but only for the SOAP11 binding. As the web services requires SOAP12, the client will send the message using this protocol, the handler will not be activated, and of course the message will be rejected.
There a two fixes: first provide a custom client configuration that adds the WS-Security handler for both protocols bindings (which is what I've done), second modify the standard configuration provided with the bundled library to activate the handler for both protocols. I not sure if later versions have already fixed this problems but, if not, would it possible to include this change in the standard config?
All the best,
Riccardo.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544747#544747]
Start a new discussion in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 11 months