Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6428

EJB2 InvokerInterceptor isLocal returns true when it should return false

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.2 ER1
    • EAP 5.0.1
    • Clustering
    • None
    • Release Notes
    • Hide
      When the same EJB is deployed to two different clusters, the InvokerInterceptor calls the local EJB instead of the EJB on cluster 2, even though the InitialContext is pointed to the JNDI of a server in cluster 2. This problem is not yet resolved but to work around the issue, set the following configuration item either via the JAVA_OPTS environment variable or in $JBOSS_HOME/bin/run.conf:

      <screen>-Dorg.jboss.invocation.use.partition.name=true</screen>
      Show
      When the same EJB is deployed to two different clusters, the InvokerInterceptor calls the local EJB instead of the EJB on cluster 2, even though the InitialContext is pointed to the JNDI of a server in cluster 2. This problem is not yet resolved but to work around the issue, set the following configuration item either via the JAVA_OPTS environment variable or in $JBOSS_HOME/bin/run.conf: <screen>-Dorg.jboss.invocation.use.partition.name=true</screen>
    • Documented as Known Issue
    • NEW

    Description

      When the same ejb is deployed in two different clusters, the InvokerInterceptor is calling localhost ejb instead of the ejb in cluster 2 even though the InitialContext is pointed to the JNDI of a server in cluster 2.

      Attachments

        Activity

          People

            rhn-support-bmaxwell Brad Maxwell
            rhn-support-bmaxwell Brad Maxwell
            Russell Dickenson Russell Dickenson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: