1 2 Previous Next 15 Replies Latest reply on May 2, 2006 11:06 AM by Ovidiu Feodorov

    Problem with JBoss Messaging installation

    Philippe Larouche Newbie

      Hi, I tried to install JBoss Messaging but even if the installation was successful, I can't run examples and when I start the server with "run.bat -c messaging" command, here's the error I got when executed:


      15:07:52,554 INFO [ServiceConfigurator] Problem configuring service jboss.messaging:service=PersistenceManager
      org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@3a9d95 on mbean jboss.messaging:service=PersistenceMa
      nager; - nested throwable: (java.lang.reflect.UndeclaredThrowableException)
      at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698)
      at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:380)
      at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
      at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
      at org.jboss.system.ServiceController.install(ServiceController.java:226)
      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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
      at $Proxy4.install(Unknown Source)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
      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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
      at $Proxy6.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:334)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:522)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:207)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:280)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:974)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
      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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:477)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:357)
      at org.jboss.Main.boot(Main.java:200)
      at org.jboss.Main$1.run(Main.java:464)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.reflect.UndeclaredThrowableException

      blablablablabla..........



      I use JBoss AS 4.0.4RC1.

      Need help! I know it's a really newby question, but I have no clue on what could cause this...

      Thx
      korg

        • 1. Re: Problem with JBoss Messaging installation
          Ovidiu Feodorov Master

          Tried 4.0.4.RC1 and works fine for me:

          20:28:25,838 INFO [ServerPeer] JMS ServerPeer [server.0] started, connection failure checking active, lease period 20000 ms
          20:28:25,848 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] deployed
          20:28:25,878 INFO [Topic] Topic[/topic/testTopic] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,878 INFO [Topic] Topic[/topic/securedTopic] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,878 INFO [Topic] Topic[/topic/testDurableTopic] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,898 INFO [Queue] Queue[/queue/testQueue] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,898 INFO [Queue] Queue[/queue/DLQ] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,898 INFO [Queue] Queue[/queue/A] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,898 INFO [Queue] Queue[/queue/B] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,918 INFO [Queue] Queue[/queue/C] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,938 INFO [Queue] Queue[/queue/D] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,968 INFO [Queue] Queue[/queue/ex] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:25,968 INFO [Topic] Topic[/topic/openTopic] started, fullSize=75000, pageSize=2000, downCacheSize=1000
          20:28:26,008 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
          20:28:26,469 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
          20:28:26,719 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
          20:28:26,719 INFO [JkMain] Jk running ID=0 time=0/190 config=null
          20:28:26,729 INFO [Server] JBoss (MX MicroKernel) [4.0.4RC1 (build: CVSTag=JBoss_4_0_4_RC1 date=200604032022)] Started in 21s:321ms


          Have you modifed the "default" configuration? The installation script uses the "default" configuration as a base for the "messaging" configuration.

          Recompile JBoss4.0.4.RC1 to generate a fresh default configuration and try again with that. Or, use JBoss 4.0.3SP1 to see if you get the same problem.

          • 2. Re: Problem with JBoss Messaging installation
            Philippe Larouche Newbie

            I receive the same error with AS 4.0.4RC2, 4.0.4RC1 and 4.0.3SP1. I didn't modify anything, just run the JBoss AS installer, then the automated procedure as described at section 4.1.1 in the Getting Started document available with JBoss Messaging.

            Korg

            • 3. Re: Problem with JBoss Messaging installation
              Ovidiu Feodorov Master

              Looking into it. I may need additional information.

              • 4. Re: Problem with JBoss Messaging installation
                Ovidiu Feodorov Master

                What Java version are you using to run the JBoss server?

                • 5. Re: Problem with JBoss Messaging installation
                  Balu Gopalakrishna Pillai Newbie

                  After installing JBossMessaging, when I try to verify the installation by running /examples/queue, I get the following exception:
                  E:\Projects\JBossMessaging\jboss-messaging-1.0.0.GA\examples\queue>ant
                  Buildfile: build.xml

                  identify:
                  [echo] Running the queue example
                  [echo] The queue: testQueue

                  sanity-check:

                  init:

                  compile:

                  run:
                  [java] javax.naming.CommunicationException [Root exception is java.lang.Cla
                  ssNotFoundException: org.jboss.jmx.adaptor.rmi.RMIAdaptor (no security manager:
                  RMI class loader disabled)]
                  [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:72
                  8)
                  [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:58
                  7)
                  [java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
                  [java] at org.jboss.example.jms.common.Util.lookupMBeanServerProxy(Util
                  .java:88)
                  [java] at org.jboss.example.jms.common.Util.deployQueue(Util.java:57)
                  [java] at org.jboss.example.jms.common.ExampleSupport.setup(ExampleSupp
                  ort.java:148)
                  [java] at org.jboss.example.jms.common.ExampleSupport.run(ExampleSuppor
                  t.java:57)
                  [java] at org.jboss.example.jms.queue.QueueExample.main(QueueExample.ja
                  va:125)
                  [java] Caused by: java.lang.ClassNotFoundException: org.jboss.jmx.adaptor.r
                  mi.RMIAdaptor (no security manager: RMI class loader disabled)
                  [java] at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.jav
                  a:531)
                  [java] at java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoade
                  r.java:639)
                  [java] at java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.
                  java:309)
                  [java] at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalIn
                  putStream.java:241)
                  [java] at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.jav
                  a:1469)
                  [java] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.jav
                  a:1432)
                  [java] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStrea
                  m.java:1626)
                  [java] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:
                  1274)
                  [java] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:3
                  24)
                  [java] at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
                  [java] at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePai
                  r.java:72)
                  [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:65
                  2)
                  [java] ... 7 more

                  [java] #####################
                  [java] ### FAILURE! ###
                  [java] #####################

                  BUILD FAILED
                  E:\Projects\JBossMessaging\jboss-messaging-1.0.0.GA\examples\queue\build.xml:77:
                  Java returned: 1

                  Total time: 1 second
                  E:\Projects\JBossMessaging\jboss-messaging-1.0.0.GA\examples\queue>

                  • 6. Re: Problem with JBoss Messaging installation
                    Ovidiu Feodorov Master

                    Fortunately, there's nothing wrong with Messaging, but with the example fixture. I tried to make it run out of the box everywhere and I didn't quite suceed :)

                    I assume you're running one of 4.0.0 - 4.0.2 releases.

                    If your server did deploy correctly, just try to validate it the old fashioned way: write a simple JMS client that looks up a ConnectionFactory, then creates a connection, a session, etc.

                    In the mean time, I am fixing the fixture (http://jira.jboss.org/jira/browse/JBMESSAGING-320).

                    A 1.0.1 release with all these deployment annoyances fixed should be out some time next week: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel

                    • 7. Re: Problem with JBoss Messaging installation
                      flkjdj poifjepoij Newbie

                      I'm having the same problem as the original poster when trying to install the new messaging into JBoss 4.0.3SP1

                      • 8. Re: Problem with JBoss Messaging installation
                        Ovidiu Feodorov Master

                        OK, I need to understand what you are doing, so I can replicate the steps.

                        • 9. Re: Problem with JBoss Messaging installation
                          flkjdj poifjepoij Newbie

                          I downloaded the JBoss messaging 1.0GA and read the instructions. I then installed JBoss Application server and installed it through the jnlp installer and did not touch its original configuration. I ran the
                          C:\jboss-messaging-1.0.0.GA\util\create-messaging-config.xml
                          ant script.

                          When trying to run the server (run.bat -c messaging) I get the exact exception that the original poster (korg) got.

                          • 10. Re: Problem with JBoss Messaging installation
                            Arvinder Singh Novice

                            Use the 4.0.4 CR2 release from http://labs.jboss.com/portal/jbossas/download and jdk1.5, just get the full download and unzip it. I had the same issue with the previous release, but using the release above and the automated message server creation, should work, well it did for me.

                            • 11. Re: Problem with JBoss Messaging installation
                              Ovidiu Feodorov Master

                              Thanks for the help.

                              Truth is I did not smoke test the release with an installer-generated JBoss instance, only with compiled-from-source ones. I will do it shortly, however and fix what needs to be fixed (the installation script, most likely, which is rather simple minded)

                              Thanks to you, this will make it to the smoke test matrix so we won't have this problem with the next release.

                              • 12. Re: Problem with JBoss Messaging installation
                                Ovidiu Feodorov Master

                                The problem is caused by http://jira.jboss.org/jira/browse/JBMESSAGING-337 and it only affects deployments within a JBoss instance created with the JNLP installer.

                                The fix will be available with 1.0.1 (or 1.0.0.SP1 if we decide to release just a service pack). In the mean time, use the workaround suggested by arvinder.

                                • 13. Re: Problem with JBoss Messaging installation
                                  Philippe Larouche Newbie

                                  Sorry guys for not responding to your questions about my original concern, but I was out of office, so it gone out of my mind. But another user explained exactly the procedure I followed and it seems to have done the job so ovidiu found what the problem was. I'll wait for the next release and try it when available.


                                  Thx for help, hope to be able to use JBoss Messaging soon.
                                  Korg

                                  • 14. Re: Problem with JBoss Messaging installation
                                    Eric Ran Newbie

                                    Is this problem fixed or has anyone have a workaround on this one? I tried all all the releases and get the same exception when I follow the installation instr.

                                    1 2 Previous Next