File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes XFire WS showing HTTP status code 500 on JBoss 5 on SunOS 5.10 after remaining idle for few hours Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "XFire WS showing HTTP status code 500 on JBoss 5 on SunOS 5.10 after remaining idle for few hours" Watch "XFire WS showing HTTP status code 500 on JBoss 5 on SunOS 5.10 after remaining idle for few hours" New topic
Author

XFire WS showing HTTP status code 500 on JBoss 5 on SunOS 5.10 after remaining idle for few hours

Nikul Suthar
Greenhorn

Joined: Oct 25, 2012
Posts: 1

I've an XFire WS deployed on web container "JBoss 5.1.0.EAP" on virtual machine "SunOS iruxpds1z 5.10 Generic_142900-13 sun4v sparc SUNW,T5240". This WS gets deployed successfully, shows the WSDL page properly and functions correctly. But after it remains idle, meaning no requests send overnight or for 7-8 hours, it starts showing HTTP status code 500 for the WSDL page and throws following error log for a WS consumption call:


The same web service war does not show this issue if deployed on the same web container on virtual machine "Red Hat Enterprise Linux Server release 6.1 (Santiago)". Any help would be highly appreciated.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: XFire WS showing HTTP status code 500 on JBoss 5 on SunOS 5.10 after remaining idle for few hours