[
https://issues.apache.org/jira/browse/CXF-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088535#comment-13088535
]
ext2 edited comment on CXF-3750 at 8/23/11 2:44 AM:
----------------------------------------------------
oneway-deadlock-temporary-file.zip is a test case show this problem;
1) ProductService.java : service which receive a request which contains a big
attachment;
and service's business logical will consume and close the attachment's input
stream, then raise a runtime exception
2) ProductClient.java: client;
once the service is invoked, a temporary file will left in the "./attservice"
directory;
That to say: now the user must make sure there is no any exception(even
runtime exception) occurs in the one-way business logical. Otherwise a
temporary file may left in the disk;
But I am not sure if this problem should be take care of by CXF or the end user;
Some source code of patch relate to the problem is:
OneWayProcessorInterceptor.handleMessage(){
....
DelegatingInputStream in = message.getContent(DelegatingInputStream.class);
.....
}
was (Author: ext2xhb):
1) service, the service 'stemporary file directory is set to "./attservice"
directory;
2) service's business logical will consume and close the attachment's input
stream and raise a runtime exception
3) once the service is invoked, a temporary file will left in the
"./attservice" directory;
the temporary file is not the attachment's inputstream left, but the
inputstream stand for the underly transport left;
OneWayProcessorInterceptor.handleMessage(){
....
DelegatingInputStream in = message.getContent(DelegatingInputStream.class);
.....
}
> Sometimes, CXF servlet will blocked until bussiness logical finished for
> one-way operation
> ------------------------------------------------------------------------------------------
>
> Key: CXF-3750
> URL: https://issues.apache.org/jira/browse/CXF-3750
> Project: CXF
> Issue Type: Bug
> Environment: CXF2.3.3 windows xp, jdk1.5_22 or jdk1.6_17
> Reporter: ext2
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.3.7, 2.4.3
>
> Attachments: oneway-deadlock-temporary-file.zip, oneway-deadlock.zip
>
>
> sometime,the servlet handle(JettyHTTPHandler) at server side doesn't return
> back to servlet engine(Jetty) immediately, it will waiting until the
> asynchrouse business logical finished;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
