Description of problem: I checked functionality of ejb-multi-server quickstart example and tried to go to URL http://localhost:8380/appweb/. It is unavailable : responce code is 404 - JBWEB000069: description JBWEB000124: The requested resource is not available. After server reload I can see in log also: 11:54:03,900 INFO [org.jboss.as.process.Server:app-web.status] (reaper for Server:app-web) JBAS012010: Process 'Server:app-web' finished with an exit status of 1 [Host Controller] 11:54:03,906 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server app-web Version-Release number of selected component (if applicable): EAP 6.2.0 ER5.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Did you see the Note in that section? NOTE : A new feature in EAP 6.1 or later will deny the invocation of unsecured methods of appOne/appTwo since security is enabled but the method does not include @Roles. You need to set ‘default-missing-method-permissions-deny-access = false’ for the ejb3 subsystem within the domain profile “ha” and “default” to allow the method invocation. See the install-domain.cli script. Did you follow those instructions? I am tempted to remove that entire section. I'm not sure it shows anything since it does not work by default anad you have to jump through hoops for it to work.
I didn't follow that, but as I can see, these changes were made in domain.xml configuration, so it should work. It's better to remove this entire section, if it doesn't work.
Adding Wolf so he can comment.
I finally got a chance to test this and it doesn't work for me either. I sent an email to Wolf to ask if he wants to debug this or if we should just remove the section.
As the deployment names are changed a WEB-INF/jboss-web.xml is necesarry to set the correct context-root. PR send https://github.com/jboss-developer/jboss-eap-quickstarts/pull/685
I closed the above pull because we don't want to hard-code the context-root. We wnat to use the name generated by the build using the variable: ${project.artifactId} I did the following: * Removed the hard-code context root from app-main/ear/pom.xml * Udated the access URLs in the README to use the generated contexts * Moved the section on adding users. It was in the middle of the section on configuring the server and it was confusing. I moved that section prior to the server configuration. Fixes are in this pull: https://github.com/jboss-developer/jboss-eap-quickstarts/pull/686
Fixed with this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/88ca906a911049ba91ca3817b4486f7d3420b117
Verified on EAP 6.2 ER7