You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by "Stelianos G. Sfakianakis" <sg...@gmail.com> on 2007/10/17 13:48:09 UTC
NPE when deploying BPEL
Hi,
I am using ODE 1.1 in Tomcat 6 and I have created by hand a "simple"
BPEL that imports an additional WSDL (the deployment folder with all
the necessary wsdls/bpel, etc. is attached) . When I deploy manually
this process as described in
<http://ode.apache.org/user-guide.html#UserGuide-ProcessDeployment> I
get the following errors:
DEBUG - GeronimoLog.debug(66) | Process store event:
{ProcessStoreEvent#DEPLOYED:{http://localhost/acgt/awe/stelios}TestBPELn-40}
DEBUG - GeronimoLog.debug(66) | Ignoring store event:
{ProcessStoreEvent#DEPLOYED:{http://localhost/acgt/awe/stelios}TestBPELn-40}
DEBUG - GeronimoLog.debug(66) | Process store event:
{ProcessStoreEvent#ACTVIATED:{http://localhost/acgt/awe/stelios}TestBPELn-40}
INFO - GeronimoLog.info(79) | Process
{http://localhost/acgt/awe/stelios}TestBPELn-40 has been unregistered.
DEBUG - GeronimoLog.debug(66) | register:
{http://localhost/acgt/awe/stelios}TestBPELn-40
DEBUG - GeronimoLog.debug(66) | Registering process
{http://localhost/acgt/awe/stelios}TestBPELn-40 with server.
DEBUG - GeronimoLog.debug(66) | Register process:
serviceId={http://localhost/acgt/awe/stelios}TestBPEL-Service:TestBPEL-Port,
process=BpelProcess[{http://localhost/acgt/awe/stelios}TestBPELn-40]
DEBUG - GeronimoLog.debug(66) | Activating
{http://localhost/acgt/awe/stelios}TestBPELn-40
DEBUG - GeronimoLog.debug(66) | Destroying service
{http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
DEBUG - GeronimoLog.debug(66) | Couldn't find service
{http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
to destroy.
DEBUG - GeronimoLog.debug(66) | Create AxisService:
service={http://localhost/acgt/awe/stelios}TestBPEL-Service
port=TestBPEL-Port WSDL=TestBPEL.wsdl BPEL=TestBPEL.bpel
DEBUG - GeronimoLog.debug(66) | Setting service with empty namespace replication
DEBUG - GeronimoLog.debug(66) | Created Axis2 service
{http://localhost/acgt/awe/stelios}TestBPEL-Service
DEBUG - GeronimoLog.debug(66) | Activated
{http://localhost/acgt/awe/stelios}TestBPELn-40 myrole
TestBPEL_Server: EPR is org.apache.ode.bpel.epr.WSAEndpoint@1a8885f
DEBUG - GeronimoLog.debug(66) | Activated
{http://localhost/acgt/awe/stelios}TestBPELn-40
DEBUG - GeronimoLog.debug(66) | Rehydrating process
{http://localhost/acgt/awe/stelios}TestBPELn-40
ERROR - GeronimoLog.error(104) | Latch error, was releasing for state
1 but actually in -1
WARN - GeronimoLog.warn(92) | Deployment failed within the engine,
store undeploying process.
DEBUG - GeronimoLog.debug(66) | Process store event:
{ProcessStoreEvent#UNDEPLOYED:{http://localhost/acgt/awe/stelios}TestBPELn-40}
DEBUG - GeronimoLog.debug(66) | Deactivating process
{http://localhost/acgt/awe/stelios}TestBPELn-40
DEBUG - GeronimoLog.debug(66) | Destroying service
{http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
INFO - GeronimoLog.info(79) | Process
{http://localhost/acgt/awe/stelios}TestBPELn-40 has been unregistered.
ERROR - GeronimoLog.error(108) | Deployment of test failed, aborting for now.
org.apache.ode.bpel.iapi.ContextException: Deployment failed within the engine.
at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:291)
at org.apache.ode.axis2.deploy.DeploymentPoller.check(DeploymentPoller.java:144)
at org.apache.ode.axis2.deploy.DeploymentPoller.access$300(DeploymentPoller.java:55)
at org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(DeploymentPoller.java:188)
Caused by: java.lang.NullPointerException
at org.apache.ode.axis2.BindingContextImpl.createPartnerRoleChannel(BindingContextImpl.java:76)
at org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.doHydrate(BpelProcess.java:711)
at org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.access$100(BpelProcess.java:654)
at org.apache.ode.bpel.engine.BpelProcess$HydrationLatch$2.run(BpelProcess.java:666)
at org.apache.ode.bpel.engine.NStateLatch.latch(NStateLatch.java:89)
at org.apache.ode.bpel.engine.BpelProcess.hydrate(BpelProcess.java:547)
at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:277)
at org.apache.ode.axis2.ODEServer.handleEvent(ODEServer.java:526)
at org.apache.ode.axis2.ODEServer.access$100(ODEServer.java:70)
at org.apache.ode.axis2.ODEServer$ProcessStoreListenerImpl.onProcessStoreEvent(ODEServer.java:512)
at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:501)
at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:507)
at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:284)
Searching the archives I have found a similar error described in
<https://issues.apache.org/jira/browse/ODE-146> and indeed deploying
the HelloWorld.zip referenced in that page to my installation yields
the same errors.
Can you please check if either I am doing something wrong or if it's a
bug on the ODE's side?
Thank you very much for your time
Cheers
Stelios
Re: Failure when deploying HelloWorld2 process to ode in weblogic 9.2
Posted by Paul Brown <pa...@gmail.com>.
On Dec 11, 2007, at 3:26 PM, Matthieu Riou wrote:
> On Dec 11, 2007 12:46 PM, Jackson, Douglas <dj...@ugs.com> wrote:
>> I suspect that this must be due to some version of the xml parser
>> conflicting with the one Ode wants to use. Has anyone encountered
>> this
>> before?
> That's what it looks like to me as well. I haven't tried Tomcat 6
> so far
> (still conservatively on 5.5) but I'd check the xerces version
> distributed
> with Tomcat and compare it with the ODE one. You'll probably have
> to replace
> one with the other, like make ODE use the Tomcat one.
AFAIK, Tomcat6 doesn't bundle Xerces. If you read the Tomcat docs on
the subject, it attributes the issues to the Java 5 environment:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
-- Paul
Re: Failure when deploying HelloWorld2 process to ode in weblogic 9.2
Posted by Matthieu Riou <ma...@offthelip.org>.
On Dec 11, 2007 12:46 PM, Jackson, Douglas <dj...@ugs.com> wrote:
> Hi!
> I am just getting started with Ode and I am feeling some pain. :)
>
> I got the HelloWorld2 BPEL process to work on TomCat 6.0, and then ran
> into a deployment problem with my first attempt at deploying a process.
> The
> error message wasn't particularly informative, so I thought I would try
> to debug it remotely and could not figure out how to enable remote
> debugging
> with the tomcat.exe. So, I deployed the ode war to weblogic and
> tried to deploy the HelloWorld2 process there along with the other
> examples,
> and they all failed with the following trace.
>
> I suspect that this must be due to some version of the xml parser
> conflicting with the one Ode wants to use. Has anyone encountered this
> before?
That's what it looks like to me as well. I haven't tried Tomcat 6 so far
(still conservatively on 5.5) but I'd check the xerces version distributed
with Tomcat and compare it with the ODE one. You'll probably have to replace
one with the other, like make ODE use the Tomcat one.
Matthieu
>
> Thanks in advance,
> -Doug.
>
> org.apache.ode.bpel.iapi.ContextException: Deploy failed;
> file:/D:/ode-war/WEB-INF/processes/HelloWo
> rld2/HelloWorld2.bpel:0: error: [BpelParseErr] Error parsing BPEL
> process: the BPEL is either malfor
> med or is invalid.
> at
> org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:169)
> at
> org.apache.ode.axis2.deploy.DeploymentPoller.check(DeploymentPoller.java
> :144)
> at
> org.apache.ode.axis2.deploy.DeploymentPoller.access$300(DeploymentPoller
> .java:55)
> at
> org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(Deploymen
> tPoller.java:188)
>
> Caused by: org.apache.ode.bpel.compiler.api.CompilationException:
> file:/D:/ode-war/WEB-INF/processes
> /HelloWorld2/HelloWorld2.bpel:0: error: [BpelParseErr] Error parsing
> BPEL process: the BPEL is eithe
> r malformed or is invalid.
> at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:321)
> at
> org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:16
> 1)
> at
> org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:12
> 5)
> at
> org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:165)
> ... 3 more
> Caused by: java.lang.RuntimeException: Internal compiler error
> at
> org.apache.ode.bpel.compiler.bom.BpelObjectFactory.createBpelObject(Bpel
> ObjectFactory.jav
> a:277)
> at
> org.apache.ode.bpel.compiler.bom.BpelObjectFactory.parse(BpelObjectFacto
> ry.java:307)
> at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:317)
> ... 6 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
> ccessorImpl.java:
> 39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
> tructorAccessorIm
> pl.java:27)
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at
> org.apache.ode.bpel.compiler.bom.BpelObjectFactory.createBpelObject(Bpel
> ObjectFactory.jav
> a:273)
> ... 8 more
> Caused by: java.lang.AbstractMethodError:
> org.apache.xerces.dom.AttrNSImpl.getTextContent()Ljava/lan
> g/String;
> at
> org.apache.ode.bpel.compiler.bom.BpelObject.initNSContext(BpelObject.jav
> a:268)
> at
> org.apache.ode.bpel.compiler.bom.BpelObject.<init>(BpelObject.java:65)
> at
> org.apache.ode.bpel.compiler.bom.JoinFailureSuppressor.<init>(JoinFailur
> eSuppressor.java:
> 33)
> at org.apache.ode.bpel.compiler.bom.Scope.<init>(Scope.java:40)
> at
> org.apache.ode.bpel.compiler.bom.Process.<init>(Process.java:38)
> ... 13 more
>
>
Failure when deploying HelloWorld2 process to ode in weblogic 9.2
Posted by "Jackson, Douglas" <dj...@ugs.com>.
Hi!
I am just getting started with Ode and I am feeling some pain. :)
I got the HelloWorld2 BPEL process to work on TomCat 6.0, and then ran
into a deployment problem with my first attempt at deploying a process.
The
error message wasn't particularly informative, so I thought I would try
to debug it remotely and could not figure out how to enable remote
debugging
with the tomcat.exe. So, I deployed the ode war to weblogic and
tried to deploy the HelloWorld2 process there along with the other
examples,
and they all failed with the following trace.
I suspect that this must be due to some version of the xml parser
conflicting with the one Ode wants to use. Has anyone encountered this
before?
Thanks in advance,
-Doug.
org.apache.ode.bpel.iapi.ContextException: Deploy failed;
file:/D:/ode-war/WEB-INF/processes/HelloWo
rld2/HelloWorld2.bpel:0: error: [BpelParseErr] Error parsing BPEL
process: the BPEL is either malfor
med or is invalid.
at
org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:169)
at
org.apache.ode.axis2.deploy.DeploymentPoller.check(DeploymentPoller.java
:144)
at
org.apache.ode.axis2.deploy.DeploymentPoller.access$300(DeploymentPoller
.java:55)
at
org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(Deploymen
tPoller.java:188)
Caused by: org.apache.ode.bpel.compiler.api.CompilationException:
file:/D:/ode-war/WEB-INF/processes
/HelloWorld2/HelloWorld2.bpel:0: error: [BpelParseErr] Error parsing
BPEL process: the BPEL is eithe
r malformed or is invalid.
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:321)
at
org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:16
1)
at
org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:12
5)
at
org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:165)
... 3 more
Caused by: java.lang.RuntimeException: Internal compiler error
at
org.apache.ode.bpel.compiler.bom.BpelObjectFactory.createBpelObject(Bpel
ObjectFactory.jav
a:277)
at
org.apache.ode.bpel.compiler.bom.BpelObjectFactory.parse(BpelObjectFacto
ry.java:307)
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:317)
... 6 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:
39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorIm
pl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.apache.ode.bpel.compiler.bom.BpelObjectFactory.createBpelObject(Bpel
ObjectFactory.jav
a:273)
... 8 more
Caused by: java.lang.AbstractMethodError:
org.apache.xerces.dom.AttrNSImpl.getTextContent()Ljava/lan
g/String;
at
org.apache.ode.bpel.compiler.bom.BpelObject.initNSContext(BpelObject.jav
a:268)
at
org.apache.ode.bpel.compiler.bom.BpelObject.<init>(BpelObject.java:65)
at
org.apache.ode.bpel.compiler.bom.JoinFailureSuppressor.<init>(JoinFailur
eSuppressor.java:
33)
at org.apache.ode.bpel.compiler.bom.Scope.<init>(Scope.java:40)
at
org.apache.ode.bpel.compiler.bom.Process.<init>(Process.java:38)
... 13 more
Re: NPE when deploying BPEL
Posted by Tammo van Lessen <tv...@gmail.com>.
Hi,
2007/10/17, Stelianos G. Sfakianakis <sg...@gmail.com>:
> Some better error reporting would be good, because a Null Pointer
> exception is not quite informative.
Absolutely! I filed a jira for that:
https://issues.apache.org/jira/browse/ODE-197
Best,
Tammo
--
Tammo van Lessen - tvanlessen@gmail.com - http://www.taval.de
Re: NPE when deploying BPEL
Posted by "Stelianos G. Sfakianakis" <sg...@gmail.com>.
On 10/17/07, Alex Boisvert <bo...@intalio.com> wrote:
> Hi Stelios,
>
> Looks like you have a partnerLink named "SRV_0" in your process that is not
> bound in deploy.xml. You can comment it if you don't use it.
That is true, I thought that in deploy.xml I need to "bind" only the
partner link that is related to the BPEL process itself and not all
the others partners that the process contacts. Rereading the
documentation I found that:
"Every partner link used with a <receive> activity must be matched
with a <provide> element, and every partnerLink used in an <invoke>
activity must be matched with an <invoke> element in deploy.xml "
Doh! Now it makes sense! Thank you very much!
> I need to
> review the code to decide if we can avoid the error or we should provide
> better error reporting.
Some better error reporting would be good, because a Null Pointer
exception is not quite informative.
Thank you again!
Cheers
Stelios
Re: NPE when deploying BPEL
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Stelios,
Looks like you have a partnerLink named "SRV_0" in your process that is not
bound in deploy.xml. You can comment it if you don't use it. I need to
review the code to decide if we can avoid the error or we should provide
better error reporting.
thanks,
alex
On 10/17/07, Stelianos G. Sfakianakis <sg...@gmail.com> wrote:
>
> Hi,
>
> I am using ODE 1.1 in Tomcat 6 and I have created by hand a "simple"
> BPEL that imports an additional WSDL (the deployment folder with all
> the necessary wsdls/bpel, etc. is attached) . When I deploy manually
> this process as described in
> <http://ode.apache.org/user-guide.html#UserGuide-ProcessDeployment> I
> get the following errors:
>
> DEBUG - GeronimoLog.debug(66) | Process store event:
> {ProcessStoreEvent#DEPLOYED:{
> http://localhost/acgt/awe/stelios}TestBPELn-40}
> DEBUG - GeronimoLog.debug(66) | Ignoring store event:
> {ProcessStoreEvent#DEPLOYED:{
> http://localhost/acgt/awe/stelios}TestBPELn-40}
> DEBUG - GeronimoLog.debug(66) | Process store event:
> {ProcessStoreEvent#ACTVIATED:{
> http://localhost/acgt/awe/stelios}TestBPELn-40}
>
> INFO - GeronimoLog.info(79) | Process
> {http://localhost/acgt/awe/stelios}TestBPELn-40 has been unregistered.
>
> DEBUG - GeronimoLog.debug(66) | register:
> {http://localhost/acgt/awe/stelios}TestBPELn-40
>
> DEBUG - GeronimoLog.debug(66) | Registering process
> {http://localhost/acgt/awe/stelios}TestBPELn-40 with server.
>
> DEBUG - GeronimoLog.debug(66) | Register process:
> serviceId={
> http://localhost/acgt/awe/stelios}TestBPEL-Service:TestBPEL-Port,
> process=BpelProcess[{http://localhost/acgt/awe/stelios}TestBPELn-40]
>
> DEBUG - GeronimoLog.debug(66) | Activating
> {http://localhost/acgt/awe/stelios}TestBPELn-40
>
> DEBUG - GeronimoLog.debug(66) | Destroying service
> {http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
>
> DEBUG - GeronimoLog.debug(66) | Couldn't find service
> {http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
> to destroy.
>
> DEBUG - GeronimoLog.debug(66) | Create AxisService:
> service={http://localhost/acgt/awe/stelios}TestBPEL-Service
> port=TestBPEL-Port WSDL=TestBPEL.wsdl BPEL=TestBPEL.bpel
>
> DEBUG - GeronimoLog.debug(66) | Setting service with empty namespace
> replication
>
> DEBUG - GeronimoLog.debug(66) | Created Axis2 service
> {http://localhost/acgt/awe/stelios}TestBPEL-Service
>
> DEBUG - GeronimoLog.debug(66) | Activated
> {http://localhost/acgt/awe/stelios}TestBPELn-40 myrole
> TestBPEL_Server: EPR is org.apache.ode.bpel.epr.WSAEndpoint@1a8885f
>
> DEBUG - GeronimoLog.debug(66) | Activated
> {http://localhost/acgt/awe/stelios}TestBPELn-40
>
> DEBUG - GeronimoLog.debug(66) | Rehydrating process
> {http://localhost/acgt/awe/stelios}TestBPELn-40
>
> ERROR - GeronimoLog.error(104) | Latch error, was releasing for state
> 1 but actually in -1
>
> WARN - GeronimoLog.warn(92) | Deployment failed within the engine,
> store undeploying process.
>
> DEBUG - GeronimoLog.debug(66) | Process store event:
> {ProcessStoreEvent#UNDEPLOYED:{
> http://localhost/acgt/awe/stelios}TestBPELn-40}
>
> DEBUG - GeronimoLog.debug(66) | Deactivating process
> {http://localhost/acgt/awe/stelios}TestBPELn-40
>
> DEBUG - GeronimoLog.debug(66) | Destroying service
> {http://localhost/acgt/awe/stelios}TestBPEL-Service port TestBPEL-Port
>
> INFO - GeronimoLog.info(79) | Process
> {http://localhost/acgt/awe/stelios}TestBPELn-40 has been unregistered.
>
> ERROR - GeronimoLog.error(108) | Deployment of test failed, aborting for
> now.
>
> org.apache.ode.bpel.iapi.ContextException: Deployment failed within the
> engine.
>
> at org.apache.ode.store.ProcessStoreImpl.deploy(
> ProcessStoreImpl.java:291)
>
> at org.apache.ode.axis2.deploy.DeploymentPoller.check(
> DeploymentPoller.java:144)
>
> at org.apache.ode.axis2.deploy.DeploymentPoller.access$300(
> DeploymentPoller.java:55)
>
> at org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(
> DeploymentPoller.java:188)
>
> Caused by: java.lang.NullPointerException
>
> at
> org.apache.ode.axis2.BindingContextImpl.createPartnerRoleChannel(
> BindingContextImpl.java:76)
>
> at org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.doHydrate
> (BpelProcess.java:711)
>
> at
> org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.access$100(
> BpelProcess.java:654)
>
> at org.apache.ode.bpel.engine.BpelProcess$HydrationLatch$2.run(
> BpelProcess.java:666)
>
> at org.apache.ode.bpel.engine.NStateLatch.latch(NStateLatch.java
> :89)
>
> at org.apache.ode.bpel.engine.BpelProcess.hydrate(BpelProcess.java
> :547)
>
> at org.apache.ode.bpel.engine.BpelServerImpl.register(
> BpelServerImpl.java:277)
>
> at org.apache.ode.axis2.ODEServer.handleEvent(ODEServer.java:526)
>
> at org.apache.ode.axis2.ODEServer.access$100(ODEServer.java:70)
>
> at
> org.apache.ode.axis2.ODEServer$ProcessStoreListenerImpl.onProcessStoreEvent
> (ODEServer.java:512)
>
> at org.apache.ode.store.ProcessStoreImpl.fireEvent(
> ProcessStoreImpl.java:501)
>
> at org.apache.ode.store.ProcessStoreImpl.fireStateChange(
> ProcessStoreImpl.java:507)
>
> at org.apache.ode.store.ProcessStoreImpl.deploy(
> ProcessStoreImpl.java:284)
>
>
> Searching the archives I have found a similar error described in
> <https://issues.apache.org/jira/browse/ODE-146> and indeed deploying
> the HelloWorld.zip referenced in that page to my installation yields
> the same errors.
>
> Can you please check if either I am doing something wrong or if it's a
> bug on the ODE's side?
>
> Thank you very much for your time
> Cheers
> Stelios
>
>