[
https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2406:
----------------------------------
Fix Version/s: jbossws-native-3.2.1
(was: jbossws-native-3.2.0)
Assignee: Richard Opalka
Reassigning to Richard and moving to 3.2.1.
As a side note on this, while working on JBWS-2554 I've already implemented the last
option we said we need to investigate, ie. forking thread on client side (because of the
way Netty works). I've put in place check on the maintain session prop, so that if
that's not used, clients calls to oneway methods just wait for the http message to be
sent and do not wait for the connection to be closed by the server. This should help for
this topic. We still need to investigate/implement proper solution on server side.
Make OneWay Operations Non-Blocking
-----------------------------------
Key: JBWS-2406
URL:
https://jira.jboss.org/jira/browse/JBWS-2406
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Assignee: Richard Opalka
Fix For: jbossws-native-3.2.1
Currently the @OneWay operations block while the business logic executes on the server
and does not return a response until processing is complete.
This feature request is to modify one-way operations to be non-blocking.
There are various options to be investigated: -
- As soon as server knows it is a valid message send HTTP response but thread continue
to process.
- Fork a new thread server side to call business method.
- Fork thread client side for the call.
(This is not an exhaustive list just some of the current suggestions)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira