Announcement Announcement Module
No announcement yet.
NO_IMPLEMENT Error on WS6.0 Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • NO_IMPLEMENT Error on WS6.0

    We have setup a two node cluster WebSphere 6.0 JMS Server.

    Using Spring-JMS, I am able to send and receive (point-to-point) messages to this cluster from a standalone java application. This is running on Sun JDK 1.4.x.

    The settings we use are:
    <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
    <property name="environment">
    <prop key="java.naming.factory.initial">
    <prop key="java.naming.provider.url">,:ghlx0
    <prop key="">

    Please not the provider url: corbaloc:iiop:.....

    However, if I run the same exact code and settings within a web application running on Web Sphere 6.0 (IBM JDK 1.4.x), I receive the following error:

    Exception stack trace:
    javax.naming.NamingException: Error during resolve. Root exception is org.omg.CORBA.NO_IMPLEMENT: No available target vmcid: 0x49421000 minor code: 40 completed: No

    Here is the really baffling thing, sometimes, despite the error message it works. However, when it does not work, I get the same error above for each call to send or receive a message.

    If I change the provider url to: iiop://, it initializes correctly and I am able to send and receive messages.

    So I wrote some manual jms code with in the WAS6.0 web application.

    Properties env = new Properties();

    env.put(Context.PROVIDER_URL, ",:ghlx");
    env.put(Context.INITIAL_CONTEXT_FACTORY, " ");
    env.put("", "");

    InitialContext ctx = new InitialContext(env);
    Queue queue = (Queue) ctx.lookup("jms/test_queue");
    QueueConnectionFactory factory = (QueueConnectionFactory)ctx.lookup("jms/test_factory");
    QueueConnection conn = factory.createQueueConnection();
    QueueSession session = conn.createQueueSession(false, 0);
    QueueSender sender = session.createSender(queue);

    This above code, using the same provider url that failed using Spring-JMS, works.

    Any idea what might be causing my issue?


    Last edited by dkichline; Feb 7th, 2008, 12:04 AM.

  • #2
    Never mind

    We ended up putting the cluster behind a load balancer (F5 BIGIP) and we just hit a single address. We were able to use the iiop://... url instead.