Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1478414582.1207585833311.JavaMail.jira@brutus>
Date: Mon, 7 Apr 2008 09:30:33 -0700 (PDT)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1616) JMS Compliance - Closing a closed
 connection should not throw an exception
In-Reply-To: <86747072.1205257595066.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42039#action_42039 ] 

Hiram Chirino commented on AMQ-1616:
------------------------------------

That part of the spec is in conflict with JMS API documentation which states:

that the close() method throws "JMSException - if the JMS provider fails to close the connection due to some internal error. For example, a failure to release resources or to close a socket connection can cause this exception to be thrown."

So I don't think we are in violation of the spec.  If they really did not want an exception to be thrown, they would have not added the "throws JMSException" to the API.


> JMS Compliance - Closing a closed connection should not throw an exception
> --------------------------------------------------------------------------
>
>                 Key: AMQ-1616
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1616
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>         Environment: Ubuntu Linux
>            Reporter: Geoff Holden
>            Priority: Minor
>         Attachments: close_connection.patch
>
>
> According to the JMS Spec, section 4.3.5, "Closing a closed connection must NOT throw an exception."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.