You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org> on 2009/02/14 11:47:59 UTC
[jira] Created: (QPID-1664) Asynchronous notification capability
Asynchronous notification capability
------------------------------------
Key: QPID-1664
URL: https://issues.apache.org/jira/browse/QPID-1664
Project: Qpid
Issue Type: Sub-task
Components: Java Management : QMan
Affects Versions: M5
Environment: J2SE 1.5 or higher
Reporter: Andrea Gazzarini
Assignee: Andrea Gazzarini
Priority: Critical
Fix For: M5
The current implementation of WS-Notification engine is synchronous. That means the publisher (QMan) will remain blocked until the notification has been processed on oberserver (client) side...this is in generarl not acceptable because a server component depends on a client behaviour...
So, notifications should be processed in separate threads. JDK 1.5 introduced a TrheadPoolEXecutor that is something like a WorkManager in a JEE environment.
Qman will use it for asynchronous notification capability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-1664) Asynchronous notification capability
Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Gazzarini resolved QPID-1664.
------------------------------------
Resolution: Fixed
Feature has been added. Now there's a WorkManager that can be used for send asynch notification(s).
That new component will be configured using the qman-config.xml. Therefore a new section has been added to that configuration file in order to provide configuration for :
- Thread pool size (default : 5);
- Max Thread pool size (default 15);
- Keep Alive time (defalut 5000 millisecs);
> Asynchronous notification capability
> ------------------------------------
>
> Key: QPID-1664
> URL: https://issues.apache.org/jira/browse/QPID-1664
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Management : QMan
> Affects Versions: M5
> Environment: J2SE 1.5 or higher
> Reporter: Andrea Gazzarini
> Assignee: Andrea Gazzarini
> Priority: Critical
> Fix For: M5
>
> Original Estimate: 24h
> Time Spent: 24h
> Remaining Estimate: 0h
>
> The current implementation of WS-Notification engine is synchronous. That means the publisher (QMan) will remain blocked until the notification has been processed on oberserver (client) side...this is in generarl not acceptable because a server component depends on a client behaviour...
> So, notifications should be processed in separate threads. JDK 1.5 introduced a TrheadPoolEXecutor that is something like a WorkManager in a JEE environment.
> Qman will use it for asynchronous notification capability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org