jboss as 7.1.1 final stop or freezes when starting it under AIX
samyomar82 Sep 4, 2012 2:10 PMI am trying to run Jboss as under our production server but it stopped while starting.
OS: AIX 5.3
JDK: 6 (64 bit)
Jboss as: 7.1.1
attached the server.log and boot.log files it may help
steps I did :
1- I copied the unzipped folder for jboss as to its directory under AIX (I unzipped it under windows with winrar instead of using TAR command, as it trim long file names).
2- I tested the Java_home by typing on server consol, java -jar --> it show the correct installed java 6 (64 bit) path
$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460sr10fp1-20120321_01(SR10 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr10fp1-2012020
2_101568 (JIT enabled, AOT enabled)
J9VM - 20120202_101568
JIT - r9_20111107_21307ifx1
GC - 20120202_AA)
JCL - 20120320_01
3- then I executed the standalone.sh file
The consol printed this below, it stopped after printing "Bound data source [java:jboss/datasources/ExampleDS]"
and get freezed.
$ standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /app/chub/jboss-as-7.1.1.Final
JAVA: /usr/java6_64/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx
512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.w
arning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInter
val=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=tr
ue -Djboss.server.default.config=standalone.xml
========================================================================
17:03:32,701 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:03:33,966 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:03:34,315 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" sta
rting
17:03:39,089 INFO [org.xnio] XNIO Version 3.0.3.GA
17:03:39,152 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
17:03:39,193 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
17:03:39,239 INFO [org.jboss.as.server] JBAS015888: Creating http management se
rvice using socket-binding (management-http)
17:03:39,508 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin
Subsystem
17:03:39,539 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating I
nfinispan subsystem.
17:03:39,563 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
17:03:39,661 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices
Extension
17:03:39,799 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
17:03:39,823 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log han
dlers
17:03:40,168 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100:
Current PicketBox version=4.0.7.Final
17:03:40,481 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: St
arting Naming Service
17:03:41,848 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS01
5400: Bound mail session [java:jboss/mail/Default]
17:03:42,171 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC se
rvice thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
17:03:42,780 INFO [org.jboss.as.connector.subsystems.datasources] (ServerServic
e Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Dr
iver (version 1.3)
17:03:42,823 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
17:03:44,062 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100:
Listening on /127.0.0.1:9999
17:03:44,138 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread
1-3) JBAS015012: Started FileSystemDeploymentService for directory /app/chub/jbo
ss-as-7.1.1.Final/standalone/deployments
17:03:44,312 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Attached:
- server.log
- boot.log
- Thread stack dump file (created using kill -QUIT <pid> on another terminal)
As a result I cant shudown the app server propeply (as its not started correctly).
what can I do with this strange and very annoying issue ???
your help is highly ppretiated .............
Regards
Samy
-
server.log.zip 663 bytes
-
boot.log.zip 2.6 KB