Re: [Axis2][1.0] "Transport error 500" for EchoBlockingDualClient & echoF
Hi Deepal,
Thanks for the reply. I had already created a JIRA issue:
http://issues.apache.org/jira/browse/AXIS2-741
Regards,
Ali Sadik Kumlali
--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> create a JIRA
>
> Ali Sadik Kumlali wrote:
>
> >Hi all,
> >
> >When I use EchoBlockingDualClient to invoke echoF service which
> throws
> >AxisFault, I run into a strange(?) situation.
> >
> >Server returnes back an error through the *first* channel. Error
> says
> >"Transport error 500 . Error Message is Apache
> >Tomcat/5.5.14 - Error report...".
> >
> >Then the server sends the actual error over the *second* channel.
> >
> >When I look at the server logs, AxisFault thrown by echoF is shown.
> >There seems no transport related errors.
> >
> >However, client *only* catches the first error and writes it down to
> >the console. Then, it throws another exception that says
> >"org.apache.axis2.AxisFault: Time out while waiting for the server
> to
> >send the response"
> >
> >I've listed echoF and the client side stack trace below.
> >
> >Is this the expected behaviour or should I create a JIRA log?
> >
> >Thanks in advance,
> >
> >Ali Sadik Kumlali
> >
> >
> >
> >public OMElement echoF(OMElement element) throws AxisFault {
> > throw new AxisFault("MyFault message", "MyFaultCode");
> >}
> >
> >
> >- Transport error 500 . Error Message is Apache
> >Tomcat/5.5.14 - Error report
> >HTTP Status 500 - >noshade="noshade">type Status reportmessage
> >description The server encountered an
> internal
> >error () that prevented it from fulfilling this request. >size="1" noshade="noshade">Apache
> Tomcat/5.5.14;
> >nested exception is:
> >...
> >
> >
> >org.apache.axis2.AxisFault: Time out while waiting for the server to
> >send the response[SimpleHTTPServer] Stop called
> > at
>
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:448)
> > at
>
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
> > at
>
>userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:54)
> >
> >
> >__
> >Do You Yahoo!?
> >Tired of spam? Yahoo! Mail has the best spam protection around
> >http://mail.yahoo.com
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
>
> ~Future is Open~
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][1.0] "Transport error 500" for EchoBlockingDualClient & echoF
create a JIRA
Ali Sadik Kumlali wrote:
>Hi all,
>
>When I use EchoBlockingDualClient to invoke echoF service which throws
>AxisFault, I run into a strange(?) situation.
>
>Server returnes back an error through the *first* channel. Error says
>"Transport error 500 . Error Message is Apache
>Tomcat/5.5.14 - Error report...".
>
>Then the server sends the actual error over the *second* channel.
>
>When I look at the server logs, AxisFault thrown by echoF is shown.
>There seems no transport related errors.
>
>However, client *only* catches the first error and writes it down to
>the console. Then, it throws another exception that says
>"org.apache.axis2.AxisFault: Time out while waiting for the server to
>send the response"
>
>I've listed echoF and the client side stack trace below.
>
>Is this the expected behaviour or should I create a JIRA log?
>
>Thanks in advance,
>
>Ali Sadik Kumlali
>
>
>
>public OMElement echoF(OMElement element) throws AxisFault {
> throw new AxisFault("MyFault message", "MyFaultCode");
>}
>
>
>- Transport error 500 . Error Message is Apache
>Tomcat/5.5.14 - Error report
>HTTP Status 500 - noshade="noshade">type Status reportmessage
>description The server encountered an internal
>error () that prevented it from fulfilling this request.size="1" noshade="noshade">Apache Tomcat/5.5.14;
>nested exception is:
>...
>
>
>org.apache.axis2.AxisFault: Time out while waiting for the server to
>send the response[SimpleHTTPServer] Stop called
> at
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:448)
> at
>org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
> at
>userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:54)
>
>
>__
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>
>
>
--
Thanks,
Deepal
~Future is Open~
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][1.0] "Transport error 500" for EchoBlockingDualClient & echoF
Hi,
Since I beleive this is a bug, to enable easier following, I created a
JIRA log: http://issues.apache.org/jira/browse/AXIS2-741
Since separate listener case is very important, I beleive this is
actually a blocker issue. (If I'm not missing something ;-)
Regards,
Ali Sadik Kumlali
--- Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> When I use EchoBlockingDualClient to invoke echoF service which
> throws
> AxisFault, I run into a strange(?) situation.
>
> Server returnes back an error through the *first* channel. Error says
> "Transport error 500 . Error Message is Apache
> Tomcat/5.5.14 - Error report...".
>
> Then the server sends the actual error over the *second* channel.
>
> When I look at the server logs, AxisFault thrown by echoF is shown.
> There seems no transport related errors.
>
> However, client *only* catches the first error and writes it down to
> the console. Then, it throws another exception that says
> "org.apache.axis2.AxisFault: Time out while waiting for the server to
> send the response"
>
> I've listed echoF and the client side stack trace below.
>
> Is this the expected behaviour or should I create a JIRA log?
>
> Thanks in advance,
>
> Ali Sadik Kumlali
>
>
>
> public OMElement echoF(OMElement element) throws AxisFault {
> throw new AxisFault("MyFault message", "MyFaultCode");
> }
>
>
> - Transport error 500 . Error Message is Apache
> Tomcat/5.5.14 - Error report
> HTTP Status 500 - noshade="noshade">type Status reportmessage
> description The server encountered an
> internal
> error () that prevented it from fulfilling this request. size="1" noshade="noshade">Apache
> Tomcat/5.5.14;
> nested exception is:
> ...
>
>
> org.apache.axis2.AxisFault: Time out while waiting for the server to
> send the response[SimpleHTTPServer] Stop called
> at
>
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:448)
> at
>
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
> at
>
userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:54)
>
>
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Axis2][1.0] "Transport error 500" for EchoBlockingDualClient & echoF
Hi all,
When I use EchoBlockingDualClient to invoke echoF service which throws
AxisFault, I run into a strange(?) situation.
Server returnes back an error through the *first* channel. Error says
"Transport error 500 . Error Message is Apache
Tomcat/5.5.14 - Error report...".
Then the server sends the actual error over the *second* channel.
When I look at the server logs, AxisFault thrown by echoF is shown.
There seems no transport related errors.
However, client *only* catches the first error and writes it down to
the console. Then, it throws another exception that says
"org.apache.axis2.AxisFault: Time out while waiting for the server to
send the response"
I've listed echoF and the client side stack trace below.
Is this the expected behaviour or should I create a JIRA log?
Thanks in advance,
Ali Sadik Kumlali
public OMElement echoF(OMElement element) throws AxisFault {
throw new AxisFault("MyFault message", "MyFaultCode");
}
- Transport error 500 . Error Message is Apache
Tomcat/5.5.14 - Error report
HTTP Status 500 - type Status reportmessage
description The server encountered an internal
error () that prevented it from fulfilling this request.Apache Tomcat/5.5.14;
nested exception is:
...
org.apache.axis2.AxisFault: Time out while waiting for the server to
send the response[SimpleHTTPServer] Stop called
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:448)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
at
userguide.clients.EchoBlockingDualClient.main(EchoBlockingDualClient.java:54)
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
