ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JMSOutput node for 3rd Party JMS Provider

Post new topic  Reply to topic
 JMSOutput node for 3rd Party JMS Provider « View previous topic :: View next topic » 
Author Message
jcarr
PostPosted: Wed Jul 19, 2006 2:43 pm    Post subject: JMSOutput node for 3rd Party JMS Provider Reply with quote

Novice

Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN

I've been working on this for a few days with no luck. Here's the story:

I have a flow that takes a MQ message as input (MQInput) uses the MQJMSTransform node next, then put the message into a JMSOutput node. Everything works great when WebSphere MQ is the provider.
When using another JMS provider, like OpenJMS, I get some errors (see below)

Here are some attributes for the JMSOutput node:

Initial context Factory: org.exolab.jms.jndi.InitialContextFactory
Location of JNDI Bindings: tcp://localhost:3035/
Connection Factory Name: ConnectionFactory


I can use this information to create a Java class to connect to OpenJMS with no problems.

This is what I get for the ExceptionList:

(
(0x01000000):RecoverableException = (
(0x03000000):File = 'F:\build\S600_P\src\DataFlowEngine\JMSTransform\ImbMqJmsTransformNode.cpp'
(0x03000000):Line = 380
(0x03000000):Function = 'ImbMqJmsTransformNode::evaluate'
(0x03000000):Type = 'ComIbmMQJMSTransformNode'
(0x03000000):Name = 'JMSTest#FCMComposite_1_5'
(0x03000000):Label = 'JMSTest.MQJMSTransform'
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Caught exception and rethrowing'
(0x01000000):RecoverableException = (
(0x03000000):File = 'F:\build\S600_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp'
(0x03000000):Line = 922
(0x03000000):Function = 'ImbJniNode::evaluate'
(0x03000000):Type = 'ComIbmJniNode'
(0x03000000):Name = 'JMSTest#FCMComposite_1_8'
(0x03000000):Label = 'JMSTest.JMSOutput1'
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Caught exception and rethrowing'
(0x01000000):RecoverableException = (
(0x03000000):File = 'JMSClientErrors.java'
(0x03000000):Line = 548
(0x03000000):Function = 'JMSClientOutputNode::lookUpFactoryInJNDI()'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 4640
(0x03000000):Text = 'Unable to get JNDI Initial Context'
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'Broker 'WBRK6_DEFAULT_BROKER'; Execution Group 'default'; Message Flow 'JMSTest'; Node 'ComIbmJMSClientOutputNode::JMSOutput1' '
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'org.exolab.jms.jndi.InitialContextFactory'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'tcp://localhost:3035/'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'ConnectionFactory'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'queue2'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'Failed to lookup JNDI provider for URL: tcp://localhost:3035/'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = ' Failed to lookup JNDI provider for URL: tcp://localhost:3035/'
)
)
)
)
)


I have all necessary jar files in the message broker shared-classes folder.

Any ideas?
_________________
If you can read this, you're too close.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Jul 19, 2006 3:11 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

How would you set this up outside of the broker.
Is the provider url really tcp://myhost:port or more something like ioop://myhost:port?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jcarr
PostPosted: Wed Jul 19, 2006 7:35 pm    Post subject: Reply with quote

Novice

Joined: 25 Apr 2006
Posts: 20
Location: Minneapolis, MN

It's tcp. While testing with a Java class, I changed the protocol to iiop://localhost:1099 (that's where OpenJMS has a RMI listener). I get an error with that code.

I also tried using the iiop:// protocol in the JMSOutput node and had problems as well. I tried many combinations of tcp:// and iiop://.

Again, I can get a good connection in my Java class using tcp://localhost:3035 or tcp://<servername>:3035, but I can't get it working with my flow.

I may be making this harder than what it should be, but I believe I'm giving MB everything it needs: provider jars, the context factory, location of JNDI bindings, connection factory name, and queue name.

I'm using MB Toolkit and Runtime 6.0.0.1 running on Windows.

Has anyone had success using the JMSInput or JMSOutput nodes with a provider other than WebSphere MQ?
_________________
If you can read this, you're too close.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JMSOutput node for 3rd Party JMS Provider
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.