You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Brian Shields <bg...@yahoo.com> on 2003/04/14 18:55:23 UTC
EJB and org.apache.soap.rpc.Call
Hi,
I am trying to call a web service from an ejb. the bean crashes as soon as i try to access any of the methods of the org.apache.soap.rpc.Call class. It creates the object but crashes if i try to populate parameters. I have this working in an application. Am i allowed to call a web service normally from an EJB ar is there an alternative approach?
Thanks,
Brian.
---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
Re: EJB and org.apache.soap.rpc.Call
Posted by Martin Gainty <mg...@hotmail.com>.
Brian
what happens when you surround the bean code with try{ call }
catch(EJBException e)
{e.getMessage(); } ??
and Can you ping the SOAP host from the Bean container?
finally where is the allocation for the allocation happening?
-Martin
----- Original Message -----
From: "Scott Nichol" <sn...@scottnichol.com>
To: <so...@ws.apache.org>
Sent: Tuesday, April 15, 2003 7:10 AM
Subject: Re: EJB and org.apache.soap.rpc.Call
> My experience with Java in general is that when an exception string
> is the name of a class, the exception is something like
> ClassNotFoundException.
>
> Is the message always org/apache/soap/rpc/RPCMessage, regardless of
> the Call method you invoke?
>
> Are you certain this happens on a method call and not the
> constructor? It's usually the constructor that causes secondary
> classes to be loaded.
>
> How have you made the SOAP classes available to your EJB? Have you
> deployed soap.jar as part of an ent-app containing your EJB? Is
> there any chance the SOAP classes might be loading from two different
> places? This can happen, e.g., if soap.jar is part of your ent-app
> but also in a common library directory or some place like
> $JAVA_HOME/jre/lib/ext.
>
> On 15 Apr 2003 at 1:41, Brian Shields wrote:
>
> > i am getting the following 2 exceptions from the log files of the EJB:
javax.ejb.EJBException: org/apache/soap/rpc/RPCMessage
> > at
com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.ja
va:1560)
> > at
com.sun.ejb.containers.BaseContainer.checkExceptionNoTx(BaseContainer.java:1
407)
> > at
com.sun.ejb.containers.BaseContainer.checkExceptionBeanMgTx(BaseContainer.ja
va:1354)
> > at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1253)
> > at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:403)
> > at
com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.ja
va:28)
> > at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown
Source)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPO
AServerSC.java:520)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOA
ServerSC.java:210)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC
.java:112)
> > at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> > at
com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.jav
a:84)
> > at
com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.jav
a:99) java.rmi.RemoteException: org/apache/soap/rpc/RPCMessage
> > at
com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:389)
> > at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:431)
> > at
com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.ja
va:28)
> > at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown
Source)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPO
AServerSC.java:520)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOA
ServerSC.java:210)
> > at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC
.java:112)
> > at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> > at
com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.jav
a:84)
> > at
com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.jav
a:99)
> > I have a client calling a remote bean, which in turn tries to call a
remote service. It crashes when i try to use any of the Call objects
methods, ie, to populate parameters etc. Any help would be
appreciated!!Thanks,Brian.
> >
> > Scott Nichol <sn...@scottnichol.com> wrote:I believe you should be
able to call from an EJB. The SOAP client
> > code does not do much special, e.g. no listening on server sockets,
> > no thread creation, so I don't think there should be a problem with
> > EJB.
> >
> > What EJB container are you using? Do you get any sort of diagnostic,
> > such as an exception message or (better still) a stack dump to a log
> > file? How have you deployed Apache SOAP classes to provide access
> > from the EJB?
> >
> > On 14 Apr 2003 at 9:55, Brian Shields wrote:
> >
> > > Hi,
> > > I am trying to call a web service from an ejb. the bean crashes as
soon as i try to access any of the methods of the org.apache.soap.rpc.Call
class. It creates the object but crashes if i try to populate parameters. I
have this working in an application. Am i allowed to call a web service
> > normally from an EJB ar is there an alternative approach?
> > >
> > > Thanks,
> > > Brian.
> > >
> > >
> > > ---------------------------------
> > > Do you Yahoo!?
> > > Yahoo! Tax Center - File online, calculators, forms, and more
> >
> >
> > Scott Nichol
> >
> > Do not reply directly to this e-mail address,
> > as it is filtered to only receive e-mail from
> > specific mailing lists.
> >
> >
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
Re: EJB and org.apache.soap.rpc.Call
Posted by Brian Shields <bg...@yahoo.com>.
got it working, i had to include soap.jar into a library in the bean before deploying. a silly mistake, although odd because it was not throwing an error on construction of the Class object only when methods were used!!! Thanks for the help scott!!Brian.
Scott Nichol <sn...@scottnichol.com> wrote:My experience with Java in general is that when an exception string
is the name of a class, the exception is something like
ClassNotFoundException.
Is the message always org/apache/soap/rpc/RPCMessage, regardless of
the Call method you invoke?
Are you certain this happens on a method call and not the
constructor? It's usually the constructor that causes secondary
classes to be loaded.
How have you made the SOAP classes available to your EJB? Have you
deployed soap.jar as part of an ent-app containing your EJB? Is
there any chance the SOAP classes might be loading from two different
places? This can happen, e.g., if soap.jar is part of your ent-app
but also in a common library directory or some place like
$JAVA_HOME/jre/lib/ext.
On 15 Apr 2003 at 1:41, Brian Shields wrote:
> i am getting the following 2 exceptions from the log files of the EJB: javax.ejb.EJBException: org/apache/soap/rpc/RPCMessage
> at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:1560)
> at com.sun.ejb.containers.BaseContainer.checkExceptionNoTx(BaseContainer.java:1407)
> at com.sun.ejb.containers.BaseContainer.checkExceptionBeanMgTx(BaseContainer.java:1354)
> at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1253)
> at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:403)
> at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
> at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
> at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
> at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99) java.rmi.RemoteException: org/apache/soap/rpc/RPCMessage
> at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:389)
> at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:431)
> at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
> at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
> at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
> at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)
> I have a client calling a remote bean, which in turn tries to call a remote service. It crashes when i try to use any of the Call objects methods, ie, to populate parameters etc. Any help would be appreciated!!Thanks,Brian.
>
> Scott Nichol wrote:I believe you should be able to call from an EJB. The SOAP client
> code does not do much special, e.g. no listening on server sockets,
> no thread creation, so I don't think there should be a problem with
> EJB.
>
> What EJB container are you using? Do you get any sort of diagnostic,
> such as an exception message or (better still) a stack dump to a log
> file? How have you deployed Apache SOAP classes to provide access
> from the EJB?
>
> On 14 Apr 2003 at 9:55, Brian Shields wrote:
>
> > Hi,
> > I am trying to call a web service from an ejb. the bean crashes as soon as i try to access any of the methods of the org.apache.soap.rpc.Call class. It creates the object but crashes if i try to populate parameters. I have this working in an application. Am i allowed to call a web service
> normally from an EJB ar is there an alternative approach?
> >
> > Thanks,
> > Brian.
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Tax Center - File online, calculators, forms, and more
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
Re: EJB and org.apache.soap.rpc.Call
Posted by Scott Nichol <sn...@scottnichol.com>.
My experience with Java in general is that when an exception string
is the name of a class, the exception is something like
ClassNotFoundException.
Is the message always org/apache/soap/rpc/RPCMessage, regardless of
the Call method you invoke?
Are you certain this happens on a method call and not the
constructor? It's usually the constructor that causes secondary
classes to be loaded.
How have you made the SOAP classes available to your EJB? Have you
deployed soap.jar as part of an ent-app containing your EJB? Is
there any chance the SOAP classes might be loading from two different
places? This can happen, e.g., if soap.jar is part of your ent-app
but also in a common library directory or some place like
$JAVA_HOME/jre/lib/ext.
On 15 Apr 2003 at 1:41, Brian Shields wrote:
> i am getting the following 2 exceptions from the log files of the EJB: javax.ejb.EJBException: org/apache/soap/rpc/RPCMessage
> at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:1560)
> at com.sun.ejb.containers.BaseContainer.checkExceptionNoTx(BaseContainer.java:1407)
> at com.sun.ejb.containers.BaseContainer.checkExceptionBeanMgTx(BaseContainer.java:1354)
> at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1253)
> at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:403)
> at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
> at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
> at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
> at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99) java.rmi.RemoteException: org/apache/soap/rpc/RPCMessage
> at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:389)
> at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:431)
> at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
> at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
> at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
> at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
> at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
> at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)
> I have a client calling a remote bean, which in turn tries to call a remote service. It crashes when i try to use any of the Call objects methods, ie, to populate parameters etc. Any help would be appreciated!!Thanks,Brian.
>
> Scott Nichol <sn...@scottnichol.com> wrote:I believe you should be able to call from an EJB. The SOAP client
> code does not do much special, e.g. no listening on server sockets,
> no thread creation, so I don't think there should be a problem with
> EJB.
>
> What EJB container are you using? Do you get any sort of diagnostic,
> such as an exception message or (better still) a stack dump to a log
> file? How have you deployed Apache SOAP classes to provide access
> from the EJB?
>
> On 14 Apr 2003 at 9:55, Brian Shields wrote:
>
> > Hi,
> > I am trying to call a web service from an ejb. the bean crashes as soon as i try to access any of the methods of the org.apache.soap.rpc.Call class. It creates the object but crashes if i try to populate parameters. I have this working in an application. Am i allowed to call a web service
> normally from an EJB ar is there an alternative approach?
> >
> > Thanks,
> > Brian.
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Tax Center - File online, calculators, forms, and more
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address,
> as it is filtered to only receive e-mail from
> specific mailing lists.
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
Re: EJB and org.apache.soap.rpc.Call
Posted by Brian Shields <bg...@yahoo.com>.
i am getting the following 2 exceptions from the log files of the EJB: javax.ejb.EJBException: org/apache/soap/rpc/RPCMessage
at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:1560)
at com.sun.ejb.containers.BaseContainer.checkExceptionNoTx(BaseContainer.java:1407)
at com.sun.ejb.containers.BaseContainer.checkExceptionBeanMgTx(BaseContainer.java:1354)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1253)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:403)
at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99) java.rmi.RemoteException: org/apache/soap/rpc/RPCMessage
at com.sun.enterprise.iiop.POAProtocolMgr.mapException(POAProtocolMgr.java:389)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:431)
at com.xess.engine.ejb.RMLBean_EJBObjectImpl.submitRML(RMLBean_EJBObjectImpl.java:28)
at com.xess.engine.ejb._RMLBean_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)
I have a client calling a remote bean, which in turn tries to call a remote service. It crashes when i try to use any of the Call objects methods, ie, to populate parameters etc. Any help would be appreciated!!Thanks,Brian.
Scott Nichol <sn...@scottnichol.com> wrote:I believe you should be able to call from an EJB. The SOAP client
code does not do much special, e.g. no listening on server sockets,
no thread creation, so I don't think there should be a problem with
EJB.
What EJB container are you using? Do you get any sort of diagnostic,
such as an exception message or (better still) a stack dump to a log
file? How have you deployed Apache SOAP classes to provide access
from the EJB?
On 14 Apr 2003 at 9:55, Brian Shields wrote:
> Hi,
> I am trying to call a web service from an ejb. the bean crashes as soon as i try to access any of the methods of the org.apache.soap.rpc.Call class. It creates the object but crashes if i try to populate parameters. I have this working in an application. Am i allowed to call a web service
normally from an EJB ar is there an alternative approach?
>
> Thanks,
> Brian.
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
Re: EJB and org.apache.soap.rpc.Call
Posted by Scott Nichol <sn...@scottnichol.com>.
I believe you should be able to call from an EJB. The SOAP client
code does not do much special, e.g. no listening on server sockets,
no thread creation, so I don't think there should be a problem with
EJB.
What EJB container are you using? Do you get any sort of diagnostic,
such as an exception message or (better still) a stack dump to a log
file? How have you deployed Apache SOAP classes to provide access
from the EJB?
On 14 Apr 2003 at 9:55, Brian Shields wrote:
> Hi,
> I am trying to call a web service from an ejb. the bean crashes as soon as i try to access any of the methods of the org.apache.soap.rpc.Call class. It creates the object but crashes if i try to populate parameters. I have this working in an application. Am i allowed to call a web service
normally from an EJB ar is there an alternative approach?
>
> Thanks,
> Brian.
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
Scott Nichol
Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.