3 Replies Latest reply on Dec 6, 2001 1:34 PM by ptran83

    Problem of using JMS as the managed resource example using J

    ptran83

      Hi,

      I have problem of running the example using ant jms-topic-hello24 using JBOSS 2.4.3. I wonder I have to modify the resource file for this version of JBOSS.

      Thanks in advance

      The following is the stack trace:

      hello-client:
      [java] [java] Error: javax.naming.NameNotFoundException: TopicHello no
      t bound
      javax.naming.NameNotFoundException: TopicHello not bound
      [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServe
      r(StreamRemoteCall.java:245)
      [java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCa
      ll.java:220)
      [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
      [java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:34
      9)
      [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:33
      3)
      [java] at javax.naming.InitialContext.lookup(InitialContext.java:350)
      [java] at org.jboss.docs.jms.ra.HelloClient.setUp(HelloClient.java:52)
      [java] at org.jboss.docs.jms.ra.HelloClient.(HelloClient.java:43)

      [java] at org.jboss.docs.jms.ra.HelloClient.main(HelloClient.java:69)

      undeploy-bean:
      [echo] Undeploying bean: TopicHello24.jar
      [java] Undeploying C:\FreeSoftwares\JBoss-2.4.3_Tomcat-3.2.3\jboss\examples
      _jboss/build-examples/jms/TopicHello24.jar
      [java] javax.naming.NameNotFoundException: jmx not bound
      [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServe
      r(StreamRemoteCall.java:245)
      [java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCa
      ll.java:220)
      [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
      [java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:34
      9)
      [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:33
      3)
      [java] at javax.naming.InitialContext.lookup(InitialContext.java:350)
      [java] at org.jboss.jmx.client.Deployer.lookupAdaptor(Deployer.java:104
      )
      [java] at org.jboss.jmx.client.Deployer.undeploy(Deployer.java:75)
      [java] at org.jboss.jmx.client.Deployer.main(Deployer.java:41)
      [java] Exception in thread "main"
      [java] Java Result: 1

        • 1. Re: Problem of using JMS as the managed resource example usi

          Hi, sorry but the deployment does not seem to work. I have not been able to follow suite in the deployment changed made in JBoss lately. You may do it by manually deploying the bean...but I guess that was not the answer you wanted to hear.

          I will try and look over the examples when the new 2.4.4 arrive.

          //Peter

          • 2. Re: Problem of using JMS as the managed resource example usi

            Hm, just tested with a 2.4.3 bin release and the lates manual cvs code and it still worked swell. Have you got a correct JBOSS_DIST? Or have you tampered with your dist?

            //Peter

            • 3. Re: Problem of using JMS as the managed resource example usi
              ptran83

              Peter, thanks.

              Thanks for looking at this problem. I reinstall JBOSS to different directory and the problem is not there with clean installation. The problem happens on both NT and Solaris 2.8. I only change the config files to have SQL data source (on NT) and Oracle data source (on Solaris) and adding new JMS topic. MDB and other works well except the JMS as the managed resource. I will take a look of these environments and let you know in details.