I have seen a NPE in a few unit tests that were caused by currenDelivery changing between these two steps:
i - if (currentDelivery != null)
ii - .... currentDelivery.getPos();
instead of adding extra synchronization I'm caching the currentValue what would been enough on this case.
This is just to avoid NPEs
Avoid loading problems of file configurations in
servlet containers when packaging the hornetq libs
not in the war file (e.g. in tomcat/lib/)
This was done with some refactoring from Clebert.
cherry-picking this from https://github.com/hornetq/hornetq/pull/1999
https://issues.apache.org/jira/browse/ACTIVEMQ6-95
The message.copy is broken when you set persistence=false, and the bridge will use that method before forwarding the message
this commit is fixing NullStorageLargeServerMessage.copy and adding the proper testcase to validate the fix
https://issues.apache.org/jira/browse/ACTIVEMQ6-89
I have done a lot of refactoring on this. So we can a different version of the interceptor for each protocol based on a base class now.
Just an abstract class over Stomp would be a bit hacky... this is a better approach.
For some reason the ProtonCPP is missing a Java class to send and receive messages
also fixing the pom properly accordingly to other examples
This closes#187 as I did some rebasing in top of Howard's
Adds in the Geronimo 1.1 Annotation spec jar as a replacement for the
jboss annotation spec jar, pulled in via Rest Easy. Also cleans up
dependency exclusions, removing them from sub modules and added to the
dependency management section of the main pom.
I also did some review of the huge table we have,
removed a few columns such as the datatype and
embedded the default on the description. Just trying to make easier to render and read
Also a few fixes on the doc context such as adding links and improving configuration-index