Announcement Announcement Module
No announcement yet.
Weblogic JMS Proxy Issue Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weblogic JMS Proxy Issue

    Hi guys, I'm having a problem writing code to do a JNDI look-up and send JMS messages to Oracle Weblogic queues.

    The problem is this: We don't want the JNDI to be eagerly loaded up on application startup, because we want to be decoupled from the middleware.

    We are using this:
    <jee:jndi-lookup id="policeRequestQueue" jndi-name="POLICE-RequestQueue" environment-ref="jndiEnvironment" lookup-on-startup="true"/>
    Now, I've tried using
    lookup-on-startup="false" proxy-interface="javax.jms.QueueConnectionFactory"
    to lazy load the jndi reference, which would have worked, but unfortunately Weblogic server has a frustrating check where on receipt on a JMS message, it looks to see if the sending object is an instanceof WLConnectionImpl.class which the proxy object isn't. Weblogic then rejects the message.

    Anyone know a good solution? Our app is pure Spring Integration, and I'm trying to minimize hand coding a way around the problem.

  • #2
    Can you post your question to JMS forum?
    This one is for Spring Integration project