RE: httptunneling/callback

You also need to specify the tunnel in the JNDI provider URL:
 
String url = "https://safhome:8443/openjms-tunnel/tunnel";

props.put(Context.PROVIDER_URL, url);

 

-----Original Message-----
From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Tim Anderson
Sent: Saturday, 30 April 2005 11:25 PM
To: [email protected]
Subject: RE: [openjms-user] httptunneling/callback


How have you deployed the tunnel?
 

Given your configuration, the WAR needs to be copied to: 
  <TOMCAT_HOME>/webapps/openjms-tunnel.war
 
 
 -----Original Message-----
From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Laszlo
Schaffer personal
Sent: Friday, 29 April 2005 5:43 PM
To: [email protected]
Subject: RE: [openjms-user] httptunneling/callback



Hello!

 

I have tried the https/tunneling feature.

The Tomcat5 and JMS Server have been configured as you have suggested. 

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 

 

props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.exolab.jms.jndi.InitialContextFactory");

//URL=https://safhome:8443

props.put(Context.PROVIDER_URL, url);

 

context = new InitialContext(props); // drop exception

 

factory = (QueueConnectionFactory) context.lookup("QueueConnectionFactory");

 

connection = factory.createQueueConnection();

connection.start();

…

 

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: 

            org.exolab.jms.net.connector.ConnectException: Failed to connect
to URI=https://safhome:8443/]

            at
org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFa
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)



 

And here is my jmsconfig

 

<HttpsConfiguration webServerHost="safhome"

            webServerPort="8443"

            port="3030"

            servlet="/openjms-tunnel/tunnel"  />

 

 

   <Connectors>

      <Connector scheme="https">

         <ConnectionFactories>

             <TopicConnectionFactory name="TopicConnectionFactory" />

             <QueueConnectionFactory name="QueueConnectionFactory" />

        </ConnectionFactories>

     </Connector>

   </Connectors>

 

Any suggestion?

 

Thanks

Laszlo Schaffer

 

-----Original Message-----
From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Daniel Otero
Sent: 2005. április 8. 0:04
To: [email protected]
Subject: Re: [openjms-user] httptunneling/callback

 

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="https">
<ConnectionFactories>
<TopicConnectionFactory name="TopicConnectionFactory" />
<QueueConnectionFactory name="QueueConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>

<HttpsConfiguration webServerHost="your.webserver.com"
webServerPort="9999"
port="3030"
servlet="/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="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="$TSTORE"
-Djavax.net.ssl.keyStore="$KSTORE" -Djavax.net.ssl.keyStoreType="jks"
-Djavax.net.ssl.keyStorePassword="$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=local.proxy.com
org.exolab.jms.net.https.proxyPort=3128

if user authentication is required you can also use the following:

org.exolab.jms.net.https.proxyUser=user
org.exolab.jms.net.https.proxyPassword=password

On Apr 7, 2005, at 11:07 AM, Laszlo Schaffer personal wrote:

Hello!

 

It is possible to use MessageListener…onMessage() 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?

 

Thanks

saf