You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/03/14 07:38:32 UTC
[jira] Assigned: (AMQ-1618) Improper handling of container
restrictions in creation of sessions
[ https://issues.apache.org/activemq/browse/AMQ-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned AMQ-1618:
---------------------------------
Assignee: David Jencks
> Improper handling of container restrictions in creation of sessions
> -------------------------------------------------------------------
>
> Key: AMQ-1618
> URL: https://issues.apache.org/activemq/browse/AMQ-1618
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector, Geronimo Integration
> Affects Versions: 4.1.1, 5.0.0
> Environment: All
> Reporter: Manu T George
> Assignee: David Jencks
> Fix For: 4.1.2, 5.1.0, 5.2.0
>
>
> In the getServerSession() method of org.apache.activemq.ra.ServerSessionPoolImpl there is an issue with the code block given below
> ServerSessionImpl ss = createServerSessionImpl();
> // We may not be able to create a session due to the container
> // restricting us.
> if (ss == null) {
> if (idleSessions.size() == 0) {
> throw new JMSException("Endpoint factory did not allows to any endpoints.");
> }
> return getExistingServerSession();
> }
> If the container restricts the creation of a session then messages should be queued to an existing session. So the check should be
> if (activeSessions.size() == 0) {
> throw new JMSException("Endpoint factory did not allows to any endpoints.");
> }
> instead of the one above
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.