You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Warner (JIRA)" <ji...@apache.org> on 2008/05/08 22:54:55 UTC
[jira] Created: (GERONIMO-4007) Exceptions received in Async HTTP
sample app when under heavy load.
Exceptions received in Async HTTP sample app when under heavy load.
-------------------------------------------------------------------
Key: GERONIMO-4007
URL: https://issues.apache.org/jira/browse/GERONIMO-4007
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: sample apps
Affects Versions: 2.2
Reporter: Jason Warner
Assignee: Jason Warner
Priority: Minor
Fix For: 2.2
During testing of the Asynchronous HTTP Client using the Async HTTP sample app, there were multiple exceptions caused by lack of synchronization in the application and some not thread safe code in event handling.
Changes include:
*Increase synchronization
*Access session Id only on begin event
*Addition of a debug option
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4007) Exceptions received in Async HTTP
sample app when under heavy load.
Posted by "Jason Warner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Warner closed GERONIMO-4007.
----------------------------------
Resolution: Fixed
Changes made in revision 655505
> Exceptions received in Async HTTP sample app when under heavy load.
> -------------------------------------------------------------------
>
> Key: GERONIMO-4007
> URL: https://issues.apache.org/jira/browse/GERONIMO-4007
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: sample apps
> Affects Versions: 2.2
> Reporter: Jason Warner
> Assignee: Jason Warner
> Priority: Minor
> Fix For: 2.2
>
>
> During testing of the Asynchronous HTTP Client using the Async HTTP sample app, there were multiple exceptions caused by lack of synchronization in the application and some not thread safe code in event handling.
> Changes include:
> *Increase synchronization
> *Access session Id only on begin event
> *Addition of a debug option
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.