[
https://issues.apache.org/jira/browse/CXF-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031015#comment-13031015
]
ext2 commented on CXF-3505:
---------------------------
1)attachment is a POM project for testing this problem; the test app is
SunActivationClientAttachmentRelease.java
2) while I cannot give a simple assertion for such a test to check system
socket's status; but the test program has such special points:
2.1) the client will invoke the server continuously; and the KEEP-ALIVE options
is disabled;
2.2) if using geronimo's activation , we will find many "TIME_WAITING" status
socket at server side; it's correctly, because "TIME_WAITING" is inevitable
status according to tcp-ip protocol;
2.3) if using sun's activation, we will find some "FIN_WAIT2" status socket at
server side, and "CLOSE_WAITING" status at client side. this is not correctly
and indicate that the server socket is closed but client socket hasn't;
> CXF attachment doesn't compatible with SUN's ACTIVATION library
> ----------------------------------------------------------------
>
> Key: CXF-3505
> URL: https://issues.apache.org/jira/browse/CXF-3505
> Project: CXF
> Issue Type: Bug
> Reporter: ext2
> Attachments: attachment-clean.zip
>
>
> if using sun's javax.activation api (version 1.1) instead of geronimo's
> activation api. CXF's attachments . the http connection cannot be released
> corrrectly;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira