| Author |
Message
|
| Cogito-Ergo-Sum |
 Posted: Wed Feb 06, 2013 9:14 am Post subject: JMS connection failed when integrating with WAS. |
 |
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
I have implemented the steps (except number 2) as shown here to enable connection from a JMSInput node to a topic string on WAS. I have tried every combination of JNDI bindings location string. I have tried every combination of connection factory string, source queue. And yet, I keep getting this error message.
| Code: |
( BRKR01.WODMDEMO ) WMB JMSClient. ''Broker 'BRKR01'; Execution Group 'WODMDEMO'; Message Flow 'jmsDecisionServer.JmsDecisionServerFlow'; Node 'ComIbmJMSClientInputNode::JMI01::ComIbmJMSClientInputNode' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''iiop://localhost:2809''. ConnectionFactory Name = ''jms/WbeQueueConnectionFactory''. JMS destination = ''jms/wodmActionQueue''. The exception text is : ''Error getting WsnNameService properties''.
|
Do you think, if I have left out anything obvious ? What should I do to get better trace/debug output ?
WMB 8.0.0.1
| Code: |
C:\Program Files\IBM\MQSI\8.0.0.1>mqsiservice -v
BIPmsgs en_US
Console OEM CP=437, ICU CCSID=5348
Default codepage=ibm-5348_P100-1997, in ascii=ibm-5348_P100-1997
JAVA console codepage name=cp437
BIP8996I: Version: 8001
BIP8997I: Product: WebSphere Message Broker
BIP8998I: CMVC Level: S800-L120815
BIP8999I: Build Type: Production, 32 bit, x86_nt_4
BIP8071I: Successful command completion.
|
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Feb 06, 2013 9:29 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Feb 06, 2013 9:36 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
The message flow is unable to establish a connection. This is the error message I see in Event Viewer.
| Code: |
( BRKR01.WODMDEMO ) WMB JMSClient. ''Broker 'BRKR01'; Execution Group 'WODMDEMO'; Message Flow 'jmsDecisionServer.JmsDecisionServerFlow'; Node 'ComIbmJMSClientInputNode::JMI01::ComIbmJMSClientInputNode' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''iiop://localhost:2809''. ConnectionFactory Name = ''jms/WbeQueueConnectionFactory''. JMS destination = ''jms/wodmActionQueue''. The exception text is : ''Error getting WsnNameService properties''. |
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 06, 2013 9:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Feb 06, 2013 10:50 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Ok, I wasn't using the sample whose link you had provided. I was given the WAS end of integration and I picked up the instructions from here.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Feb 06, 2013 11:57 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
The WMB Infocenter does not explicitly mention WAS 8 for SIBus integration.
| Quote: |
You can configure a stand-alone JMS client and JMS nodes to communicate with service integration bus (SIBus) in WebSphere® Application Server Version 6 and Version 7. |
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 07, 2013 2:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| do you see any errors on the WAS side when broker tries to connect? |
|
| Back to top |
|
|
| mb01mqbrkrs |
| Posted: Thu Feb 07, 2013 3:37 am Post subject: |
|
|
Apprentice
Joined: 18 Nov 2011
Posts: 48
|
| IIRC - WAS 8 uses SSL for JMS by default. I believe that the infocenter currently doesn't take this into account and officially WMB doesn't support WAS V8 |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Feb 07, 2013 6:15 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Cogito-Ergo-Sum wrote: |
| Ok, I wasn't using the sample whose link you had provided. I was given the WAS end of integration and I picked up the instructions from here. |
Build and deploy the JMS sample provided with WMB following the step-by-step instructions. It will work. If it does not, open a PMR to get an APAR for WAS 8.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
