|
From: Laszlo S. p. <las...@ax...> - 2005-04-29 07:43:23
|
Hello!
=20
I have tried the https/tunneling feature.
The Tomcat5 and JMS Server have been configured as you have suggested.=20
They are working fine (with jms admin I can connect to the server)
But from my test app I could not connect to the server
Here is the code=20
=20
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.exolab.jms.jndi.InitialContextFactory");
//URL=3Dhttps://safhome:8443
props.put(Context.PROVIDER_URL, url);
=20
context =3D new InitialContext(props); // drop exception
=20
factory =3D (QueueConnectionFactory) =
context.lookup("QueueConnectionFactory");
=20
connection =3D factory.createQueueConnection();
connection.start();
=85
=20
EXCEPTION
2005-04-29 09:24:56,921 ERROR TestViewController - connect:
javax.naming.CommunicationException: Failed to get registry service for =
URL:
https://safhome:8443 [Root exception is java.rmi.ConnectIOException: =
Failed
to create connection; nested exception is:=20
org.exolab.jms.net.connector.ConnectException: Failed to =
connect
to URI=3Dhttps://safhome:8443/]
at
org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContex=
tFa
ctory.java:109)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
=20
And here is my jmsconfig
=20
<HttpsConfiguration webServerHost=3D"safhome"
webServerPort=3D"8443"
port=3D"3030"
servlet=3D"/openjms-tunnel/tunnel" />
=20
=20
<Connectors>
<Connector scheme=3D"https">
<ConnectionFactories>
<TopicConnectionFactory name=3D"TopicConnectionFactory" />
<QueueConnectionFactory name=3D"QueueConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>
=20
Any suggestion?
=20
Thanks
Laszlo Schaffer
=20
-----Original Message-----
From: ope...@li...
[mailto:ope...@li...] On Behalf Of Daniel =
Otero
Sent: 2005. =E1prilis 8. 0:04
To: ope...@li...
Subject: Re: [openjms-user] httptunneling/callback
=20
Hi saf, what you need to do (if you are using the 0.7.7-dev version) is =
(if
you can wait a few days things will be simplified a bit):
On the server side:
1) place the .war in the webapps/ directory.
2) define the https connector and it's configuration like this (in the
openjms.xml):
<Connectors>
<Connector scheme=3D"https">
<ConnectionFactories>
<TopicConnectionFactory name=3D"TopicConnectionFactory" />
<QueueConnectionFactory name=3D"QueueConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>
<HttpsConfiguration webServerHost=3D"your.webserver.com"
webServerPort=3D"9999"
port=3D"3030"
servlet=3D"/openjms-tunnel/tunnel"
/>
Note: in the next few days the TopicConnectionFactory and
QueueConnectionFactory will be replaced by a single entry like so - and =
the
examples should be modified accordingly:
<ConnectionFactory name=3D"ConnectionFactory" />
On the cliet side...
1) You need to set up your keystore and run your java client with the =
usual
parameters (-Djavax.net.ssl.trustStore=3D"$TSTORE"
-Djavax.net.ssl.keyStore=3D"$KSTORE" =
-Djavax.net.ssl.keyStoreType=3D"jks"
-Djavax.net.ssl.keyStorePassword=3D"$KPASS" )
I believe the plan is to make these part of the jndi.properties file =
(i.e.
look in examples/basic and see 2) below). But that won't happen for a =
few
days...
2) The good news is that if you need to use a proxy-server to get =
through
the corporate firewall the properties to do this can already be =
specified in
the jndi.properties file like so (much like the ssl ones will probably =
end
up):
org.exolab.jms.net.https.proxyHost=3Dlocal.proxy.com
org.exolab.jms.net.https.proxyPort=3D3128
if user authentication is required you can also use the following:
org.exolab.jms.net.https.proxyUser=3Duser
org.exolab.jms.net.https.proxyPassword=3Dpassword
On Apr 7, 2005, at 11:07 AM, Laszlo Schaffer personal wrote:
Hello!
=20
It is possible to use MessageListener=85onMessage() behind a client =
firewall?
I have read something about this TunnelServlet but I do not know how can =
I
use this?
What I need a configuration where a client there is behind a firewall =
(the
jms server server also) and the connection is being made using https
Recently have download and compiled the 0.7.7-dev version but how can I =
use
this Tunneling feature?
=20
Thanks
saf
|