[
https://issues.apache.org/jira/browse/ARTEMIS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-125:
---
Description:
If standalone shared backup is configured with disabled scale-down policy then
Miroslav Novak created ARTEMIS-125:
--
Summary: Standalone backup server with shared store does not start
if scaledown policy is defined but not enabled
Key: ARTEMIS-125
URL:
Miroslav Novak created ARTEMIS-179:
--
Summary: Artemis is logging warnings during reconnecting cluster
connection on server shut down
Key: ARTEMIS-179
URL: https://issues.apache.org/jira/browse/ARTEMIS-179
Miroslav Novak created ARTEMIS-185:
--
Summary: Clients should not throw HornetQException/JMSException to
application code during failover
Key: ARTEMIS-185
URL: https://issues.apache.org/jira/browse/ARTEMIS-185
[
https://issues.apache.org/jira/browse/ARTEMIS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-157:
---
Priority: Critical (was: Major)
Connection factory ignores HA property when serialized to
[
https://issues.apache.org/jira/browse/ARTEMIS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634815#comment-14634815
]
Miroslav Novak commented on ARTEMIS-157:
Increasing priority to blocker as this
[
https://issues.apache.org/jira/browse/ARTEMIS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-157:
---
Priority: Blocker (was: Critical)
Connection factory ignores HA property when serialized
[
https://issues.apache.org/jira/browse/ARTEMIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940898#comment-14940898
]
Miroslav Novak commented on ARTEMIS-160:
Any update on this? This is not a blocker but quite
Miroslav Novak created ARTEMIS-242:
--
Summary: IllegalStateException thrown during producer.send()
Key: ARTEMIS-242
URL: https://issues.apache.org/jira/browse/ARTEMIS-242
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302193#comment-15302193
]
Miroslav Novak commented on ARTEMIS-541:
I understand the reasons. Idea was to make something
Miroslav Novak created ARTEMIS-541:
--
Summary: Optimize live/backup replication after failback
Key: ARTEMIS-541
URL: https://issues.apache.org/jira/browse/ARTEMIS-541
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-541:
---
Issue Type: New Feature (was: Bug)
> Optimize live/backup replication after failback
>
Miroslav Novak created ARTEMIS-546:
--
Summary: Allow to disable client-side load-balancing
Key: ARTEMIS-546
URL: https://issues.apache.org/jira/browse/ARTEMIS-546
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/ARTEMIS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307591#comment-15307591
]
Miroslav Novak commented on ARTEMIS-546:
Looking at the code in
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak resolved ARTEMIS-359.
Resolution: Fixed
> [TestSuite] IBM JDK does not allow to instrument classes
>
Miroslav Novak created ARTEMIS-359:
--
Summary: [TestSuite] IBM JDK does not allow to instrument classes
Key: ARTEMIS-359
URL: https://issues.apache.org/jira/browse/ARTEMIS-359
Project: ActiveMQ
Miroslav Novak created ARTEMIS-473:
--
Summary: Activate server with most up-to-date journal from
live/backup pair
Key: ARTEMIS-473
URL: https://issues.apache.org/jira/browse/ARTEMIS-473
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276039#comment-15276039
]
Miroslav Novak commented on ARTEMIS-517:
[~jbertram] Thanks Justin for update! We'll try it and
Miroslav Novak created ARTEMIS-516:
--
Summary: Rebalancing of outbound connections if cluster topology
changes
Key: ARTEMIS-516
URL: https://issues.apache.org/jira/browse/ARTEMIS-516
Project:
Miroslav Novak created ARTEMIS-517:
--
Summary: Provide public API method to check whether backup is
synchronized with live server
Key: ARTEMIS-517
URL: https://issues.apache.org/jira/browse/ARTEMIS-517
Miroslav Novak created ARTEMIS-665:
--
Summary: Optimize master/slave replication after failback - slave
does not have to resync journal from master after failback
Key: ARTEMIS-665
URL:
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417115#comment-15417115
]
Miroslav Novak commented on ARTEMIS-473:
This feature request should handle options a) and b). c)
[
https://issues.apache.org/jira/browse/ARTEMIS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417112#comment-15417112
]
Miroslav Novak commented on ARTEMIS-679:
In replicated journal when backup is started before
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-473:
---
Description:
If master-slave pair is configured using replicated journal and there are no
Miroslav Novak created ARTEMIS-679:
--
Summary: Activate most up to date server from
master-slave(live-backup) pair
Key: ARTEMIS-679
URL: https://issues.apache.org/jira/browse/ARTEMIS-679
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-679:
---
Priority: Critical (was: Major)
> Activate most up to date server from
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416643#comment-15416643
]
Miroslav Novak edited comment on ARTEMIS-473 at 8/11/16 6:39 AM:
-
I've
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416620#comment-15416620
]
Miroslav Novak commented on ARTEMIS-473:
Sorry, the title says something different then there is
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416643#comment-15416643
]
Miroslav Novak commented on ARTEMIS-473:
I've created new jira for the description - ARTEMIS-679
Miroslav Novak created ARTEMIS-600:
--
Summary: Enterprise message grouping
Key: ARTEMIS-600
URL: https://issues.apache.org/jira/browse/ARTEMIS-600
Project: ActiveMQ Artemis
Issue Type: New
[
https://issues.apache.org/jira/browse/ARTEMIS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356589#comment-15356589
]
Miroslav Novak commented on ARTEMIS-599:
Cool, thanks!
> Add --f option to ignore locking of
[
https://issues.apache.org/jira/browse/ARTEMIS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1583#comment-1583
]
Miroslav Novak commented on ARTEMIS-600:
I did not create jiras for points 3, 4, 5. I did some
[
https://issues.apache.org/jira/browse/ARTEMIS-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak closed ARTEMIS-946.
--
Resolution: Fixed
Just tried If I can move jira - not possible :-( Closing.
> CLONE -
[
https://issues.apache.org/jira/browse/ARTEMIS-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829502#comment-15829502
]
Miroslav Novak commented on ARTEMIS-926:
I agree with Clebert, Methods on Properties class are
Miroslav Novak created ARTEMIS-681:
--
Summary: Do not use just one "sf.my-cluster..." queue for message
load-balancing and redistribution
Key: ARTEMIS-681
URL: https://issues.apache.org/jira/browse/ARTEMIS-681
[
https://issues.apache.org/jira/browse/ARTEMIS-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-681:
---
Priority: Critical (was: Major)
> Do not use just one "sf.my-cluster..." queue for message
Miroslav Novak created ARTEMIS-1001:
---
Summary: slow-consumer-check-period is in minutes but behaves like
with seconds
Key: ARTEMIS-1001
URL: https://issues.apache.org/jira/browse/ARTEMIS-1001
[
https://issues.apache.org/jira/browse/ARTEMIS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887539#comment-15887539
]
Miroslav Novak commented on ARTEMIS-1001:
-
5 second window for calculating msg/s rate for
Miroslav Novak created ARTEMIS-1011:
---
Summary: Slow consumer detection - producer msg/s rate for queue
should take into account messages which are already in queue
Key: ARTEMIS-1011
URL:
[
https://issues.apache.org/jira/browse/ARTEMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891700#comment-15891700
]
Miroslav Novak commented on ARTEMIS-921:
[~clebertsuconic] Ok, I've created new jira
[
https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432755#comment-15432755
]
Miroslav Novak commented on ARTEMIS-473:
[~clebertsuconic] do you think that options a) and b)
[
https://issues.apache.org/jira/browse/ARTEMIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541709#comment-15541709
]
Miroslav Novak commented on ARTEMIS-709:
PR is merged, should this be resolved?
> Possible NPE
[
https://issues.apache.org/jira/browse/ARTEMIS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-809:
---
Issue Type: Bug (was: Improvement)
> Trace logs contain content of large messages creating
Miroslav Novak created ARTEMIS-809:
--
Summary: Trace logs contain content of large messages creating
really huge log files
Key: ARTEMIS-809
URL: https://issues.apache.org/jira/browse/ARTEMIS-809
Miroslav Novak created ARTEMIS-804:
--
Summary: Log message id for dropped messages
Key: ARTEMIS-804
URL: https://issues.apache.org/jira/browse/ARTEMIS-804
Project: ActiveMQ Artemis
Issue
[
https://issues.apache.org/jira/browse/ARTEMIS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-804:
---
Priority: Minor (was: Major)
> Log message id for dropped messages
>
[
https://issues.apache.org/jira/browse/ARTEMIS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Novak updated ARTEMIS-804:
---
Issue Type: Improvement (was: Bug)
> Log message id for dropped messages
>
[
https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727905#comment-15727905
]
Miroslav Novak commented on ARTEMIS-201:
I agree with Jeff, just not sure if to reduce it to INFO
[
https://issues.apache.org/jira/browse/ARTEMIS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901302#comment-15901302
]
Miroslav Novak commented on ARTEMIS-1001:
-
Thanks [~jbertram], I just "git blamed" the
[
https://issues.apache.org/jira/browse/ARTEMIS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898920#comment-15898920
]
Miroslav Novak commented on ARTEMIS-1011:
-
Looks like that ActiveMQ 5.x does not bother by
[
https://issues.apache.org/jira/browse/ARTEMIS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898875#comment-15898875
]
Miroslav Novak commented on ARTEMIS-1011:
-
This is similar to DROP policy than to Artemis slow
[
https://issues.apache.org/jira/browse/ARTEMIS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896893#comment-15896893
]
Miroslav Novak commented on ARTEMIS-1011:
-
At this moment If producer does not send any messages
[
https://issues.apache.org/jira/browse/ARTEMIS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893884#comment-15893884
]
Miroslav Novak commented on ARTEMIS-1011:
-
> I'm not clear why you need the AtomicLong
[
https://issues.apache.org/jira/browse/ARTEMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890330#comment-15890330
]
Miroslav Novak commented on ARTEMIS-921:
There is still a problem how producer msg/s rate is
[
https://issues.apache.org/jira/browse/ARTEMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890341#comment-15890341
]
Miroslav Novak commented on ARTEMIS-921:
Can we fix it in scope of this jira? I can't reopen it
[
https://issues.apache.org/jira/browse/ARTEMIS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900789#comment-15900789
]
Miroslav Novak commented on ARTEMIS-1011:
-
Agreed, thanks [~jbertram] for looking at it. My
Miroslav Novak created ARTEMIS-1743:
---
Summary: NPE in server log when Artemis trace logging is enabled
Key: ARTEMIS-1743
URL: https://issues.apache.org/jira/browse/ARTEMIS-1743
Project: ActiveMQ
Miroslav Novak created ARTEMIS-2171:
---
Summary: ThreadPoolExecutor leak under SM due to lack of
privileged block
Key: ARTEMIS-2171
URL: https://issues.apache.org/jira/browse/ARTEMIS-2171
Project:
Miroslav Novak created ARTEMIS-2109:
---
Summary: Cannot build Artemis with JDK 11
Key: ARTEMIS-2109
URL: https://issues.apache.org/jira/browse/ARTEMIS-2109
Project: ActiveMQ Artemis
Issue
Miroslav Novak created ARTEMIS-2284:
---
Summary: Artemis 2.7.0 logs password for STOMP protocol in clear
text in debug logs
Key: ARTEMIS-2284
URL: https://issues.apache.org/jira/browse/ARTEMIS-2284
60 matches
Mail list logo
