| Author |
Message
|
| sourdas2 |
 Posted: Wed Mar 14, 2007 11:19 pm Post subject: WBIMB JMS nodes with WAS6.0.2 |
 |
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
I am using WBIMB V6.0.2 in Win2000 FP 4. I am looking to integrate WAS 6.0.2 with MB through JMS nodes.
The message flow is simple.
JMSInput -> JMSMQTransform -> MQOutput
The message flow and JMS objects is configured appropriately.
But while deploying the message flow to broker, windows event log generating a error -
| Code: |
| BIP4395 Java exception: ''java.lang.NoSuchMethodError''; thrown from class name: ''com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl'', method name: ''createCoreConnection'', file: ''JmsJcaConnectionFactoryImpl.java''. |
I have also included the class in broker shared-class library.
Any suggestion would be very helpfull.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
 |
| marcin.kasinski |
| Posted: Thu Mar 15, 2007 12:36 am Post subject: Re: WBIMB JMS nodes with WAS6.0.2 |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| sourdas2 wrote: |
I have also included the class in broker shared-class library.
Any suggestion would be very helpfull. |
Which classes have you included anf from which version of MQ ?
From tutirial...
http://www-128.ibm.com/developerworks/websphere/library/techarticles/0610_bicheno/0610_bicheno.html
| Quote: |
Copy the jar files
Now that you have created the JMS components and defined them in JNDI, you must make the WebSphere MQ client classes available to the broker. To do this, copy the *.jar files and any native libraries for the MQ JMS client from <WebSphere MQ Install Dir>\Java\lib into the broker shared-classes directory C:\Documents and Settings\All Users\Application Data\IBM\MQSI\shared-classes. This ensures that the Java class path for the JMS nodes is set correctly. |
Marcin |
|
| Back to top |
|
|
| sourdas2 |
| Posted: Thu Mar 15, 2007 1:27 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
I am using Websphere application server V6.0.2 as JMS provider not Websphere MQ which is the second scenario as per the article you mentioned.
I have followed the same article to configure WAS V6.0.2 as JMS provider and create a JMS message flow.
I have copied the two jar file 'sibc.jms.jar' and 'sibc.jndi.jar' in message broker shared-class lib. The jar files have been copied from WAS client V6.0.2.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| sourdas2 |
| Posted: Thu Mar 22, 2007 5:03 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
Hi All,
My WAS version has been upgraded to WAS 6.0.2.17.
I am using the 'IBM Client for JMS on J2SE with IBM WebSphere Application Server' jar files to connect WAS from WBIMB.
Now, there error has been changed to
| Code: |
| CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to connect to bus JMSBUS because the following bootstrap servers could not be contacted [localhost:7276:BootstrapBasicMessaging] and the following bootstrap servers returned an error condition []. See previous messages for the reason for each bootstrap server failure. |
So the error is due to either WAS server internal error or the JMS client jar file error.
Any suggestion would be helpful as I have very few knoledge on WAS.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 22, 2007 5:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd say you have configured the wrong Bootstrap port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sourdas2 |
| Posted: Thu Mar 22, 2007 9:33 pm Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
I have checked application server bootstrap port which is default to 7276.
If I change it to any vacant port of the system and configure connection factory accordingly, then also it is throwing same error - bus could not be reached on localhost:port:BootstrapBasicMessaging.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| sourdas2 |
| Posted: Thu Mar 22, 2007 9:38 pm Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
A correction of previous post
It would bo SIB_ENDPOINT_ADDRESS of bootsrap server rather than bootstrap port
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
|
|
