No 'started' message (JBAS015874) on console or failure if EAP6 is stared with init script
Issue
-
there is no message on the console that the server has been started if I use ‘standalone-full-ha‘ profile. So a timeout message is shown if the server is started in
standalone-full-hamode by init-script -
jbossasstartup script provided with the RPM installer shows times out on startup/etc/init.d/jbossas start Starting jbossas: jbossas startup has timed out, process still running. -
when I use the
standalone-full-ha.xmlthe scriptjboss-as-standalone.shfails although JBoss starts successfully. I found that the scriptjboss-as-standalone.shis failing because of this part of the script:"grep 'JBAS015874:' $JBOSS_CONSOLE_LOG > /dev/null". I examined thestandalone*.xmlfiles and I found out the thestandalone-full-ha.xmlis missing the console handlers so the message JBAS015874 isn't logged to the console and the startup script fails.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
