You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/06/15 16:58:09 UTC
[jira] Closed: (AXIS-1395) attachment produces InnovationTargetException for some files
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Tue, 15 Jun 2004 7:56 AM
closing bug as per rich's request.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1395
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1395
Summary: attachment produces InnovationTargetException for some files
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Axis
Components:
Basic Architecture
Versions:
current (nightly)
Assignee: Davanum Srinivas
Reporter: rich gooding
Created: Tue, 15 Jun 2004 7:13 AM
Updated: Tue, 15 Jun 2004 7:56 AM
Environment: websphere application server providing webservice for .jws class. Called form java test harnesss.
Description:
I have a test harness to call my .jws webservice with a couple of attachments. This works fine for some files but not for others.
So far I cant spot an obvious reason (eg file size or content).
I have done a little debugging - might be helpful:
seems like code breaks in org.apache.axis.Message.class (axis.jar)
about line 339/341 :
mAtt = (Attachments) attachImplConstr.newInstance(
new Object[] {
initialContents,
contentType,
ContentLocation });
where initialContents isa HttpInputStream
ContentType = "multipart/related; .... (129 chars) "
contentLocation = null
I have added a little bit of code to print out the request headers (see output below)
RG
--------------------- output log including stack trace and list of request headers -------------------------------------------------
15/06/04 14:52:14:378 BST] 6413bad4 WebGroup I SRVE0180I: [ws_att] [/ws_att] [Servlet.LOG]: AxisServlet: init
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : content-type
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : accept
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : user-agent
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : host
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : cache-control
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : pragma
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : soapaction
[15/06/04 14:52:15:550 BST] 6413bad4 SystemOut O req.header : content-length
[15/06/04 14:52:21:159 BST] 6413bad4 Message F org.apache.axis.Message InvocationTargetException:
[15/06/04 14:52:21:159 BST] 6413bad4 Message F org.apache.axis.Message TRAS0014I: The following exception was logged java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:79)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled Code))
at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
at org.apache.axis.Message.setup(Message.java:341)
at org.apache.axis.Message.<init>(Message.java:232)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:578)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:301)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Caused by: Error reading data stream: Error in input stream;
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira