1 Reply Latest reply on Sep 22, 2004 4:21 PM by simps05192

    Possible JBoss bug

      Windows XP, JBoss 4.0.0RC2

      I am running the examples in Monson-Haefel's Enterprise Javabeans book fourth edition. I ran the first example ex04_1, Client_1 and the output worked just fine. When I ran the second example, I got

      Buildfile: D:\sandbox\ex04_1\build.xml
      prepare:
      compile:
       [javac] Compiling 5 source files to D:\sandbox\ex04_1\build\classes
      ejbjar:
       [jar] Building jar: D:\sandbox\ex04_1\build\titan.jar
       [copy] Copying 1 file to D:\Apps\jboss-4.0.0RC2\server\default\deploy
      run.client_41b:
       [java] java.lang.IllegalArgumentException: null object name
       [java] at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:495)
       [java] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:636)
       [java] at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:775)
       [java] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382)
       [java] at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
       [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       [java] at java.lang.reflect.Method.invoke(Method.java:324)
       [java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
       [java] at sun.rmi.transport.Transport$1.run(Transport.java:148)
       [java] at java.security.AccessController.doPrivileged(Native Method)
       [java] at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
       [java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
       [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
       [java] at java.lang.Thread.run(Thread.java:534)
       [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
       [java] at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
       [java] at sun.rmi.server.UnicastRef.invoke(Unknown Source)
       [java] at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
       [java] at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
       [java] at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:96)
       [java] at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
       [java] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
       [java] at org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:97)
       [java] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
       [java] at $Proxy1.setBedCount(Unknown Source)
       [java] at com.titan.clients.Client_2.makeCabins(Client_2.java:91)
       [java] at com.titan.clients.Client_2.main(Client_2.java:27)
      


      which looks like some kind of internal error. Interestingly, I deleted the hypersonic DB and reran Client_1 followed by Client_2 and now the second invocation worked.

        • 1. Re: Possible JBoss bug

          I can exercise this bug pretty consistently. If I take out the copy of titan.jar to the deploy directory, then it seems to work. Therefore, it seems to be some kind of race condition between the copy of the titan.jar file to the deploy directory (which gets redeployed) and then running the EJB by using the Client_1 and Client_2 Ant targets.