This is actually something which is a rather major issue (IMO). The good news is that you can fix it by changing a configuration file (details follow). The bad news is that JBoss seems to be suffering from the same issues that have plagued IIS for years -- a default configuration that does not seem too concerned with security.
In your deploy directory, you should have a file called "security-service.xml" -- open it and find the following line: 1800 change it to: 0 Save and restart JBoss. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910052#3910052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910052 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
