5 Replies Latest reply on May 14, 2005 11:26 AM by Andy Smith

    JBoss Portal won't work after deployment

    Andy Smith Newbie

      Hello,

      I've installed JBoss 4.0.2, MySQL 4.1.11 (both for Windows 2000 Pro) and on there own they work fine. Which is good as I needed them for JBoss Portal :D.

      I've then tried both the binary and source distributions of JBoss-portal 2.0 RC. When ever the .sar is placed in server/default/deploy I get the following on the console:


      10:07:41,793 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
      10:07:42,981 INFO [Server] Core system initialized
      10:07:47,231 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
      ce:log4j.xml
      10:07:47,528 INFO [WebService] Using RMI server codebase: http://gondor:8083/
      10:07:48,028 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=
      1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server Socket
      Factory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
      10:08:41,700 ERROR [MainDeployer] could not create deployment: file:/D:/jboss-4.
      0.2/server/default/deploy/jboss-portal.sar
      org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect
      .UndeclaredThrowableException)
      at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
      :143)
      at org.jboss.system.ServiceController.install(ServiceController.java:202
      )
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
      er.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
      java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.install(Unknown Source)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:220)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:918)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
      er.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

      Then later on after most of the other apps have deployed i get the notification that jboss-portal is being destroyed due to the deployment failure.

      I have checked and double checked the installation guide and also tried to investigate further. But as I am relatively new to JBoss and application servers there is nothing obviously wrong to me.

      Any help/guidance gratefully accepted - even if it is "you dumbo you haven't do x,y,z :)

      All the best

      Andy



        • 1. Re: JBoss Portal won't work after deployment
          Martin Giljohann Newbie

          The recommended JBoss version is 4.0.1 - did you try this one as well?

          Martin

          • 2. Re: JBoss Portal won't work after deployment
            Andy Smith Newbie

             

            "martingi" wrote:
            The recommended JBoss version is 4.0.1 - did you try this one as well?

            Martin


            No that is my current line of investigation - I will post a reply when its been tested again 4.0.1.

            Thanks

            • 3. Re: JBoss Portal won't work after deployment
              Andy Smith Newbie

              Well I get a little further with JBoss 4.0.1sp1 - thanks.

              But now I get the following during deployment. Sorry if this is the result of a real dumb person installing it but I just don't know how to fix this latest issue :(


              14:52:26,086 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/D
              :/jboss-4.0.1sp1/server/default/deploy/jmx-console.war/
              14:52:26,555 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/D
              :/jboss-4.0.1sp1/server/default/deploy/management/web-console.war/
              14:52:27,555 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
              MBeans waiting for other MBeans:
              ObjectName: portal:service=CMS
              state: CONFIGURED
              I Depend On: jboss.cache:service=InvalidationManager
              jboss.jca:name=PortalDS,service=DataSourceBinding

              Depends On Me: portal:service=Tree

              ObjectName: portal:service=Hibernate
              state: CONFIGURED
              I Depend On: jboss.jca:name=PortalDS,service=DataSourceBinding

              Depends On Me: portal:service=Module,type=User
              portal:service=Module,type=Role
              portal:service=Module,type=Security
              portal:service=ServerManager

              ObjectName: portal:service=Tree
              state: CONFIGURED
              I Depend On: portal:service=CMS

              Depends On Me: portal:service=Module,type=Security

              ObjectName: portal:service=Module,type=User
              state: CONFIGURED
              I Depend On: portal:service=Hibernate

              Depends On Me: portal:service=Module,type=Mail

              ObjectName: portal:service=Module,type=Role
              state: CONFIGURED
              I Depend On: portal:service=Hibernate

              Depends On Me:
              ObjectName: portal:service=Module,type=Security
              state: CONFIGURED
              I Depend On: portal:service=Hibernate
              portal:service=Tree

              Depends On Me:
              ObjectName: portal:service=Module,type=Mail
              state: CONFIGURED
              I Depend On: portal:service=Module,type=User

              Depends On Me:
              ObjectName: portal:service=ServerManager
              state: CONFIGURED
              I Depend On: portal:service=Hibernate
              portal:service=Configuration
              portal:service=ObjectFactory
              portal:service=ThemeServer
              portal:service=LayoutServer

              Depends On Me: portal:service=Deployer,type=PortalWebApp

              ObjectName: portal:service=Deployer,type=PortalWebApp
              state: CONFIGURED
              I Depend On: jboss.system:service=MainDeployer
              portal:service=ServerManager

              Depends On Me: portal:service=Deployer,type=JBoss
              portal:service=Deployer,type=Adapter

              ObjectName: portal:service=Deployer,type=JBoss
              state: CONFIGURED
              I Depend On: portal:service=Deployer,type=PortalWebApp

              Depends On Me:
              ObjectName: portal:service=Deployer,type=Adapter
              state: CONFIGURED
              I Depend On: portal:service=Deployer,type=PortalWebApp
              jboss.web:service=WebServer

              Depends On Me:

              MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
              ObjectName: jboss.jca:name=PortalDS,service=DataSourceBinding
              state: NOTYETINSTALLED
              I Depend On:
              Depends On Me: portal:service=CMS
              portal:service=Hibernate


              14:52:27,867 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-808
              0
              14:52:28,164 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
              14:52:28,180 INFO [JkMain] Jk running ID=0 time=0/172 config=null
              14:52:28,195 INFO [Server] JBoss (MX MicroKernel) [4.0.1sp1 (build: CVSTag=JBos
              s_4_0_1_SP1 date=200502160314)] Started in 40s:797ms

              Thanks for any help/advice

              Andy

              • 4. Re: JBoss Portal won't work after deployment
                Roy Russo Master

                Did you follow the install steps in the guide? Mainly, did you copy over the portal-ds.xml and run the sql and ddl files on your mySQL install?

                • 5. Re: JBoss Portal won't work after deployment
                  Andy Smith Newbie

                   

                  "roy.russo@jboss.com" wrote:
                  Did you follow the install steps in the guide? Mainly, did you copy over the portal-ds.xml and run the sql and ddl files on your mySQL install?


                  Yes - that is one of things I've double checked and also dropped the database and done it again - just to make sure :D

                  Well to honnest - and this is the embarassing point I'd correctly copied the .sar file from Jboss-4.0.2 but forgot the portal-ds.xml file :((

                  Now I do get the Portal deployed - Yippee, and thanks very much for your help.

                  Now I can start to get to grips with it and hopefully start creating my own portlets.

                  All the best

                  Andy