osdir.com
mailing list archive

Subject: RE: Http-Binding Example - msg#00028

List: java.servicemix.user

Date: Prev Next Index Thread: Prev Next Index
Just in case others are having the same issue, turns out that I needed
to get to version 2.0.3 for this example to work properly.

-----Original Message-----
From: Blitzer, Brian L
Sent: Thursday, December 29, 2005 11:39 AM
To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx
Subject: RE: [servicemix-user] Http-Binding Example

I added some debugging in the HelloWorldComponent.java file in the
servicemix-web war. I am running tomcat-5.5.12 and have tried java 1.5.4
and 1.5.6. The results of the http get do not change still
<hello>null</hello>.

NormalizedMessage Content:StringSource[<payload/>] NormalizedMessage
Property Names:[] NormalizedMessage Attachment Names:[] MessageExchange
EndPointName:echo MessageExchange PropertyNames:[connection, host,
javax.jbi.messaging.sendSync, user-agent, referer, accept-language,
cookie, accept] MessageExchange Status:Active this.description:POJO
Component this.endpoint:echo this.CurrentState:Running

Any ideas?

-Brian Blitzer

-----Original Message-----
From: Blitzer, Brian L
Sent: Tuesday, December 27, 2005 4:47 PM
To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx
Subject: RE: [servicemix-user] Http-Binding Example

Thanks Guillaume worked like a charm. I have a few questions to the
group on the tomcat integration portion of servicemix.
I downloaded tomcat version 5.5.12 built and deployed the servicemix-web
war and I can see the following:
The JMX view where I can see the JMXServlet, Bindings, etc. I get to the
http://localhost:8080/servicemix-web/examples/ page and I can see the
form with the text input field and the submit button. When I hit submit
the response is <hello>null</hello>.

My other question is really when servicemix is run in a large
(critical/clustered) environment, is it embedded in a web
server/container like tomcat or is it run as a stand-alone?
Thanks
Brian



-----Original Message-----
From: Guillaume Nodet
[mailto:guillaume.nodet-s1sOSHjJPfVQTA9JCo65QQ@xxxxxxxxxxxxxxxx]
Sent: Tuesday, December 27, 2005 3:37 PM
To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx
Subject: Re: [servicemix-user] Http-Binding Example

The java.util.Collections.emptyList is JDK 5 specific.
Could you provide the whole stack trace, so that we can locate this
error more precisely ?

For a workaround, you may want to use JDK 5.

Cheers,
Guillaume Nodet

Blitzer, Brian L wrote:

>Hello all, I am having trouble executing the http-binding example and I

>do not think I should. I start the example following the README and the

>servicemix site. The server seems to startup properly (I am using the
>SNAPSHOT 2.1) When I call the HttpClient the server throws this
>exception:
>DEBUG - AbstractFlow.send(117) | Called Flow send DEBUG -
>AbstractFlow.doRouting(175) | Called Flow doRouting WARN -
>ServletHandler.handle(618) | Error for /
>java.lang.NoSuchMethodError:
>java.util.Collections.emptyList()Ljava/util/List; at
>com.sun.xml.messaging.saaj.soap.MessageImpl.<clinit>(MessageImpl.java
>:736)
>
>The error I get when running the HttpClient through ant is :
> [java] java.io.IOException: Server returned HTTP response code:
>500 for URL: http://localhost:8912
> [java] at
>sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConne
>c
>tion.java:791)
> [java] at HttpClient.main(Unknown Source)
>
>When I start servicemix and then look at http://localhost:8912 I get
>this error:
>HTTP ERROR: 500
>java.util.Collections.emptyList()Ljava/util/List;
>RequestURI=/
>I am new to servicemix so I thought that I must be missing something
>really simple. I appreciate any help.
>
>
>Brian L Blitzer
>
>
>-----------------------------------------------------------------------
>-------
>----
>This message is intended only for the personal and confidential use of
the designated recipient(s) named. If you are not the intended recipient
of this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be
regarded as an offer to sell or as a solicitation of an offer to buy any
financial product, an official confirmation of any transaction, or as an
official statement of Aurora Loan Services. Email transmission cannot be
guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be
relied upon as such. All information is subject to change without
notice.
>
>
>
>
>






