[
https://issues.jboss.org/browse/AS7-4016?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4016:
-----------------------------------
{quote}
In multinode part of testsuite does not work binding of local initial context on client
server. It seems that it's returned remote context (of the second server) everytime.
As well in case that lookup is made from injected InitialContext.
@Resource InitialContext ctx;
{quote}
Sorry, but I didn't understand that part. Can you explain a bit more?
Btw, we have users successfully invoking on remote server instances (from within another
server or even standalone client), so I believe this is just a configuration issue.
EJB invocations from a remote server instance does not work properly
--------------------------------------------------------------------
Key: AS7-4016
URL:
https://issues.jboss.org/browse/AS7-4016
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: Ondřej Chaloupka
Assignee: jaikiran pai
Labels: jndi
It seems that the EJB invocations from a remote server instance does not work.
In multinode part of testsuite does not work binding of local initial context on client
server. It seems that it's returned remote context (of the second server) everytime.
As well in case that lookup is made from injected InitialContext.
{code}
@Resource InitialContext ctx;
{code}
The mentioned test could be found here:
https://github.com/ochaloup/jboss-as/commit/a5a5405894080dc01925a7d47640a...
The second problem occurs on deploying app on "standalone" server (out of the
testsuite). It seems that server does not see any other server and it binds local context
instead of remote one. E.g. When I ran only one server and deployed application with
jboss-ejb-client.xml pointing to outbound-connection it does not throw an exception that
the outbound-connection can't be caught but it throw exception:
{code}
javax.ejb.EJBException: java.lang.RuntimeException: java.lang.IllegalStateException: No
EJB receiver available for handling [appName:,modulename:myejb,distinctname:] combination
{code}
which means that it found an context but didn't find a receiver. In fact it was found
context of the running (local) server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira