ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Tranquillini <stefano.tranquill...@gmail.com>
Subject Re: Error: Two services cannot have same name, why?
Date Thu, 14 Jan 2010 13:06:52 GMT
thanks for reply
i don't really undestand two things: your patch is current working? if so,
how can i install it?
otherwise the bug still remains until the fixing in the 1.3.4, right?
there's a couple oh hint to avoid this problem? (like invok services not
before 30seconds of previous one or smt like that)

thanks.


On Thu, Jan 14, 2010 at 13:05, Tammo van Lessen <tvanlessen@gmail.com>wrote:

> Stefano,
>
> please see https://issues.apache.org/jira/browse/ODE-647. We're actively
> working on a fix for ODE 1.3.4.
>
> Best,
>  Tammo
>
> On 14.01.2010 13:03, Stefano Tranquillini wrote:
> > Someone can explain me why ode rise up this error?
> >
> > org.apache.axis2.AxisFault: Two services cannot have same name.  A
> service
> > with the axis_service_for_{
> >
> http://www.unitnt.it/JS/LocalSearch}LocalSearchPortTypeInvokeBindingSOAPService#LocalSearchPortTypeInvokeBindingSOAPPortLocalSearch_master_hqejbhcnphr4wpfta1ti9mname<http://www.unitnt.it/JS/LocalSearch%7DLocalSearchPortTypeInvokeBindingSOAPService#LocalSearchPortTypeInvokeBindingSOAPPortLocalSearch_master_hqejbhcnphr4wpfta1ti9mname>
> > already exists in the system.
> >   at
> >
> org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:172)
> >   at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:139)
> >   at
> >
> org.apache.ode.axis2.SoapExternalService.getServiceClient(SoapExternalService.java:281)
> >   at
> >
> org.apache.ode.axis2.SoapExternalService.invoke(SoapExternalService.java:140)
> >   at
> >
> org.apache.ode.axis2.MessageExchangeContextImpl.invokePartner(MessageExchangeContextImpl.java:52)
> >   at
> >
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.invoke(BpelRuntimeContextImpl.java:781)
> >   at org.apache.ode.bpel.runtime.INVOKE.run(INVOKE.java:91)
> >   at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
> >   at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >   at java.lang.reflect.Method.invoke(Method.java:597)
> >   at
> > org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)
> >   at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> >   at
> >
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:875)
> >   at
> >
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeNewInstance(PartnerLinkMyRoleImpl.java:206)
> >   at
> >
> org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:237)
> >   at
> >
> org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:408)
> >   at
> >
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:439)
> >   at
> >
> org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:441)
> >   at
> >
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:411)
> >   at
> >
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:405)
> >   at
> >
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:218)
> >   at
> >
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:404)
> >   at
> >
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:401)
> >   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >   at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >   at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >   at java.lang.Thread.run(Thread.java:619)
> > DEBUG - GeronimoLog.debug(66) | replyWithFailure
> mex=hqejbhcnphr4wpfta1tiai
> > failureType=COMMUNICATION_ERROR description=Error sending message to
> Axis2
> > for ODE mex {PartnerRoleMex#hqejbhcnphr4wpfta1tiai [PID {
> > http://unitn.it/bpelUI/esempio}TestNatale-5<http://unitn.it/bpelUI/esempio%7DTestNatale-5>]
> calling null.Update(...)}
> > details=null
> >
> > where is the mistake?
> > it said:  " Two services cannot have same name. " but what does it means?
> > services in the wsdl?
> > is a my problem or is a problem of the ode's runtime
> >
> >
> >
>
>
> --
> Tammo van Lessen - http://www.taval.de
>



-- 
Stefano

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message