1 Reply Latest reply on Nov 2, 2011 10:51 AM by peterj

Not Starting JBoss EAP 4.3

msurenderforu Nov 2, 2011 8:11 AM

Hi,

I am trying to Jboss EAP 4.3 server on multiple ports on one machine.

For this configuration I followed Jboss url http://community.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine

I followed/have done exactly as above url but not starting Jboss eap on two different ports. I followed as below

1) I copied .../server/default all folders to .../server/node1

2) from node1 I edited jboss-eap-4.3\jboss-as\server\node1\conf\jboss-service.xml and uncommented "Service Bindings" section

3) I ran default as "run_orisinal.bat -c default -b 131.107.0.83 220.227.247.124 -DBT_II_HOME=D:\BT_HOME_DIR" which is started fine but

4) Then I ran node1 as "run_orisinal.bat -c node1 -b 131.107.0.83 220.227.247.124 -DDAX_II_HOME=D:\DAX_HOME_DIR" whixh is not started properly, gave below Exception/Stacktrace.

D:\jboss-eap-4.3\jboss-as\bin>run_orisinal.bat -c node1 -b 131.107.0.83 220.227.247.124 -DBT_II_HOME=D:\BT_HOME_DIR

===============================================================================

JBoss Bootstrap Environment

JBOSS_HOME: D:\jboss-eap-4.3\jboss-as

JAVA: C:\Program Files\Java\jdk1.5.0_07\bin\java

JAVA_OPTS: -Xms512M -Xmx1024M -XX:MaxPermSize=256M -Dprogram.name=run_orisinal.bat -server -DBT_HOME_DIR=D:\BT_HOME_DIR -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

CLASSPATH: C:\Program Files\Java\jdk1.5.0_07\lib\tools.jar;D:\jboss-eap-4.3\jboss-as\bin\run.jar

===============================================================================

run_orisinal.bat: unused non-option argument: 220.227.247.124

16:58:26,734 INFO [Server] Starting JBoss (MX MicroKernel)...

16:58:26,734 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP04 (build: SVNTag=JBPAPP_4_3_0_GA_CP04 date=200902200048)

16:58:26,734 INFO [Server] Home Dir: D:\jboss-eap-4.3\jboss-as

16:58:26,734 INFO [Server] Home URL: file:/D:/jboss-eap-4.3/jboss-as/

16:58:26,734 INFO [Server] Patch URL: null

16:58:26,734 INFO [Server] Server Name: node1

16:58:26,734 INFO [Server] Server Home Dir: D:\jboss-eap-4.3\jboss-as\server\node1

16:58:26,734 INFO [Server] Server Home URL: file:/D:/jboss-eap-4.3/jboss-as/server/node1/

16:58:26,734 INFO [Server] Server Log Dir: D:\jboss-eap-4.3\jboss-as\server\node1\log

16:58:26,734 INFO [Server] Server Temp Dir: D:\jboss-eap-4.3\jboss-as\server\node1\tmp

16:58:26,734 INFO [Server] Root Deployment Filename: jboss-service.xml

16:58:27,140 INFO [ServerInfo] Java version: 1.5.0_07,Sun Microsystems Inc.

16:58:27,140 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_07-b03,Sun Microsystems Inc.

16:58:27,140 INFO [ServerInfo] OS-System: Windows XP 5.1,x86

16:58:28,968 INFO [Server] Core system initialized

17:00:08,218 INFO [ServiceBindingManager] Initializing store

17:00:08,218 INFO [ServiceBindingManager] Using StoreURL: file:/D:/jboss-eap-4.3/jboss-as/docs/examples/binding-manager/sample-bindings.xml

17:00:08,968 INFO [WebService] Using RMI server codebase: http://131.107.0.83:8183/

17:00:08,968 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml

log4j:WARN Continuable parsing error 378 and column 23

log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,appender*,(category|logger)*,root?,categoryFactory?)".

log4j:WARN No such property [target] in org.jboss.logging.appender.DailyRollingFileAppender.

17:00:09,843 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.

17:00:09,843 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer

17:00:10,062 INFO [TransactionManagerService] Starting recovery manager

17:00:10,203 INFO [TransactionManagerService] Recovery manager started

17:00:10,203 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

17:00:43,312 INFO [EJB3Deployer] Starting java:comp multiplexer

17:02:21,062 INFO [NativeServerConfig] JBoss Web Services - Native

17:02:21,062 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2_CP05 (build=200902200020)

17:02:42,593 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\jdk1.5.0_07\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jdk1.5.0_07\bin;C:\Program Files\Common Files\NetSarang;C:\apache

17:02:42,671 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-131.107.0.83-8180

17:02:42,687 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-131.107.0.83-8109

17:02:42,687 INFO [Catalina] Initialization processed in 302 ms

17:02:42,687 INFO [StandardService] Starting service jboss.web

17:02:42,687 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA_CP

17:02:42,734 INFO [Catalina] Server startup in 50 ms

17:02:42,890 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/

17:02:43,968 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/

17:02:44,812 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../tmp/deploy/tmp56191juddi-exp.war/

17:02:44,921 INFO [RegistryServlet] Loading jUDDI configuration.

17:02:44,921 WARN [RegistryServlet] Could not locate jUDDI properties '/WEB-INF/juddi.properties'. Using defaults.

17:02:44,921 INFO [RegistryServlet] Initializing jUDDI components.

17:02:45,171 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/

17:02:45,859 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/

17:02:46,500 INFO [MailService] Mail Service bound to java:/Mail

17:02:46,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar

17:02:46,968 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar

17:02:47,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar

17:02:47,156 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=juddiDB' to JNDI name 'java:juddiDB'

17:02:47,156 INFO [JuddiRMIService] starting juddi RMI service

17:02:48,125 INFO [SoapUI] initialized soapui-settings from [D:\jboss-eap-4.3\jboss-as\server\node1\data\soapui-settings.xml]

17:02:48,281 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar

17:02:48,828 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms-ra.rar

17:02:48,968 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar

17:02:49,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar

17:02:49,109 INFO [QuartzResourceAdapter] start quartz!!!

17:02:49,187 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main

17:02:49,218 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

17:02:49,218 INFO [RAMJobStore] RAMJobStore initialized.

17:02:49,218 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

17:02:49,218 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2

17:02:49,218 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

17:02:49,578 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

17:02:50,359 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.

17:02:50,421 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP07 server [0] started

17:02:50,859 INFO [ConnectionFactory] Connector bisocket://131.107.0.83:4557 has leasing enabled, lease period 10000 milliseconds

17:02:50,859 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@6d98 started

17:02:50,859 INFO [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

17:02:50,859 INFO [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

17:02:50,859 INFO [ConnectionFactory] Connector bisocket://131.107.0.83:4557 has leasing enabled, lease period 10000 milliseconds

17:02:50,859 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1fe256b started

17:02:50,859 INFO [ConnectionFactory] Connector bisocket://131.107.0.83:4557 has leasing enabled, lease period 10000 milliseconds

17:02:50,859 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@739136 started

17:02:50,968 ERROR [ExceptionUtil] Queue[/queue/DLQ] startService

javax.jms.InvalidDestinationException: Destination DLQ already exists

at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(DestinationJNDIMapper.java:122)

at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:150)

at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)

at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)

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:264)

at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)

at $Proxy0.start(Unknown Source)

at org.jboss.system.ServiceController.start(ServiceController.java:417)

at org.jboss.system.ServiceController.start(ServiceController.java:435)

at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)

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:264)

at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)

at $Proxy4.start(Unknown Source)

at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)