Re: [Axis2] - Production problem
Hi Guido, your service running on production server isn't able to connect to a local service? Maybe the ports are not open for connection from production area to your local network? I know, it's the same network, you said. Is it really? Are you able to reach ip:port of A from C manually? Thanks. Markus Barbaglia, Guido (ESTG) schrieb: Each node has send/receive capabilities, so the service is running on every node. But I have the "did not accept connection" error even with a simple ping service. I've checked the network configuration and everything seems ok, moreover all the 'nodes' belong to the same network, the only difference with node C is that it can be accessed by external browsers. If I try a ping or resources exchange between A and B (my development laptops) everything works fine, when I try the same between A/B and C (which has its own installation with the same software) things fail... I've tried to increase the timeout but the problem is the same. What can I try? Best regards Guido Barbaglia -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Fri 10/24/2008 12:55 PM To: axis-user@ws.apache.org Cc: Subject:Re: [Axis2] - Production problem Guido, On 24 Oct 2008, at 11:08, Barbaglia, Guido (ESTG) wrote: I've tested my Axis2 application on two machines (let's say A and B) belonging to the same local network, and everything works very well. Then I installed it on a production server C (with pubblic access and belonging to the same network) and I tried to test the communication between A and C, but I had connection timeout problem. It seems that node A did not accept the connection within timeout of xyz ms from the node C. isn't your service running on node C? If so, why did you state "it seems that node A did not accept the connection..."? BTW, could it be a firewall/proxy/network configuration issue? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ANON_OUT_IN_OP and HTTP 202 Status Code
Sorry, I was wrong. HTTP allows a response, and at least SOAP 1.2 allows
a response with 202, but not specifies the behaviour. [1]
In Axis2, as I see, the org.apache.axis2.transport.http.HTTPSender
sender ignores the response and just drops the InputStream, in case of
status code 202 [2].
@all: What's your opinion?
Thanks,
Markus
[1] see
http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#http-reqbindrecstate
"The response MAY be of content type other than "application/soap+xml".
Such usage is considered non-normative, and accordingly is not modeled
in the state machine. Interpretation of such responses is at the
discretion of the receiver. Similarly, receipt of any response
entity-body with a status code of 202 is not normative. If such an
unexpected response is of type "application/soap+xml", then SOAP
processing of that response is beyond the scope of the specification for
this binding."
[2]
if (statusCode == HttpStatus.SC_OK) {
processResponse(method, msgContext);
} else if (statusCode == HttpStatus.SC_ACCEPTED) {
} else if (statusCode == HttpStatus.SC_INTERNAL_SERVER_ERROR || ...
Gordon Rogers schrieb:
>From my understanding status code 202 means that the service has
accepted the response and may process it. The HTTP spec does say that
the response should contain an indication of the request's current state
which I take it can mean that a payload is allowed.
The service I'm trying to build against specifies that an ebXML
acknowledgement will be returned on the same connection with a status
code of 202, so that's the behaviour I'm trying to mimic in my test
harness.
Will keep on investigating and post any findings.
Thanks,
Gordon
-Original Message-
From: Markus Tost [mailto:[EMAIL PROTECTED]
Sent: 26 September 2008 11:15
To: axis-user@ws.apache.org
Subject: Re: ANON_OUT_IN_OP and HTTP 202 Status Code
Hi Gordon,
why do you need to use status code 202? It's only for HTTP-Responses
without payload, isn't it?
I guess Axis2 transport mechanism drops the connection without getting
the InputStream in case of status code 202.
Thanks,
Markus
Gordon Rogers schrieb:
Hi
I'm having some difficulty with using the ANON_OUT_IN_OP MEP when the
status code of the response is not 200 ok. I'm implementing a
specification that takes a request and returns a response on the same
connection, but with a status code of 202. Since the request and
response are on the same connection I need to use the In-Out MEP, I
think.
Everything works fine when the service responds with a status code of
200, but as soon as I change the status code (and nothing else) the
following error occurs on the client:
org.apache.axis2.AxisFault: The input stream for an incoming message
is null.
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:72)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out
InAxisOperation.java:353)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
)
My request looks like:
POST /fis/FISservices/TestService HTTP/1.1
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456;
type="text/xml";
start="<0.urn:uuid:[EMAIL PROTECTED]>"
SOAPAction: "urn:anonOutInOp"
User-Agent: Axis2
Host: 127.0.0.1
Transfer-Encoding: chunked
940
--MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <0.urn:uuid:[EMAIL PROTECTED]>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-head
er-2_0.xsd">
from_party
to_party
1234-5678-9012-3456
9ddf202fc0a800e600f4f44a53ab205c
service
action
9ddf1f15c0a800e600f4f44af5c3e3d2
2008-09-26T09:55:57.743+01:00
eb:version="2.0" eb:actor="actor" />
http://www.w3.org/1999/xlink";
axis2ns3:href="urn:uuid:41FA027BFE1CB14DFB1222419357634" />
b44
--MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456
[... I've left of the attachment for brevity ...]
My response looks like:
HTTP/1.1 100 Continue
Server: Oracle Application Server Containers for J2EE 10g (9.0.4.2.0)
Date: Fri, 26 Sep 2008 08:55:57 GMT
HTTP/1.1 202 Accepted
Date: Fri, 26 Sep 2008 08:55:58 GMT
Server: Oracle Application Server Containers for J2EE 10g (9.0.4.2.0)
Connection: Close
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
113
xmlns
Re: ANON_OUT_IN_OP and HTTP 202 Status Code
Hi Gordon, why do you need to use status code 202? It's only for HTTP-Responses without payload, isn't it? I guess Axis2 transport mechanism drops the connection without getting the InputStream in case of status code 202. Thanks, Markus Gordon Rogers schrieb: Hi I’m having some difficulty with using the ANON_OUT_IN_OP MEP when the status code of the response is not 200 ok. I’m implementing a specification that takes a request and returns a response on the same connection, but with a status code of 202. Since the request and response are on the same connection I need to use the In-Out MEP, I think. Everything works fine when the service responds with a status code of 200, but as soon as I change the status code (and nothing else) the following error occurs on the client: org.apache.axis2.AxisFault: The input stream for an incoming message is null. at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:72) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) My request looks like: POST /fis/FISservices/TestService HTTP/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456; type="text/xml"; start="<0.urn:uuid:[EMAIL PROTECTED]>" SOAPAction: "urn:anonOutInOp" User-Agent: Axis2 Host: 127.0.0.1 Transfer-Encoding: chunked 940 --MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <0.urn:uuid:[EMAIL PROTECTED]> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd";> from_party to_party 1234-5678-9012-3456 9ddf202fc0a800e600f4f44a53ab205c service action 9ddf1f15c0a800e600f4f44af5c3e3d2 2008-09-26T09:55:57.743+01:00 eb:version="2.0" eb:actor="actor" /> http://www.w3.org/1999/xlink"; axis2ns3:href="urn:uuid:41FA027BFE1CB14DFB1222419357634" /> b44 --MIMEBoundaryurn_uuid_41FA027BFE1CB14DFB1222419358456 [... I’ve left of the attachment for brevity ...] My response looks like: HTTP/1.1 100 Continue Server: Oracle Application Server Containers for J2EE 10g (9.0.4.2.0) Date: Fri, 26 Sep 2008 08:55:57 GMT HTTP/1.1 202 Accepted Date: Fri, 26 Sep 2008 08:55:58 GMT Server: Oracle Application Server Containers for J2EE 10g (9.0.4.2.0) Connection: Close Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked 113 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> 0 I’m hoping there’s something obvious I’m missing as I don’t think any of the other message patterns match what I need. Thanks in advance for any help. If you need more information let me know. Gordon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP Faults and the SOAP specification
Moin, the FaultCode relates to SOAP 1.1. As the namespace of your Enevelop is SOAP 1.1 NS, "Server" is correct here. See: http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383510 Cheers, Markus Tobias Anstett schrieb: Hi, I am a little bit confused of the SOAP12 implementation of axis2 (1.4). When my web service throws a standard AxisFault without specifying the fault code manually, soapUI receives the following message: xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> soapenv:Server unknown The reason for this post is that I am not familiar with the fault code “Server”, because the soap 1.2 specification states that there are only the following fault codes: (http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#faultcodes) - VersionMismatch - MustUnderstand - DataEncodingUnknown - Sender - Receiver So, have I got something wrong ? Cheers, Tobias P.S.: I know how to set the code manually, this question is just for my understanding of axis and soap - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom MEP sample impl?
Deepal jayasinghe wrote: Markus Tost wrote: Hi, I want to implement custom MEPs with Axis2. As I see so far, I have to extend the OperationClient and the OperationContext. Also a custom MessageReceiver may be needed. If you are going to implement that in the server side then you do not need to extend OperationClient. And also OperationContext is generic , what you have to implement is new AxisOperation and a MessageReceiver. Actually, I want to implement both the server side and the client side. They will have "matching" MEPs, e.g. In-Out-In at server side and Out-In-Out at client side. Good point about the description class(es). I shouldn't forget them. Is there any sample code of a MEP implementation which goes beyond the request-response style of the built-in WSDL 2.0 MEPs (e.g. Out-In-In, Out-Out-In, In-In-Out)? Not in the Axis2 code base Are there any written tutorials / best practises / guidelines for implementing such custom MEPs? Would you share your experience with me? I will try to write a sample and a tutorial soon. (I was waiting until a user ask for such a request :) ) Sounds great! I'm looking forward to read it. :) Thank you! Markus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Custom MEP sample impl?
Hi, I want to implement custom MEPs with Axis2. As I see so far, I have to extend the OperationClient and the OperationContext. Also a custom MessageReceiver may be needed. Is there any sample code of a MEP implementation which goes beyond the request-response style of the built-in WSDL 2.0 MEPs (e.g. Out-In-In, Out-Out-In, In-In-Out)? Are there any written tutorials / best practises / guidelines for implementing such custom MEPs? Would you share your experience with me? Thanks in advance, Markus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
