Picon

Build failed in Jenkins: ActiveMQ #868

See <https://builds.apache.org/job/ActiveMQ/868/changes>

Changes:

[tabish] fix for: https://issues.apache.org/jira/browse/AMQ-3137
fix for: https://issues.apache.org/jira/browse/AMQ-2455
fix for: https://issues.apache.org/jira/browse/AMQ-3635

Adds reconnect logic and tests along with a policy class to allow for control over the reconnect process.
Reconnection of both local and foreign side of the JmsConnector is supported.

------------------------------------------
[...truncated 5146 lines...]
[INFO] Unable to find resource 'classworlds:classworlds:pom:1.1' in repository apache.snapshots (https://repository.apache.org/content/repositories/snapshots/)
Downloading: http://repository.springsource.com/maven/bundles/external/classworlds/classworlds/1.1/classworlds-1.1.pom
[INFO] Unable to find resource 'classworlds:classworlds:pom:1.1' in repository
com.springsource.repository.bundles.external (http://repository.springsource.com/maven/bundles/external)
Downloading: http://repo1.maven.org/maven2/classworlds/classworlds/1.1/classworlds-1.1.pom

Downloading: http://repository.apache.org/snapshots/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.pom
[INFO] Unable to find resource 'org.apache.maven:maven-archiver:pom:2.4.1' in repository
apache.snapshots (https://repository.apache.org/content/repositories/snapshots/)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.pom

Downloading: http://repository.apache.org/snapshots/org/apache/maven/shared/maven-shared-components/15/maven-shared-components-15.pom
[INFO] Unable to find resource 'org.apache.maven.shared:maven-shared-components:pom:15' in
repository apache.snapshots (https://repository.apache.org/content/repositories/snapshots/)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/shared/maven-shared-components/15/maven-shared-components-15.pom

Downloading: http://repository.apache.org/snapshots/org/apache/maven/maven-artifact/2.0.6/maven-artifact-2.0.6.pom
(Continue reading)

Picon
Favicon

[jira] [Created] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461

Upgrade Jetty to address CVE-2011-4461
--------------------------------------

                 Key: AMQ-3693
                 URL: https://issues.apache.org/jira/browse/AMQ-3693
             Project: ActiveMQ
          Issue Type: Task
            Reporter: Bruce Snyder
         Attachments: upgrade-jetty.patch

Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461|CVE-2011-4461] for more
information. See also the attached patch for changes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon
Favicon

[jira] [Updated] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


     [
https://issues.apache.org/jira/browse/AMQ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-3693:
------------------------------

    Attachment: upgrade-jetty.patch

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>            Reporter: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
> Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461|CVE-2011-4461] for more
information. See also the attached patch for changes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)

Picon
Favicon

[jira] [Updated] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


     [
https://issues.apache.org/jira/browse/AMQ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-3693:
------------------------------

    Affects Version/s: 5.5.1
             Assignee: Bruce Snyder

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.5.1
>            Reporter: Bruce Snyder
>            Assignee: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
> Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461|CVE-2011-4461] for more
information. See also the attached patch for changes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
(Continue reading)

Picon
Favicon

[jira] [Updated] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


     [
https://issues.apache.org/jira/browse/AMQ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-3693:
------------------------------

    Description: Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability.
See the [CVE-2011-4461|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461] for more
information. See also the attached patch for changes.   (was: Upgrade Jetty to the 7.6.0 release when it
becomes final so as to address a DoS vulnerability. See the
[http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461|CVE-2011-4461] for more
information. See also the attached patch for changes. )

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.5.1
>            Reporter: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
> Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[CVE-2011-4461|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461] for more
information. See also the attached patch for changes. 

(Continue reading)

Picon
Favicon

[jira] [Updated] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


     [
https://issues.apache.org/jira/browse/AMQ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-3693:
------------------------------

    Assignee:     (was: Bruce Snyder)

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.5.1
>            Reporter: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
> Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461|CVE-2011-4461] for more
information. See also the attached patch for changes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)

Picon
Favicon

[jira] [Commented] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


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

Bruce Snyder commented on AMQ-3693:
-----------------------------------

I have attached a patch for this work, but please note that the patch was created against Jetty 7.6.0.RC4.
The changes will need to use the full Jetty 7.6.0 release when that release is made available. 

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.5.1
>            Reporter: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
> Upgrade Jetty to the 7.6.0 release when it becomes final so as to address a DoS vulnerability. See the
[CVE-2011-4461|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4461] for more
information. See also the attached patch for changes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
(Continue reading)

Picon
Favicon

[jira] [Issue Comment Edited] (AMQ-3693) Upgrade Jetty to address CVE-2011-4461


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

Bruce Snyder edited comment on AMQ-3693 at 2/1/12 3:06 AM:
-----------------------------------------------------------

I have attached a patch for this work, but please note that the patch was created against Jetty 7.6.0.RC4.
The changes will need to use the full Jetty 7.6.0 release when that release is made available. 

Is it possible to get a new version of ActiveMQ cut when Jetty 7.6.0 is released so that this CVE can be
addressed right away?  

      was (Author: bsnyder):
    I have attached a patch for this work, but please note that the patch was created against Jetty 7.6.0.RC4.
The changes will need to use the full Jetty 7.6.0 release when that release is made available. 

> Upgrade Jetty to address CVE-2011-4461
> --------------------------------------
>
>                 Key: AMQ-3693
>                 URL: https://issues.apache.org/jira/browse/AMQ-3693
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.5.1
>            Reporter: Bruce Snyder
>         Attachments: upgrade-jetty.patch
>
>
(Continue reading)

Picon
Favicon

[jira] [Commented] (AMQ-2921) Allow to "reschedule" messages


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

Farhad Dehghani commented on AMQ-2921:
--------------------------------------

I'm not sure if it's possible to reschedule and/or re-add a message that is already scheduled. This is due to
the fact that there is no way (or at least not clear how) to get hold on to the original message once it is
scheduled, neither through the mbeans or through the browse feature you've described above.

> Allow to "reschedule" messages
> ------------------------------
>
>                 Key: AMQ-2921
>                 URL: https://issues.apache.org/jira/browse/AMQ-2921
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.4.0
>            Reporter: Norman Maurer
>
> We use the new delay / scheduling feature which comes with activemq 5.4.0. This is really cool and works out
well. However we need to be able to "reschedule" the message. So we would like be able to remove / change the
delay after adding the message to the queue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Picon
Favicon

[jira] [Commented] (AMQ-3685) Failover cluster update broken when url contains server side options


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

Dejan Bosanac commented on AMQ-3685:
------------------------------------

Another commit (svn revison 1239118) goes further and improves the behavior of this feature in situations like:

- using backup transports
- using multiple transport connectors per broker

> Failover cluster update broken when url contains server side options
> --------------------------------------------------------------------
>
>                 Key: AMQ-3685
>                 URL: https://issues.apache.org/jira/browse/AMQ-3685
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.6.0
>
>
> When transport connector contains some server side config options like
> {code}tcp://localhost:61617?transport.closeAsync=false{code}
> failover transport can fail as it can try connecting to that url with all its server side options.

(Continue reading)


Gmane