2 Replies Latest reply on Jul 21, 2011 3:51 AM by se.sheetal

    deploying ejb2 in jboss5.0.0 GA

    se.sheetal

      Hi Frnz,

       

      I am migrating from jboss 3.2.6 to jboss 5.0.0 GA. In our project we are using ejb 2. While deploying my ear I am getting following error.

       

       

       

      16:13:02,733 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war

      16:13:02,842 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war

      16:13:02,983 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080

      16:13:03,077 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009

      16:13:03,139 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)] Started in 54s:218ms

      16:14:21,061 INFO [TomcatDeployment] deploy, ctxPath=/joa, vfsUrl=joa.ear/joa.war

      16:17:49,452 INFO [STDOUT] - BasicUtilities not bound

       

      javax.naming.NameNotFoundException

      -

      BasicUtilities not bound 

       

      at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

      at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

      at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

      at org.jnp.server.NamingServer.lookup(NamingServer.java:443)

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      at java.lang.reflect.Method.invoke(Method.java:585)

      at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)

      at sun.rmi.transport.Transport$1.run(Transport.java:153)

      at java.security.AccessController.doPrivileged(Native Method)

      at sun.rmi.transport.Transport.serviceCall(Transport.java:149)

      at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)

      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)

      at java.lang.Thread.run(Thread.java:595)

      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)

      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)

      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)

      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)

      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)

      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)

      at javax.naming.InitialContext.lookup(InitialContext.java:351)

       

      I it because of ejb2 or something else?? Do we need to make any configuration changes for deploying ejb2 in jboss, if yes, what are they.