문제

We use JacORB 2.3.0 with Java 6 and JBoss 5.1.0 in a legacy project. The CORBA infrastructure and the old versions of the ORB, Java and JBoss are given and not a subject of change.

After a migration project (the application was originally deployed in separate J2EE application servers, but is now migrated to one application within the JBoss using partially Java EE 5 and one standalone Java application) we now have the situation that a CORBA request from within the JBoss leads to an org.omg.CORBA.OBJECT_NOT_EXIST exception.

I verified the situation by writing a small test class doing the call in question and letting it run once from outside the JBoss via a standalone Java program and once from inside within an MBean via JBoss' JMX console. In the first case, everything works fine, in the second case I get the error.

I already stepped into some generated code and ORB code and found out that when the stub distinguishes between local and remote call, it finds a POA and goes for the local call, despite the fact that the opposite part of that request is in a separate JVM process.

Any ideas what could cause that and where I should take a deeper look or maybe able to configure something? Even a workaround would be fine (like avoiding the local call), since those calls are not critical performance wise.

도움이 되었습니까?

해결책

It turned out, that there was a CORBA service registered locally, but no implementation for it available. So it was a problem of assembling the correct deploy artifact.

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top