[ 
https://issues.apache.org/jira/browse/AXIS2-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506343#comment-16506343
 ] 

robert lazarski commented on AXIS2-5918:
----------------------------------------

The axis2 version is not listed, and the stack trace does not line up with the 
last few releases. What version are you running? I suggest upgrading to 1.7.8 
as the first next step.

Best I can tell, RPCUtil.invokeServiceClass() is failing in its reflection 
attempt because the number of arguments is not what is expected, i.e. your 
param list has too many or too few arguments.

If your problem is time sensitive I suggest compiling from source from the 
latest release, and adding some debug statements around the reflection area in 
RPCUtil.invokeServiceClass() .

svn co http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.8/

 

 

 

> Axis2 migration failure with SOAP with Attachment
> -------------------------------------------------
>
>                 Key: AXIS2-5918
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5918
>             Project: Axis2
>          Issue Type: Bug
>            Reporter: Anoobkumar
>            Priority: Major
>
> I am migrating a project which accepts SOAP with Attachment as request from 
> Axis to Axis2 framework. Modules, services everything created and 
> build/deployment went fine. But when I try a request, I am getting below 
> error. in log. Any advise to share?
>  
> 01 Jun 2018 11:21:01 ERROR : wrong number of arguments
> java.lang.IllegalArgumentException: wrong number of arguments
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:497)
>  at 
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
>  at 
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>  at 
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>  at 
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>  at 
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>  at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>  at 
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
>  at 
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
>  at 
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
>  at 
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
>  at 
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3732)
>  at 
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
>  at 
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
>  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
>  at 
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
>  at 
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
>  at 
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
>  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
>  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to