3 Replies Latest reply on May 19, 2008 11:14 AM by Peter Johnson

    Not able to access https://localhost:8009 or http://localhos

    Kapil Sharma Newbie

      hi Guys

      I am not new to JBoss but yes it is the first time for me to configure it with eclipse in Window Vista home premium and the link which I have used to configure it is: http://ist.berkeley.edu/as-ag/tools/howto/jboss-eclipse.html . I have the beta 4 release for JBOSS and I already configured this with the latest version of eclipse available and in the program argument I have given

      -c default -b 127.0.0.1

      and in the vmargument I have given the following:
      -Dprogram.name=run.bat -Djava.endorsed.dirs=C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/bin/../lib/endorsed -Xms128m -Xmx512m -XX:MaxPermSize=256m

      and the my working directory is
      C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/bin

      but when I try to run the jboss server by right clicking this. I got the following logs in the eclipse console:

      21:34:21,269 INFO [ServerImpl] Starting JBoss (Microcontainer)...
      21:34:21,269 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)
      21:34:21,269 INFO [ServerImpl] Home Dir: C:\Users\user_name\Dev_Environment\jboss_home\jboss_5Beta4
      21:34:21,269 INFO [ServerImpl] Home URL: file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/
      21:34:21,269 INFO [ServerImpl] Library URL: file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/lib/
      21:34:21,269 INFO [ServerImpl] Patch URL: null
      21:34:21,269 INFO [ServerImpl] Server Name: default
      21:34:21,269 INFO [ServerImpl] Server Home Dir: C:\Users\user_name\Dev_Environment\jboss_home\jboss_5Beta4\server\default
      21:34:21,269 INFO [ServerImpl] Server Home URL: file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/
      21:34:21,269 INFO [ServerImpl] Server Data Dir: C:\Users\user_name\Dev_Environment\jboss_home\jboss_5Beta4\server\default\data
      21:34:21,269 INFO [ServerImpl] Server Temp Dir: C:\Users\user_name\Dev_Environment\jboss_home\jboss_5Beta4\server\default\tmp
      21:34:21,269 INFO [ServerImpl] Server Config URL: file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/conf/
      21:34:21,269 INFO [ServerImpl] Server Library URL: file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/lib/
      21:34:21,269 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
      21:34:21,472 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/conf/bootstrap-beans.xml
      21:34:21,909 INFO [ProfileImpl] Using profile root:C:\Users\user_name\Dev_Environment\jboss_home\jboss_5Beta4\server\default
      21:34:22,158 INFO [ServerInfo] Java version: 1.6.0-oem,Sun Microsystems Inc.
      21:34:22,158 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-oem-b104,Sun Microsystems Inc.
      21:34:22,158 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86
      21:34:22,159 INFO [JMXKernel] Legacy JMX core initialized
      21:34:23,595 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      21:34:24,001 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      21:34:24,001 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      21:34:24,188 INFO [TransactionManagerService] Starting recovery manager
      21:34:24,282 INFO [TransactionManagerService] Recovery manager started
      21:34:24,282 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      21:34:34,484 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@830624 for BaseClassLoader@1893c7{vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/ejb3-interceptors-aop.xml}
      21:34:35,390 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
      21:34:35,390 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
      21:34:35,437 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      21:34:35,671 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      21:34:35,703 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      21:34:35,703 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
      21:34:35,719 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
      21:34:35,719 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
      21:34:35,719 INFO [JobStoreCMT] JobStoreCMT initialized.
      21:34:35,719 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
      21:34:35,719 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      21:34:35,719 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
      21:34:35,719 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
      21:34:35,719 INFO [JobStoreCMT] Recovery complete.
      21:34:35,719 INFO [JobStoreCMT] Removed 0 'complete' triggers.
      21:34:35,719 INFO [JobStoreCMT] Removed 0 stale fired job entries.
      21:34:35,734 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
      21:34:37,170 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jre1.6.0\bin\client;C:\Program Files\Java\jre1.6.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\
      21:34:37,342 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
      21:34:37,342 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
      21:34:37,342 INFO [Catalina] Initialization processed in 686 ms
      21:34:37,342 INFO [StandardService] Starting service jboss.web
      21:34:37,358 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.0.CR12
      21:34:37,451 INFO [Catalina] Server startup in 111 ms
      21:34:37,483 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
      21:34:39,401 INFO [NativeServerConfig] JBoss Web Services - Native
      21:34:39,401 INFO [NativeServerConfig] jbossws-native-2.0.3.GA (build=200801241020)
      21:34:40,541 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-context.war
      21:34:40,620 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/jms-ra.rar/META-INF/ra.xml
      21:34:40,667 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
      21:34:41,899 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
      21:34:41,947 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/mail-ra.rar/META-INF/ra.xml
      21:34:42,072 INFO [MailService] Mail Service bound to java:/Mail
      21:34:42,337 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
      21:34:43,476 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
      21:34:43,742 INFO [ServerPeer] JBoss Messaging 1.4.1.Beta1 server [0] started
      21:34:43,805 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      21:34:43,805 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
      21:34:43,805 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
      21:34:43,883 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      21:34:43,883 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1573137 started
      21:34:43,883 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      21:34:43,883 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1e8f789 started
      21:34:43,883 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      21:34:43,883 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@6dbdc1 started
      21:34:43,883 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      21:34:43,898 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      21:34:43,914 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Users/user_name/Dev_Environment/jboss_home/jboss_5Beta4/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
      21:34:43,945 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      21:34:43,945 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      21:34:43,945 INFO [RAMJobStore] RAMJobStore initialized.
      21:34:43,945 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      21:34:43,945 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      21:34:43,945 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      21:34:43,961 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
      21:34:44,226 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      21:34:44,366 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      21:34:44,366 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)] Started in 23s:97ms
      21:37:29,211 ERROR [AjpMessage] Invalid message recieved with signature 5635
      21:37:58,166 ERROR [AjpMessage] Invalid message recieved with signature 32829
      21:41:10,274 ERROR [AjpMessage] Invalid message recieved with signature 5635


      but I cannot access localhost:8080 and 8009. Please help me on that.

      I would really appreciate this help.


      cool_coder

        • 1. Re: Not able to access https://localhost:8009 or http://loca
          Peter Johnson Master

          According to this line:

          21:34:44,226 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080

          port 8080 is open so you should be able to open a browser on the same machine, enter http://localhost:8080 into the address bar, and see the home page.

          Note that 8080 is not the https port, and 8009 is not the http port!

          • 2. Re: Not able to access https://localhost:8009 or http://loca
            Kapil Sharma Newbie

            Thanks Man

            I was struggling on it and you got it. The trick is I should use http:localhost:8080 instead of https://localhost:8080.

            But these lines still bothering my mind:


            19:06:14,410 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jre1.6.0\bin\client;C:\Program Files\Java\jre1.6.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\

            19:06:22,857 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

            19:06:23,458 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
            19:06:23,458 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing

            I know if I would read the documentation I would know what the exact problem is but little bit help would be really helpful.

            Thanks in advance.

            • 3. Re: Not able to access https://localhost:8009 or http://loca
              Peter Johnson Master

              The AprLifecycleListner message is expected. It just means that it could not find the platform-specific APR dlls, and thus will run pure Java. If you want the APR dlls, you can download them from http://www.jboss.org/jbossweb/downloads/jboss-native/?action=a&windowstate=maximized.

              The SecurityMetadataStore indicates that you have not secured a part of messaging. As the text states, the docs will tell you how to fix this.

              The other two indicate that there is a conflict (whether to be clustered or not) between messaging attributes and that you are running non-clustered.

              Bottom line - non of these warnings indicates a problem that would prevent anything from running.