Client Locally transmitted context data is not received by EJB in JBoss EAP 6

Solution Verified - Updated -

Issue

  • We need to propagate a session key between Local and RMI calls.The client will be satisfied when the key can be propagated between two separate ears. We created a proof of concept using JBoss specific calls, but the key stored in the clientInterceptor is not available for the remoteInterceptor. https://community.jboss.org/message/757687 EAP 6.0.1 has a bug fixed which should allow the contextData to be passed: https://issues.jboss.org/browse/AS7-5021 Why is the contextData not available to the ejb?

  • Data from EJB client invocation context is not transferred to invoked remote EJB

  • When trying to transfer data from an EJB client to a remote EJB using an EJBClientInterceptor and the associated EJBClientInvocationContext, this data does not appear in the target EJB’s InvocationContext.

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6.0.1

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