Anonymous_User Absent Member.
Absent Member.
431 views

JMS Driver - SSL connection to JNDI server


Hi,
I am having this problem while attempting to connect using SSL to a
Tibco JNDI server. The driver connects fine if I dont use ssl.
I give an ssl connection string which somehow gets converted to tcp(in
trace below) and returns an error on jndi lookup that it cant find the
server.
It seems this is because it treats the ssl connection as a normal
unsecure tcp connection.
I am posting some trace here below... Can somebody point what the
problem is? Does the driver require any extra configuration for ssl
connection.



01/22/13 18:21:35.460]:OQS-JMS
PT:JMSPublicationShim.pollMonitoredDestinations()
[01/22/13 18:21:35.460]:OQS-JMS PT:JMSChannel.connect()
[01/22/13 18:21:35.461]:OQS-JMS PT:BEGIN Connect
[01/22/13 18:21:35.461]:OQS-JMS PT: Attempting to connect to broker
'Tibco EMS 5'.
[01/22/13 18:21:35.461]:OQS-JMS PT: BEGIN Get JNDI context
[01/22/13 18:21:35.461]:OQS-JMS PT: BEGIN JNDI context properties
[01/22/13 18:21:35.462]:OQS-JMS PT: java.naming.provider.url =
'ssl://tibdevjndi03.swacorp.com:11100'
[01/22/13 18:21:35.462]:OQS-JMS PT: java.naming.factory.initial =
'com.tibco.tibjms.naming.TibjmsInitialContextFactory'
[01/22/13 18:21:35.463]:OQS-JMS PT: java.naming.security.principal
= 'idm'
[01/22/13 18:21:35.463]:OQS-JMS PT:
java.naming.security.credentials = (content suppressed)
[01/22/13 18:21:35.463]:OQS-JMS PT: END JNDI context properties
[01/22/13 18:21:35.464]:OQS-JMS PT: JNDI context:
javax.naming.InitialContext@4608008e
[01/22/13 18:21:35.464]:OQS-JMS PT: END Get JNDI context
[01/22/13 18:21:35.464]:OQS-JMS PT: BEGIN Get connection factory
[01/22/13 18:21:35.464]:OQS-JMS PT: Looking-up JNDI connection
factories on broker 'Tibco EMS 5'.
[01/22/13 18:21:36.010]:OQS-JMS PT:
javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed
to connect to the server at tcp://tibdevjndi03.swacorp.com:11100 [Root
exception is javax.jms.JMSException: Failed to connect to the server at
tcp://tibdevjndi03.swacorp.com:11100]
[01/22/13 18:21:36.011]:OQS-JMS PT: javax.jms.JMSException: Failed to
connect to the server at tcp://tibdevjndi03.swacorp.com:11100
[01/22/13 18:21:36.011]:OQS-JMS PT: Unable to connect to JMS broker
'Tibco EMS 5'.
[01/22/13 18:21:36.012]:OQS-JMS PT: GUID summary:
Publisher GUID: FE294BCB08324FE43E81CB4B29FE3208
Driver GUID: DAD4974E889142ADACB54E97D4DA9188
Subscriber GUID: D9710D1094D74FFC7E80100D71D9D794
[01/22/13 18:21:36.012]:OQS-JMS PT:Receiving DOM document from
application.
[01/22/13 18:21:36.013]:OQS-JMS PT:
<nds dtdversion="3.0" xmlns:jms="urn:idm:jms">
<source>
<product build="20090520_1228"
instance="\DEV_SWACO_ID\swaiddev\Services\DirXML\Driver Set v3\OQS-JMS"
version="3.5.3">Identity Manager Driver for JMS</product>
<contact>Novell</contact>
</source>
<input>
<status level="warning" type="app-connection">
<description>Unable to connect to JMS broker 'Tibco EMS
5'.</description>
<exception class-name="javax.naming.ServiceUnavailableException">
<message>Failed to query JNDI: Failed to connect to the server
at tcp://tibdevjndi03.swacorp.com:11100</message>
</exception>
<exception class-name="javax.jms.JMSException">
<message>Failed to connect to the server at
tcp://tibdevjndi03.swacorp.com:11100</message>
</exception>
</status>
</input>
</nds>


--
varunece
------------------------------------------------------------------------
varunece's Profile: https://forums.netiq.com/member.php?userid=3140
View this thread: https://forums.netiq.com/showthread.php?t=46611

Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: JMS Driver - SSL connection to JNDI server



It may help if you post the full startup trace, maybe even showing the
difference when set for TCP vs. SSL.

Also, I assume you're pointing to a different port for SSL vs. non-SSL
connection; what's the other port? Any error message from the Tibco side
when connecting either way?

Good luck.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.