Calling EJB in cluster jndi:1100 from action

[wlabuschagne]

When I try and call a EJB3 that runs in the cluster and I specify the jndi port as 1100 (HA) I get the following error. Should I open a JIRA for this or is this my own stupidity. I works if I only use the local jndi port 1099.

23:04:19,312 ERROR [STDERR] java.lang.ClassCastException: $Proxy180
23:04:19,312 ERROR [STDERR] at santam.esb.itc.ITCCallAction.getIDSScore(ITCCallAction.java:123)
23:04:19,312 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
23:04:19,312 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
23:04:19,312 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
23:04:19,312 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
23:04:19,312 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
23:04:19,312 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
23:04:19,312 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
23:04:19,312 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
23:04:19,312 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
23:04:19,312 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
23:04:19,312 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)

The properties that I use for the lookup is
Properties properties = new Properties();
properties.put("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
properties.put("java.naming.factory.url.pkgs","org.jboss.naming:org.jnp.interfaces");
properties.put("java.naming.provider.url", "jnp://127.0.0.1:1100");
properties.put("jnp.disableDiscovery", "true");

Thanks
Willem

[beve]

Hi,

are you able to invoke the EJB with a standalone client using those same jndi settings?

Regards,

/Daniel

[wlabuschagne]

Hi Yes. When I change it to 1099 then it works to.

Cheers
Willem

[beve]

Sorry, I meant are you able to use "jnp://127.0.0.1:1100" as the provider url when running from a standalone client. Do you get the same error?

Regards,

/Daniel

[wlabuschagne]

Sorry, I don't get a error. It works fine remotely with 1099 or 1100.
Its only when I use it within a action deployed as .esb archive that it does not work with port 1100. If I use port 1099 inside my esb archive it works.

Thanks
Willem

[beve]

Thanks.

Are you sharing classes/interfaces between the ejb client and the ejb. Passed in as arguments or as return values?

Regards,

/Daniel

[wlabuschagne]

I have isolation on the ejb. So I created a client.jar that I use in my esb archive. I have also created a loader for the esb with isolation.

The esb does have the right client jars avail.
The only jars that was included with the esb archive was the client.jar.

Hope this help.

[beve]

I would guess that this is a classloading issue but it's difficult to say for sure without actually seeing code and your packaged ejb and .esb archives.

There is an example of calling an EJB3 using the ejbprocessor. This can be found in this following branch:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/ejbprocessor/
I've tried this with jboss-4.2.2.GA and using the "all" configuration.

Regards,

/Daniel