I'm trying to set up a bridge between HornetQ (JBoss 5.1) and WebLogic 10.3. The bridge should be set up on WebLogic. It'll read messages from queue on HornetQ and post them on WebLogic Queue.
Here are my preferences on Source Destination:
Adapter JNDI Name eis.jms.WLSConnectionFactoryJNDINoTx
Classpath: empty (?)
Connection URL: jnp://<hostName>:1099
Initial Context Factory: org.jnp.interfaces.NamingContextFactory
Connection Factory JNDI Name: /tp/ConnectionFactory
Connection JNDI Name: /etgreceiver/queue
Destination Type: Queue
User Name: guest
User Password: guest.
WebLogic prints a warning: <12.10.2010 18:25:40 MSD> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > resourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =org.jnp.interfaces.NamingContextFactory, url = jnp://AIskrich:11099, user name = guest) ">
I have no idea what the problem is, could anyone help?
Hi, I am doing the same thing. My BPEL will consume data from HornetQ and will post it to JMS. Can you please tell me what are the other configurations you have done for HornetQ in your Weblogic server? I have all the related jar files. Have you done any changes into pre_classpath in setDomainEnv script?
Yes - I think "pre_classpath" is probably the right place to reference the non-WebLogic jars. That said, layered products like BPEL often provide tooling that simplifies messaging integration -- I assume some even help setup classpaths and may have their own recommended unique way to set them. So I recommend consulting your layered product's documentation and forums.
It looks like this posting already covers the needed HornetQ specific settings. If it turns out that you're still interested in working directly at the WebLogic layer instead of the BPEL layer, see the interop FAQ http://docs.oracle.com/cd/E21764_01/web.1111/e13727/interop.htm#JMSPG553 for a full treatment of WebLogic's built in JMS provider integration features.