A StatefulSessionBean with 'passivationCapable=false' is not sticky on a cluster node

Solution Verified - Updated -

Issue

  • To disable state replication in a cluster for a StatefulSessionBean the documentation mentions:

    Starting JBoss EAP 7, if JBoss EAP is started using an HA profile, the state of your SFSBs will be replicated. You no longer need to use the @Clustered annotation to enable clustering behavior.

    Disabling this behavior is achievable on a per-EJB basis by annotating your bean using @Stateful(passivationCapable=false), which is new to the EJB 3.2 specification; or globally, via the ejb3 subsystem.

    But this is not the case. When invoking multiple methods on a StatefulSessionBean, different target nodes are being used.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.1
    • 7.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content