Deployment of same Ear/Ejbs behaving differently in different machines.

Question

I have configured an ejb and introduced only local interface for the same. All the localhome, localinterface and ejb implementation classes are packaged inside myejbs.jar. This is placed inside myapp.ear .
//MyEjbLocal.java
public interface MyEjbLocal extends  EJBLocalObject {
    public void someMethod() throws MyRemoteException;
//MyRemoteException.java
public class MyRemoteException extends RemoteException{
}When try to deploy this under weblogic9.2, it fails with following exception,
weblogic.ejb.container.compliance.ComplianceException: In EJB MyLocalSession, method someMethod() defined in the local interface must not include java.rmi.RemoteException in its throws clause.
     at weblogic.ejb.container.compliance.EJBObjectClassChecker.checkMethodsThrowRemoteException(EJBObjectClassChecker.java:182)
Which is expected, since local interfaces should not throw RemoteExceptions, they should throw EjbException. ( as per specification ).
But the question here is, the same ear is being successfully deployed in some other machines. Dont knw how....
When I checked my server log I found out that, weblogic server is failing to deploy ejbs when it is trying to compile ejbs
*'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1247035767016> <BEA-010087> <The EJB deployment named: myejbs.jar is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a stand-alone tool to generate the required classes. The generated source files will be placed in /data/weblogic92/user_projects/domains/mydomain/servers/myserver/cache/EJBCompilerCache/12z5b5x2cmp3g.>*
But the same log is not present in other machines where it is deploying successfully.
Any idea on what could be the reason??? Why it is not working in my system??
All the machines are using same Weblogic version i.e. 9.2

Answer 1

Thanks Guys.
I have found the root cause of this issue i.e even though mapping program is same in 2 environments,standard functions(i.e concat Text function)  behaviour may change based on support package versions.
As i explained in previous posts
(QA mapping program not generating some of the node in IDOC as DEV does, basically its SOAP to IDOC mapping)
QA(PI7.0 SP15) and DEV(PI7.0 SP10) have different Java support package stacks, especially SAP_XITOOL component.
Untill PI7.0 SP10 concat standard function was working for Queue values but in next SP releases it wasn't working(SAP made it Value function i guess, no where its documented by SAP as far as i know).
So I am sending this issue to SAP.
Cheers,
Jag
Edited by: jag on Sep 18, 2008 11:24 AM
Edited by: jag on Sep 18, 2008 11:39 AM
Edited by: jag on Sep 18, 2008 11:42 AM