------------------------------------------------------------------------
------
----
This message is intended only for the personal and confidential use of
the designated recipient(s) named. If you are not the intended recipient
of this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be
regarded as an offer to sell or as a solicitation of an offer to buy any
financial product, an official confirmation of any transaction, or as an
official statement of Aurora Loan Services. Email transmission cannot be
guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be
relied upon as such. All information is subject to change without
notice.



------------------------------------------------------------------------
------
This message is intended only for the personal and confidential use of
the designated recipient(s) named. If you are not the intended recipient
of this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be
regarded as an offer to sell or as a solicitation of an offer to buy any
financial product, an official confirmation of any transaction, or as an
official statement of Aurora Loan Services. Email transmission cannot be
guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be
relied upon as such. All information is subject to change without
notice.




------------------------------------------------------------------------
------
----
This message is intended only for the personal and confidential use of
the designated recipient(s) named. If you are not the intended recipient
of this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be
regarded as an offer to sell or as a solicitation of an offer to buy any
financial product, an official confirmation of any transaction, or as an
official statement of Aurora Loan Services. Email transmission cannot be
guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be
relied upon as such. All information is subject to change without
notice.



------------------------------------------------------------------------
------
----
This message is intended only for the personal and confidential use of
the designated recipient(s) named. If you are not the intended recipient
of this message, you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be
regarded as an offer to sell or as a solicitation of an offer to buy any
financial product, an official confirmation of any transaction, or as an
official statement of Aurora Loan Services. Email transmission cannot be
guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be
relied upon as such. All information is subject to change without
notice.




------------------------------------------------------------------------------
----
This message is intended only for the personal and confidential use of the
designated recipient(s) named. If you are not the intended recipient of this
message, you are hereby notified that any review, dissemination, distribution
or copying of this message is strictly prohibited. This communication is for
information purposes only and should not be regarded as an offer to sell or as
a solicitation of an offer to buy any financial product, an official
confirmation of any transaction, or as an official statement of Aurora Loan
Services. Email transmission cannot be guaranteed to be secure or error-free.
Therefore, we do not represent that this information is complete or accurate
and it should not be relied upon as such. All information is subject to change
without notice.




Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

RE: Problems with JSM flow and SOAP messages

