Here's what i have been beating my head against for a day now.
I have an older version of jboss (jboss4), and from within it i am launching some code to go out and connect to an implementation of sonic mq (7.6, i think) where i am running as a client. I am running java 1.6.0_23. That being said i am seeing very weird behavior that i cant seem to figure out.
When my process starts i load all of the jndi props that i need to establish a connection to the sonic mq server, then i call out like this
Context ic = new InitialContext(jndiEnv);
however i see no traffic on my wire shark at that point and it is baffling me. Eventually this will time out giving me the exception
javax.naming.NamingException. Root exception is com.sonicsw.mf.comm.ConnectTimeoutException: Timeout occured while attempting to connect
The real kick in the teeth is that i run my process from a standalone jar (instead of from within jboss) on the same server and it connects fine?
Hey anyone that comes across this... So i solved my issue and thought i would share it ...
it turns out that even tho the sonic tech team said that their code never looks at the jvm variable javax.ssl.keystore ... it does...
It was set like this javax.ssl.keystore=C:something which would cause the initial context generation to hang until time out. however this javax.ssl.keystore=C:\something would work. and if its not set it will work as well...
i would have expect some kind of exception to be thrown :?
I hope this helps someone sometime! :)
thanks J