You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Timour Mouratov <mt...@gmail.com> on 2005/03/22 17:26:19 UTC

"Invocation arguments were modified" exception in HandlerChainImpl class

Hello, 

We've started getting the following exception in axis 1.2RC2+: 

java.lang.RuntimeException: Invocation arguments were modified
at org.apache.axis.handlers.HandlerChainImpl.postInvoke(HandlerChainImpl.java:201)
at org.apache.axis.handlers.HandlerChainImpl.handleRequest(HandlerChainImpl.java:154)

Some special(maintenance)  requests that come to axis service are
blocked by our rpc handler. When handler catches special type of
request  it _empties_ it and returns false from 
handleRequest(MessageContext context) method , and this is the moment
when exception occurs.

I checked the CVS and found that modification were made to
org.apache.axis.handlers.HandlerChainImpl (revision 1.16). There is if
statement now in "postInvoke" method (line 199)  that checks cached
value of jaxrpc method info with actual one. In our case they are not
equal because our handler _emptied_  a message.

Is this is proper behaviour or a bug ? 

Thanks. 
Timour

Re: "Invocation arguments were modified" exception in HandlerChainImpl class

Posted by Timour Mouratov <mt...@gmail.com>.

It's even more restricted, I can not modify (remove or replace) a soap
body child anywhere in rpc handler.

On Tue, 22 Mar 2005 11:26:19 -0500, Timour Mouratov <mt...@gmail.com> wrote:
> Hello,
> 
> We've started getting the following exception in axis 1.2RC2+:
> 
> java.lang.RuntimeException: Invocation arguments were modified
> at org.apache.axis.handlers.HandlerChainImpl.postInvoke(HandlerChainImpl.java:201)
> at org.apache.axis.handlers.HandlerChainImpl.handleRequest(HandlerChainImpl.java:154)
> 
> Some special(maintenance)  requests that come to axis service are
> blocked by our rpc handler. When handler catches special type of
> request  it _empties_ it and returns false from
> handleRequest(MessageContext context) method , and this is the moment
> when exception occurs.
> 
> I checked the CVS and found that modification were made to
> org.apache.axis.handlers.HandlerChainImpl (revision 1.16). There is if
> statement now in "postInvoke" method (line 199)  that checks cached
> value of jaxrpc method info with actual one. In our case they are not
> equal because our handler _emptied_  a message.
> 
> Is this is proper behaviour or a bug ?
> 
> Thanks.
> Timour
>