3 Replies Latest reply on May 7, 2007 6:23 AM by visolvejboss

    jboss-4.2.0.CR2 +  1.5.0_07 + Mac OS X 10.4.9,ppc problem

    thorgal

      Hi all,

      I test a migration from jboss 4.0.5 with jboss-4.2.0CR2.
      All works fine with 4.0.5 on port 8100
      I launch 4.2.0CR2, all seems ok but when i connect with my browser on port 8100, nothing happens (The connection has timed out)

      Any idea ?

      Thanks in advance.

      Here is my log file and no error message

      10:29:05,286 INFO [Server] Starting JBoss (MX MicroKernel)...
      10:29:05,288 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR2 (build: SVNTag=JBoss_4_2_0_CR2 date=200704160918)
      10:29:05,299 INFO [Server] Home Dir: /usr/local/jboss-4.2.0.CR2
      10:29:05,300 INFO [Server] Home URL: file:/usr/local/jboss-4.2.0.CR2/
      10:29:05,301 INFO [Server] Patch URL: null
      10:29:05,301 INFO [Server] Server Name: default
      10:29:05,301 INFO [Server] Server Home Dir: /usr/local/jboss-4.2.0.CR2/server/default
      10:29:05,302 INFO [Server] Server Home URL: file:/usr/local/jboss-4.2.0.CR2/server/default/
      10:29:05,302 INFO [Server] Server Log Dir: /usr/local/jboss-4.2.0.CR2/server/default/log
      10:29:05,303 INFO [Server] Server Temp Dir: /usr/local/jboss-4.2.0.CR2/server/default/tmp
      10:29:05,303 INFO [Server] Root Deployment Filename: jboss-service.xml
      10:29:05,972 INFO [ServerInfo] Java version: 1.5.0_07,Apple Computer, Inc.
      10:29:05,972 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_07-87,"Apple Computer, Inc."
      10:29:05,973 INFO [ServerInfo] OS-System: Mac OS X 10.4.9,ppc
      10:29:07,061 INFO [Server] Core system initialized
      10:29:11,231 INFO [WebService] Using RMI server codebase: http://localhost:8083/
      10:29:11,237 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      10:29:12,371 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      10:29:12,371 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      10:29:12,690 INFO [TransactionManagerService] Starting recovery manager
      10:29:12,884 INFO [TransactionManagerService] Recovery manager started
      10:29:12,885 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      10:29:17,824 INFO [EJB3Deployer] Starting java:comp multiplexer
      10:29:21,079 INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756)
      10:29:23,593 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
      10:29:23,789 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8100
      10:29:23,790 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
      10:29:23,791 INFO [Catalina] Initialization processed in 502 ms
      10:29:23,791 INFO [StandardService] Starting service jboss.web
      10:29:23,795 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.CR1
      10:29:23,911 INFO [Catalina] Server startup in 120 ms
      10:29:24,157 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
      10:29:25,363 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
      10:29:25,824 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp10244jbossws-context-exp.war/
      10:29:26,124 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
      10:29:27,592 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
      10:29:28,652 INFO [MailService] Mail Service bound to java:/Mail
      10:29:28,890 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
      10:29:28,941 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
      10:29:28,980 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
      10:29:29,024 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
      10:29:29,163 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
      10:29:29,202 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
      10:29:29,251 INFO [QuartzResourceAdapter] start quartz!!!
      10:29:29,836 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      10:29:29,878 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      10:29:29,882 INFO [RAMJobStore] RAMJobStore initialized.
      10:29:29,883 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      10:29:29,884 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      10:29:29,885 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      10:29:31,921 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      10:29:32,370 INFO [A] Bound to JNDI name: queue/A
      10:29:32,374 INFO [B] Bound to JNDI name: queue/B
      10:29:32,377 INFO [C] Bound to JNDI name: queue/C
      10:29:32,380 INFO [D] Bound to JNDI name: queue/D
      10:29:32,383 INFO [ex] Bound to JNDI name: queue/ex
      10:29:32,416 INFO [testTopic] Bound to JNDI name: topic/testTopic
      10:29:32,419 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      10:29:32,423 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
      10:29:32,429 INFO [testQueue] Bound to JNDI name: queue/testQueue
      10:29:32,507 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
      10:29:32,565 INFO [DLQ] Bound to JNDI name: queue/DLQ
      10:29:32,787 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      10:29:32,866 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      10:29:33,282 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8100
      10:29:33,309 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      10:29:33,329 INFO [Server] JBoss (MX MicroKernel) [4.2.0.CR2 (build: SVNTag=JBoss_4_2_0_CR2 date=200704160918)] Started in 28s:21ms

        • 1. Re: jboss-4.2.0.CR2 +  1.5.0_07 + Mac OS X 10.4.9,ppc proble
          visolvejboss

          Hello,

          I'm not sure from which machine (local or external), your accessing the jboss jmx console through browser. If i'm rite, your accessing from the external machine.

          Have a look at the following section of log.

          10:29:23,593 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
          10:29:23,789 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8100
          10:29:23,790 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
          10:29:23,791 INFO [Catalina] Initialization processed in 502 ms


          The http port (8100) has been bind to local address. Try running jboss by specifying the ip address to bind.



          • 2. Re: jboss-4.2.0.CR2 +  1.5.0_07 + Mac OS X 10.4.9,ppc proble
            thorgal

            ok, thx !

            I've removed address="${jboss.bind.address}" in server.xml

            • 3. Re: jboss-4.2.0.CR2 +  1.5.0_07 + Mac OS X 10.4.9,ppc proble
              visolvejboss

              Hello,

              Try run the jboss with the following command

              ./run.sh -b <ip-address>


              where ip-address can be specified as an ip-address which can be accessible from outside. Other than that, no change is required, even you can revert the change you have done.