How do you start the server and when you see the message?
The performance is mostly related to the application and its requirements. The first point to check is the JVM GC behaviour which often cause issues. Check whether you use the same JVM version and settings and monitor/tune the GC.
So, the JBoss EAP is started as a service.
In most cases, the server is restarted (so that it stops and starts again)
service jboss restart
service jboss start
service jboss stop
where jboss is a file created under /etc/init.d
I thing noticed was that the stop command is not working.
Although, the command prompt states OK, there is no entry in the log to state that server has been stopped.
Also, on server startup, 2 issues are seen
1) Failure to start server as address is already is use (which is expected if jboss did not stop correctly before)
2) An error on the prompt which states Failed. However, as per server.log, there was no issue on startup
On using the command: systemctl -l status jboss.service
, below error message is seen that indicates that server did not startup on time allocated.
[root@ip-12-1-0-26 log]# systemctl -l status jboss.service
jboss.service - SYSV: JBoss AS Standalone
Loaded: loaded (/etc/rc.d/init.d/jboss)
Active: failed (Result: exit-code) since Tue 2014-07-01 20:39:20 EDT; 54s ago
Process: 2642 ExecStart=/etc/rc.d/init.d/jboss start (code=exited, status=7)
Jul 01 20:38:49 ip-12-1-0-26.ec2.internal systemd: Starting SYSV: JBoss AS Standalone...
Jul 01 20:38:49 ip-12-1-0-26.ec2.internal runuser: pam_unix(runuser:session): session opened for user jboss by (uid=0)
Jul 01 20:39:20 ip-12-1-0-26.ec2.internal jboss: Starting jboss-as: jboss-as failed to startup in the time allotted
Jul 01 20:39:20 ip-12-1-0-26.ec2.internal jboss: [FAILED]
Jul 01 20:39:20 ip-12-1-0-26.ec2.internal systemd: jboss.service: control process exited, code=exited status=7
Jul 01 20:39:20 ip-12-1-0-26.ec2.internal systemd: Failed to start SYSV: JBoss AS Standalone.
Jul 01 20:39:20 ip-12-1-0-26.ec2.internal systemd: Unit jboss.service entered failed state.
any luck with this? i am having the same problem...
This problem ive faced when i configure Jboss as Server in eclipse... How do you run your jboss from some IDE or Shell/Command Window ?
we both run it as a service
Realize this might be OBE but I got around this by editing the jboss-as.conf file and adding uncommenting/editing this line:
# The amount of time to wait for startup
After that I didn't get the error anymore. It's an imperfect solution as it seems to act like a 1 minute delay as opposed to an actual timeout but it's an acceptable workaround for me.
You might check the logfiles if there is a hint what need a long time, maybe initializing some resources took longer and you are able to improve here.