With Friday's changes, JBoss hangs, with the last messages on the console shown
below.
If you've committed stuff on Friday, please take a closer look:
18:13:06,359 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.Secu
reDeploymentManager ejbName: SecureDeploymentManager
18:13:06,453 INFO [JndiSessionRegistrarBase] Binding the following Entries in G
lobal JNDI:
SecureDeploymentManager/remote - EJB3.x Default Remote Business Interfac
e
SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy
.DeploymentManager - EJB3.x Remote Business Interface
18:13:06,515 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice
-secured.jar,name=SecureManagementView,service=EJB3
18:13:06,515 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.Secu
reManagementView ejbName: SecureManagementView
18:13:06,531 INFO [JndiSessionRegistrarBase] Binding the following Entries in G
lobal JNDI:
SecureManagementView/remote - EJB3.x Default Remote Business Interface
SecureManagementView/remote-org.jboss.deployers.spi.management.Managemen
tView - EJB3.x Remote Business Interface
18:13:06,625 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice
-secured.jar,name=SecureProfileService,service=EJB3
18:13:06,625 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.Secu
reProfileServiceBean ejbName: SecureProfileService
18:13:06,625 INFO [JndiSessionRegistrarBase] Binding the following Entries in G
lobal JNDI:
SecureProfileService/remote - EJB3.x Default Remote Business Interface
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
- EJB3.x Remote Business Interface
18:13:06,859 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
18:13:06,875 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009