The SaajMarshaller now works as expected. The HttpSoapConnector, however, using Xfire, still fails to copy the xmlns information from within the SOAP envelope. > -----Original Message----- > From: Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx > [mailto:Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx] > Sent: Thursday, January 05, 2006 10:45 AM > To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > Subject: RE: [servicemix-user] Problems with JSM flow and > SOAP messages > > > Guillaume, > > I will test the revised class ASAP. > > Do you know if it will be possible to modify the Xfire > classes to preserve > XML namespace information when stripping the SOAP envelope? > > /jonathan > > > -----Original Message----- > > From: Guillaume Nodet > > [mailto:guillaume.nodet-s1sOSHjJPfVQTA9JCo65QQ@xxxxxxxxxxxxxxxx] > > Sent: Thursday, January 05, 2006 4:24 AM > > To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > Subject: Re: [servicemix-user] Problems with JSM flow and > > SOAP messages > > > > > > ServiceMix uses axis-1.3, but it seems there may be some differences > > between the sun saaj for namespace / attributes handling on > > soap elements. > > Sun does not use namespaces, whereas axis do not include namespace > > declaration > > in attributes. So i had to put both codes ... > > > > I think the problem can finally be closed. Could you > confirm please ? > > > > Cheers, > > Guillaume Nodet > > > > Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx wrote: > > > > >Guillaume, > > > > > >Any luck with reproducing the error that I had described (using the > > >different versions of the SaajMarshaller and HttpInOutBinding)? > > > > > >Also, have you taken a look at the potential namespace issue > > in the HttpSoap > > >layer (where incoming SOAP messages have partial namespace > > reproduction)? > > > > > >/jonathan > > > > > > > > > > > >>-----Original Message----- > > >>From: Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx > > >>[mailto:Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx] > > >>Sent: Friday, December 30, 2005 12:02 PM > > >>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>Subject: RE: [servicemix-user] Problems with JSM flow and > > >>SOAP messages > > >> > > >> > > >>Guillaume, > > >> > > >>One more thing: Can you verify that the HttpInOutBinding > > (and related > > >>components) is properly capturing all of the namespaces when > > >>stripping the > > >>SOAP-ENV? It seems like the inbound request messages are > > >>missing the "d" > > >>namespace. The SaajMarshaller is ok. > > >> > > >>/jonathan > > >> > > >> > > >> > > >>>-----Original Message----- > > >>>From: Guillaume Nodet > > >>>[mailto:guillaume.nodet-s1sOSHjJPfVQTA9JCo65QQ@xxxxxxxxxxxxxxxx] > > >>>Sent: Friday, December 30, 2005 1:42 AM > > >>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>Subject: Re: [servicemix-user] Problems with JSM flow and > > >>>SOAP messages > > >>> > > >>> > > >>>This seems strange, as my test case fails with the old > > >>> > > >>> > > >>SaajMarshaler > > >> > > >> > > >>>code, and works with the new one. > > >>>I changed, but i was quite sure it was working before, > as you said. > > >>>It may be related to class loader issues, if the library > > >>> > > >>> > > >>used are not > > >> > > >> > > >>>the same : we recently changed > > >>>to maven 2, so that the order of included jars ma be > > >>> > > >>> > > >>different. I'll > > >> > > >> > > >>>try to investigate it. > > >>> > > >>>Guillaume > > >>> > > >>>Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx wrote: > > >>> > > >>> > > >>> > > >>>>Guillaume, > > >>>> > > >>>>If I use only the modified HttpInOutBinding, and the older > > >>>> > > >>>> > > >>>SaajMarshaller > > >>> > > >>> > > >>>>(with the org.w3c.dom.Attr import), everything works > > >>>> > > >>>> > > >>>properly. This leads me > > >>> > > >>> > > >>>>to believe that there is an issue with the latest changes to the > > >>>>SaajMarshaller. > > >>>> > > >>>>/jonathan > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>>>-----Original Message----- > > >>>>>From: Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx > > [mailto:Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx] > > >>>>>Sent: Thursday, December 29, 2005 7:44 PM > > >>>>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>>>Subject: RE: [servicemix-user] Problems with JSM flow and > > >>>>>SOAP messages > > >>>>> > > >>>>> > > >>>>>I rebuilt using the full files from Apache-HEAD, but get the > > >>>>>same namespace > > >>>>>issues; no "d". I am trying to narrow down the problem on my > > >>>>>end. Should I > > >>>>>use all of the latest components in http and saaj? > > >>>>> > > >>>>>/jonathan > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>>-----Original Message----- > > >>>>>>From: Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx > > >>>>>> > > >>>>>> > > >>[mailto:Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx] > > >> > > >> > > >>>>>>Sent: Thursday, December 29, 2005 6:53 PM > > >>>>>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>>>>Subject: RE: [servicemix-user] Problems with JSM flow and > > >>>>>>SOAP messages > > >>>>>> > > >>>>>> > > >>>>>>This is for a slightly different service, but the basic > > >>>>>> > > >>>>>> > > >>problem is > > >> > > >> > > >>>>>>illustrated. Your example has the "d" xmlns, but my result > > >>>>>>does not. On > > >>>>>>further review, my source classes were slightly out of date > > >>>>>>with yours. I > > >>>>>>will try again tomorrow morning using the straight java > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>files from the > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>>Apache-HEAD (with package corrections), and let you know if > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>the issue > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>>persists. > > >>>>>> > > >>>>>><?xml version="1.0" encoding="UTF-8" standalone="yes"?> > > >>>>>><soap:Envelope > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > >>>>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > > >>>>>> <soap:Body> > > >>>>>> <wn2:getPersonResponse > > >>>>>>xmlns:wn2="http://systinet.com/wsdl/com/cexp/ws/test/"> > > >>>>>> <wn2:response i:type="wn2:Person" > > >>>>>> > > >>>>>> > > >>>>>> > > >>>xmlns:i="http://www.w3.org/2001/XMLSchema-instance" > > >>> > > >>> > > >>>>>> > > >>>>>>xmlns:wn2="http://systinet.com/wsdl/com/cexp/ws/test/"> > > >>>>>> <wn2:description i:type="d:string" > > >>>>>> > > >>>>>>xmlns:wn2="http://systinet.com/wsdl/com/cexp/ws/test/">Desktop > > >>>>>>customizer > > >>>>>>(1135883476645)</wn2:description> > > >>>>>> <wn2:firstName i:type="d:string" > > >>>>>>xmlns:wn2="http://systinet.com/wsdl/com/cexp/ws/test/">Jonatha > > >>>>>>n</wn2:firstNa > > >>>>>>me> > > >>>>>> <wn2:lastName i:type="d:string" > > >>>>>>xmlns:wn2="http://systinet.com/wsdl/com/cexp/ws/test/">Edwards > > >>>>>></wn2:lastName > > >>>>>> > > >>>>>> > > >>>>>> </wn2:response> > > >>>>>> </wn2:getPersonResponse> > > >>>>>> </soap:Body> > > >>>>>></soap:Envelope> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>>-----Original Message----- > > >>>>>>>From: Guillaume Nodet > > >>>>>>>[mailto:guillaume.nodet-s1sOSHjJPfVQTA9JCo65QQ@xxxxxxxxxxxxxxxx] > > >>>>>>>Sent: Thursday, December 29, 2005 1:16 PM > > >>>>>>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>>>>>Subject: Re: [servicemix-user] Problems with JSM flow and > > >>>>>>>SOAP messages > > >>>>>>> > > >>>>>>> > > >>>>>>>I have a test case which is the same as yours (or should be) > > >>>>>>>and the result I have is the following : > > >>>>>>> > > >>>>>>><?xml version="1.0" encoding="UTF-8"?> > > >>>>>>><soap:Envelope > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > >>>>>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > > >>>>>>> <soap:Body> > > >>>>>>> <wn1:getCustomerInfo > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>xmlns:d="http://www.w3.org/2001/XMLSchema" > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>>> xmlns:e="http://schemas.xmlsoap.org/soap/envelope/" > > >>>>>>> xmlns:i="http://www.w3.org/2001/XMLSchema-instance" > > >>>>>>> xmlns:wn0="http://systinet.com/xsd/SchemaTypes/" > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>xmlns:wn1="http://systinet.com/wsdl/com/cexp/coe/bob/ws/ > > customer/" > > >>>>>> > > >>>>>> > > >>>>>>> xmlns:wn2="http://systinet.com/soap-jta/" > > > >>>>>>>xmlns:wn3="http://systinet.com/wsdl/com/cexp/coe/bob/services/ > > >>>>>>>order/pojo/"> > > >>>>>>> <wn1:userId i:type="d:string" > > > >>>>>>>xmlns:wn1="http://systinet.com/wsdl/com/cexp/coe/bob/ws/custom > > >>>>>>>er/">akayali</wn1:userId> > > >>>>>>> </wn1:getCustomerInfo> > > >>>>>>> </soap:Body> > > >>>>>>></soap:Envelope> > > >>>>>>> > > >>>>>>>This one seems good. > > >>>>>>>What is the exact result you have ? > > >>>>>>> > > >>>>>>>Cheers, > > >>>>>>>Guillaume Nodet > > >>>>>>> > > >>>>>>>Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx wrote: > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>Guillaume, > > >>>>>>>> > > >>>>>>>>After applying the changes that you sent me in the diff > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>links the JMS flow > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>now returns the full SOAP body. However, the SOAP messages > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>are now missing > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>the "i" and "d" namespaces that you had worked on fixing > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>last week. > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>>/jonathan > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>>>-----Original Message----- > > >>>>>>>>>From: Guillaume Nodet > [mailto:guillaume.nodet-s1sOSHjJPfVQTA9JCo65QQ@xxxxxxxxxxxxxxxx] > > >>>>>>>>>Sent: Thursday, December 29, 2005 2:51 AM > > >>>>>>>>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>>>>>>>Subject: Re: [servicemix-user] Problems with JSM flow and > > >>>>>>>>>SOAP messages > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>You can grab the new versions of SaajMarshaler and > > >>>>>>>>>HttpSoapInOutBinding. > > >>>>>>>>>The problem should be fixed now. > > >>>>>>>>> > > >>>>>>>>>Here are the diffs you should report to your sources (the > > >>>>>>>>>package have > > >>>>>>>>>been renamed) > > >>>>>>>>> * > > >>>>>>>>>http://svn.apache.org/viewcvs.cgi/incubator/servicemi > > x/trunk/s > > >>>>>>>>>ervicemix-components/src/main/java/org/apache/service > > mix/compo > > >>>>>>>>>nents/http/HttpSoapInOutBinding.java?rev=359186&r1=35 > > 9767&r2=3 > > >>>>>>>>>59186&diff_format=h > > >>>>>>>>> * > > >>>>>>>>>http://svn.apache.org/viewcvs.cgi/incubator/servicemi > > x/trunk/s > > >>>>>>>>>ervicemix-components/src/main/java/org/apache/service > > mix/compo > > >>>>>>>>>nents/saaj/SaajMarshaler.java?rev=359186&r1=359767&r2 > > =359186&d > > >>>>>>>>>iff_format=h > > >>>>>>>>> > > >>>>>>>>>Cheers, > > >>>>>>>>>Guillaume Nodet > > >>>>>>>>> > > >>>>>>>>>Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx wrote: > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>Two steps forward, one step back, or so it seems. > > >>>>>>>>>> > > >>>>>>>>>>The jmsFlow seems to be broken - at least in my > > custom build > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>of ServiceMix. > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>The version of the codebase that I am using is 1055, with > > >>>>>>>>>>"servicemix/components/http/*" and > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>"servicemix/components/saaj/*" from the > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>Apache-HEAD. In addition, I am using the > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>xfire-all-1.0-20051222.jar. This is > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>happening using the Sun Java 5 JVM for both > ActiveMQ 3.2.1 > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>and ServiceMix. > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>With this build, the SEDA flow works properly, and the > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>client gets the > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>response from the invoked SOAP service (SOAP client -> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>HttpSoapClient -> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>SaajComponent -> SOAP service). When I change the flow to > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>JMS, using > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>>>ActiveMQ 3.2.1 with the "reliable" connect string, my > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>client throws a > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>>>NullPointerException. This is because the > SOAP-Body in the > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>response is > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>completely empty. I have verified that the body is > > populated > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>correclty by > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>the SaajComponent (visible in the DEBUG output in log4j), > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>but the actual > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>HttpResponse from the HttpSoapConnector has an empty > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>SOAP-Body. As this > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>problem only presents itself using the JMS flow, and only > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>surfaced after > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>using the newer classes and library, I am fairly certain > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>that these events > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>are all highly correlated, but I am not sure what > the root > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>cause is. I need > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>the new classes, and the newer xfire library in > > order for my > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>services to > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>call successfully under SEDA, and cannot revert. > > >>>>>>>>>> > > >>>>>>>>>>regards, > > >>>>>>>>>>/jonathan > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>>>-----Original Message----- > > >>>>>>>>>>>From: Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>[mailto:Jonathan.Edwards-JaHLKqi3HGE@xxxxxxxxxxxxxxxx] > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>>>>>>Sent: Wednesday, December 28, 2005 9:53 AM > > >>>>>>>>>>>To: user-DYbmDgQgSeCNERRUb84KwOb9Vox/ZU2A@xxxxxxxxxxxxxxxx > > >>>>>>>>>>>Subject: RE: [servicemix-user] Problems invoking a web > > >>>>>>>>>>>service with SOAP > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>>Guillaume, > > >>>>>>>>>>> > > >>>>>>>>>>>Installing the new Xfire library did the trick: The XML > > >>>>>>>>>>>returned from the > > >>>>>>>>>>>SaajComponent is well formed, and the HttpSoapConnector > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>handles the > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>>>>>Http+SOAP calls properly. Thanks to everyone who > helped me > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>to get Soap > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>> > > >>>>>>>>>>>communication working, especially Guillaume :-) > > >>>>>>>>>>> > > >>>>>>>>>>>Now I'm off to wrestle with the IBM Java 5 JVM > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>(beta) on AIX. > > >> > > >> > > >>>>>>>>>>>best wishes for the holidays, > > >>>>>>>>>>>/jonathan > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>> > > >>>> > > >>>> > > >>>> > > > > > > > > > > > > > > >

