ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ciaran <ciar...@gmail.com>
Subject Re: Re: A suspectable bug of 1.3.3 - AxisFault: Two services cannot havesame name
Date Tue, 18 Aug 2009 19:00:29 GMT
Somewhat more usefully a link the to actual message ;)
http://mail-archives.apache.org/mod_mbox/ode-dev/200907.mbox/%3C654f1dd70907290707q540b9d6fjf3a9992f9349a80f@mail.gmail.com%3E
-c j.

On Tue, Aug 18, 2009 at 7:59 PM, Ciaran <ciaranj@gmail.com> wrote:

> Fwiw, I raised this issue in the dev mailing list last month and outlined
> the changeset that introduced this break (
> http://mail-archives.apache.org/mod_mbox/ode-dev/200907.mbox/browser ) ..
> but I guess no-one saw it ?
> -cj.
>
>
> On Thu, Aug 13, 2009 at 4:00 PM, Alex Boisvert <boisvert@intalio.com>wrote:
>
>> Alright, we'll take a look at it.
>>
>> thanks!
>>
>> 2009/8/13 ZHAO Wenfeng <zhaowenfeng@gmail.com>
>>
>> > Hello Alex,
>> >
>> >        I've created one: ODE-647 (
>> > https://issues.apache.org/jira/browse/ODE-647).
>> >
>> >    If there is anything I didn't express out clearly, please let me
>> know.
>> > Thanks.
>> >
>> >
>> > Best Regard,
>> > Wenfeng
>> >
>> >
>> > =======On 2009-08-13 at 20:07:23 Alex Boisvert wrote: =======
>> >
>> > >Hi Wenfeng,
>> > >
>> > >Can you open a Jira and attach your processes and information there?
>> > Your
>> > >attachments didn't make it to the mailing list.
>> > >
>> > >alex
>> > >
>> > >2009/8/10 ZHAO Wenfeng <zhaowenfeng@gmail.com>
>> > >
>> > >> Hello,
>> > >>
>> > >>  With ODE 1.3.3, it seems that multiple consecutive invocations to
a
>> > same
>> > >> component service will incur the following exception:
>> > >>
>> > >> ERROR - GeronimoLog.error(108) | Error sending message to Axis2 for
>> ODE
>> > mex
>> > >> {PartnerRoleMex#hqejbhcnphr4i3dscxlf10 [PID {
>> > >>
>> http://scqr.bupt.edu.cn/solution}process_SyntheticBookService_sol2-12<http://scqr.bupt.edu.cn/solution%7Dprocess_SyntheticBookService_sol2-12>
>> <http://scqr.bupt.edu.cn/solution%7Dprocess_SyntheticBookService_sol2-12>
>> > <
>> http://scqr.bupt.edu.cn/solution%7Dprocess_SyntheticBookService_sol2-12>]
>> > >> calling null.operation1(...)}
>> > >> org.apache.axis2.AxisFault: Two services cannot have same name.  A
>> > service
>> > >> with the axis_service_for_{
>> > >>
>> >
>> http://example.org/writerInfo}writerInfoService#writerInfoPort_hqejbhcnphr4i3dscxlf0r<http://example.org/writerInfo%7DwriterInfoService#writerInfoPort_hqejbhcnphr4i3dscxlf0r>
>> <
>> http://example.org/writerInfo%7DwriterInfoService#writerInfoPort_hqejbhcnphr4i3dscxlf0r
>> >
>> > <
>> >
>> http://example.org/writerInfo%7DwriterInfoService#writerInfoPort_hqejbhcnphr4i3dscxlf0r
>> >name
>> > 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:100)
>> > >>        at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown
>> Source)
>> > >>        at
>> > >>
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> > >>        at java.lang.reflect.Method.invoke(Method.java:585)
>> > >>        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.BpelProcess.handleWorkEvent(BpelProcess.java:438)
>> > >>        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:269)
>> > >>        at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>> > >>        at
>> > >>
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>> > >>        at
>> > >>
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>> > >>        at java.lang.Thread.run(Thread.java:595)
>> > >>
>> > >>
>> > >> But the same actions doesn't incur any exception in with 1.3.2 or
>> 2.0.
>> > So I
>> > >> think this maybe is a bug, isn't it?
>> > >>
>> > >> And I noted that a similar problem has been discussed in 2007(
>> > >>
>> >
>> https://issues.apache.org/jira/browse/AXIS2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476874
>> > ).
>> > >>
>> > >> The attached is almost all the needed to replay the exception - the
>> > >> process, 2 component services(running in Axis2), and the SOAP request
>> > >> message of the process.  There is another coponent service which is
>> > omitted
>> > >> for space reason. But in most cases, the previous exception will
>> occur
>> > >> before it is invoked.
>> > >>
>> > >>
>> > >> Best Regards,
>> > >> Wenfeng
>> > >>
>> > >> = = = = = = = = = = = = = = = = = = = =
>> > >> ZHAO Wenfeng (赵文峰)
>> > >> Ph.D. Candidate
>> > >> http://www.bupt.edu.cn
>> > >>
>> > >>
>> >
>> > = = = = = = = = = = = = = = = = = = = =
>> > ZHAO Wenfeng (赵文峰)
>> > Ph.D. Candidate
>> > http://www.bupt.edu.cn
>> >
>> >
>>
>
>

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