Justin Bertram

Merge pull request #2015 from jbertram/2.4.x

Release work for 2.4.7.Final

Revert "2.4.7.Final release update"

This reverts commit d41218217184881e06601b4f097a2e47269e0eaa.

    • -1
    • +1
    /examples/core/embedded-remote/pom.xml
    • -1
    • +1
    /examples/core/twitter-connector/pom.xml
  1. … 143 more files in changeset.
2.4.7.Final release update

    • -1
    • +1
    /examples/core/embedded-remote/pom.xml
    • -1
    • +1
    /examples/core/twitter-connector/pom.xml
  1. … 143 more files in changeset.
BZ-1115300 HORNETQ-1365 backport MDB interrupt fix

https://bugzilla.redhat.com/show_bug.cgi?id=1115300

https://issues.jboss.org/browse/HORNETQ-1365

use waitforonmessage when the MDB is being interrupted

    • -0
    • +61
    /src/main/org/hornetq/utils/FutureLatch.java
Merge pull request #2012 from clebertsuconic/master

improving print-data on journal

Merge pull request #2011 from clebertsuconic/2.4.x

improving print-data on journal

Merge pull request #2010 from clebertsuconic/2.3.x

improving print-data on journal

Merge pull request #2008 from clebertsuconic/master

HORNETQ-1467 / BZ-1207707 large messages sending over bridge when non persistent

Merge pull request #2007 from clebertsuconic/2.4.x

HORNETQ-1467 / BZ-1207707 large messages sending over bridge when non persistent

Merge pull request #2006 from clebertsuconic/2.3.x

HORNETQ-1467 / BZ-1207707 large messages sending over bridge when non persistent

BZ-1202368 print POODLE WARN just once

BZ-1202368 print POODLE WARN just once

Fix a few tests using the wrong destinationType

BZ-1195210 Backup fails to announce to live server

When a live and backup server are both started at or near the same moment

there is a small window where the live server's acceptors have been

started but the server's state != STARTED. During this window if the

backup sends its announcement the announcement will fail and the backup

will shutdown. This fix closes this small window by only starting the

acceptors until the server is fully started.

BZ-1195210 Backup fails to announce to live server

When a live and backup server are both started at or near the same moment

there is a small window where the live server's acceptors have been

started but the server's state != STARTED. During this window if the

backup sends its announcement the announcement will fail and the backup

will shutdown. This fix closes this small window by only starting the

acceptors until the server is fully started.

BZ-1195210 Backup fails to announce to live server

When a live and backup server are both started at or near the same moment

there is a small window where the live server's acceptors have been

started but the server's state != STARTED. During this window if the

backup sends its announcement the announcement will fail and the backup

will shutdown. This fix closes this small window by only starting the

acceptors until the server is fully started.

Conflicts:

hornetq-server/src/main/java/org/hornetq/core/remoting/server/impl/RemotingServiceImpl.java

hornetq-server/src/main/java/org/hornetq/core/server/impl/HornetQServerImpl.java

BZ-1195210 Backup fails to announce to live server

When a live and backup server are both started at or near the same moment

there is a small window where the live server's acceptors have been

started but the server's state != STARTED. During this window if the

backup sends its announcement the announcement will fail and the backup

will shutdown. This fix closes this small window by only starting the

acceptors until the server is fully started.

Add test for BZ-1193085 just to be safe.

Add test for BZ-1193085 just to be safe.

Merge pull request #1987 from dpocock/dpocock/2.3.x

Update jboss-logging and jboss-logmanager dependencies

BZ-1193085 critical IO error on client disconnect

When a Netty OIO thread servicing a client performs work on the journal

(e.g. creating a new page file, etc.) there is a small window where if

the connection is closed (either via administrative intervention or

because of ping failure, etc.) the Netty thread can be interrupted and

HornetQ will interpret this as a critical journal failure and shut

itself down.

(cherry picked from commit 54165e6c36fc96fef57422eb0245ce2c90f06a1b)

BZ-1193085 critical IO error on client disconnect

When a Netty OIO thread servicing a client performs work on the journal

(e.g. creating a new page file, etc.) there is a small window where if

the connection is closed (either via administrative intervention or

because of ping failure, etc.) the Netty thread can be interrupted and

HornetQ will interpret this as a critical journal failure and shut

itself down.

BZ-1193085 critical IO error on client disconnect

When a Netty OIO thread servicing a client performs work on the journal

(e.g. creating a new page file, etc.) there is a small window where if

the connection is closed (either via administrative intervention or

because of ping failure, etc.) the Netty thread can be interrupted and

HornetQ will interpret this as a critical journal failure and shut

itself down.

BZ-1193085 critical IO error on client disconnect

When a Netty OIO thread servicing a client performs work on the journal

(e.g. creating a new page file, etc.) there is a small window where if

the connection is closed (either via administrative intervention or

because of ping failure, etc.) the Netty thread can be interrupted and

HornetQ will interpret this as a critical journal failure and shut

itself down.

(cherry picked from commit 54165e6c36fc96fef57422eb0245ce2c90f06a1b)

BZ-1193085 critical IO error on client disconnect

When a Netty OIO thread servicing a client performs work on the journal

(e.g. creating a new page file, etc.) there is a small window where if

the connection is closed (either via administrative intervention or

because of ping failure, etc.) the Netty thread can be interrupted and

HornetQ will interpret this as a critical journal failure and shut

itself down.

(cherry picked from commit 54165e6c36fc96fef57422eb0245ce2c90f06a1b)

Merge pull request #1984 from clebertsuconic/master

BZ Fixes

Merge pull request #1983 from clebertsuconic/2.4.x

BZ Fixes

Merge pull request #1982 from clebertsuconic/2.3.x

BZ Fixes

back to snapshot

    • -1
    • +1
    /examples/core/embedded-remote/pom.xml
    • -1
    • +1
    /examples/core/twitter-connector/pom.xml
  1. … 129 more files in changeset.
release 2.3.21.2.Final out of branch 2.3.eap6_3

    • -1
    • +1
    /examples/core/embedded-remote/pom.xml
    • -1
    • +1
    /examples/core/twitter-connector/pom.xml
  1. … 129 more files in changeset.