Darryl Baker wrote:
Now I'd like to fix some other message the first is this series:
[ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:43,566 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
16:14:43,676 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:43,770 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp3718574988013474295jbossws-context-exp.war/
16:14:43,879 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:44,035 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
16:14:44,113 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
16:14:45,145 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
16:14:45,363 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
Which I think should be fixable by defining a security role in server/myserver/deploy/jbossweb-tomcat55.sar/conf/web.xml but I don't understand how to do that well enough. I'm also not sure how to debug my attempts.
Looks like someone has changed the web.xml files of web-console, jbossmq-httpil.war, ROOT.war and others. What does one of those web.xml look like? You'll have to do the changes to each of those web.xml to fix the WARN message.
Darryl Baker wrote:
The next error message is:
[STDERR] The developer file [null] does not exist and will not be used.
Obviously we are not using a developer file but what is it? What are the possible values? Where should it be set? Since we are not using it how do I set it to a value that does not break the applications yet has the eqivalent effect as now but without an error message.
This doesn't look like being logged by JBoss AS. It appears to be logged from the application deployed on that server. Do you see this error message on a clean installation, without any of your applications?