Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 76711 invoked from network); 25 Apr 2005 23:03:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Apr 2005 23:03:35 -0000 Received: (qmail 48490 invoked by uid 500); 25 Apr 2005 23:04:01 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 48408 invoked by uid 500); 25 Apr 2005 23:04:01 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 48320 invoked by uid 99); 25 Apr 2005 23:04:00 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 25 Apr 2005 16:04:00 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 5549D2E0 for ; Tue, 26 Apr 2005 01:03:24 +0200 (CEST) Message-ID: <655692702.1114470204334.JavaMail.jira@ajax.apache.org> Date: Tue, 26 Apr 2005 01:03:24 +0200 (CEST) From: "Davanum Srinivas (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Resolved: (AXIS-796) Getting a Socket Writer Error in the client while throwing an AxisFault in a handler Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXIS-796?page=all ] Davanum Srinivas resolved AXIS-796: ----------------------------------- Assign To: (was: Axis Developers Mailing List) Resolution: Invalid we've implemented several such mechanisms in wss4j. works fine. please try latest rc/nightly/cvs. -- dims > Getting a Socket Writer Error in the client while throwing an AxisFault in a handler > ------------------------------------------------------------------------------------ > > Key: AXIS-796 > URL: http://issues.apache.org/jira/browse/AXIS-796 > Project: Axis > Type: Bug > Components: Basic Architecture > Versions: 1.1rc2 > Environment: Operating System: Windows NT/2K > Platform: PC > Reporter: Yann Raoul > > My test is: > - a client calls an axis service on tomcat with authentication (basic, through > axis api) > - a handler (home made, inheriting BasicHandler) checks the user ability to > access the service and throws an Axisfault if the user is not correct: > throw new AxisFault("Server.Unauthenticated", Messages.getMessage("cantAuth01", > context.getUsername()), null, null); > The problem is: sometimes, my client gets the right answer : 401 Unauthorized > Sometimes I get the following stack trace. > This behavior is absolutely not determinist. > java.net.SocketException: Software caused connection abort: socket write error > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:126) > at java.io.BufferedOutputStream.flushBuffer > (BufferedOutputStream.java:69) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127) > at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1090) > at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:635) > at javax.mail.internet.MimeMultipart.writeTo(MimeMultipart.java:233) > at com.sun.mail.handlers.multipart_mixed.writeTo > (multipart_mixed.java:68) > at javax.activation.ObjectDataContentHandler.writeTo > (DataHandler.java:849) > at javax.activation.DataHandler.writeTo(DataHandler.java:305) > at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1089) > at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1527) > at org.apache.axis.attachments.MimeUtils.writeToMultiPartStream > (MimeUtils.java:238) > at org.apache.axis.attachments.AttachmentsImpl.writeContentToStream > (AttachmentsImpl.java:500) > at org.apache.axis.Message.writeTo(Message.java:447) > at org.apache.axis.transport.http.HTTPSender.writeToSocket > (HTTPSender.java:466) > at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:122) > at org.apache.axis.strategies.InvocationStrategy.visit > (InvocationStrategy.java:71) > at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150) > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120) > at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180) > at org.apache.axis.client.Call.invokeEngine(Call.java:2492) > at org.apache.axis.client.Call.invoke(Call.java:2481) > at org.apache.axis.client.Call.invoke(Call.java:2176) > at org.apache.axis.client.Call.invoke(Call.java:2099) > at org.apache.axis.client.Call.invoke(Call.java:1622) > at > fr.urssaf.sepia.transmitter.WebServiceFileTransmitterClient.sendFileReally > (WebServiceFileTransmitterClient.java:244) > at fr.urssaf.sepia.transmitter.WebServiceFileTransmitterClient.sendFile > (WebServiceFileTransmitterClient.java:173) > at fr.urssaf.sepia.transmitter.WebServiceFileTransmitterClient.main > (WebServiceFileTransmitterClient.java:107) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira