[jboss-jira] [JBoss JIRA] Commented: (JBAS-7096) SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup

[Scott Marlow (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556895#action_12556895 ] 

Scott Marlow commented on JBAS-7096:
------------------------------------

For another clue, look in the logs for value "add, key=". 

I see hits for "FarmProfileRepositoryClusteringHandler" and "HAModClusterService".

More worrisome, I don't see hits for "HASingletonDeployer", which probably explains why we hit the "no replicants" case that returns true on both nodes.

Interesting...

> SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7096
>                 URL: https://jira.jboss.org/browse/JBAS-7096
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-5.1.0.GA
>         Environment: RHEL 4 Update 7 (and OSX 10.5.7), Sun JRE 1.6.0_12, JBoss 5.1.0 - "all" configuration
>            Reporter: Richard Taylor
>            Assignee: Scott Marlow
>            Priority: Minor
>             Fix For: TBD
>
>
> Basic cluster, two JBoss 5.1.0 nodes, "all" configuration.   First node starts fine.  Second node starts, however at the end of starting, any SLSBs that depend on the barrier result in an error being logged at startup (on the second node). 
> Example:
> DEPLOYMENTS MISSING DEPENDENCIES:
>   Deployment "jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3" is missing the following dependencies:
>     Dependency "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" (should be in state "Described", bu
> t is actually in state "** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **")
> DEPLOYMENTS IN ERROR:
>   Deployment "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" is in error due to the following reas
> on(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **
> The SLSBs on node 2 do properly start in a failover scenario when node 1 goes down.  So functionally things seem OK.  However the error message is a little concerning and it leaves us wondering if there is more to the problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira