ClassNotFound Exception accessing EJBs in a cluster

Question

I am experiencing some weird behavior when attempting to access EJBs in a
          Weblogic 5.1.0 cluster. The cluster nodes startup fine, and the EJBs are
          correctly deployed. However, when my test client attempts to access them I
          get the ClassNotFoundException listed below. This same client can access the
          same EJBs deployed in a non-clustered environment without any problems, so
          it's definitely related to my cluster configuration. The problem seems to be
          that the client is not receiving the client-side stub. To confim this, I put
          the stub in the client's classpath, and did NOT get the
          ClassNotFoundException. Has anyone else seen this error?
          BTW, I have compiled the EJB both with and without the <home-is-clusterable>
          flag set to true. I get the same exception either way.
          Thanks for any assistance,
          Jason Donnell
          javax.naming.CommunicationException. Root exception is
          java.lang.ClassNotFoundException: class
          com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
          previously not found
          at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:184)
          at weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
          at weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:700)
          at
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          a:34)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
          at weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
          at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
          at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          --------------- nested within: ------------------
          weblogic.rmi.UnmarshalException: Unmarshalling return
          - with nested exception:
          [java.lang.ClassNotFoundException: class
          com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
          previously not found]
          at
          weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
          a:256)
          at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
          at javax.naming.InitialContext.lookup(InitialContext.java:350)
          at
          com.landacorp.maxmc.ejb.security.ClusterSecurityTest.main(ClusterSecurityTes
          t.java:52)
          

Answer 1

