|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
WS-Notification : "Unexpected EOF in prolog" errorHy,
I try to test the use case WS-Notification mecanism implemented in PEtALS SOAP-BC. To do I follow the recommendations written in the documentation : petals-soap-usecases-080804.pdf So after launching the quickstart PEtALS 2.2, I deploy the components and launch them using the ANT script : D:\petals\petals-quickstart-2.2\usecases\petals-soap-topic>ant Buildfile: build.xml deploy: [echo] Installing components... [jbi-install-component] Getting the InstallerConfigurationMBean:org.ow2.petals:t ype=custom,name=bootstrap_petals-bc-soap [jbi-install-component] 0 parameters to be set [jbi-install-component] The component 'petals-bc-soap' has been installed [jbi-install-component] Getting the InstallerConfigurationMBean:null [jbi-install-component] 0 parameters to be set [jbi-install-component] The component 'petals-sample-client-1.5' has been instal led [echo] Starting components... [jbi-start-component] Invoking 'start' on component 'petals-bc-soap' [jbi-start-component] Invoking 'start' on component 'petals-sample-client-1.5' [echo] Deploying service assemblies [jbi-deploy-service-assembly] The service assembly 'sa-soap-topic' has been depl oyed [echo] Starting service assemblies [jbi-start-service-assembly] Service assembly named 'sa-soap-topic' has been set to state : start BUILD SUCCESSFUL Total time: 12 seconds .... I then launch the client which will register notification consumers into the Web Service Notification manager : D:\petals\petals-quickstart-2.2\usecases\petals-soap-topic>ant client Buildfile: build.xml client: [echo] Launching client... [java] 2008-09-23 12:38:02.117::INFO: Logging to STDERR via org.mortbay.lo g.StdErrLog [java] 2008-09-23 12:38:02.210::INFO: jetty-6.1.4 [java] 2008-09-23 12:38:02.351::INFO: Started SocketConnector@0.0.0.0:9999 [java] Subscribing to topic TopicSample on WSN producer EPR : http://localh ost:8084/wsn/producer [java] Notification will be sent to EPR : http://localhost:9999/notif/Consu mer [java] org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog [java] at [row,col {unknown-source}]: [1,0] [java] at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBui lder.java:239) [java] at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSO APEnvelope(StAXSOAPModelBuilder.java:161) [java] at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.ident ifySOAPVersion(StAXSOAPModelBuilder.java:133) [java] at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init >(StAXSOAPModelBuilder.java:98) [java] at org.ow2.petals.ws.client.SimpleSoapClient.getSOAPResponse(Sim pleSoapClient.java:186) [java] at org.ow2.petals.ws.client.SimpleSoapClient.send(SimpleSoapClie nt.java:108) [java] at org.ow2.petals.ws.client.AbstractWSClient.callWS(AbstractWSCl ient.java:86) [java] at org.ow2.petals.ws.client.WsnProducerClient.subscribe(WsnProdu cerClient.java:87) [java] at org.objectweb.petals.usecase.soaptopic.TopicSubscriptionClien t.subscribe(TopicSubscriptionClient.java:101) [java] at org.objectweb.petals.usecase.soaptopic.TopicSubscriptionClien t.main(TopicSubscriptionClient.java:68) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.jav a:217) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava .java:152) [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:747) [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:201) [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja va:288) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchU tils.java:105) [java] at org.apache.tools.ant.Task.perform(Task.java:348) [java] at org.apache.tools.ant.Target.execute(Target.java:357) [java] at org.apache.tools.ant.Target.performTasks(Target.java:385) [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.jav a:1329) [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [java] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(De faultExecutor.java:41) [java] at org.apache.tools.ant.Project.executeTargets(Project.java:1181 ) [java] at org.apache.tools.ant.Main.runBuild(Main.java:698) [java] at org.apache.tools.ant.Main.startAnt(Main.java:199) [java] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [java] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [java] Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prol og [java] at [row,col {unknown-source}]: [1,0] [java] at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanne r.java:661) [java] at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader .java:2134) [java] at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamR eader.java:2040) [java] at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java :1069) [java] at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBui lder.java:153) [java] ... 35 more [java] Type Control-C to quit Do you have an idea of the issue ? Please help me. Richard. |
|
|
Re: WS-Notification : "Unexpected EOF in prolog" errorHi,
I have already see this. I do not remember exactly the reason but I think that the usecase works no ? On Tue, Sep 23, 2008 at 2:14 PM, aillet <richard.aillet@...> wrote:
-- Christophe Hamerling PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing http://petals.ow2.org http://petals.ebmwebsourcing.com Phone : +33534320314 Skype : christophe.hamerling -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Re: WS-Notification : "Unexpected EOF in prolog" errorHi Richard
An error encapsulated in org.apache.axiom.om.OMException has actually occured on the server side rather than the client side, look for logs there. "Unexpected EOF in prolog" means the XML message was not wholly received by the server. There can be various causes, up to antivirii, being wrongly multipart, or badly encapsulated internal error messages. Regards, Marc aillet a écrit : > Hy, > > I try to test the use case WS-Notification mecanism implemented in PEtALS > SOAP-BC. > To do I follow the recommendations written in the documentation : > petals-soap-usecases-080804.pdf > > So after launching the quickstart PEtALS 2.2, I deploy the components and > launch them using the ANT script : > D:\petals\petals-quickstart-2.2\usecases\petals-soap-topic>ant > Buildfile: build.xml > > deploy: > [echo] Installing components... > [jbi-install-component] Getting the > InstallerConfigurationMBean:org.ow2.petals:t > ype=custom,name=bootstrap_petals-bc-soap > [jbi-install-component] 0 parameters to be set > [jbi-install-component] The component 'petals-bc-soap' has been installed > [jbi-install-component] Getting the InstallerConfigurationMBean:null > [jbi-install-component] 0 parameters to be set > [jbi-install-component] The component 'petals-sample-client-1.5' has been > instal > led > [echo] Starting components... > [jbi-start-component] Invoking 'start' on component 'petals-bc-soap' > [jbi-start-component] Invoking 'start' on component > 'petals-sample-client-1.5' > [echo] Deploying service assemblies > [jbi-deploy-service-assembly] The service assembly 'sa-soap-topic' has been > depl > oyed > [echo] Starting service assemblies > [jbi-start-service-assembly] Service assembly named 'sa-soap-topic' has been > set > to state : start > > BUILD SUCCESSFUL > Total time: 12 seconds > .... > > I then launch the client which will register notification consumers into the > Web Service Notification manager : > D:\petals\petals-quickstart-2.2\usecases\petals-soap-topic>ant client > Buildfile: build.xml > > client: > [echo] Launching client... > [java] 2008-09-23 12:38:02.117::INFO: Logging to STDERR via > org.mortbay.lo > g.StdErrLog > [java] 2008-09-23 12:38:02.210::INFO: jetty-6.1.4 > [java] 2008-09-23 12:38:02.351::INFO: Started > SocketConnector@...:9999 > > [java] Subscribing to topic TopicSample on WSN producer EPR : > http://localh > ost:8084/wsn/producer > [java] Notification will be sent to EPR : > http://localhost:9999/notif/Consu > mer > [java] org.apache.axiom.om.OMException: > com.ctc.wstx.exc.WstxEOFException: > Unexpected EOF in prolog > [java] at [row,col {unknown-source}]: [1,0] > [java] at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBui > lder.java:239) > [java] at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSO > APEnvelope(StAXSOAPModelBuilder.java:161) > [java] at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.ident > ifySOAPVersion(StAXSOAPModelBuilder.java:133) > [java] at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init > >> (StAXSOAPModelBuilder.java:98) >> > [java] at > org.ow2.petals.ws.client.SimpleSoapClient.getSOAPResponse(Sim > pleSoapClient.java:186) > [java] at > org.ow2.petals.ws.client.SimpleSoapClient.send(SimpleSoapClie > nt.java:108) > [java] at > org.ow2.petals.ws.client.AbstractWSClient.callWS(AbstractWSCl > ient.java:86) > [java] at > org.ow2.petals.ws.client.WsnProducerClient.subscribe(WsnProdu > cerClient.java:87) > [java] at > org.objectweb.petals.usecase.soaptopic.TopicSubscriptionClien > t.subscribe(TopicSubscriptionClient.java:101) > [java] at > org.objectweb.petals.usecase.soaptopic.TopicSubscriptionClien > t.main(TopicSubscriptionClient.java:68) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces > sorImpl.java:39) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet > hodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:597) > [java] at > org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.jav > a:217) > [java] at > org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava > .java:152) > [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:747) > [java] at > org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:201) > > [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) > [java] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja > va:288) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces > sorImpl.java:39) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet > hodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:597) > [java] at > org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchU > tils.java:105) > [java] at org.apache.tools.ant.Task.perform(Task.java:348) > [java] at org.apache.tools.ant.Target.execute(Target.java:357) > [java] at org.apache.tools.ant.Target.performTasks(Target.java:385) > [java] at > org.apache.tools.ant.Project.executeSortedTargets(Project.jav > a:1329) > [java] at > org.apache.tools.ant.Project.executeTarget(Project.java:1298) > > [java] at > org.apache.tools.ant.helper.DefaultExecutor.executeTargets(De > faultExecutor.java:41) > [java] at > org.apache.tools.ant.Project.executeTargets(Project.java:1181 > ) > [java] at org.apache.tools.ant.Main.runBuild(Main.java:698) > [java] at org.apache.tools.ant.Main.startAnt(Main.java:199) > [java] at > org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) > [java] at > org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) > [java] Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in > prol > og > [java] at [row,col {unknown-source}]: [1,0] > [java] at > com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanne > r.java:661) > [java] at > com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader > .java:2134) > [java] at > com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamR > eader.java:2040) > [java] at > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java > :1069) > [java] at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBui > lder.java:153) > [java] ... 35 more > [java] Type Control-C to quit > > Do you have an idea of the issue ? > Please help me. > > Richard. > > -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Re: WS-Notification : "Unexpected EOF in prolog" errorChristophe,
do you mean "the use case works on" instead of "work no" (this not the same) ? Anyway I 'm not sure the usecase works because 1) it is not a warning but an exception error 2) and the raised exception carries on with the following message : ... Unsubscribing from Topic Unsubscribing from Topic... ... on my client console command. So there is no subscription. Richard.
|
|
|
Re: Re: WS-Notification : "Unexpected EOF in prolog" errorI think that it works.
Even if there is an exception, the unsubscribe method is only called if you hit CTRL+C. Right? On Tue, Sep 23, 2008 at 3:30 PM, aillet <richard.aillet@...> wrote:
-- Christophe Hamerling PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing http://petals.ow2.org http://petals.ebmwebsourcing.com Phone : +33534320314 Skype : christophe.hamerling -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
RE: Re: Re: WS-Notification : "Unexpected EOF in prolog" errorNo. The unsubscribe method in my case is called just after
the raised exception.
Richard. De : chamerling.ebmws@... [mailto:chamerling.ebmws@...] De la part de Christophe Hamerling - eBM WebSourcing Envoyé : mardi 23 septembre 2008 16:17 À : petals-users@... Objet : [petals-users] Re: Re: WS-Notification : "Unexpected EOF in prolog" error I think that it works.
Even if there is an exception, the unsubscribe method is only called if you hit CTRL+C. Right? On Tue, Sep 23, 2008 at 3:30 PM, aillet <richard.aillet@...>
wrote:
-- Christophe Hamerling PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing http://petals.ow2.org http://petals.ebmwebsourcing.com Phone : +33534320314 Skype : christophe.hamerling -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Re: RE: Re: Re: WS-Notification : "Unexpected EOF in prolog" errorStrange, can you post a bug here http://forge.objectweb.org/tracker/?group_id=213 ?
On Tue, Sep 23, 2008 at 4:27 PM, Richard AILLET <richard.aillet@...> wrote:
-- Christophe Hamerling PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing http://petals.ow2.org http://petals.ebmwebsourcing.com Phone : +33534320314 Skype : christophe.hamerling -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
| Free embeddable forum powered by Nabble | Forum Help |