| Author |
Message
|
| jogger05 |
 Posted: Thu Mar 08, 2007 10:58 am Post subject: WMBv6 JMSInput Node and LDAP |
 |
|
Newbie
Joined: 04 Oct 2006
Posts: 5
|
I got the error message while implement a JMSInput node with LDAP setting in Redhat linux. The LDAP setting looks correct. The error message is
“Mar 8 12:12:39 swim05 WebSphere Broker v6002[7383]: (S05NPBRK.S05NPEG)[-1411384400]BIP4640E: WBIMB JMSClient. 'Broker 'S05NPBRK'; Execution Group 'S05NPEG'; Message Flow 'swimesb_noaaport.swimesb_noaaport_1'; Node 'ComIbmJMSClientInputNode::NPJMSInput' ' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://158.147.47.81:389/dc=swim'. ConnectionFactory Name = 'S05.NOAAPORT.TCF'. JMS destination = ''. The exception text is : ' javax.naming.NameNotFoundException : [LDAP: error code 32 - No Such Object]'. : S05NPBRK.36b18d29-1101-0000-0080-900bdfece5f3: JMSClientErrors.java: 548: JMSClientErrors:handleJNDIException(): :”
I also got a message “BIP15366S:The Configuration Manager was unable to register fro internal subscriptions with broker” from the toolkit workspace.
Do you have any idea about this error?
Thanks! |
|
| Back to top |
|
 |
