Problems using HTTPS connector

Hello to every one.

I'm trying to use openjms 0.7.6 server through Https from clients deployed 
anywhere. I do not expose Tomcat (with the openjms.war servlet code) 
directly but it's running on a internal machine getting (together with 
the openjms server) connections from an Apache Server through a ajp13 
connection.

Clients succesfully connect to the openjms server and correctly create 
queues and topics using appropriated factories.

Problems arise when a client tries to put a message to an openjms 
destination. At this point we get this exception:

1:01:28.625 ERROR [Scheduler-Worker-0] -
org.exolab.jms.server.ClientDisconnectionException:
sun.security.validator.ValidatorException: No trusted certificate found
org.exolab.jms.server.ClientDisconnectionException:
sun.security.validator.ValidatorException: No trusted certificate found at
org.exolab.jms.server.http.HttpJmsSessionSender.onMessage(HttpJmsSessionSender.java:155) at
org.exolab.jms.server.JmsServerSession.onMessage(JmsServerSession.java:942) at
org.exolab.jms.messagemgr.QueueConsumerEndpoint.deliverMessages(QueueConsumerEndpoint.java:177) at
org.exolab.jms.messagemgr.ConsumerEndpoint.run(ConsumerEndpoint.java:425) at
org.exolab.core.threadPool.ThreadPoolWorker.runIt(ThreadPoolWorker.java:191) at
org.exolab.core.threadPool.ThreadPoolWorker.runWork(ThreadPoolWorker.java:178) at 
org.exolab.core.threadPool.ThreadPoolWorker.access$000(ThreadPoolWorker.java:67) at
org.exolab.core.threadPool.ThreadPoolWorker$1.run(ThreadPoolWorker.java:122) at 
java.lang.Thread.run(Thread.java:534)

We have a working https enabled webserver with its certificate on th 
public machine "www.webserver.org" as shown in the configuration 
file and internal machine (192.168.X.Y) where Tomcat and the openjms 
server are running.

Please note that:
If I use Http instead of HTTPS everything seems to work fine.
My openjms.xml configuration file is attached below.
I'm sure that I'm missing a point in the whole flow and I hope that 
someone can clarify it to me.
Thank you.

<Configuration>

  <!-- Optional. This represents the default configuration  -->
  <ServerConfiguration host="192.168.X.Y" embeddedJNDI="true" />
  
    <Connector scheme="rmi">
      <ConnectionFactories>
        <QueueConnectionFactory name="JmsQueueConnectionFactory" />
        <TopicConnectionFactory name="JmsTopicConnectionFactory" />
      </ConnectionFactories>
    </Connector>

    <Connector scheme="http">
      <ConnectionFactories>
        <QueueConnectionFactory name="HTTPQueueConnectionFactory"/>
        <TopicConnectionFactory name="HTTPTopicConnectionFactory"/>
      </ConnectionFactories>
    </Connector>

    <Connector scheme="https">
      <ConnectionFactories>
        <QueueConnectionFactory name="HTTPSQueueConnectionFactory"/>
        <TopicConnectionFactory name="HTTPSTopicConnectionFactory"/>
      </ConnectionFactories>
    </Connector>

    <Connector scheme="tcp">
      <ConnectionFactories>
        <QueueConnectionFactory name="TCPQueueConnectionFactory"/>
        <TopicConnectionFactory name="TCPTopicConnectionFactory"/>
      </ConnectionFactories>
    </Connector>
  </Connectors>

  <TcpConfiguration internalHost="192.168.X.Y" port="3030" 
jndiPort="3035" />

  <HttpsConfiguration port="443" host="www.webserver.org" />

  <HttpConfiguration port="80" host="www.webserver.org" />

  [...]
</Configuration>

-- 
-----------------------------------------------------
I wish I had a kryptonite cross, 
because then you could keep Dracula and Superman away. 
J.Handey
-----------------------------------------------------








-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click