This content has been marked as final. Show 7 replies
Did you ensure that the HornetQ client classes are in the classpath used by the bridge?
Other things to check:
looks like this jars are missing from wls classpath
* hornetq-core-client.jar -- HornetQ client library
* hornetq-jms-client.jar -- client implementation of the JMS API
* netty.jar -- the high-performance client/server socket framework
* hornetq-transports.jar -- integration code to use Netty with HornetQ
* jnp-client.jar -- JNDI library
The library jboss-logging.jar is also needed
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.
Thank you for reply in such a short time. And it is really helping for setting up the WL. In parallel I was going through some other blogs and what I came across is
Which tells all the steps for configuration. But at the end it is modifying MDB so i didn't get which MDB shall i modify and why?
Your using BPEL, and I don't recall whether BPEL even uses MDBs. This type of question is best answered in a BPEL forum.