[jira] [Resolved] (ACTIVEMQ6-111) Journal directory created even if persistence is disabled

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-111. -- Resolution: Fixed Fix Version/s: 1.0.0 Resolved via

[jira] [Resolved] (ARTEMIS-19) Disable Server Side Load Balancing on message routing

[ https://issues.apache.org/jira/browse/ARTEMIS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-19. --- Resolution: Fixed Disable Server Side Load Balancing on message routing

[jira] [Resolved] (ARTEMIS-134) Include jgroups.jar in distribution

[ https://issues.apache.org/jira/browse/ARTEMIS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-134. Resolution: Fixed Include jgroups.jar in distribution

[jira] [Resolved] (ARTEMIS-79) JMX: getFirstMessageAsJSON not suitable for large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-79. --- Resolution: Fixed I believe this was fixed via 00837c120d131cd6db706aed5f549db06cd7b1e7.

[jira] [Assigned] (ARTEMIS-79) JMX: getFirstMessageAsJSON not suitable for large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-79: - Assignee: Justin Bertram JMX: getFirstMessageAsJSON not suitable for large messages

[jira] [Closed] (ARTEMIS-123) Import ActiveMQ OpenWire test framework

[ https://issues.apache.org/jira/browse/ARTEMIS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-123. -- Resolution: Duplicate Import ActiveMQ OpenWire test framework

[jira] [Closed] (ARTEMIS-122) Import ActiveMQ OpenWire test framework

[ https://issues.apache.org/jira/browse/ARTEMIS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-122. -- Resolution: Duplicate Import ActiveMQ OpenWire test framework

[jira] [Commented] (ARTEMIS-142) Fix test failures

[ https://issues.apache.org/jira/browse/ARTEMIS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14593942#comment-14593942 ] Justin Bertram commented on ARTEMIS-142: Something from

[jira] [Comment Edited] (ARTEMIS-142) Fix test failures

[ https://issues.apache.org/jira/browse/ARTEMIS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14593942#comment-14593942 ] Justin Bertram edited comment on ARTEMIS-142 at 6/19/15 9:03 PM:

[jira] [Commented] (ARTEMIS-70) Implement resource limits

[ https://issues.apache.org/jira/browse/ARTEMIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601340#comment-14601340 ] Justin Bertram commented on ARTEMIS-70: --- I implemented: * overall number of

[jira] [Created] (ARTEMIS-141) Refactor classloading into ServiceRegistry

Justin Bertram created ARTEMIS-141: -- Summary: Refactor classloading into ServiceRegistry Key: ARTEMIS-141 URL: https://issues.apache.org/jira/browse/ARTEMIS-141 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-142) Fix test failures

[ https://issues.apache.org/jira/browse/ARTEMIS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14593553#comment-14593553 ] Justin Bertram commented on ARTEMIS-142: [~clebertsuconic], I believe your commit

[jira] [Resolved] (ARTEMIS-105) ActiveMQServerControl#forceFailover() always throw an exception

[ https://issues.apache.org/jira/browse/ARTEMIS-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-105. Resolution: Fixed ActiveMQServerControl#forceFailover() always throw an exception

[jira] [Commented] (ARTEMIS-109) Divert routing name is no longer optional

[ https://issues.apache.org/jira/browse/ARTEMIS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582550#comment-14582550 ] Justin Bertram commented on ARTEMIS-109: Looks like this functionality was

[jira] [Closed] (ARTEMIS-90) ClassNotFoundException when a backup server fails over after having failed back

[ https://issues.apache.org/jira/browse/ARTEMIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-90. - Resolution: Fixed ClassNotFoundException when a backup server fails over after having failed

[jira] [Resolved] (ARTEMIS-109) Divert routing name is no longer optional

[ https://issues.apache.org/jira/browse/ARTEMIS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-109. Resolution: Fixed Divert routing name is no longer optional

[jira] [Commented] (ARTEMIS-123) Import ActiveMQ OpenWire test framework

[ https://issues.apache.org/jira/browse/ARTEMIS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586320#comment-14586320 ] Justin Bertram commented on ARTEMIS-123: This looks like a duplicate of

[jira] [Comment Edited] (ARTEMIS-90) ClassNotFoundException when a backup server fails over after having failed back

[ https://issues.apache.org/jira/browse/ARTEMIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586622#comment-14586622 ] Justin Bertram edited comment on ARTEMIS-90 at 6/15/15 8:31 PM:

[jira] [Assigned] (ARTEMIS-90) ClassNotFoundException when a backup server fails over after having failed back

[ https://issues.apache.org/jira/browse/ARTEMIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-90: - Assignee: Justin Bertram ClassNotFoundException when a backup server fails over after

[jira] [Created] (ARTEMIS-180) Remove example profile

Justin Bertram created ARTEMIS-180: -- Summary: Remove example profile Key: ARTEMIS-180 URL: https://issues.apache.org/jira/browse/ARTEMIS-180 Project: ActiveMQ Artemis Issue Type: Task

[jira] [Assigned] (ARTEMIS-162) Can't create colocated HA topology with JGroups discovery

[ https://issues.apache.org/jira/browse/ARTEMIS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-162: -- Assignee: Justin Bertram Can't create colocated HA topology with JGroups discovery

[jira] [Commented] (ARTEMIS-162) Can't create colocated HA topology with JGroups discovery

[ https://issues.apache.org/jira/browse/ARTEMIS-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649741#comment-14649741 ] Justin Bertram commented on ARTEMIS-162: [~jmesnil], can you attach your

[jira] [Assigned] (ARTEMIS-179) Artemis is logging warnings during reconnecting cluster connection on server shut down

[ https://issues.apache.org/jira/browse/ARTEMIS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-179: -- Assignee: Justin Bertram Artemis is logging warnings during reconnecting cluster

[jira] [Resolved] (ARTEMIS-179) Artemis is logging warnings during reconnecting cluster connection on server shut down

[ https://issues.apache.org/jira/browse/ARTEMIS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-179. Resolution: Fixed Artemis is logging warnings during reconnecting cluster connection on

[jira] [Assigned] (ARTEMIS-205) Keepalive not working on OpenWire

[ https://issues.apache.org/jira/browse/ARTEMIS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-205: -- Assignee: Justin Bertram Keepalive not working on OpenWire

[jira] [Assigned] (ARTEMIS-161) Graceful shutdown: add a timeout to stop Artemis

[ https://issues.apache.org/jira/browse/ARTEMIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-161: -- Assignee: Justin Bertram Graceful shutdown: add a timeout to stop Artemis

[jira] [Created] (ARTEMIS-210) Outbound connections aren't load-balanced as expected

Justin Bertram created ARTEMIS-210: -- Summary: Outbound connections aren't load-balanced as expected Key: ARTEMIS-210 URL: https://issues.apache.org/jira/browse/ARTEMIS-210 Project: ActiveMQ Artemis

[jira] [Updated] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections

[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-289: --- Description: org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns the

[jira] [Updated] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections

[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-289: --- Affects Version/s: 1.1.0 > Potential ConcurrentModificationException when closing

[jira] [Updated] (ARTEMIS-168) Pluggable ACL Hierarchies

[ https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-168: --- Fix Version/s: (was: 1.3.0) 1.1.1 > Pluggable ACL Hierarchies >

[jira] [Resolved] (ARTEMIS-255) Make failover timeout for non-blocking sends configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-255. Resolution: Fixed > Make failover timeout for non-blocking sends configurable >

[jira] [Resolved] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections

[ https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-289. Resolution: Fixed > Potential ConcurrentModificationException when closing connections >

[jira] [Resolved] (ARTEMIS-168) Pluggable ACL Hierarchies

[ https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-168. Resolution: Fixed > Pluggable ACL Hierarchies > - > >

[jira] [Commented] (ARTEMIS-283) Protocol independent JMSMessageID from management interface

[ https://issues.apache.org/jira/browse/ARTEMIS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976491#comment-14976491 ] Justin Bertram commented on ARTEMIS-283: Couple of questions: # I don't quite understand why

[jira] [Commented] (ARTEMIS-93) OSGI support

[ https://issues.apache.org/jira/browse/ARTEMIS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976699#comment-14976699 ] Justin Bertram commented on ARTEMIS-93: --- [~ch...@die-schneider.net], I think that would be great. >

[jira] [Assigned] (ARTEMIS-261) Allow certificate based JAAS security

[ https://issues.apache.org/jira/browse/ARTEMIS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-261: -- Assignee: Justin Bertram > Allow certificate based JAAS security >

[jira] [Assigned] (ARTEMIS-168) Pluggable ACL Hierarchies

[ https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-168: -- Assignee: Justin Bertram > Pluggable ACL Hierarchies > - > >

[jira] [Resolved] (ARTEMIS-299) Improve performance of TextFileCertificateLoginModule when many entries in user file

[ https://issues.apache.org/jira/browse/ARTEMIS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-299. Resolution: Fixed > Improve performance of TextFileCertificateLoginModule when many

[jira] [Resolved] (ARTEMIS-298) IPv6 escape doesn't always work

[ https://issues.apache.org/jira/browse/ARTEMIS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-298. Resolution: Fixed > IPv6 escape doesn't always work > --- > >

[jira] [Resolved] (ARTEMIS-286) Upgrade Netty to version 4.0.32.Final

[ https://issues.apache.org/jira/browse/ARTEMIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-286. Resolution: Fixed > Upgrade Netty to version 4.0.32.Final >

[jira] [Created] (ARTEMIS-304) Prompt for role when creating instance

Justin Bertram created ARTEMIS-304: -- Summary: Prompt for role when creating instance Key: ARTEMIS-304 URL: https://issues.apache.org/jira/browse/ARTEMIS-304 Project: ActiveMQ Artemis Issue

[jira] [Resolved] (ARTEMIS-263) etc folder not included at runtime

[ https://issues.apache.org/jira/browse/ARTEMIS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-263. Resolution: Fixed This looks resolved to me so I'm marking it as such. Feel free to change

[jira] [Resolved] (ARTEMIS-276) JMSBridge should be TCCL aware

[ https://issues.apache.org/jira/browse/ARTEMIS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-276. Resolution: Fixed This looks resolved to me so I'm marking it as such. Feel free to change

[jira] [Created] (ARTEMIS-299) Improve performance of TextFileCertificateLoginModule when many entries in user file

Justin Bertram created ARTEMIS-299: -- Summary: Improve performance of TextFileCertificateLoginModule when many entries in user file Key: ARTEMIS-299 URL: https://issues.apache.org/jira/browse/ARTEMIS-299

[jira] [Created] (ARTEMIS-298) IPv6 escape doesn't always work

Justin Bertram created ARTEMIS-298: -- Summary: IPv6 escape doesn't always work Key: ARTEMIS-298 URL: https://issues.apache.org/jira/browse/ARTEMIS-298 Project: ActiveMQ Artemis Issue Type:

[jira] [Resolved] (ARTEMIS-293) Rebalance JCA RA inflow connections when cluster topology changes

[ https://issues.apache.org/jira/browse/ARTEMIS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-293. Resolution: Fixed > Rebalance JCA RA inflow connections when cluster topology changes >

[jira] [Created] (ARTEMIS-300) Make JAAS properties login module default and deprecate "basic"

Justin Bertram created ARTEMIS-300: -- Summary: Make JAAS properties login module default and deprecate "basic" Key: ARTEMIS-300 URL: https://issues.apache.org/jira/browse/ARTEMIS-300 Project:

[jira] [Created] (ARTEMIS-293) Rebalance JCA RA inflow connections when cluster topology changes

Justin Bertram created ARTEMIS-293: -- Summary: Rebalance JCA RA inflow connections when cluster topology changes Key: ARTEMIS-293 URL: https://issues.apache.org/jira/browse/ARTEMIS-293 Project:

[jira] [Resolved] (ARTEMIS-256) Orchestrate fail-back deterministically

[ https://issues.apache.org/jira/browse/ARTEMIS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-256. Resolution: Fixed > Orchestrate fail-back deterministically >

[jira] [Closed] (ARTEMIS-242) IllegalStateException thrown during producer.send()

[ https://issues.apache.org/jira/browse/ARTEMIS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-242. -- Resolution: Duplicate > IllegalStateException thrown during producer.send() >

[jira] [Updated] (ARTEMIS-254) Don't throw IllegalStateException from JMS producer implementation

[ https://issues.apache.org/jira/browse/ARTEMIS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-254: --- Description: Sometimes during failback a JMS producer can get

[jira] [Updated] (ARTEMIS-254) Don't throw IllegalStateException from JMS producer implementation

[ https://issues.apache.org/jira/browse/ARTEMIS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-254: --- Fix Version/s: 1.1.1 > Don't throw IllegalStateException from JMS producer implementation >

[jira] [Closed] (ARTEMIS-254) Don't throw IllegalStateException from JMS producer implementation

[ https://issues.apache.org/jira/browse/ARTEMIS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-254. -- Resolution: Duplicate > Don't throw IllegalStateException from JMS producer implementation >

[jira] [Reopened] (ARTEMIS-242) IllegalStateException thrown during producer.send()

[ https://issues.apache.org/jira/browse/ARTEMIS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reopened ARTEMIS-242: Assignee: Justin Bertram > IllegalStateException thrown during producer.send() >

[jira] [Resolved] (ARTEMIS-242) IllegalStateException thrown during producer.send()

[ https://issues.apache.org/jira/browse/ARTEMIS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-242. Resolution: Fixed > IllegalStateException thrown during producer.send() >

[jira] [Created] (ARTEMIS-255) Make failover timeout for non-blocking sends configurable

Justin Bertram created ARTEMIS-255: -- Summary: Make failover timeout for non-blocking sends configurable Key: ARTEMIS-255 URL: https://issues.apache.org/jira/browse/ARTEMIS-255 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-160) After failback backup prints warnings to log

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009497#comment-15009497 ] Justin Bertram commented on ARTEMIS-160: Log debug instead of throwing the IllegalStateException

[jira] [Comment Edited] (ARTEMIS-160) After failback backup prints warnings to log

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009444#comment-15009444 ] Justin Bertram edited comment on ARTEMIS-160 at 11/17/15 8:34 PM: -- The

[jira] [Assigned] (ARTEMIS-160) After failback backup prints warnings to log

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-160: -- Assignee: Justin Bertram > After failback backup prints warnings to log >

[jira] [Commented] (ARTEMIS-160) After failback backup prints warnings to log

[ https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009444#comment-15009444 ] Justin Bertram commented on ARTEMIS-160: The runAfterActive was implemented here because of

[jira] [Assigned] (ARTEMIS-212) Unable to parse IPv6 address

[ https://issues.apache.org/jira/browse/ARTEMIS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-212: -- Assignee: Justin Bertram Unable to parse IPv6 address

[jira] [Resolved] (ARTEMIS-212) Unable to parse IPv6 address

[ https://issues.apache.org/jira/browse/ARTEMIS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-212. Resolution: Fixed Unable to parse IPv6 address

[jira] [Comment Edited] (ARTEMIS-212) Unable to parse IPv6 address

[ https://issues.apache.org/jira/browse/ARTEMIS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715571#comment-14715571 ] Justin Bertram edited comment on ARTEMIS-212 at 8/26/15 9:40 PM:

[jira] [Commented] (ARTEMIS-212) Unable to parse IPv6 address

[ https://issues.apache.org/jira/browse/ARTEMIS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715571#comment-14715571 ] Justin Bertram commented on ARTEMIS-212: Maybe I'm thick, but I can't reproduce

[jira] [Assigned] (ARTEMIS-206) HTTP Upgrade does not work over HTTPS

[ https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-206: -- Assignee: Justin Bertram HTTP Upgrade does not work over HTTPS

[jira] [Commented] (ARTEMIS-206) HTTP Upgrade does not work over HTTPS

[ https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718586#comment-14718586 ] Justin Bertram commented on ARTEMIS-206: I'm trying to get a test-case set up for

[jira] [Commented] (ARTEMIS-206) HTTP Upgrade does not work over HTTPS

[ https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14719969#comment-14719969 ] Justin Bertram commented on ARTEMIS-206: Nevermind. I got past the SSL handshake

[jira] [Commented] (ARTEMIS-206) HTTP Upgrade does not work over HTTPS

[ https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723496#comment-14723496 ] Justin Bertram commented on ARTEMIS-206: I made a small change to the NettyConnector to use

[jira] [Comment Edited] (ARTEMIS-206) HTTP Upgrade does not work over HTTPS

[ https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723496#comment-14723496 ] Justin Bertram edited comment on ARTEMIS-206 at 8/31/15 2:48 PM: - I just

[jira] [Updated] (ARTEMIS-211) Memory leak using wildcard topic

[ https://issues.apache.org/jira/browse/ARTEMIS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-211: --- Fix Version/s: 1.1.0 > Memory leak using wildcard topic > >

[jira] [Resolved] (ARTEMIS-211) Memory leak using wildcard topic

[ https://issues.apache.org/jira/browse/ARTEMIS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-211. Resolution: Fixed > Memory leak using wildcard topic > >

[jira] [Commented] (ARTEMIS-211) Memory leak using wildcard topic

[ https://issues.apache.org/jira/browse/ARTEMIS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14711944#comment-14711944 ] Justin Bertram commented on ARTEMIS-211: I've reproduced this and I'm

[jira] [Assigned] (ARTEMIS-225) Incomplete Activation Validation

[ https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-225: -- Assignee: Justin Bertram > Incomplete Activation Validation >

[jira] [Assigned] (ARTEMIS-224) java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager

[ https://issues.apache.org/jira/browse/ARTEMIS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-224: -- Assignee: Justin Bertram > java.lang.ClassNotFoundException:

[jira] [Commented] (ARTEMIS-225) Incomplete Activation Validation

[ https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14902861#comment-14902861 ] Justin Bertram commented on ARTEMIS-225: [~jmesnil], I don't believe my fix is valid per

[jira] [Commented] (ARTEMIS-225) Incomplete Activation Validation

[ https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14902763#comment-14902763 ] Justin Bertram commented on ARTEMIS-225: The "fix" I sent to validate the activation spec breaks

[jira] [Updated] (ARTEMIS-314) Support JCA inflow connection rebalancing when reconnectAttempts == -1

[ https://issues.apache.org/jira/browse/ARTEMIS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-314: --- Affects Version/s: 1.1.0 > Support JCA inflow connection rebalancing when reconnectAttempts

[jira] [Created] (ARTEMIS-314) Support JCA inflow connection rebalancing when reconnectAttempts == -1

Justin Bertram created ARTEMIS-314: -- Summary: Support JCA inflow connection rebalancing when reconnectAttempts == -1 Key: ARTEMIS-314 URL: https://issues.apache.org/jira/browse/ARTEMIS-314 Project:

[jira] [Commented] (ARTEMIS-303) listDurableSubscriptionsAsJson fails if there is a durable subscription on a JMS topic

[ https://issues.apache.org/jira/browse/ARTEMIS-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047032#comment-15047032 ] Justin Bertram commented on ARTEMIS-303: Thanks. I've reproduced the exception, and I'm

[jira] [Updated] (ARTEMIS-309) Upgrade commons-collections

[ https://issues.apache.org/jira/browse/ARTEMIS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-309: --- Fix Version/s: (was: 1.2.0) > Upgrade commons-collections > ---

[jira] [Updated] (ARTEMIS-310) Upgrade jolokia to 1.3.2

[ https://issues.apache.org/jira/browse/ARTEMIS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-310: --- Affects Version/s: 1.1.0 > Upgrade jolokia to 1.3.2 > > >

[jira] [Assigned] (ARTEMIS-309) Upgrade commons-collections

[ https://issues.apache.org/jira/browse/ARTEMIS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-309: -- Assignee: Justin Bertram > Upgrade commons-collections > ---

[jira] [Updated] (ARTEMIS-310) Upgrade jolokia to 1.3.2

[ https://issues.apache.org/jira/browse/ARTEMIS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-310: --- Fix Version/s: (was: 1.2.0) 1.1.1 > Upgrade jolokia to 1.3.2 >

[jira] [Resolved] (ARTEMIS-310) Upgrade jolokia to 1.3.2

[ https://issues.apache.org/jira/browse/ARTEMIS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-310. Resolution: Fixed > Upgrade jolokia to 1.3.2 > > >

[jira] [Assigned] (ARTEMIS-317) Large Message Failure in calling interceptor java.lang.ClassCastException

[ https://issues.apache.org/jira/browse/ARTEMIS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-317: -- Assignee: Justin Bertram > Large Message Failure in calling interceptor

[jira] [Assigned] (ARTEMIS-310) Upgrade jolokia to 1.3.2

[ https://issues.apache.org/jira/browse/ARTEMIS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-310: -- Assignee: Justin Bertram > Upgrade jolokia to 1.3.2 > > >

[jira] [Commented] (ARTEMIS-317) Large Message Failure in calling interceptor java.lang.ClassCastException

[ https://issues.apache.org/jira/browse/ARTEMIS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048957#comment-15048957 ] Justin Bertram commented on ARTEMIS-317: Can you try this on the "master" branch from our Git

[jira] [Resolved] (ARTEMIS-303) listDurableSubscriptionsAsJson fails if there is a durable subscription on a JMS topic

[ https://issues.apache.org/jira/browse/ARTEMIS-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-303. Resolution: Fixed > listDurableSubscriptionsAsJson fails if there is a durable

[jira] [Updated] (ARTEMIS-315) NullPointerException when trying to list prepared transactions as JSON

[ https://issues.apache.org/jira/browse/ARTEMIS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-315: --- Fix Version/s: 1.1.1 > NullPointerException when trying to list prepared transactions as

[jira] [Resolved] (ARTEMIS-315) NullPointerException when trying to list prepared transactions as JSON

[ https://issues.apache.org/jira/browse/ARTEMIS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-315. Resolution: Fixed Assignee: Justin Bertram This looks fixed so I'm resolving it.

[jira] [Assigned] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-312: -- Assignee: Justin Bertram > Artemis clients use by default an unbounded global thread

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049330#comment-15049330 ] Justin Bertram commented on ARTEMIS-312: > This default global pool looks misconfigured. If a

[jira] [Comment Edited] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15049330#comment-15049330 ] Justin Bertram edited comment on ARTEMIS-312 at 12/9/15 8:22 PM: - > This

[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)

[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051688#comment-15051688 ] Justin Bertram commented on ARTEMIS-318: I was able to reproduce this. As far as I can tell the

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051654#comment-15051654 ] Justin Bertram commented on ARTEMIS-312: As I'm sure you understand, a message broker is a

[jira] [Assigned] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)

[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-318: -- Assignee: Justin Bertram > Allow extra settings on command line for JVM (remote JMX &

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051748#comment-15051748 ] Justin Bertram commented on ARTEMIS-312: To Clebert's point, we can certainly add more

[jira] [Comment Edited] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051748#comment-15051748 ] Justin Bertram edited comment on ARTEMIS-312 at 12/10/15 10:17 PM: --- To

[jira] [Comment Edited] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15053027#comment-15053027 ] Justin Bertram edited comment on ARTEMIS-312 at 12/11/15 5:06 PM: --

[jira] [Commented] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool

[ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15053027#comment-15053027 ] Justin Bertram commented on ARTEMIS-312: JNDI would be appealing for anybody who doesn't want to

  1   2   3   4   5   6   7   8   9   10   >