[Clustering/JBoss] - Shutting down a node causes shutdown on other cluster nodes
by giustrov
Hello,
we have a production environment with four jboss 4.2.2.GA nodes in cluster. All works fine, but when we perform shutdown on a node with "shutdown.sh -s jnp://" it happens that other nodes in the cluster immediately perform shutdown also, with this message in log:
2008-10-31 12:23:12,449 INFO [org.jboss.system.server.Server] Shutting down the server, blockingShutdown: false
| 2008-10-31 12:23:12,451 INFO [org.jboss.system.server.Server] Server exit(0) called
| 2008-10-31 12:23:12,475 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
| 2008-10-31 12:23:12,476 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
Jboss runs Liferay portal and Alfresco.
I've searched jboss.org JIRA for this topic, but found nothing. Any help would be very appreciated.
Giuseppe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185998#4185998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185998
17 years, 5 months
[Security & JAAS/JBoss] - @SecurityDomain, Principal resolution
by cro110011
hello
I have configured a security domain using the @SecurityDomain ("esvRealm") annotation on a bean; in the login-config.xml file I have added an app policy with the same name:
<application-policy name = "esvRealm">
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag = "required">
<module-option name="usersProperties">esv-users.properties</module-option>
<module-option name="rolesProperties">esv-roles.properties</module-option>
<module-option name="unauthenticatedIdentity">esv_anonymous</module-option>
<module-option name="restore-login-identity">true</module-option>
</login-module>
</application-policy>
when i make remote calls to the bean the principal cannot be extracted from the ejb context; the principal name is always set to esv_anonymous as defined in the policy (which shows me that the poicy somehow is recognized but cannot resolve the user ..); in the (standalone remote java) client I'm setting the following properties:
env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.jboss.security.jndi.JndiLoginInitialContextFactory" );
env.setProperty( Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory" );
env.setProperty( Context.PROVIDER_URL, "jnp://localhost:1099/" );
env.setProperty( Context.SECURITY_AUTHENTICATION, "simple" );
env.setProperty( Context.SECURITY_PRINCIPAL, user );
env.setProperty( Context.SECURITY_CREDENTIALS, password );
any help is appreciated :-)
regards, christian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185991#4185991
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185991
17 years, 5 months
[EJB 3.0] - Re: UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
by jaikiran
"nanda_kishore" wrote : to overcome this error i removed files. can u please give me solution for this problem.
I was (and am still) confused by your first post, in which the failures were because of missing DefaultDS and your post saying:
"nanda_kishore" wrote :
| i removed all %JBOSS_HOME%/server/< serverName>/deploy folder/messaging files and i removed hssql-ds.xml . now i left with this error UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **.
Based on your console logs, it looks like the only problem you are having is this:
anonymous wrote :
| 05:47:21,724 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deploymen
| ts (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
|
| jboss.j2ee:ear=iBlue.ear,jar=iBlue-ejb.jar,name=TemperatureFacade,service=EJB3
| -> {Described:** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| -> ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **
|
To summarize, on a clean JBoss if you place your EJB3 application in the deploy folder and start the server you see this exception. Is my understanding correct? If yes, then i think this was a bug which was fixed in the EJBTHREE project. If you use JBoss-5 CR2, the fix is available. The workaround for this issue was to remove the application from the deploy folder, start the server, wait for it to completely start without any errors and then place the application in the deploy folder to be hot deployed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185986#4185986
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185986
17 years, 5 months