| marcin.kasinski |
| Posted: Thu Mar 08, 2007 11:38 am Post subject: Re: WMBv6 JMSInput Node and LDAP |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| jogger05 wrote: |
I got the error message while implement a JMSInput node with LDAP setting in Redhat linux. The LDAP setting looks correct. The error message is
“Mar 8 12:12:39 swim05 WebSphere Broker v6002[7383]: (S05NPBRK.S05NPEG)[-1411384400]BIP4640E: WBIMB JMSClient. 'Broker 'S05NPBRK'; Execution Group 'S05NPEG'; Message Flow 'swimesb_noaaport.swimesb_noaaport_1'; Node 'ComIbmJMSClientInputNode::NPJMSInput' ' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://158.147.47.81:389/dc=swim'. ConnectionFactory Name = 'S05.NOAAPORT.TCF'. JMS destination = ''. The exception text is : ' javax.naming.NameNotFoundException : [LDAP: error code 32 - No Such Object]'. : S05NPBRK.36b18d29-1101-0000-0080-900bdfece5f3: JMSClientErrors.java: 548: JMSClientErrors:handleJNDIException(): :”
I also got a message “BIP15366S:The Configuration Manager was unable to register fro internal subscriptions with broker” from the toolkit workspace.
Do you have any idea about this error?
Thanks! |
Try to list LDAP objects and then compare it with your configuration.
Marcin |
|
| Back to top |
|
|
| jogger05 |
| Posted: Thu Mar 08, 2007 12:56 pm Post subject: |
|
|
Newbie
Joined: 04 Oct 2006
Posts: 5
|
well, that LDAP object S05NPBRK.36b18d29-1101-0000-0080-900bdfece5f3 is not set or created by us, i think it is used internally by WMB. From the LDAP app you cannot see it.
thanks |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Thu Mar 08, 2007 10:11 pm Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| jogger05 wrote: |
well, that LDAP object S05NPBRK.36b18d29-1101-0000-0080-900bdfece5f3 is not set or created by us, i think it is used internally by WMB. From the LDAP app you cannot see it.
thanks |
Can you list here your LDAP objects and show configuration of nodee ?
Marcin |
|
| Back to top |
|
|
| jogger05 |
| Posted: Fri Mar 09, 2007 7:32 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2006
Posts: 5
|
Here are the JMSAdmin objects I have:
InitCtx> dis ctx
Contents of InitCtx
[D] cn=Directory Administrators javax.naming.directory.DirContext
[D] ou=Groups javax.naming.directory.DirContext
[D] ou=People javax.naming.directory.DirContext
[D] ou=Special Users javax.naming.directory.DirContext
a cn=MYQCF com.ibm.mq.jms.MQQueueConnectionFactory
a cn=swim_qcf com.ibm.mq.jms.MQQueueConnectionFactory
a cn=WXTCF com.ibm.mq.jms.MQTopicConnectionFactory
a cn=WXPUB com.ibm.mq.jms.MQTopic
a cn=WXSUB com.ibm.mq.jms.MQTopic
a cn=PUB.WX com.ibm.mq.jms.MQTopic
a cn=SUB.WX com.ibm.mq.jms.MQTopic
a cn=WXTCF_SC08JMS com.ibm.mq.jms.MQTopicConnectionFactory
a cn=PUB_SC08JMS.WX com.ibm.mq.jms.MQTopic
a cn=SUB_SC08JMS.WX com.ibm.mq.jms.MQTopic
a cn=WXTCF_JMS76 com.ibm.mq.jms.MQTopicConnectionFactory
a cn=WX.ONDEMAND com.ibm.mq.jms.MQTopic
a cn=WXTCF_JMS81 com.ibm.mq.jms.MQTopicConnectionFactory
a cn=S05.ADSB.TCF com.ibm.mq.jms.MQTopicConnectionFactory
a cn=S05.NAIS.TCF com.ibm.mq.jms.MQTopicConnectionFactory
a cn=SWIM.ADSB.CNTR.DAB com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.CNTR.SDF com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.TRACON.DAB com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.TRACON.SDF com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.TOWER.DAB com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.TOWER.SDF com.ibm.mq.jms.MQTopic
a cn=SWIM.ADSB.RAW com.ibm.mq.jms.MQTopic
a cn=S05.NOAAPORT.TCF com.ibm.mq.jms.MQTopicConnectionFactory
a cn=NGATS.WEATHER.ADDRESSED_MESSAGE.BMBB01 com.ibm.mq.jms.MQTopic
a cn=S05.HWDS.TCF com.ibm.mq.jms.MQTopicConnectionFactory
a cn=NGATS.WX.ADDRESSED_MESSAGE.BMBB01 com.ibm.mq.jms.MQTopic
a cn=NGATS.WX.NOTAMS.PN1 com.ibm.mq.jms.MQTopic
31 Object(s)
4 Context(s)
27 Binding(s), 27 Administered
The properties of JMSInput node:
Initial Context Factory=com.sun.jndi.ldap.LdapCtxFactory
Location JNDI Bindings=ldap://158.147.47.81:389/dc=swim
Connection Factory Name=cn= S05.ADSB.TCF
Subscription Topic=cn=SWIM.ADSB.RAW
I also get another error message from system log:
Mar 9 10:27:49 swim05 WebSphere Broker v6002[27736]: (S05ADSBBKR.S05ADSBEG)[-1366926416]BIP4640E: WBIMB JMSClient. 'Broker 'S05ADSBBKR'; Execution Group 'S05ADSBEG'; Message Flow 'swimesb_adsb_raw.swimesb_adsb_raw'; Node 'ComIbmJMSClientInputNode::ADSBRAWJMSInput' ' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://158.147.47.81:389/dc=swim'. ConnectionFactory Name = 'cn=S05.ADSB.TCF'. JMS destination = 'cn=SWIM.ADSB.RAW'. The exception text is : ' java.lang.ClassCastException : javax.naming.Reference'. : S05ADSBBKR.ae035524-1101-0000-0080-e448e914c638: JMSClientErrors.java: 548: JMSClientErrors:handleJNDIException(): :
Thanks! |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Fri Mar 09, 2007 9:50 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Now I think you should check configuration of TCF and Topic.
Hint :Write simple JMS code with data listed below and try it outside broker.
Initial Context Factory=com.sun.jndi.ldap.LdapCtxFactory
Location JNDI Bindings=ldap://158.147.47.81:389/dc=swim
Connection Factory Name=cn= S05.ADSB.TCF
Subscription Topic=cn=SWIM.ADSB.RAW
In my opinion you have problem with definition of S05.ADSB.TCF or SWIM.ADSB.RAW (wrong topic, QM, queue or other attribute).
Marcin |
|
| Back to top |
|
|
| jogger05 |
| Posted: Fri Mar 09, 2007 12:32 pm Post subject: |
|
|
Newbie
Joined: 04 Oct 2006
Posts: 5
|
Here is my script to create TCF and topic:
DEFINE TCF(S05.ADSB.TCF) TRANSPORT(CLIENT) +
PORT(3415) +
CHANNEL(S05SCC) +
HOSTNAME(158.147.38.138) +
QMANAGER(S05ADSBQM) +
CCSID(1208) +
BROKERPUBQ(S05.ADSB.PUBQUEUE) +
BROKERSUBQ(SYSTEM.JMS.ND.S05.ADSB.SUBQUEUE) +
PUBACKINT(0) +
SYNCPOINTALLGETS(YES)
DIS CTX
END
DEFINE T(SWIM.ADSB.CNTR.DAB) TOPIC(SWIM/ADSB/CNTR/DAB)
DEFINE T(SWIM.ADSB.CNTR.SDF) TOPIC(SWIM/ADSB/CNTR/SDF)
DEFINE T(SWIM.ADSB.TRACON.DAB) TOPIC(SWIM/ADSB/TRACON/DAB)
DEFINE T(SWIM.ADSB.TRACON.SDF) TOPIC(SWIM/ADSB/TRACON/SDF)
DEFINE T(SWIM.ADSB.TOWER.DAB) TOPIC(SWIM/ADSB/TOWER/DAB)
DEFINE T(SWIM.ADSB.TOWER.SDF) TOPIC(SWIM/ADSB/TOWER/SDF)
DEFINE T(SWIM.ADSB.RAW) TOPIC(SWIM/ADSB/RAW)
DIS CTX
END
Does this ring a bell?
I also did some search in the Web, looks like someone got the similar problem with WAS when they looked up QueueConnectionFactory. That problem was caused by missing some jar files in classpath for the client app. I assume JMSInput node is a MQ/JMS client app and JMSInput node got the similar problem, but I don’t know how to include jar files in classpath for the JMSInput node and which jar files I need |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Fri Mar 09, 2007 1:26 pm Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| marcin.kasinski wrote: |
Hint :Write simple JMS code with data listed below and try it outside broker.
Marcin |
Did you tried it ?
I dont have access to your system so I can only suggest you how to fix it .
Please write simple JAVA JMS app with the same LDAP Provider , TCF and Topic and check results.
PS Below you have dscription of your BIP message...
Message
WBIMB JMSClient. '<insert_0>' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = '<insert_1>'. Location of the bindings = '<insert_2>'. ConnectionFactory Name = '<insert_3>'. JMS destination = '<insert_4>'. The exception text is : '<insert_5>'.
Explanation
The node could not obtain a JNDI Administered Object because some of the values specified in the node attributes are incorrect
Response
Check the JNDI Administered configuration for the JMS provider used by the node. Either modify the JNDI Administered objects and rebuild the bindings, or change the node attributes and re-deploy the message flow.
The most important message here is "Check the JNDI Administered configuration for the JMS provider used by the node"
PS.
Connection Factory Name=cn= S05.ADSB.TCF
Subscription Topic=cn=SWIM.ADSB.RAW
Is is correct definition ? Shouldnt it be (without cn=):
Connection Factory Name=S05.ADSB.TCF
Subscription Topic=SWIM.ADSB.RAW
Marcin |
|
| Back to top |
|
|
| jogger05 |
| Posted: Mon Mar 12, 2007 8:18 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2006
Posts: 5
|
After putting ldap.jar and jndi.jar into /var/mqsi/shared-classes and restarting the broker, I see the error in the log:
Mar 12 10:53:07 swim05 WebSphere Broker v6002[8207]: (S05ADSBBKR.S05ADSBEG)[-1356141648]BIP4640E: WBIMB JMSClient. 'Broker 'S05ADSBBKR'; Execution Group 'S05ADSBEG'; Message Flow 'swimesb_adsb.swimesb_adsb'; Node 'ComIbmJMSClientInputNode::ADSBJMSInput' ' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://158.147.47.81:389/dc=swim'. ConnectionFactory Name = 'cn=S05.ADSB.TCF,dc=swim'. JMS destination = ''. The exception text is : ' '. : S05ADSBBKR.6ab17bda-1001-0000-0080-c83dbc0b9180: JMSClientErrors.java: 548: JMSClientErrors:handleJNDIException(): :
The error is different from the one I had last week. This time WMB JMSInput node doesn’t say it cannot find the LDAP object, but returning an empty exception text.
I have not tried JMS/LDAP testing app yet, but it worked before with MQ base broker to connect to the same LADP server with different TCF and topics. |
|
| Back to top |
|
|
|
|
