Bug 1068738

Summary: inconsistent behaviour of a non clustered EJB application if a clustered application is deployed at the same server
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: wfink
Component: EJBAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED WONTFIX QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: high    
Version: 6.2.0CC: dereed, jason.greene, paul.ferraro, rhusar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-03 18:19:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wfink 2014-02-21 19:20:34 UTC 
If a not clustered EJB application is deployed and a client try to access it by defining only one server connection the expectation is that exact this server is used and, if this server failed, the EJB can not longer be invoked.

In case of a clustered server environment this will be the case as long as there is no clustered application and the cluster subsystem is not started.
But if there is a clustered application deployed at the same time the non clustered application change the behaviour to soemwhat clustered with LB and failover.

1)
  it is not expected that a non clustered application has some kind of LB and failover without any configuration at client side as it is intentional that there is only one server configured and the application is not clustered!
2)
  The behaviour of application / client should not effected by other deployed applications
3)
  The credentials are not passed to the servers which are added internaly if the configuration does not contain the "cluster" part

The same problem is visible if there is a mix of clustered and non clustered EJB's in one application archive
Comment 1 Jan Martiska 2014-07-02 13:08:30 UTC 
Proposing for EAP 6.4.
Comment 3 Jason T. Greene 2014-09-03 18:19:57 UTC 
This is just a side effect of the design. If you don't like this behavior you have three options:

1) Use distinct name
2) Don't deploy EJBs on servers you don't want clients to call
3) Write your own DeploymentNodeSelector, and use deployment.node.selector
Comment 4 dereed 2014-09-03 18:29:58 UTC 
> This is just a side effect of the design.

Then the design is broken and needs to be fixed.

If the behavior of one application changes simply because another unrelated application is deployed on the same server, that's a bug.
Comment 5 Jason T. Greene 2014-09-03 18:38:22 UTC 
The definition of a bug is behavior that is not intended.
Comment 6 JBoss JIRA Server 2014-09-03 18:41:58 UTC 
Jason Greene <jason.greene> updated the status of jira EJBCLIENT-102 to Closed
Comment 7 JBoss JIRA Server 2014-09-03 18:55:29 UTC 
Jason Greene <jason.greene> updated the status of jira EJBCLIENT-102 to Reopened
Comment 8 Jason T. Greene 2014-09-03 18:58:13 UTC 
Just to be clear though, we are planning on moving to a new invocation behavior pattern. We just can't really fix this in a 6.x release. The best that could be done is a workaround of some kind, but we are swamped and can't do everything.
Comment 10 Red Hat Bugzilla 2023-09-14 02:04:04 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days