Next Message by Date: click to view message preview

JMS Flow Behavior in a Load-balanced environment

Fellow ServiceMix users and developers, I am experiencing some rather odd behavior when using the JMS Flow in a load balanced environment, that is, where http traffic is round robined between two HttpSoapConnectors running in separate ServiceMix containers. I'll illustrate the course of events below. 1. Start up two separate ActiveMQ 3.2.1 instances on two separate hosts, each pointing to the other via the <networkConnector> directive in the conf/activemq.xml file. 2. Startup two separate ServiceMix 2.x instances on two separate hosts, each pointing to both of the ActiveMQ instance started up in (1) via the flowName="jms?jmsURL=reliable(tcp://activeMQ_A, tcp://activeMQ_B)". 3. Deploy the same service assembly to each ServiceMix installation. The SA will create an HttpSoapConnector and SaajComponent. 4. From a SOAP+HTTP client, connect to http://serviceMix_A/HttpSoapConnector, which will take the SOAP message and send it to the SaajComponent. The SaajComponent will invoke a specified web service and then return the result back to the HttpSoapConnector, and finally back to the SOAP+HTTP client. The expected response is received. 5. Execute same flow from (4), but point to http://serviceMix_B/HttpSoapConnector. The expected response is received. 6. Kill serviceMix_A, the re-execute (5). The expected response may be returned, OR the call may hang with no visible errors. Things that I have noticed during steps (4) and (5): a. The debug output indicates that service execution is not confined to the container hosting the HttpSoapConnector being posted to. That is to say that any node of the cluster might execute the SaajComponent invocation; even though the SaajComponent service is deployed locally in the same container hosting the invoked HttpSoapConnector, a remote instance of the SaajComponent hosted by another node of the cluster might be invoked. (Please note that the ServiceMix instance have different named in the servicemix.xml file). Which instance of the SajjComponent that is invoked seems to be based upon which instance was first invoked (i.e. which ServiceMix instance was first part of the exchange). b. When one of the two nodes is shutdown, and the other node's HttpSoapConnector is invoked, the SaajComponent local to that active node may not ever be called; the JMS Flow seems to attempt an invocation of the SaajComponent hosted by the downed node. This can be verified by calling the same service multiple times: If the first invocation results in a timeout (because the cluster is trying to utilize the downed node), and the downed node is re-started, subsequent calls will succeed. c. If you kill one of the ActiveMQ instances once you enter the hung state, the flow will pick up correctly once the active ServiceMix node has failed-over to the secondary ActiveMQ node. So you would then have one ActiveMQ instance and one ServiceMix instance. Once you have killed and restarted the ActiveMQ instance, the problem may be very hard to recreate. It only seems to happen when the environment is brought up from scratch. This behavior makes no sense. I would expect that if a node of a cluster was shutdown BEFORE any calls were made, that all of the calls to the cluster would be honored by the active nodes. There are no exceptions being thrown by the bus, and no exceptions being thrown by ActiveMQ. As it is (with an Oracle DS in place for ActiveMQ OR with Derby), the JMS Flow results in a more fragile environment than simply running with SEDA flow and HTTP load balancing provided by Apache. I cannot imagine that this behavior is by design, but don't have any more information to help diagnose the error. Moreover, I am confused by the execution of services on a remote note, when the local node itself has a copy of the service. I would think that the local copy would be selected first; is there someway to enforce a "LOCAL_FIRST" policy, or is it not something that can be easily done (I know if two policies: RandomChoice and FirstChoice)? Does the bus know if a certain service is local or remote? I ask this question because with the current behavior (which sometimes selects remote over local), you cannot effectively load balance across multiple ServiceMix nodes when they are deployed ccntrally; service execution will take place on, at best, a subset of nodes (and that subset might only be one node). In summary, I have two questions herein: [1] How can you control service selection and execution in a cluster? [2] Why are the JMS Flow fragile to the point of haveing to bounce various parts when a node dies? Put another way, why can't I add and remove ServiceMix nodes without haveing to worry about re-starting one or more of the ActiveMQ nodes. regards, /jonathan

