7 Replies Latest reply on Apr 23, 2003 11:41 PM by andygallo.cti

    jboss-3.2.0_tomcat-4.1.24 start up problem

    philiptsekh

      Hello,

      I get the tomcat 4.1.24 run already, and now I placed the jboss 3.2 (with tomcat 4.1.24) in a folder and run the run.bat, then I get the following errors:

      03:02:43,985 INFO [TransactionManagerService] Creating
      03:02:43,985 INFO [TransactionManagerService] Created
      03:02:44,005 INFO [EJBDeployer] Creating
      03:02:44,015 INFO [EJBDeployer] Created
      03:02:44,015 INFO [JRMPInvoker] Creating
      03:02:44,015 INFO [JRMPInvoker] Created
      03:02:44,015 INFO [InvokerAdaptorService] Creating
      03:02:44,015 INFO [InvokerAdaptorService] Created
      03:02:44,025 INFO [LocalInvoker] Creating
      03:02:44,025 INFO [LocalInvoker] Created
      03:02:44,025 INFO [PooledInvoker] Creating
      03:02:44,025 INFO [PooledInvoker] Created
      03:02:44,025 INFO [ClientUserTransactionService] Creating
      03:02:44,025 INFO [ClientUserTransactionService] Created
      03:02:44,025 INFO [CachedConnectionManager] Creating
      03:02:44,025 INFO [CachedConnectionManager] Created
      03:02:44,025 INFO [TxConnectionManager] Creating
      03:02:44,025 INFO [TxConnectionManager] Created
      03:02:44,025 INFO [PersistenceManager] Creating
      03:02:44,025 INFO [PersistenceManager] Created
      03:02:44,035 INFO [DestinationManager] Creating
      03:02:44,045 INFO [DestinationManager] Created
      03:02:44,065 INFO [A] Creating
      03:02:44,065 INFO [A] Created
      03:02:44,065 INFO [B] Creating
      03:02:44,065 INFO [B] Created
      03:02:44,065 INFO [C] Creating
      03:02:44,065 INFO [C] Created
      03:02:44,065 INFO [D] Creating
      03:02:44,065 INFO [D] Created
      03:02:44,065 INFO [ex] Creating
      03:02:44,065 INFO [ex] Created
      03:02:44,065 INFO [SecurityManager] Creating
      03:02:44,065 INFO [SecurityManager] Created
      03:02:44,075 INFO [testTopic] Creating
      03:02:44,075 INFO [testTopic] Created
      03:02:44,075 INFO [securedTopic] Creating
      03:02:44,075 INFO [securedTopic] Created
      03:02:44,075 INFO [testDurableTopic] Creating
      03:02:44,075 INFO [testDurableTopic] Created
      03:02:44,075 INFO [testQueue] Creating
      03:02:44,075 INFO [testQueue] Created
      03:02:44,075 INFO [InterceptorLoader] Creating
      03:02:44,075 INFO [InterceptorLoader] Created
      03:02:44,075 INFO [Invoker] Creating
      03:02:44,075 INFO [Invoker] Created
      03:02:44,075 INFO [JVMServerILService] Creating
      03:02:44,075 INFO [JVMServerILService] Created
      03:02:44,075 INFO [RMIServerILService] Creating
      03:02:44,085 INFO [RMIServerILService] Created
      03:02:44,085 INFO [OILServerILService] Creating
      03:02:44,085 INFO [OILServerILService] Created
      03:02:44,085 INFO [UILServerILService] Creating
      03:02:44,085 INFO [UILServerILService] Created
      03:02:44,085 INFO [OIL2ServerILService] Creating
      03:02:44,085 INFO [OIL2ServerILService] Created
      03:02:44,085 INFO [UILServerILService] Creating
      03:02:44,085 INFO [UILServerILService] Created
      03:02:44,085 INFO [DLQ] Creating
      03:02:44,085 INFO [DLQ] Created
      03:02:44,085 INFO [TxConnectionManager] Creating
      03:02:44,085 INFO [TxConnectionManager] Created
      03:02:44,085 INFO [ServerSessionPoolLoader] Starting
      03:02:44,095 INFO [ServerSessionPoolLoader] pool factory StdJMSPool bound to ja
      va:/StdJMSPool
      03:02:44,095 INFO [ServerSessionPoolLoader] Started
      03:02:44,095 INFO [TransactionManagerService] Starting
      03:02:44,145 INFO [TransactionManagerService] Started
      03:02:44,145 INFO [EJBDeployer] Starting
      03:02:44,155 INFO [MainDeployer] Adding deployer: org.jboss.ejb.EJBDeployer@1eb
      0c6
      03:02:44,155 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/jbossmq-httpil.sar/jbossmq-httpil.war/
      03:02:44,155 INFO [MainDeployer] deployment waiting for deployer: file:/D:/Appl
      /JBoss/server/default/deploy/jbossmq-httpil.sar/jbossmq-httpil.war/
      03:02:44,155 INFO [MainDeployer] Deployment of package: file:/D:/Appl/JBoss/ser
      ver/default/deploy/jbossmq-httpil.sar/jbossmq-httpil.war/ is waiting for an appr
      opriate deployer.
      03:02:44,155 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/http-invoker.sar/invoker.war/
      03:02:44,155 INFO [MainDeployer] deployment waiting for deployer: file:/D:/Appl
      /JBoss/server/default/deploy/http-invoker.sar/invoker.war/
      03:02:44,155 INFO [MainDeployer] Deployment of package: file:/D:/Appl/JBoss/ser
      ver/default/deploy/http-invoker.sar/invoker.war/ is waiting for an appropriate d
      eployer.
      03:02:44,155 INFO [EJBDeployer] Started
      03:02:44,155 INFO [JRMPInvoker] Starting
      03:02:44,185 INFO [JRMPInvoker] Started
      03:02:44,185 INFO [InvokerAdaptorService] Starting
      03:02:44,265 INFO [InvokerAdaptorService] Started
      03:02:44,265 INFO [LocalInvoker] Starting
      03:02:44,265 INFO [LocalInvoker] Started
      03:02:44,265 INFO [PooledInvoker] Starting
      03:02:44,295 INFO [PooledInvoker] Started
      03:02:44,295 INFO [ClientUserTransactionService] Starting
      03:02:44,325 INFO [ClientUserTransactionService] Started
      03:02:44,325 INFO [CachedConnectionManager] Starting
      03:02:44,325 INFO [CachedConnectionManager] Started
      03:02:44,336 INFO [TxConnectionManager] Starting
      03:02:44,346 INFO [DefaultDS] Bound connection factory for resource adapter for
      ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'jav
      a:/DefaultDS'
      03:02:44,346 INFO [TxConnectionManager] Started
      03:02:44,346 INFO [PersistenceManager] Starting
      03:02:44,586 WARN [WrappedConnection] Closing a statement you left open, please
      do your own housekeeping
      03:02:44,586 WARN [WrappedConnection] Closing a statement you left open, please
      do your own housekeeping
      03:02:44,586 INFO [PersistenceManager] Started
      03:02:44,586 INFO [DestinationManager] Starting
      03:02:44,596 INFO [DestinationManager] Started
      03:02:44,616 INFO [A] Starting
      03:02:44,646 INFO [A] Bound to JNDI name: queue/A
      03:02:44,646 INFO [A] Started
      03:02:44,646 INFO [B] Starting
      03:02:44,656 INFO [B] Bound to JNDI name: queue/B
      03:02:44,656 INFO [B] Started
      03:02:44,656 INFO [C] Starting
      03:02:44,656 INFO [C] Bound to JNDI name: queue/C
      03:02:44,656 INFO [C] Started
      03:02:44,656 INFO [D] Starting
      03:02:44,676 INFO [D] Bound to JNDI name: queue/D
      03:02:44,676 INFO [D] Started
      03:02:44,676 INFO [ex] Starting
      03:02:44,686 INFO [ex] Bound to JNDI name: queue/ex
      03:02:44,686 INFO [ex] Started
      03:02:44,686 INFO [SecurityManager] Starting
      03:02:44,706 INFO [JaasSecurityManagerService] Created securityMgr=org.jboss.se
      curity.plugins.JaasSecurityManager@1d03a4e
      03:02:44,726 INFO [JaasSecurityManagerService] setCachePolicy, c=org.jboss.util
      .TimedCachePolicy@1a034d
      03:02:44,726 INFO [JaasSecurityManagerService] Added jbossmq, org.jboss.securit
      y.plugins.SecurityDomainContext@1cee792 to map
      03:02:44,736 INFO [SecurityManager] Started
      03:02:44,736 INFO [testTopic] Starting
      03:02:44,736 INFO [testTopic] Bound to JNDI name: topic/testTopic
      03:02:44,746 INFO [testTopic] Started
      03:02:44,746 INFO [securedTopic] Starting
      03:02:44,746 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      03:02:44,746 INFO [securedTopic] Started
      03:02:44,746 INFO [testDurableTopic] Starting
      03:02:44,746 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic

      03:02:44,746 INFO [testDurableTopic] Started
      03:02:44,746 INFO [testQueue] Starting
      03:02:44,756 INFO [testQueue] Bound to JNDI name: queue/testQueue
      03:02:44,756 INFO [testQueue] Started
      03:02:44,756 INFO [InterceptorLoader] Starting
      03:02:44,756 INFO [InterceptorLoader] Started
      03:02:44,756 INFO [Invoker] Starting
      03:02:44,756 INFO [Invoker] Started
      03:02:44,756 INFO [JVMServerILService] Starting
      03:02:44,796 INFO [JVMServerILService] Started
      03:02:44,796 INFO [RMIServerILService] Starting
      03:02:44,876 INFO [RMIServerILService] Started
      03:02:44,876 INFO [OILServerILService] Starting
      03:02:44,886 INFO [OILServerILService] JBossMQ OIL service available at : 0.0.0
      .0/0.0.0.0:8090
      03:02:44,916 INFO [OILServerILService] Started
      03:02:44,916 INFO [UILServerILService] Starting
      03:02:44,936 INFO [UILServerILService] JBossMQ UIL service available at : 0.0.0
      .0/0.0.0.0:8091
      03:02:44,956 INFO [UILServerILService] Started
      03:02:44,956 INFO [OIL2ServerILService] Starting
      03:02:44,966 INFO [OIL2ServerILService] JBossMQ OIL2 service available at : 0.0
      .0.0/0.0.0.0:8092
      03:02:44,986 INFO [OIL2ServerILService] Started
      03:02:44,986 INFO [UILServerILService] Starting
      03:02:44,996 INFO [UILServerILService] JBossMQ UIL service available at : 0.0.0
      .0/0.0.0.0:8093
      03:02:45,067 INFO [UILServerILService] Started
      03:02:45,067 INFO [DLQ] Starting
      03:02:45,067 INFO [DLQ] Bound to JNDI name: queue/DLQ
      03:02:45,067 INFO [DLQ] Started
      03:02:45,067 INFO [TxConnectionManager] Starting
      03:02:45,077 INFO [JaasSecurityManagerService] Created securityMgr=org.jboss.se
      curity.plugins.JaasSecurityManager@a33ce2
      03:02:45,077 INFO [JaasSecurityManagerService] setCachePolicy, c=org.jboss.util
      .TimedCachePolicy@f221f6
      03:02:45,077 INFO [JaasSecurityManagerService] Added JmsXARealm, org.jboss.secu
      rity.plugins.SecurityDomainContext@93c4f1 to map
      03:02:45,087 INFO [JmsXA] Bound connection factory for resource adapter for Con
      nectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
      03:02:45,087 INFO [TxConnectionManager] Started
      03:02:45,107 INFO [MainDeployer] Deployed package: file:/D:/Appl/JBoss/server/d
      efault/deploy/transaction-service.xml
      03:02:45,107 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/user-service.xml
      03:02:45,127 INFO [SARDeployer] looking for nested deployments in : file:/D:/Ap
      pl/JBoss/server/default/deploy/user-service.xml
      03:02:45,137 INFO [MainDeployer] Deployed package: file:/D:/Appl/JBoss/server/d
      efault/deploy/user-service.xml
      03:02:45,137 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/ejb-management.jar
      03:02:45,267 INFO [EJBDeployer] looking for nested deployments in : file:/D:/Ap
      pl/JBoss/server/default/deploy/ejb-management.jar
      03:02:45,707 INFO [EjbModule] Creating
      03:02:45,717 INFO [EjbModule] Deploying MEJB
      03:02:45,848 INFO [StatelessSessionContainer] Creating
      03:02:45,858 INFO [StatelessSessionInstancePool] Creating
      03:02:45,858 INFO [StatelessSessionInstancePool] Created
      03:02:45,868 INFO [StatelessSessionContainer] Created
      03:02:45,868 INFO [EjbModule] Created
      03:02:45,868 INFO [EjbModule] Starting
      03:02:45,878 INFO [StatelessSessionContainer] Starting
      03:02:45,918 INFO [StatelessSessionInstancePool] Starting
      03:02:45,918 INFO [StatelessSessionInstancePool] Started
      03:02:45,918 INFO [StatelessSessionContainer] Started
      03:02:45,918 INFO [EjbModule] Started
      03:02:45,978 INFO [MainDeployer] Deployed package: file:/D:/Appl/JBoss/server/d
      efault/deploy/ejb-management.jar
      03:02:45,988 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/jmx-ejb-adaptor.jar
      03:02:46,088 INFO [EJBDeployer] looking for nested deployments in : file:/D:/Ap
      pl/JBoss/server/default/deploy/jmx-ejb-adaptor.jar
      03:02:46,378 INFO [EjbModule] Creating
      03:02:46,378 INFO [EjbModule] Deploying jmx/ejb/Adaptor
      03:02:46,388 INFO [StatelessSessionContainer] Creating
      03:02:46,398 INFO [StatelessSessionInstancePool] Creating
      03:02:46,398 INFO [StatelessSessionInstancePool] Created
      03:02:46,398 INFO [StatelessSessionContainer] Created
      03:02:46,398 INFO [EjbModule] Created
      03:02:46,398 INFO [EjbModule] Starting
      03:02:46,398 INFO [StatelessSessionContainer] Starting
      03:02:46,439 INFO [StatelessSessionInstancePool] Starting
      03:02:46,439 INFO [StatelessSessionInstancePool] Started
      03:02:46,439 INFO [StatelessSessionContainer] Started
      03:02:46,439 INFO [EjbModule] Started
      03:02:46,459 INFO [MainDeployer] Deployed package: file:/D:/Appl/JBoss/server/d
      efault/deploy/jmx-ejb-adaptor.jar
      03:02:46,459 INFO [MainDeployer] Starting deployment of package: file:/D:/Appl/
      JBoss/server/default/deploy/jmx-console.war/
      03:02:46,459 INFO [MainDeployer] deployment waiting for deployer: file:/D:/Appl
      /JBoss/server/default/deploy/jmx-console.war/
      03:02:46,459 INFO [MainDeployer] Deployment of package: file:/D:/Appl/JBoss/ser
      ver/default/deploy/jmx-console.war/ is waiting for an appropriate deployer.
      03:02:46,459 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
      ration 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:
      [org.jboss.deployment.DeploymentInfo@9b714197 { url=file:/D:/Appl/JBoss/server/d
      efault/deploy/jbossmq-httpil.sar/jbossmq-httpil.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/Appl/JBoss/server/default/deploy/jbossmq-httpil.sar/jbossmq-ht
      tpil.war/
      lastDeployed: 1050260564155
      lastModified: 1050246918000
      mbeans:
      , org.jboss.deployment.DeploymentInfo@db96b47a { url=file:/D:/Appl/JBoss/server/
      default/deploy/http-invoker.sar/invoker.war/ }
      deployer: null
      status: Starting
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/Appl/JBoss/server/default/deploy/http-invoker.sar/invoker.war/

      lastDeployed: 1050260564155
      lastModified: 1050246918000
      mbeans:
      , org.jboss.deployment.DeploymentInfo@b6d55d51 { url=file:/D:/Appl/JBoss/server/
      default/deploy/jmx-console.war/ }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/Appl/JBoss/server/default/deploy/jmx-console.war/
      lastDeployed: 1050260566459
      lastModified: 1050246914000
      mbeans:
      ]Incompletely deployed packages:
      [org.jboss.deployment.DeploymentInfo@b6d55d51 { url=file:/D:/Appl/JBoss/server/d
      efault/deploy/jmx-console.war/ }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/Appl/JBoss/server/default/deploy/jmx-console.war/
      lastDeployed: 1050260566459
      lastModified: 1050246914000
      mbeans:
      ]MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.web:service=WebServer
      state: FAILED
      I Depend On:
      Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
      LifecycleException: Protocol handler initialization failed: java.net.BindExcept
      ion: Address already in use: JVM_Bind:8080, ObjectName: jboss.mq:service=Invocat
      ionLayer,type=HTTP
      state: CONFIGURED
      I Depend On: jboss.mq:service=Invoker
      jboss.web:service=WebServer

      Depends On Me: ]
      03:02:46,469 INFO [URLDeploymentScanner] Started
      03:02:46,509 INFO [MainDeployer] Deployed package: file:/D:/Appl/JBoss/server/d
      efault/conf/jboss-service.xml
      03:02:46,509 INFO [Server] JBoss (MX MicroKernel) [3.2.0 (build: CVSTag=JBoss_3
      _2_0 date=200304110033)] Started in 12s:408ms

      The problem I guess is : tomcat already use the port 8080, and then jboss finds out that port is occupied. But how can jboss and tomcat integrate?

      Would you please help.

        • 1. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
          dcartier

          Hi,

          You appear to be trying to run an external Tomcat along with a copy of 3.2.0 that also has Tomcat integrated. You do NOT need the external Tomcat. JBoss 3.2.0 (with Tomcat 4.1.24) already has Tomcat in it.

          If you *really* want to run your Tomcat in a separate JVM, then you can edit the tomcat41-service.xml file in the deploy directory and comment out the HTTP connector on port 8080. This is NOT recommended though as performance *will* suffer.

          Do yourself a favour and just run the JBoss (with integrated Tomcat) only.

          Dennis

          • 2. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
            philiptsekh

            Hello dcartier,

            Thank you for your help.

            Now I stop the tomcat service and it seems that jboss can be started normally. Then I try "http://localhost:8082", but it complains cannot find server. From the localhost_access.log, it shows the following msg:

            127.0.0.1 - - [15/Apr/2003:00:11:07 8000] "GET / HTTP/1.1" 500 866

            Please I want to know how can I verify jboss has been started ok? As the quickstart manual says that to check if JBoss is running, please open a browser and enter http://localhost:8082 which will list all jboss components running.

            Further how can I set up the application base, as I want to deploy some testings (or if I just place the files on "deploy" folder and then will work?)

            Thank you again.




            • 3. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
              andygallo.cti

              Yeah, what's the deal with this localhost:8082 anyway? I've tried on 3.0.4 and 3.2.0 with the embedded Tomcat and it doesn't work for either. Error is "Can't find server."

              - andy

              • 4. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
                andygallo.cti

                OK, I downloaded the latest version of the 3.0.x freebee doc (Quick Start Guide) and the reference to localhost:8082 is missing. Now it says to validate your installation, bang on localhost:8080/jmx-console.

                8082 has a reference on page 141 which says you can use 8082 for "non-permanent configuration changes". Yeah, OK, sure.

                FWIW, :8080/jmx-console works for me fine.

                - andy

                • 5. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
                  philiptsekh

                  Hi andy,

                  It also works for me. Thank you.

                  And then, I will explore further.

                  philip

                  • 6. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
                    jyothi

                    Hi,
                    I have started the jboss-3.2.0 with integrated tomcat, how do I test to check if tomcat is running. I tested "http://localhost:8080/jmx-console" it seems to be working fine.
                    Any suggestions would be helpful?

                    • 7. Re: jboss-3.2.0_tomcat-4.1.24 start up problem
                      andygallo.cti

                      I think there are a few different ways to verify Tomcat's up - one being to deploy the Tomcat Manager app to JBoss and bang that, or another to deploy a small WAR with a static HTML page to JBoss and then smack it....then again, I think hitting jmx-console is a good test too...

                      Smack freely.

                      - andy