This content has been marked as final.
Show 6 replies
-
1. Re: application not responding after a day, server and probe
jaikiran Jul 31, 2009 3:55 AM (in response to magiccreative)Which exact version of JBossAS?
-
2. Re: application not responding after a day, server and probe
magiccreative Jul 31, 2009 9:05 AM (in response to magiccreative)thanks for the question, have forgoten to mention,
Jboss AS 4.2.2 -
3. Re: application not responding after a day, server and probe
alesj Jul 31, 2009 10:29 AM (in response to magiccreative)"magiccreative" wrote:
Jboss AS 4.2.2
So, why was this in JBoss*5* forum then?
Moved to BadPost forum. -
4. Re: application not responding after a day, server and probe
magiccreative Aug 3, 2009 2:52 AM (in response to magiccreative)because as much as I love Seam and other JBoss products, the forum is the worst organized forum I have ever seen. Where is the Jboss 4.2 forum Oo? How is search working and is it working at all?
-
5. Re: application not responding after a day, server and probe
jaikiran Aug 3, 2009 5:41 AM (in response to magiccreative)"magiccreative" wrote:
Where is the Jboss 4.2 forum Oo?
Except for AS-5, which had a major implementation change, there isn't a forum specific for each server version. You can post Installation, deployment and configuration issues in non-AS5 versions in the forum here http://www.jboss.org/index.html?module=bb&op=viewforum&f=61"magiccreative" wrote:
How is search working and is it working at all?
Completely down at this moment. I use google advanced search to search within this forum http://www.jboss.org/index.html?module=bb&op=viewtopic&t=52428#4246257 -
6. Re: application not responding after a day, server and probe wor
ajaykrishna85 Mar 25, 2010 7:17 AM (in response to magiccreative)We are facing the same issue with JBOSS EAP. The application was running fine for a day or two and later getting "Requested resource is not available for the initial jsp". From logs we can see that there are no errors while forwarding to jsp in the servlet. The issue was fixed when we restarted the server. Imagine restarting servers in production environment.