| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuration problem with the JNDI Administered objects |
« View previous topic :: View next topic » |
| Author |
Message
|
| bond_02 |
 Posted: Thu Sep 27, 2007 5:34 am Post subject: Configuration problem with the JNDI Administered objects |
 |
|
Apprentice
Joined: 21 Dec 2006
Posts: 39
Location: kolkata
|
I am facing problem during JMSInput node(WBI 6) configuration ,Event Log says-
Node 'ComIbmJMSClientInputNode::JMSInput' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''corbaloc:iiop:localhost:2809''. ConnectionFactory Name = ''QCF''. JMS destination = ''INPUTQ''. The exception text is : '' java.lang.ClassCastException : com.ibm.ws.sib.api.jms.impl.JmsConnectionFactoryImpl''.
----------------
I have set innitial Context Factory=com.ibm.websphere.naming.WsnInitialContextFactory
and Location JNDI Binding=corbaloc:iiop:localhost:2809
I have set same for JMSOutput Node..
----------
Can any one say where the problem lies?  [/b]
_________________
Never assume you know everything.
Never assume you've seen everything.
Never discount the value of a book. If only as a weapon. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Sep 27, 2007 1:41 pm Post subject: Re: Configuration problem with the JNDI Administered objects |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bond_02 wrote: |
I am facing problem during JMSInput node(WBI 6) configuration ,Event Log says-
Node 'ComIbmJMSClientInputNode::JMSInput' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''corbaloc:iiop:localhost:2809''. ConnectionFactory Name = ''QCF''. JMS destination = ''INPUTQ''. The exception text is : '' java.lang.ClassCastException : com.ibm.ws.sib.api.jms.impl.JmsConnectionFactoryImpl''.
----------------
I have set innitial Context Factory=com.ibm.websphere.naming.WsnInitialContextFactory
and Location JNDI Binding=corbaloc:iiop:localhost:2809
I have set same for JMSOutput Node..
----------
Can any one say where the problem lies? [/b] |
From your setup it looks like you are running WAS on the localhost and WAS uses port 2809.. for it's corba transport port. Have you defined your MQ JNDI setup to WAS?
Should this not be the case use the filebased initial context factory. More stable...Than the support pack... when you're not running WAS 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bond_02 |
| Posted: Fri Sep 28, 2007 2:45 am Post subject: Re: Configuration problem with the JNDI Administered objects |
|
|
Apprentice
Joined: 21 Dec 2006
Posts: 39
Location: kolkata
|
| fjb_saper wrote: |
| bond_02 wrote: |
I am facing problem during JMSInput node(WBI 6) configuration ,Event Log says-
Node 'ComIbmJMSClientInputNode::JMSInput' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''com.ibm.websphere.naming.WsnInitialContextFactory''. Location of the bindings = ''corbaloc:iiop:localhost:2809''. ConnectionFactory Name = ''QCF''. JMS destination = ''INPUTQ''. The exception text is : '' java.lang.ClassCastException : com.ibm.ws.sib.api.jms.impl.JmsConnectionFactoryImpl''.
----------------
I have set innitial Context Factory=com.ibm.websphere.naming.WsnInitialContextFactory
and Location JNDI Binding=corbaloc:iiop:localhost:2809
I have set same for JMSOutput Node..
----------
Can any one say where the problem lies? [/b] |
From your setup it looks like you are running WAS on the localhost and WAS uses port 2809.. for it's corba transport port. Have you defined your MQ JNDI setup to WAS?
Should this not be the case use the filebased initial context factory. More stable...Than the support pack... when you're not running WAS |
------------------
I am trying to set WebSphere Application Server as My JMS provider
I have created the JMS components and defined them in JNDI to WAS
Now WAS client classes suld be available to the broker.So downloaded the WAS JMS client .When I tried to install the client using --
java -jar sibc_install-<build>.jar jms_jndi_ibm c:\jmsnodes\wasclient\
it was failing again and again .So i copied sibc_install-o0727.12.jar to c:\jmsnodes\ and renamed it as "wasclient".
Copied the two jars (sibc.jms.jar, sibc.jndi.jar) from c:\jmsnodes\wasclient\sibc_output_jms-o0727.12\lib
and C:\jmsnodes\wasclient\sibc_output_jndi-o0727.12\lib to MQSI\shared-classes\
After that i configured the JMSInput and JMSOutput Node in Toollkit as stated earlier.
_________________
Never assume you know everything.
Never assume you've seen everything.
Never discount the value of a book. If only as a weapon. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 28, 2007 2:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I'd rather go with the file based JNDI. The was J2EE client footprint is rather large... and that is what you need if you want to access the WAS JNDI from outside of WAS...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
