[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ http://issues.apache.org/jira/browse/AXIS2-1134?page=comments#action_12439742 ] Thilina Gunarathne commented on AXIS2-1134: --- This problem arises in the case of AsyncMessageReceiver too... Without the above mentioned switch to send http 100 continue upon returning of the calling thread, Axis2 will not be able to send a response in the same channel in the case of AsyncMessageReceiver > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: http://issues.apache.org/jira/browse/AXIS2-1134 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core >Reporter: Thilina Gunarathne > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503113 ] Davanum Srinivas commented on AXIS2-1134: - DO we need to fix this for 1.3? > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: https://issues.apache.org/jira/browse/AXIS2-1134 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel >Reporter: Thilina Gunarathne >Assignee: Deepal Jayasinghe >Priority: Blocker > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503271 ] Eran Chinthaka commented on AXIS2-1134: --- Thilina, I have little doubt whether on doing this. The problem is there can be timeouts of the transports and some one needs to keep sending keep-alive messages. Also I am not sure about how long you can keep a socket open. So don't we need to limit this scenario only when WS-Addressing is available? > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: https://issues.apache.org/jira/browse/AXIS2-1134 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel >Reporter: Thilina Gunarathne >Assignee: Deepal Jayasinghe >Priority: Blocker > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503284 ] Thilina Gunarathne commented on AXIS2-1134: --- Yes.. TimeOut's can be an issue in this case. To be honest I cannot remember the actual use case we had.. I'm fine with restricting this scenario to only when WS-Addressing is present... But it'll be better if we can support this at least for a limited amount of time.. This issue has close ties to the AsyncReciever behaviour too... Where a client side sync request fails due to Axis2 sending back http-200-OK when the thread is returned... > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: https://issues.apache.org/jira/browse/AXIS2-1134 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel >Reporter: Thilina Gunarathne >Assignee: Deepal Jayasinghe >Priority: Blocker > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503990 ] Srinath Perera commented on AXIS2-1134: --- I purposed not to support this. It is not clear how Output stream is to be stored (serialized), and even we though able to do it, OS resources will not be avalible for ever. Supporting this will be big hassle and it will lead to many future problems. > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: https://issues.apache.org/jira/browse/AXIS2-1134 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel >Reporter: Thilina Gunarathne >Assignee: Deepal Jayasinghe >Priority: Blocker > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use
[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508655 ] Davanum Srinivas commented on AXIS2-1134: - I agree with Eran. this is a "won't fix" thanks, dims > Want to Store the MessageContext together with the OutputStream for later use > - > > Key: AXIS2-1134 > URL: https://issues.apache.org/jira/browse/AXIS2-1134 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel >Reporter: Thilina Gunarathne >Assignee: Deepal Jayasinghe > > Use Case is to be able to send a delayed reply to an InOut invocation. One > example is BPEL receive and reply activities. In this example we need to send > a reply after some time to the received invocation. Holding of the invoking > thread till we can write the response is unacceptable. > In a scenario like above, we can store the incoming messagecontext to send > the response later. But this causes the invoking thread to be returned. > Returning of that thread causes the writing of an HTTP 200 OK to the > outstream. > We can introduce a new switch, which can be set when we want to do the above > scenario. Axsi2 transport module can send an HTTP 100 Continue to the client > in the presence of that switch to let him know that we'll be sending the > response later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
