[
https://issues.apache.org/jira/browse/ARTEMIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351605#comment-15351605
]
Justin Bertram commented on ARTEMIS-569:
I imagine a patch release could be made with this (and
[
https://issues.apache.org/jira/browse/ARTEMIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-569:
--
Assignee: Justin Bertram
> property missing from XSD
> -
>
>
[
https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-595.
--
Resolution: Fixed
> When creating JMS bridge management API should pass bridge name to JMS
[
https://issues.apache.org/jira/browse/ARTEMIS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-395.
Resolution: Fixed
> Auto-delete JMS queues only if auto-delete-jms-queues = true
>
[
https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-388:
--
Assignee: Justin Bertram
> No obvious way to discover whether an embedded server
Justin Bertram created ARTEMIS-395:
--
Summary: Auto-delete JMS queues only if auto-delete-jms-queues =
true
Key: ARTEMIS-395
URL: https://issues.apache.org/jira/browse/ARTEMIS-395
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137546#comment-15137546
]
Justin Bertram edited comment on ARTEMIS-391 at 2/8/16 9:36 PM:
Adding
[
https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137546#comment-15137546
]
Justin Bertram commented on ARTEMIS-391:
Adding the logging here is easy. However, I'm not sure
[
https://issues.apache.org/jira/browse/ARTEMIS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134751#comment-15134751
]
Justin Bertram commented on ARTEMIS-390:
Can you provide details on the use-case here or
[
https://issues.apache.org/jira/browse/ARTEMIS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134745#comment-15134745
]
Justin Bertram commented on ARTEMIS-389:
Can you provide details on the use-case here or
[
https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133467#comment-15133467
]
Justin Bertram commented on AMQ-6148:
-
That's correct. ActiveMQ Artemis is not a plugin to ActiveMQ but
[
https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132471#comment-15132471
]
Justin Bertram commented on ARTEMIS-380:
Thanks for additional clarification on the use-case, but
[
https://issues.apache.org/jira/browse/ARTEMIS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-376:
---
Fix Version/s: 1.3.0
> NPE occurs when backup handover to live
>
Justin Bertram created ARTEMIS-374:
--
Summary: Support scheduled messages last-value queue
Key: ARTEMIS-374
URL: https://issues.apache.org/jira/browse/ARTEMIS-374
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-374.
Resolution: Fixed
> Support scheduled messages on last-value queue
>
[
https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-380:
--
Assignee: Justin Bertram
> Cluster Topology is wrong after update restart.
>
[
https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127199#comment-15127199
]
Justin Bertram commented on ARTEMIS-380:
Thanks for the bug report!
Can you quantify your
[
https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131329#comment-15131329
]
Justin Bertram commented on AMQ-6148:
-
[~alt_alt], the Apache ActiveMQ Artemis broker has had [3
[
https://issues.apache.org/jira/browse/ARTEMIS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-374:
---
Summary: Support scheduled messages on last-value queue (was: Support
scheduled messages
[
https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122828#comment-15122828
]
Justin Bertram commented on AMQ-6148:
-
For what it's worth, [Apache ActiveMQ
Justin Bertram created ARTEMIS-422:
--
Summary: Implement appendRollbackRecord in
o.a.a.a.c.j.i.FileWrapperJournal
Key: ARTEMIS-422
URL: https://issues.apache.org/jira/browse/ARTEMIS-422
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-422.
Resolution: Fixed
Fix Version/s: 1.3.0
> Implement appendRollbackRecord in
[
https://issues.apache.org/jira/browse/ARTEMIS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-422:
---
Affects Version/s: 1.2.0
> Implement appendRollbackRecord in
[
https://issues.apache.org/jira/browse/ARTEMIS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-419.
Resolution: Not A Problem
> Consider giving access to snapshots
>
[
https://issues.apache.org/jira/browse/ARTEMIS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-349.
Resolution: Fixed
> Implement listener for LDAP security setting plugin
>
Justin Bertram created ARTEMIS-354:
--
Summary: login.config not set properly for Windows service
Key: ARTEMIS-354
URL: https://issues.apache.org/jira/browse/ARTEMIS-354
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-344:
--
Assignee: Justin Bertram
> amqpnetlite client cannot connect a broker running as a
[
https://issues.apache.org/jira/browse/ARTEMIS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-344.
Resolution: Fixed
Fix Version/s: 1.3.0
I believe this was fixed via ARTEMIS-354.
>
[
https://issues.apache.org/jira/browse/ARTEMIS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-313.
--
Resolution: Won't Fix
> support udp transport
> -
>
> Key:
Justin Bertram created ARTEMIS-352:
--
Summary: Correct readme.html in "security" example
Key: ARTEMIS-352
URL: https://issues.apache.org/jira/browse/ARTEMIS-352
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-352:
---
Summary: Correct readme.html in security examples (was: Correct
readme.html in "security"
[
https://issues.apache.org/jira/browse/ARTEMIS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-399.
Resolution: Fixed
> Client id MDB activation config property name incorrect
>
[
https://issues.apache.org/jira/browse/ARTEMIS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-399:
---
Affects Version/s: 1.2.0
> Client id MDB activation config property name incorrect
>
[
https://issues.apache.org/jira/browse/ARTEMIS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-399:
---
Fix Version/s: 1.3.0
> Client id MDB activation config property name incorrect
>
[
https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-388.
Resolution: Fixed
Fix Version/s: 1.3.0
> No obvious way to discover whether an
[
https://issues.apache.org/jira/browse/ARTEMIS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-376.
Resolution: Fixed
> NPE occurs when backup handover to live
>
[
https://issues.apache.org/jira/browse/ARTEMIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-352.
Resolution: Fixed
> Correct readme.html in security examples
>
Justin Bertram created ARTEMIS-400:
--
Summary: Allow SSL keystores to be reloaded
Key: ARTEMIS-400
URL: https://issues.apache.org/jira/browse/ARTEMIS-400
Project: ActiveMQ Artemis
Issue
Justin Bertram created ARTEMIS-441:
--
Summary: Use proper time-unit for large message packet polling
Key: ARTEMIS-441
URL: https://issues.apache.org/jira/browse/ARTEMIS-441
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-432.
Resolution: Fixed
> Client may still get messages even if its session is stopped
>
Justin Bertram created ARTEMIS-432:
--
Summary: Client may still get messages even if its session is
stopped
Key: ARTEMIS-432
URL: https://issues.apache.org/jira/browse/ARTEMIS-432
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-435.
--
Resolution: Duplicate
> Client may still get messages even if its session is stopped
>
[
https://issues.apache.org/jira/browse/ARTEMIS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-436.
--
Resolution: Duplicate
> Client may still get messages even if its session is stopped
>
Justin Bertram created ARTEMIS-435:
--
Summary: Client may still get messages even if its session is
stopped
Key: ARTEMIS-435
URL: https://issues.apache.org/jira/browse/ARTEMIS-435
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-433.
--
Resolution: Duplicate
> Client may still get messages even if its session is stopped
>
[
https://issues.apache.org/jira/browse/ARTEMIS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram closed ARTEMIS-434.
--
Resolution: Duplicate
> Client may still get messages even if its session is stopped
>
[
https://issues.apache.org/jira/browse/ARTEMIS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-462:
--
Assignee: Justin Bertram
> JMSXGroupId is not taken into account when set on the
Justin Bertram created ARTEMIS-467:
--
Summary: Potential NPE in
JMSServerManagerImpl#shutdownConnectionFactory
Key: ARTEMIS-467
URL: https://issues.apache.org/jira/browse/ARTEMIS-467
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-476:
--
Assignee: Justin Bertram
> Instructions for running examples are triplicated and
[
https://issues.apache.org/jira/browse/ARTEMIS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-445.
Resolution: Fixed
Fix Version/s: 1.3.0
> Truststore/Keystore password cannot be
[
https://issues.apache.org/jira/browse/ARTEMIS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206930#comment-15206930
]
Justin Bertram commented on ARTEMIS-438:
I believe this was fixed via ARTEMIS-354.
> AMQ224018:
[
https://issues.apache.org/jira/browse/ARTEMIS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-438:
---
Fix Version/s: 1.3.0
> AMQ224018: Failed to create session: Security exception: Unable to
[
https://issues.apache.org/jira/browse/ARTEMIS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-438:
--
Assignee: Justin Bertram
> AMQ224018: Failed to create session: Security exception:
[
https://issues.apache.org/jira/browse/ARTEMIS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-438.
Resolution: Duplicate
> AMQ224018: Failed to create session: Security exception: Unable to
Justin Bertram created ARTEMIS-451:
--
Summary: More improvements for JAAS text file reloading
Key: ARTEMIS-451
URL: https://issues.apache.org/jira/browse/ARTEMIS-451
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204517#comment-15204517
]
Justin Bertram edited comment on ARTEMIS-445 at 3/21/16 4:12 PM:
-
FWIW,
[
https://issues.apache.org/jira/browse/ARTEMIS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-445:
--
Assignee: Justin Bertram
> Truststore/Keystore password cannot be null although null
[
https://issues.apache.org/jira/browse/ARTEMIS-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-384:
---
Fix Version/s: (was: 1.2.0)
> Different QueueBrowser Behavior
>
[
https://issues.apache.org/jira/browse/ARTEMIS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-451.
Resolution: Fixed
> More improvements for JAAS text file reloading
>
[
https://issues.apache.org/jira/browse/ARTEMIS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221815#comment-15221815
]
Justin Bertram commented on ARTEMIS-13:
---
[~michalxo], I'm not clear on what documentation needs to
[
https://issues.apache.org/jira/browse/ARTEMIS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-462.
Resolution: Fixed
Fix Version/s: 1.3.0
> JMSXGroupId is not taken into account when
[
https://issues.apache.org/jira/browse/ARTEMIS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-476:
---
Fix Version/s: 1.3.0
> Instructions for running examples are triplicated and confusing in
[
https://issues.apache.org/jira/browse/ARTEMIS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-459:
--
Assignee: Justin Bertram
> ActiveMQActivation start/shutdown sequence may cause NPE
>
[
https://issues.apache.org/jira/browse/ARTEMIS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239690#comment-15239690
]
Justin Bertram commented on ARTEMIS-457:
Can you attach the broker.xml that corresponds with this
[
https://issues.apache.org/jira/browse/ARTEMIS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-457:
--
Assignee: Justin Bertram
> Scale down with live-only ha policy failing
>
[
https://issues.apache.org/jira/browse/ARTEMIS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239765#comment-15239765
]
Justin Bertram commented on ARTEMIS-457:
BTW, I believe this is caused by a bug in JGroups for
[
https://issues.apache.org/jira/browse/ARTEMIS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239769#comment-15239769
]
Justin Bertram commented on ARTEMIS-456:
This can be resolved, no?
> Potential dead lock in
[
https://issues.apache.org/jira/browse/ARTEMIS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239833#comment-15239833
]
Justin Bertram commented on ARTEMIS-439:
Can this be resolved? It appears to be done.
>
[
https://issues.apache.org/jira/browse/ARTEMIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-504.
Resolution: Fixed
Fix Version/s: 1.3.0
> Inconsistent time unit on scheduling slow
[
https://issues.apache.org/jira/browse/ARTEMIS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-475.
Resolution: Fixed
Fix Version/s: 1.3.0
> [Artemis Testsuite]
[
https://issues.apache.org/jira/browse/ARTEMIS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256636#comment-15256636
]
Justin Bertram commented on ARTEMIS-339:
Is this done?
> Implement JDBC Journal
>
[
https://issues.apache.org/jira/browse/ARTEMIS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-501.
Resolution: Fixed
Fix Version/s: (was: 1.2.0)
1.3.0
>
[
https://issues.apache.org/jira/browse/ARTEMIS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-497.
Resolution: Fixed
Fix Version/s: 1.3.0
> Sending a message sporadically stalls for
[
https://issues.apache.org/jira/browse/ARTEMIS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-497:
--
Assignee: Justin Bertram
> Sending a message sporadically stalls for ~10 seconds when
[
https://issues.apache.org/jira/browse/ARTEMIS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-502.
Resolution: Fixed
Fix Version/s: 1.3.0
> AMQ224044, error acknowledging message:
[
https://issues.apache.org/jira/browse/ARTEMIS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-504:
--
Assignee: Justin Bertram
> Inconsistent time unit on scheduling slow consumer reaper
[
https://issues.apache.org/jira/browse/ARTEMIS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-480.
Resolution: Fixed
Fix Version/s: 1.3.0
> [Artemis Testsuite]
>
[
https://issues.apache.org/jira/browse/ARTEMIS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-472.
Resolution: Fixed
Fix Version/s: 1.3.0
> AMQ222137 warning does not display the
[
https://issues.apache.org/jira/browse/ARTEMIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-386:
--
Assignee: Justin Bertram
> fix shebang on artemis scripts
>
[
https://issues.apache.org/jira/browse/ARTEMIS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256869#comment-15256869
]
Justin Bertram commented on ARTEMIS-418:
Based on my perusal of the ActiveMQ 5.x code it looks
[
https://issues.apache.org/jira/browse/ARTEMIS-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256651#comment-15256651
]
Justin Bertram commented on ARTEMIS-482:
This looks done. If so, can you resolve it?
>
[
https://issues.apache.org/jira/browse/ARTEMIS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-496.
Resolution: Not A Bug
> Client threads allocate a lot of memory
>
[
https://issues.apache.org/jira/browse/ARTEMIS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-459:
---
Fix Version/s: 1.3.0
> ActiveMQActivation start/shutdown sequence may cause NPE
>
[
https://issues.apache.org/jira/browse/ARTEMIS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258286#comment-15258286
]
Justin Bertram commented on ARTEMIS-496:
Can you test this on HEAD rather than 1.2? I seem to
Justin Bertram created ARTEMIS-510:
--
Summary: Do not create server-side queue from client when creating
JMS producer
Key: ARTEMIS-510
URL: https://issues.apache.org/jira/browse/ARTEMIS-510
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-510:
---
Fix Version/s: 1.3.0
> Do not create server-side queue from client when creating JMS
[
https://issues.apache.org/jira/browse/ARTEMIS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264335#comment-15264335
]
Justin Bertram commented on ARTEMIS-510:
The changes in 95b6328993b8215262cb49e0bc1e5999d3537e12
[
https://issues.apache.org/jira/browse/ARTEMIS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-382.
Resolution: Not A Problem
> Synchronization performed on
[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263010#comment-15263010
]
Justin Bertram commented on ARTEMIS-245:
My point is that a single change to the
[
https://issues.apache.org/jira/browse/ARTEMIS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262953#comment-15262953
]
Justin Bertram commented on ARTEMIS-382:
The synchronization is coordinating work between the
[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262415#comment-15262415
]
Justin Bertram commented on ARTEMIS-245:
Is this patch sufficient to get the RA working with
[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262430#comment-15262430
]
Justin Bertram commented on ARTEMIS-245:
The JavaDoc for
[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263279#comment-15263279
]
Justin Bertram commented on ARTEMIS-245:
That is good to know. That said, I'm still having
[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263280#comment-15263280
]
Justin Bertram commented on ARTEMIS-245:
Understood. According to the description, that's the
[
https://issues.apache.org/jira/browse/ARTEMIS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-382:
--
Assignee: Justin Bertram
> Synchronization performed on
[
https://issues.apache.org/jira/browse/ARTEMIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-386.
Resolution: Fixed
> fix shebang on artemis scripts
> --
>
>
[
https://issues.apache.org/jira/browse/ARTEMIS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258305#comment-15258305
]
Justin Bertram commented on ARTEMIS-382:
Why exactly is this a defect?
> Synchronization
[
https://issues.apache.org/jira/browse/ARTEMIS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-485.
Resolution: Fixed
Fix Version/s: 1.3.0
>From what I can tell this issue has been
[
https://issues.apache.org/jira/browse/ARTEMIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-383.
Resolution: Won't Fix
Assignee: Justin Bertram
The code in question is in a
[
https://issues.apache.org/jira/browse/ARTEMIS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293391#comment-15293391
]
Justin Bertram commented on ARTEMIS-529:
Is there any chance you'd be willing to send a PR for
201 - 300 of 6126 matches
Mail list logo