Previous Message by Thread: click to view message preview

ClassNotFoundException during installation

Hi! When I try to install zip deployment unit generated with maven JBI plugin I get ClassNotFoundException: org.servicemix.demo.QuartzComponent Quartz component is in example-client-quartz-1.0.jar My jbi.xml looks like this: <?xml version="1.0" encoding="UTF-8"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/jbi" version="1.0"> <component type="service-engine"> <identification> <name>example-client-quartz</name> <description>This is an example of a simple quartz scheduler component written using the ServiceMix Client infrastructure</description> </identification> <component-class-name description="Component Implementation">org.servicemix.client.SpringComponent</component-class-name> <component-class-path> <path-element>lib/example-client-quartz-1.0.jar</path-element> <path-element>lib/servicemix-client-2.1-SNAPSHOT.jar</path-element> <path-element>lib/quartz-1.4.0.jar</path-element> </component-class-path> </component><services binding-component="false" xmlns:quartz="http://tempuri.org/quartz" xmlns:logger="http://tempuri.org/logger.wsdl"> <consumes interface- name="quartz:triggeredNotification" service-name="logger:example" /> </services></jbi> debug nippet: INFO - XmlBeanDefinitionReader.loadBeanDefinitions(163) | Loading XML bean defin itions from file [D:\servicemix-2.1-SNAPSHOT\wdir\defaultJBI\components\example- client-quartz\version_1\installation\META-INF\jbi-spring.xml] ERROR - InstallationService.install(345) | Failed to start Component: example-cl ient-quartz javax.jbi.JBIException: Could not initialize component at org.servicemix.client.SpringComponentLifeCycle.init(SpringComponentLi feCycle.java:139) at org.servicemix.jbi.framework.LocalComponentConnector.init(LocalCompon entConnector.java:230) at org.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBea nImpl.java:125) at org.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanI mpl.java:93) at org.servicemix.jbi.framework.InstallationService.install(Installation Service.java:336) at org.servicemix.jbi.framework.AutoDeploymentService.updateArchive(Auto DeploymentService.java:204) at org.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoDeployme ntService.java:485) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja va:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So urce) at java.lang.Thread.run(Thread.java:595) Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'myQuartzService' defined in file [D:\servicemix-2.1 -SNAPSHOT\wdir\defaultJBI\components\example-client-quartz\version_1\installatio n\META-INF\jbi-spring.xml]: Bean class [org.servicemix.demo.QuartzComponent] not found; nested exception is java.lang.ClassNotFoundException: org.servicemix.dem o.QuartzComponent ... Cheers, Simon

