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

David Law commented on AXIS2-6048:
----------------------------------

1.8.3?! (I only see 1.8.2 in Maven Central, which is where our pom.xml looks)

Yes, its a museum-piece  Basic Support expired a Decade ago!
They're in the process of upgrading. Maybe next year?...

We have the following on our Development:
Red Hat Enterprise Linux Server release 7.9 (Maipo)
Thats supported up to 2024.

In Development I've bombarded it with 60,000 Requests, Multithreaded, 
Software-Stack identical to PROD, but all OK.

But: in Development the Zips are almost identical, so if its data-related (e.g. 
Filesize) it would be much more likely to occur in PROD.

I will try a Zip which failed in PROD, but to do that I need to write a custom 
Client...

In the meantime, if you have any idea what could be triggering that (spurious?) 
2nd POST...

> SOAP Request sends 2nd POST with 0-Byte Payload (Sporadic)
> ----------------------------------------------------------
>
>                 Key: AXIS2-6048
>                 URL: https://issues.apache.org/jira/browse/AXIS2-6048
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.7.9
>         Environment: Our Client:
> SUSE Linux Enterprise Server 11 (x86_64)
> OpenJDK 64-Bit Server VM Zulu17.30+15-CA (build 17.0.1+12-LTS)
> activation-1.1.1.jar
> axiom-api-1.2.22.jar
> axiom-impl-1.2.22.jar
> axis2-kernel-1.7.9.jar
> axis2-transport-http-1.7.9.jar
> commons-httpclient-3.1.jar
> Business Partner Server:
> Axis2 v1.6.2
>            Reporter: David Law
>            Priority: Major
>         Attachments: Annotated_Log-1.txt, ByteArrayInputStream_StackTrace.xlsx
>
>
> We are using Axis2 to send Zip-Files to a Partner via SOAP.
> A POST is sent followed by multiple packets of Zip-File-Data.
> (according to the Logs, this is successful)
> Sporadically, a 2nd POST is sent containing 0 Bytes.
> (this happens roughly every 10,000 requests)
> The Transport did not report any errors.
> Our Partner sends a response, indicating the Zip has length 0.
> I'm assuming this is a Bug in the Axis2 Client?
> Please find attached:
> a) Annotated Log (107 Lines) with our (Prod) Data removed
> b) Excel documenting the ByteArrayInputStream.read(...) Stacktrace
> _) -> the Excel is just to get a feel for the read Stack
> _) -> we used a ByteArrayInputStream Subclass to get Info for the Excel
> _) -> but the error occurs with standard JDK ByteArrayInputStream
> P.S.
> We noticed 2 Lines from jdk.event.security amongst the 2nd POST Logging.
> Could this be significant?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Reply via email to