| Author |
Message
|
| rajmq |
 Posted: Thu Sep 14, 2006 1:59 pm Post subject: WMB Vs WAS JMS |
 |
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi All,
Basically I am trying to send some message thru JMSOutputNode to WAS JMS queue using JMS providers.
To achieve this I am trying two ways:
1.Broker & WAS server both are installed in the same box and using JMSOutputNode & WAS server libraries able to place the message to WAS JMS queue.
2.The same flow is unable to place message while using the Remote server WAS jms queue (WAS server is running in the different box).
Can anyone help me in finding out why the JMSOutputNode in not able place message to remote WAS server?
Regards, |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Sep 14, 2006 2:07 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Maybe we can, but you have to tell us the MQRC from the excpetion thats being throw..... 
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 14, 2006 3:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I wouldn't expect a JMSOutput node to throw an MQRC.
I would expect it to throw a provider specific error message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 14, 2006 3:36 pm Post subject: Re: WMB Vs WAS JMS |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rajmq wrote: |
Hi All,
Basically I am trying to send some message thru JMSOutputNode to WAS JMS queue using JMS providers.
To achieve this I am trying two ways:
1.Broker & WAS server both are installed in the same box and using JMSOutputNode & WAS server libraries able to place the message to WAS JMS queue.
2.The same flow is unable to place message while using the Remote server WAS jms queue (WAS server is running in the different box).
Can anyone help me in finding out why the JMSOutputNode in not able place message to remote WAS server?
Regards, |
With you was server remote, do you have all the classpath and libraries etc to obtain the right QCF / TCF doing a remote call to WAS? Seems pretty heavy as a J2EE client footpath...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rajmq |
| Posted: Fri Sep 15, 2006 7:36 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi Jeff
The error details :
RecoverableException BIP4640E: WBIMB JMSClient. ''Broker 'TEST'; Execution Group 'JMS_TEST'; Message Flow 'TOJMS_TEST'; Node 'ComIbmJMSClientOutputNode::JMSOutput' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''iiop://brewd00415671.eu2.corpnet1.com:7280/''. ConnectionFactory Name = ''jms/QCF''. JMS destination = ''jms/WBIMB_JMS_OUT''. The exception text is : ''A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://brewd00415671.eu2.corpnet1.com:7280/". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.''.
The node could not obtain a JNDI Administered Object because some of the values specified in the node attributes are incorrect
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.
Regards, |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 15, 2006 7:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| rajmq wrote: |
| A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://brewd00415671.eu2.corpnet1.com:7280/". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.''. |
Seems pretty clear to me.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rajmq |
| Posted: Fri Sep 15, 2006 2:40 pm Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
The question is
Is it possible to connect the remote WAS JMS queue using the server binaries?
Or we have to use the client binaries?
Regards, |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 15, 2006 2:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The error you posted has nothing to do with what version of the binaries (whatever those are) you are using.
It's purely a configuration or communications error.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