Next Message by Thread: click to view message preview

JMS Flow Behavior in a Load-balanced environment

Fellow ServiceMix users and developers, I am experiencing some rather odd behavior when using the JMS Flow in a load balanced environment, that is, where http traffic is round robined between two HttpSoapConnectors running in separate ServiceMix containers. I'll illustrate the course of events below. 1. Start up two separate ActiveMQ 3.2.1 instances on two separate hosts, each pointing to the other via the <networkConnector> directive in the conf/activemq.xml file. 2. Startup two separate ServiceMix 2.x instances on two separate hosts, each pointing to both of the ActiveMQ instance started up in (1) via the flowName="jms?jmsURL=reliable(tcp://activeMQ_A, tcp://activeMQ_B)". 3. Deploy the same service assembly to each ServiceMix installation. The SA will create an HttpSoapConnector and SaajComponent. 4. From a SOAP+HTTP client, connect to http://serviceMix_A/HttpSoapConnector, which will take the SOAP message and send it to the SaajComponent. The SaajComponent will invoke a specified web service and then return the result back to the HttpSoapConnector, and finally back to the SOAP+HTTP client. The expected response is received. 5. Execute same flow from (4), but point to http://serviceMix_B/HttpSoapConnector. The expected response is received. 6. Kill serviceMix_A, the re-execute (5). The expected response may be returned, OR the call may hang with no visible errors. Things that I have noticed during steps (4) and (5): a. The debug output indicates that service execution is not confined to the container hosting the HttpSoapConnector being posted to. That is to say that any node of the cluster might execute the SaajComponent invocation; even though the SaajComponent service is deployed locally in the same container hosting the invoked HttpSoapConnector, a remote instance of the SaajComponent hosted by another node of the cluster might be invoked. (Please note that the ServiceMix instance have different named in the servicemix.xml file). Which instance of the SajjComponent that is invoked seems to be based upon which instance was first invoked (i.e. which ServiceMix instance was first part of the exchange). b. When one of the two nodes is shutdown, and the other node's HttpSoapConnector is invoked, the SaajComponent local to that active node may not ever be called; the JMS Flow seems to attempt an invocation of the SaajComponent hosted by the downed node. This can be verified by calling the same service multiple times: If the first invocation results in a timeout (because the cluster is trying to utilize the downed node), and the downed node is re-started, subsequent calls will succeed. c. If you kill one of the ActiveMQ instances once you enter the hung state, the flow will pick up correctly once the active ServiceMix node has failed-over to the secondary ActiveMQ node. So you would then have one ActiveMQ instance and one ServiceMix instance. Once you have killed and restarted the ActiveMQ instance, the problem may be very hard to recreate. It only seems to happen when the environment is brought up from scratch. This behavior makes no sense. I would expect that if a node of a cluster was shutdown BEFORE any calls were made, that all of the calls to the cluster would be honored by the active nodes. There are no exceptions being thrown by the bus, and no exceptions being thrown by ActiveMQ. As it is (with an Oracle DS in place for ActiveMQ OR with Derby), the JMS Flow results in a more fragile environment than simply running with SEDA flow and HTTP load balancing provided by Apache. I cannot imagine that this behavior is by design, but don't have any more information to help diagnose the error. Moreover, I am confused by the execution of services on a remote note, when the local node itself has a copy of the service. I would think that the local copy would be selected first; is there someway to enforce a "LOCAL_FIRST" policy, or is it not something that can be easily done (I know if two policies: RandomChoice and FirstChoice)? Does the bus know if a certain service is local or remote? I ask this question because with the current behavior (which sometimes selects remote over local), you cannot effectively load balance across multiple ServiceMix nodes when they are deployed ccntrally; service execution will take place on, at best, a subset of nodes (and that subset might only be one node). In summary, I have two questions herein: [1] How can you control service selection and execution in a cluster? [2] Why are the JMS Flow fragile to the point of haveing to bounce various parts when a node dies? Put another way, why can't I add and remove ServiceMix nodes without haveing to worry about re-starting one or more of the ActiveMQ nodes. regards, /jonathan
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by