EJB 3.0 Remote Interface Not Bound

[kael20]

Hiya folks,

I have seen other people having a similar problem unfortunately either there were no solutions or their solutions were not working for me. The problem I am having is accessing my bean from another server using InitialContext lookup.

Now I have my initialContext set up correctly to point toward the correct jndi and then I have the code:

hello = (RemoteHello)ctx.lookup(Hello.class.getName());

RemoteHello is the remote interface for the bean.

I am getting this error trying to access that class:

hello = (RemoteHello)ctx.lookup(Hello.class.getName());

When I go into my jmx console and look at the global jndi namespace I see this for RemoteHello:

+- com.testing.hello.RemoteHello (proxy: $Proxy148 implements No ClassLoaders found for: com.testing.hello.RemoteHello (no security manager: RMI class loader disabled))

Being new to this, is that supposed to say implements no classloaders?

Any help would be greatly appreciated, thank you.

[amitguz]

I also encounter the same problem, any ideas?

[h2hjastermereel]

Same problem here, tried for days with no solution.

RH

[gavrilo]

I was fighting against the same problem, but finly I figure out the solution. The problem is connected with the classloading. To resolve it you have to change the paremeter UseJBossWebLoader in file JBOSS_HOME\server\default\deploy\jbossweb-tomcat55.sar\META-INF\jboss-service.xml to true:
true.
It is important to have the CallByValue parameter in JBOSS_HOME\server\default\conf\jboss-service.xml set to false.
false
In my case it solved the problem

I use JBoss 4.0.2.

[ci]

So far the same error appears, in 4.2.0.CR2 now :(

The solution offered here does not work.

I wonder whether nobody is interested in this subject.

Please help...

--
Serg

[jaikiran]

Provide more details about your application, the exception stacktrace that you are seeing and the code that you have for doing the lookup. Without these details, its not possible to point you to a solution.

[ci]

(answering to myself)

Using a default Security Manager helps.

In run.bat/run.sh:

set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager -Djava.security.policy="server.policy"

and default server.policy:

grant {
 // Allow everything for now
 permission java.security.AllPermission;
};

The working solution is taken from http://www.ubookcase.com/book/Sams/JBoss.4.0.The.Official.Guide/0672326485/ch08lev1sec6.html

--
Serg