When Setting Up a JMS Connection from an Applet, the TopicConnection Fails with a ClassNotFoundException: weblogic.messaging.dispatcher.DispatcherProxy_XXXX_WLStub (Doc ID 1300539.1)

Last updated on JUNE 30, 2011

Applies to:

Oracle Weblogic Server - Version: 9.2 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

When setting up a JMS connection from an applet, the TopicConnection fails with a ClassNotFoundException: weblogic.messaging.dispatcher.DispatcherProxy_1033_WLStub.

Steps to reproduce:

  1. Set up client/server with demo certs.
  2. Set up JMS server, module and topic. Topic name: sample.jms.SampleEventTopic.
  3. Deploy an application which downloads an applet which produces JMS messages and sends them to the topic.
  4. The applet throws the following exception:
    Creating TopicConnection...
    Exception creating InitialContext: Failed to load with ClassNotFoundException
    weblogic.messaging.dispatcher.DispatcherProxy_1033_WLStub
    java.lang.AssertionError: Failed to load with ClassNotFoundException
    weblogic.messaging.dispatcher.DispatcherProxy_1033_WLStub
    at weblogic.rmi.extensions.StubFactory.loadClassOverNetwork(StubFactory.java:95)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:72)
    etc.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms