Last night we solved the Remote Admin / JBoss conflict we had been experiencing.
The root of the problem was found to be the method used to start JBoss as a service. Prior to last night, we had used a 3rd party product called ServiceMill. Last night we switched to use the Run As Service tool that is provided by JBoss. That made the difference. Remote Admin is now able to be used on the server platform without interfering with JBoss. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920755#3920755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920755 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