Just a side note: I setup the cluster using the WebLogic recommended
          directory structure (see
          http://www.weblogic.com/docs51/cluster/setup.html#676105) and I no longer
          get the exception. I'm still interested in hearing, though, if anyone has a
          scheme for setting up the cluster in a directory that isn't directly under
          the weblogic installation directory.
          Jason
          "Jason Donnell" <[email protected]> wrote in message
          news:[email protected]...
          > My current idea is that our directory structure is not properly supported
          by
          > WebLogic. We are NOT putting everything under the weblogic install
          > directory, as the documentation suggests. Instead, it looks something like
          > this (on an NT box):
          >
          > \weblogic_install\<Weblogic 5.1.0 installation here>
          >
          > \our_weblogic\startWeblogicNode1.cmd
          > \our_weblogic\startWeblogicNode2.cmd
          > \our_weblogic\weblogic.properties (cluster-wide)
          > \our_weblogic\public_html\
          > \our_weblogic\our_cluster_name\
          > \our_weblogic\our_cluster_name\all_ejbs\<compiled beans are here>
          > \our_weblogic\our_cluster_name\server_node1\
          > \our_weblogic\our_cluster_name\server_node1\weblogic.properties
          > (server-specific)
          > \our_weblogic\our_cluster_name\server_node2\
          > \our_weblogic\our_cluster_name\server_node2\weblogic.properties
          > (server-specific)
          >
          > So, on the command line in our per-server startup scripts, we set the
          > weblogic.system.home=\our_weblogic,
          weblogic.cluster.name=our_cluster_name,
          > and weblogic.system.name=server_nodeX.
          >
          > Now, I want to emphasize that the server claims to start up just fine. It
          > claims the EJBs have been deployed. However, it is unable to deliver
          classes
          > dynamically, as we found by trying the
          > http://yourweblogic..../classes/some/class/name.class suggestion noted
          > previously.
          >
          > We had a similar directory structure for a single server, and it worked
          just
          > fine. However, in that case we obviously did not have the extra level of
          the
          > \our_cluster_name\ directory. It would seem that in the cluster
          > configuration, we cannot do it this way. I would be VERY interested to
          hear
          > if anyone else has setup a cluster in a directory that is not under the
          > weblogic installation directory.
          >
          > Hopefully this may shed some light on your problem. Feel free to contact
          me
          > if you need any additional information (or if you solve the problem!).
          >
          > Jason Donnell
          > [email protected]
          >
          >
          > "Chad" <[email protected]> wrote in message
          > news:[email protected]...
          > > I am very interested in this thread - I am having the same behavior:
          > >
          > > javax.naming.CommunicationException. Root exception is
          > > java.lang.ClassNotFoundException: class
          > > healthecare.drug.ejb.DrugAlternateBeanHomeImpl_ServiceStub previously
          > > not found
          > > at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:181)
          > > at
          > weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
          > > at
          weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
          > > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:630)
          > > at
          >
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          > a:34)
          > > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
          > > at weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
          > > at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
          > > at
          > weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
          > > at
          > weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
          > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
          > >
          > > --------------- nested within: ------------------
          > > weblogic.rmi.UnmarshalException: Unmarshalling return
          > > - with nested exception:
          > > [java.lang.ClassNotFoundException: class
          > > healthecare.drug.ejb.DrugAlternateBeanHomeImpl_ServiceStub previously
          > > not found]
          > > at
          >
          weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
          > a:256)
          > > at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
          > > at javax.naming.InitialContext.lookup(InitialContext.java:350)
          > > at healthecare.util.EJBBase.findHomeInterface(EJBBase.java:178)
          > >
          > > One additional bit of information that I can add is that when I
          > > getInitialContext() like this:
          > >
          > > public static Context getInitialContext() throws Exception
          > > {
          > > String providerURL =
          > > "t3://" + CommonUtil.getProperty("ejb.server.name") +
          > > ":" + CommonUtil.getProperty("ejb.server.port");
          > >
          > > Hashtable ht = new Hashtable();
          > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
          > > "weblogic.jndi.WLInitialContextFactory");
          > > ht.put(Context.PROVIDER_URL, providerURL);
          > >
          > > return new InitialContext(ht);
          > > }
          > >
          > > When the "ejb.server.name" property is one server, like "serverName1",
          > > the code works. But when the "ejb.server.name" property is clustered,
          > > like "serverName1, serverName2", the code throws the exception above.
          > >
          > > I'll definitely re-post if I come up with anything.
          > >
          > > thanks,
          > > chad small
          > >
          > > "Jason Donnell" <[email protected]> wrote in message
          > news:<[email protected]>...
          > > > Well, that was a good test. I discovered I am unable to download
          classes
          > > > from the clustered server when pointing my browser at it. Any ideas
          what
          > > > kind of misconfiguration on my part would cause that behavior?
          > > >
          > > > Thanks,
          > > > Jason Donnell
          > > >
          > > > "Dimitri Rakitine" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > Try to point your browser to make sure you can actually download
          > classes
          > > > from it
          > > > > (point it to http://yourweblogic..../classes/some/class/name.class)
          > > > >
          > > > > Jason Donnell <[email protected]> wrote:
          > > > > > Yes, I know. That's the behavior that I had always seen before. Do
          > you
          > > > know
          > > > > > of any directory configurations or properties file settings that
          > could
          > > > make
          > > > > > the stub not be downloaded correctly, even though the EJB is
          > deployed on
          > > > the
          > > > > > server?
          > > >
          > > > > > "Tao Xie" <[email protected]> wrote in message
          > > > > > news:[email protected]...
          > > > > >> That's weird, Replica-aware stub should be downloaded to the
          client
          > > > except
          > > > > >> the client is on another Weblogic server.
          > > > > >>
          > > > > >> "Jason Donnell" <[email protected]> wrote in message
          > > > > >> news:[email protected]...
          > > > > >> | I am experiencing some weird behavior when attempting to access
          > EJBs
          > > > in
          > > > a
          > > > > >> | Weblogic 5.1.0 cluster. The cluster nodes startup fine, and the
          > EJBs
          > > > are
          > > > > >> | correctly deployed. However, when my test client attempts to
          > access
          > > > them
          > > > I
          > > > > >> | get the ClassNotFoundException listed below. This same client
          can
          > > > access
          > > > the
          > > > > >> | same EJBs deployed in a non-clustered environment without any
          > > > problems,
          > > > so
          > > > > >> | it's definitely related to my cluster configuration. The
          problem
          > > > seems
          > > > to
          > > > be
          > > > > >> | that the client is not receiving the client-side stub. To
          confim
          > > > this, I
          > > > put
          > > > > >> | the stub in the client's classpath, and did NOT get the
          > > > > >> | ClassNotFoundException. Has anyone else seen this error?
          > > > > >> |
          > > > > >> | BTW, I have compiled the EJB both with and without the
          > > > <home-is-clusterable>
          > > > > >> | flag set to true. I get the same exception either way.
          > > > > >> |
          > > > > >> | Thanks for any assistance,
          > > > > >> | Jason Donnell
          > > > > >> |
          > > > > >> |
          > > > > >> | javax.naming.CommunicationException. Root exception is
          > > > > >> | java.lang.ClassNotFoundException: class
          > > > > >> |
          > > > > >
          > > >
          > com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
          > > > > >> | previously not found
          > > > > >> |
          > > > > >> | at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:184)
          > > > > >> |
          > > > > >> | at
          > > > > >>
          > > >
          > weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
          > > > > >> |
          > > > > >> | at
          > > >
          weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
          > > > > >> |
          > > > > >> | at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:700)
          > > > > >> |
          > > > > >> | at
          > > > > >> |
          > > > > >>
          > > > > >
          > > >
          >
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          > > > > >> | a:34)
          > > > > >> |
          > > > > >> | at
          > > > weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
          > > > > >> |
          > > > > >> | at
          > > > weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
          > > > > >> |
          > > > > >> | at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
          > > > > >> |
          > > > > >> | at
          > > > > >>
          > > >
          > weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
          > > > > >> |
          > > > > >> | at
          > > > > >>
          > > >
          > weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
          > > > > >> |
          > > > > >> | at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          > > > > >> |
          > > > > >> |
          > > > > >> |
          > > > > >> | --------------- nested within: ------------------
          > > > > >> |
          > > > > >> | weblogic.rmi.UnmarshalException: Unmarshalling return
          > > > > >> | - with nested exception:
          > > > > >> | [java.lang.ClassNotFoundException: class
          > > > > >> |
          > > > > >
          > > >
          > com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
          > > > > >> | previously not found]
          > > > > >> |
          > > > > >> | at
          > > > > >> |
          > > > > >>
          > > > > >
          > > >
          >
          weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
          > > > > >> | a:256)
          > > > > >> |
          > > > > >> | at
          > > > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
          > > > > >> |
          > > > > >> | at javax.naming.InitialContext.lookup(InitialContext.java:350)
          > > > > >> |
          > > > > >> | at
          > > > > >> |
          > > > > >>
          > > > > >
          > > >
          >
          com.landacorp.maxmc.ejb.security.ClusterSecurityTest.main(ClusterSecurityTes
          > > > > >> | t.java:52)
          > > > > >> |
          > > > > >> |
          > > > > >> |
          > > > > >> |
          > > > > >>
          > > > > >>
          > > > >
          > > > >
          > > > >
          > > > > --
          > > > > Dimitri
          >
          >
          >
          >
          >
          >