Just to address the technical question of skinning the console, we've a
vendor.js file just for that purpose. So at the simplest level skinning
would be a matter of extending the existing hawtio-web.war and replacing
the vendor.js file, and likely adding your own .css file.
So in vendor.js you
[
https://issues.apache.org/jira/browse/AMQ-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13165427#comment-13165427
]
Stan Lewis commented on AMQ-3623:
-
Yeah, totally agree, sorry I missed that. We get away
[
https://issues.apache.org/jira/browse/AMQ-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13165428#comment-13165428
]
Stan Lewis commented on AMQ-3623:
-
Yeah, totally agree, sorry I missed that. We get away
: Broker
Reporter: Stan Lewis
Priority: Minor
Left the appender added to the root appender, so here's a patch that ensures
that appender is cleaned up, thanks Claudio for spotting that.
--
This message is automatically generated by JIRA.
If you think it was sent
[
https://issues.apache.org/jira/browse/AMQ-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3628:
Attachment: 0001-Clean-up-appender.patch
AMQ3567Test doesn't clean up appender after AMQ-3623 update
[
https://issues.apache.org/jira/browse/AMQ-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3628:
Description: Left the appender added to the root appender when I updated
AMQ3567Test as part of AMQ-3623, so
[
https://issues.apache.org/jira/browse/AMQ-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13165439#comment-13165439
]
Stan Lewis commented on AMQ-3623:
-
Created AMQ-3628 for the fix since this feature's been
[
https://issues.apache.org/jira/browse/AMQ-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3625:
Attachment: 0001-Avoid-NPE.patch
NullPointer Exceptions when networked broker sends certificate
: 5.5.1
Reporter: Stan Lewis
Start up a subscriber when no messages are available and this NPE will
eventually get logged:
2011-12-02 15:01:00,588 | WARN | Failed to browse Topic: xxx |
org.apache.activemq.broker.region.Topic | ActiveMQ Broker[xxx] Scheduler
[
https://issues.apache.org/jira/browse/AMQ-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3622:
Attachment: 0001-Avoid-NPE.patch
Here's the patch!
NPE
Affects Versions: 5.5.1
Reporter: Stan Lewis
Priority: Minor
Couple tests keep an eye on the logging for specific failures, be good to have
a common approach to this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact
[
https://issues.apache.org/jira/browse/AMQ-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3623:
Attachment: 0001-Add-DefaultTestAppender-and-modify-existing-tests-to.patch
Add DefaultTestAppender
[
https://issues.apache.org/jira/browse/AMQ-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3622:
Attachment: 0002-Add-test-for-AMQ-3622.patch
Here's the test for this patch, needs patch applied for AMQ
Type: New Feature
Components: Broker
Affects Versions: 5.5.1
Reporter: Stan Lewis
There's a fairly important case where an error message is logged due to an
accept failure, however the remote address info isn't logged as part of this
message. There's a couple other
[
https://issues.apache.org/jira/browse/AMQ-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3624:
Attachment: 0001-Add-remote-host-info-to-a-couple-log-messages.patch
Add IP address of clients to ERROR
[
https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057805#comment-13057805
]
Stan Lewis commented on AMQ-3383:
-
Yeah, you're probably right. A string works for my
[
https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3383:
Attachment: AMQ-3383.diff
Add a string property (token) to ConnectionControl so the broker could
[
https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3383:
Attachment: (was: AMQ-3383.diff)
Add a string property (token) to ConnectionControl so the broker could
[
https://issues.apache.org/jira/browse/AMQ-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-3383:
Attachment: AMQ-3383.diff
Add a string property (token) to ConnectionControl so the broker could
--
Key: AMQ-3383
URL: https://issues.apache.org/jira/browse/AMQ-3383
Project: ActiveMQ
Issue Type: Improvement
Reporter: Stan Lewis
Priority: Trivial
Attachments: AMQ-3383.diff
When a client creates a connection
Maybe try running that from the root of the apollo installation? I
don't have Windows to try it out on but that's how I've used the
script to create a broker on Mac. Then to start that broker I usually
run the generated script also from the root directory of the install
as well, i.e.
Contributions are always welcomed, you should have a look at:
http://activemq.apache.org/contributing.html
which lays out the process of how to submit patches. Thanks!
On Tue, Apr 5, 2011 at 1:59 PM, Oliver ohook...@gmail.com wrote:
Hi,
Yesterday I gave the ActiveMQ init scripts (referenced
-00) on fusesource.com?
Thanks,
Lei
--
View this message in context:
http://activemq.2283324.n4.nabble.com/how-to-get-5-4-2-fuse-01-00-release-on-fusesource-com-tp3264908p3264908.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Stan Lewis
FuseSource
Email: sle
-filter-for-messages-tp3090334p3093202.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Stan Lewis
FuseSource
Email: sle...@fusesource.com
Web: http://fusesource.com
Twitter: gashcrumb
[
https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2584:
Attachment: UpdatedTestCase.patch
Looks like there's still a case this issue can occur, namely
[
https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis reopened AMQ-2584:
-
Massege store is not cleaned when durable topic subscribers are refusing
messages
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 68 ---
.../apollo/broker/perf/DeepQueueScenarios.scala| 52 +-
.../apollo/broker/perf/LargeInitialDB.scala| 123
.../apollo/broker/perf/PersistentScenario.scala|6 +
---
.../apollo/stomp/perf/StompRemoteClients.scala | 65 +--
1 files changed, 44 insertions(+), 21 deletions(-)
diff --git a/apollo-stomp/src/test/scala/org/apache/activemq/apollo/stomp/perf/StompRemoteClients.scala
---
pom.xml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/pom.xml b/pom.xml
index 47198dd..ba18d69 100755
--- a/pom.xml
+++ b/pom.xml
@@ -100,7 +100,7 @@
felix-version1.0.0/felix-version
hawtdispatch-version1.0/hawtdispatch-version
-
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 196 +---
.../apollo/broker/perf/DeepQueueScenarios.scala|9 +-
.../apollo/broker/perf/LargeInitialDB.scala| 41 ++---
.../apollo/broker/perf/PersistentScenario.scala|4 +-
---
.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/.gitignore b/.gitignore
index 763faf6..a8bb226 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,4 @@ apollo-web/activemq.xml
apollo-web/activemq.xml.*
apollo-web/overlays/
---
.../apollo/stomp/perf/StompRemoteClients.scala | 40
1 files changed, 0 insertions(+), 40 deletions(-)
diff --git a/apollo-stomp/src/test/scala/org/apache/activemq/apollo/stomp/perf/StompRemoteClients.scala
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 150 +++-
.../apollo/broker/perf/LargeInitialDB.scala| 11 +-
.../apollo/broker/perf/RemoteConnection.scala | 142 ++
.../apollo/stomp/perf/StompRemoteClients.scala | 46 +--
---
.../apollo/broker/perf/persistent-report.html | 417 +++-
.../apollo/broker/perf/BasicScenarios.scala|1 -
.../apollo/broker/perf/BrokerPerfSupport.scala |5 +-
.../apollo/broker/perf/PersistentScenario.scala|3 +-
4 files changed, 224
The next 8 patches coming in improve the apollo-stomp performance tests:
1) Adds a test that creates an initial DB with 1M messages
2) Fixes the persistent-report.html template to match up with the
BasicScenarios trait
3) Some general cleanup
---
.../apollo/stomp/perf/StompRemoteClients.scala | 65 +--
1 files changed, 44 insertions(+), 21 deletions(-)
diff --git a/apollo-stomp/src/test/scala/org/apache/activemq/apollo/stomp/perf/StompRemoteClients.scala
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 68 ---
.../apollo/broker/perf/DeepQueueScenarios.scala| 52 +-
.../apollo/broker/perf/LargeInitialDB.scala| 123
.../apollo/broker/perf/PersistentScenario.scala|6 +
---
.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/.gitignore b/.gitignore
index 763faf6..a8bb226 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,4 @@ apollo-web/activemq.xml
apollo-web/activemq.xml.*
apollo-web/overlays/
---
.../apollo/stomp/perf/StompRemoteClients.scala | 40
1 files changed, 0 insertions(+), 40 deletions(-)
diff --git a/apollo-stomp/src/test/scala/org/apache/activemq/apollo/stomp/perf/StompRemoteClients.scala
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 196 +---
.../apollo/broker/perf/DeepQueueScenarios.scala|9 +-
.../apollo/broker/perf/LargeInitialDB.scala| 41 ++---
.../apollo/broker/perf/PersistentScenario.scala|4 +-
---
pom.xml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/pom.xml b/pom.xml
index 47198dd..ba18d69 100755
--- a/pom.xml
+++ b/pom.xml
@@ -100,7 +100,7 @@
felix-version1.0.0/felix-version
hawtdispatch-version1.0/hawtdispatch-version
-
---
.../apollo/broker/perf/BrokerPerfSupport.scala | 150 +++-
.../apollo/broker/perf/LargeInitialDB.scala| 11 +-
.../apollo/broker/perf/RemoteConnection.scala | 142 ++
.../apollo/stomp/perf/StompRemoteClients.scala | 46 +--
---
.../apollo/broker/perf/persistent-report.html | 417 +++-
.../apollo/broker/perf/BasicScenarios.scala|1 -
.../apollo/broker/perf/BrokerPerfSupport.scala |5 +-
.../apollo/broker/perf/PersistentScenario.scala|3 +-
4 files changed, 224
: Transport
Affects Versions: 5.4.1
Reporter: Stan Lewis
Attachments: AMQ-2942.txt
Well, you can however the configuration isn't applied. This patch sorts that
out. Note that I couldn't automate a test for this as I had to manually kill
off one of the brokers to get
Could be related to this issue that's fixed in 5.4.1 perhaps:
https://issues.apache.org/activemq/browse/AMQ-2584
Can you try your test with 5.4.1 and see if that changes things? If
not can you create a Jira and attach your test so we can check it out:
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.0
Reporter: Stan Lewis
Attachments: AMQ-2915.txt
Basically when you create a queue/topic and connect either a producer or
consumer to that queue/topic advisory topics are created
[
https://issues.apache.org/activemq/browse/AMQ-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2915:
Attachment: AMQ-2915.txt
Associated advisory topics aren't cleaned up when a topic/queue is deleted
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis reopened AMQ-2880:
-
This problem also occurs with XA transactions (like in the example stack trace)
so we need a similar fix
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2880:
Attachment: patch_for_xa_transaction.txt
This should take care of XA transactions.
Exception thrown
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2880:
Attachment: (was: patch_for_xa_transaction.txt)
Exception thrown during commit leads to message
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2880:
Attachment: xa-test-case.txt
patch_for_xa_transaction.txt
Here's a test
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2880:
Attachment: test-case.txt
Exception thrown during commit leads to message loss
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61454#action_61454
]
Stan Lewis commented on AMQ-2880:
-
Just a note to simulate the real lock timeout exception
[
https://issues.apache.org/activemq/browse/AMQ-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2880:
Attachment: test-case.txt
This shows the problem better, as each time a new consumer is created
[
https://issues.apache.org/activemq/browse/AMQ-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2764:
Attachment: test-case.txt
Thanks for that, have re-worked the test case and it does reproduce the issue
[
https://issues.apache.org/activemq/browse/AMQ-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2764:
Attachment: test-case.txt
I've put together a test case similar to the NetworkReconnectTest
[
https://issues.apache.org/activemq/browse/AMQ-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61345#action_61345
]
Stan Lewis edited comment on AMQ-2764 at 8/23/10 4:57 PM:
--
I've put
[
https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2584:
Attachment: AMQ2584Test.java
Hey Gary, I modified the test case to use multiple consumers, I think
[
https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis reopened AMQ-2584:
-
Yup, sure thing Gary. Haven't had time to look at it other than updating the
test case, but I think it's
Issue Type: Improvement
Components: Broker
Reporter: Stan Lewis
Priority: Minor
It would be nice if a queue could have the exclusive consumer property set by
default at startup, so making all consumers connected to that queue behave like
exclusive consumers
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.0
Reporter: Stan Lewis
Priority: Trivial
Attachments: patch.txt
When you check out the ObjectName of a durable subscription there's a space
between Durable and subscriptionID:
{code
[
https://issues.apache.org/activemq/browse/AMQ-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2623:
Attachment: patch.txt
Upgrade woodstox version in activemq-xmpp
Versions: 5.3.0
Reporter: Stan Lewis
Priority: Minor
Attachments: patch.txt
Was looking to get activemq-xmpp working with Adium, during the course of this
I noticed that this component is using a pretty old version of woodstox, so
updated that and tidied up
[
https://issues.apache.org/activemq/browse/AMQ-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2622:
Attachment: unit-test.txt
Here's a unit test patch that shows the problem, am currently looking
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=57595#action_57595
]
Stan Lewis commented on AMQ-2412:
-
I'll check that out, what's the failure you're seeing
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=57598#action_57598
]
Stan Lewis commented on AMQ-2412:
-
If it's a random deadlock that occurs during that last test
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2412:
Attachment: (was: patch.txt)
Allow xmpp clients to message each other directly, more tests, updated
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2412:
Attachment: patch.txt
Okay, think I've gotten the deadlock fixed. The tests are a bit prone to
timing
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2412:
Attachment: (was: patch.txt)
Allow xmpp clients to message each other directly, more tests, updated
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2412:
Attachment: patch.txt
Updated patch that applies cleanly for 5.4-SNAPSHOT
Allow xmpp clients
[
https://issues.apache.org/activemq/browse/AMQ-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2412:
Attachment: patch.txt
Allow xmpp clients to message each other directly, more tests, updated schema
[
https://issues.apache.org/activemq/browse/AMQ-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stan Lewis updated AMQ-2406:
Attachment: patch.txt
activemq-xmpp contains some System.out.println statements
[
https://issues.apache.org/activemq/browse/AMQ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=52592#action_52592
]
Stan Lewis commented on AMQ-2094:
-
Just to add to this, with this change clustering
73 matches
Mail list logo
