We operate in a 2-way ssl environment. I'm trying to secure a jms queue I created in jboss 5.
Using jndi, I can create my initial context and send messages to the cue, but I want to lock it down.
We've switched our containers from weblogic to jboss. In weblogic, when creating an initial context,
in changing the url over, it was as simple as changing t3 to t3s and the port from 8080 to 443.
Nothing really complicated there. However, in jboss, I get all kinds of CommunicationExceptions --
failed to retrieve stub from server... when using jnps://mymachine:443
I need to be able to send messages to this machine from various remote clients in a 2-way ssl environment.
Any ideas would be greatly appreciated. Once I lock this down, I'll start asking about securing it further
by protecting with roles... :-)
Thanks,
John