-
1. Re: Workaround for Syncronization Bug in 6.1 EAP
jbertram Nov 1, 2013 9:19 PM (in response to malichtenberg)Are you asking about what can be done on your AS 7.1.1 instances? I ask because EAP 6.1 ships with HornetQ 2.3.1.Final (which has the fix for HORNETQ-1130) so the obvious solution is just to complete your move to EAP 6.1. If you are hitting an NPE in EAP 6.1 then that is a different issue from HORNETQ-1130.
-
2. Re: Workaround for Syncronization Bug in 6.1 EAP
malichtenberg Nov 1, 2013 9:24 PM (in response to jbertram)I'm using 6.1 EAP Alpha (7.2) which shipped with HornetQ 2.3.0 CR1. Apologies for not being clear.
-
3. Re: Workaround for Syncronization Bug in 6.1 EAP
jbertram Nov 1, 2013 9:32 PM (in response to malichtenberg)So why not use EAP 6.1 Final instead of the beta or alpha you're using now?
-
4. Re: Workaround for Syncronization Bug in 6.1 EAP
malichtenberg Nov 8, 2013 3:57 PM (in response to jbertram)We're coming from the community-edition and as I understand the Alpha release is the only 6.1 EAP version we can use in production under the community license.
Apologies for the lag in response. We switched to using the JmsXA pooled connections, and our problems went away. This must bypass the bug referenced as it reuses connections vs creating them for each of our web threads. Thanks for your help!