Nabble - ActiveMQ - Dev

[jira] Resolved: (AMQ-2486) systemExitOnShutdown="true" causes broker shutdown to hang

2009-11-12T03:37:53Z

[ https://issues.apache.org/activemq/browse/AMQ-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-2486.
--------------------------------

Resolution: Fixed
Fix Version/s: 5.4.0
5.3.1

Using Runtime.getRuntime().halt() instead of System.exit() as the later is not recommended to be used in shutdown hooks. There should be no problems with halt() as all resources are cleaned up before this call.

> systemExitOnShutdown="true" causes broker shutdown to hang
> ----------------------------------------------------------
>
> Key: AMQ-2486
> URL: https://issues.apache.org/activemq/browse/AMQ-2486
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.3.1, 5.4.0
>
>
> To reproduce:
> * add systemExitOnShutdown="true" to the <broker> tag
> * start a broker
> * try to stop the broker

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-2487) MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.

2009-11-12T02:45:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2487.
-----------------------------

Resolution: Fixed

resolve in r835325, modified an existing test to verify.

> MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-2487
> URL: https://issues.apache.org/activemq/browse/AMQ-2487
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Environment: N/A
> Reporter: Colin MacNaughton
> Assignee: Gary Tully
> Fix For: 5.4.0
>
> Attachments: AMQ-2487patch.txt
>
>
> Given the following broker destination policy
> {code:xml}
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic=">" producerFlowControl="true"
> memoryLimit="1mb">
> <pendingSubscriberPolicy>
> <vmCursor />
> </pendingSubscriberPolicy>
> </policyEntry>
> <policyEntry queue=">" producerFlowControl="true"
> memoryLimit="1mb">
> 
> <pendingQueuePolicy>
> <vmQueueCursor />
> </pendingQueuePolicy>
> </policyEntry>
> </policyEntries>
> </policyMap>
> </destinationPolicy>
> {code}
> If I send message to queue://TESTQ1 with an expiration of 1second, with an unreliable/slow receiver, the publisher eventually hangs sending to the queue. The underlying problem is that when the message is expired to the DLQ the MemoryUsage reference is left pointing the TESTQ1's memory limiter, instead of being reset to the DLQ limiter, and when it is added to the DLQ, TESTQ1's memory limiter is updated counteracting the decrement that is done by the TESTQ1 when the message is expired.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2487) MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.

2009-11-12T02:45:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-2487:
----------------------------

Affects Version/s: (was: 5.4.0)
5.3.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (AMQ-2487) MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.

2009-11-12T02:02:02Z

[ https://issues.apache.org/activemq/browse/AMQ-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully reassigned AMQ-2487:
-------------------------------

Assignee: Gary Tully

> MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-2487
> URL: https://issues.apache.org/activemq/browse/AMQ-2487
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Environment: N/A
> Reporter: Colin MacNaughton
> Assignee: Gary Tully
> Fix For: 5.4.0
>
> Attachments: AMQ-2487patch.txt
>
>
> Given the following broker destination policy
> {code:xml}
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic=">" producerFlowControl="true"
> memoryLimit="1mb">
> <pendingSubscriberPolicy>
> <vmCursor />
> </pendingSubscriberPolicy>
> </policyEntry>
> <policyEntry queue=">" producerFlowControl="true"
> memoryLimit="1mb">
> 
> <pendingQueuePolicy>
> <vmQueueCursor />
> </pendingQueuePolicy>
> </policyEntry>
> </policyEntries>
> </policyMap>
> </destinationPolicy>
> {code}
> If I send message to queue://TESTQ1 with an expiration of 1second, with an unreliable/slow receiver, the publisher eventually hangs sending to the queue. The underlying problem is that when the message is expired to the DLQ the MemoryUsage reference is left pointing the TESTQ1's memory limiter, instead of being reset to the DLQ limiter, and when it is added to the DLQ, TESTQ1's memory limiter is updated counteracting the decrement that is done by the TESTQ1 when the message is expired.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2488) Unable to access Serializable class when receiving ObjectMessage in OSGi environment

2009-11-12T00:23:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen updated AMQ-2488:
---------------------------------

Component/s: Broker
Affects Version/s: 5.3.0
Summary: Unable to access Serializable class when receiving ObjectMessage in OSGi environment (was: ClassNotFoundException attempting to use Log4J LoggingEvent)

This issue was originally created for ServiceMix 4, but I think the real issue is inside the activemq-core bundle.

> Unable to access Serializable class when receiving ObjectMessage in OSGi environment
> ------------------------------------------------------------------------------------
>
> Key: AMQ-2488
> URL: https://issues.apache.org/activemq/browse/AMQ-2488
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Darren Davison
> Attachments: amq-error.log, amq-headers.log, SMX4-424.diff
>
>
> I have configured applications to use Log4J's JMSAppender in order to log messages on a queue as follows;
> {noformat}
> log4j.appender.jms=org.apache.log4j.net.JMSAppender
> log4j.appender.jms.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> log4j.appender.jms.ProviderURL=tcp://localhost:61616
> log4j.appender.jms.TopicBindingName=logTopic
> log4j.appender.jms.TopicConnectionFactoryBindingName=ConnectionFactory
> {noformat}
> Each application logging statement adds a new message to topic://logTopic on the broker. I have a bundle deployed that attempts to route the messages from this topic with camel;
> {code}
> from("activemq:topic:logTopic")
> .convertBodyTo(String.class)
> .to("log:foo?level=DEBUG&showProperties=true&showHeaders=true");
> {code}
> When using servicemix 4 (Fuse 4.1.0.4), a stack trace is seen with the following message (enhanced using felix.log.level=4);
> {noformat}Caused by: java.lang.ClassNotFoundException: *** Class 'org.apache.log4j.spi.LoggingEvent'
> was not found because bundle 56 does not import 'org.apache.log4j.spi' even though bundle 84
> does export it. To resolve this issue, add an import for 'org.apache.log4j.spi' to bundle 56. ***
> {noformat}
> Bundles as follows;
> {noformat}smx@root:/> osgi/list|grep 56
> [ 56] [Active ] [ ] [ 60] activemq-core (5.3.0.fuse)
> smx@root:/> osgi/list|grep 84
> [ 84] [Active ] [ ] [ 8] OPS4J Pax Logging - API (1.3.0)
> {noformat}

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2488) Unable to access Serializable class when receiving ObjectMessage in OSGi environment

2009-11-12T00:23:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55330#action_55330 ]

Darren Davison commented on AMQ-2488:
-------------------------------------

sorry, I thought I'd included those OSGi headers in one of the attachments. It does import that package. Here are the headers from my bundle with the camel route (line breaks added by me for formatting)
\\
\\
{noformat}Application Log Router (75)
---------------------------
Manifest-Version = 1.0
Bnd-LastModified = 1257721682850
Tool = Bnd-0.0.238
Bundle-Name = Application Log Router
Built-By = darren
Import-Package = org.apache.activemq;version="5.2.0.fuse",
org.apache.camel; version="1.6.1.fuse",
org.apache.camel.builder;version="1.6.1.fuse",
org.apache.camel.component.jms;version="1.6.1.fuse",
org.apache.camel.model;version="1.6.1.fuse",
org.apache.camel.spring;version="1.6.1.fuse",
org.apache.commons.logging,
org.apache.log4j.spi,
org.davisononline.fuselogger
Bundle-SymbolicName = org.davisononline.fuse-logger
Export-Package = org.davisononline.fuselogger;
uses:="org.apache.camel.builder,org.apache.camel.model,
org.apache.commons.logging,org.apache.camel,org.apache.camel.spring"
Bundle-Version = 0.0.1.SNAPSHOT
Build-Jdk = 1.6.0_16
Created-By = Apache Maven Bundle Plugin
Bundle-ManifestVersion = 2
{noformat}
\\
\\
I queried this all with gertv on IRC, it was he that suggested this looked like an activemq bug and henced raised here.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Moved: (AMQ-2488) ClassNotFoundException attempting to use Log4J LoggingEvent

2009-11-12T00:21:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen moved SMX4-424 to AMQ-2488:
-------------------------------------------

Key: AMQ-2488 (was: SMX4-424)
Project: ActiveMQ (was: ServiceMix 4)

> ClassNotFoundException attempting to use Log4J LoggingEvent
> -----------------------------------------------------------
>
> Key: AMQ-2488
> URL: https://issues.apache.org/activemq/browse/AMQ-2488
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Darren Davison
> Attachments: amq-error.log, amq-headers.log, SMX4-424.diff
>
>
> I have configured applications to use Log4J's JMSAppender in order to log messages on a queue as follows;
> {noformat}
> log4j.appender.jms=org.apache.log4j.net.JMSAppender
> log4j.appender.jms.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> log4j.appender.jms.ProviderURL=tcp://localhost:61616
> log4j.appender.jms.TopicBindingName=logTopic
> log4j.appender.jms.TopicConnectionFactoryBindingName=ConnectionFactory
> {noformat}
> Each application logging statement adds a new message to topic://logTopic on the broker. I have a bundle deployed that attempts to route the messages from this topic with camel;
> {code}
> from("activemq:topic:logTopic")
> .convertBodyTo(String.class)
> .to("log:foo?level=DEBUG&showProperties=true&showHeaders=true");
> {code}
> When using servicemix 4 (Fuse 4.1.0.4), a stack trace is seen with the following message (enhanced using felix.log.level=4);
> {noformat}Caused by: java.lang.ClassNotFoundException: *** Class 'org.apache.log4j.spi.LoggingEvent'
> was not found because bundle 56 does not import 'org.apache.log4j.spi' even though bundle 84
> does export it. To resolve this issue, add an import for 'org.apache.log4j.spi' to bundle 56. ***
> {noformat}
> Bundles as follows;
> {noformat}smx@root:/> osgi/list|grep 56
> [ 56] [Active ] [ ] [ 60] activemq-core (5.3.0.fuse)
> smx@root:/> osgi/list|grep 84
> [ 84] [Active ] [ ] [ 8] OPS4J Pax Logging - API (1.3.0)
> {noformat}

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2487) MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.

2009-11-11T23:49:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin MacNaughton updated AMQ-2487:
-----------------------------------

Attachment: AMQ-2487patch.txt

Patch file attached. It is worth investigating if there are other problematic scenarios where BrokerRegion.doResend might be using the wrong MemoryUsage

> MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-2487
> URL: https://issues.apache.org/activemq/browse/AMQ-2487
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Environment: N/A
> Reporter: Colin MacNaughton
> Fix For: 5.4.0
>
> Attachments: AMQ-2487patch.txt
>
>
> Given the following broker destination policy
> {code:xml}
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic=">" producerFlowControl="true"
> memoryLimit="1mb">
> <pendingSubscriberPolicy>
> <vmCursor />
> </pendingSubscriberPolicy>
> </policyEntry>
> <policyEntry queue=">" producerFlowControl="true"
> memoryLimit="1mb">
> 
> <pendingQueuePolicy>
> <vmQueueCursor />
> </pendingQueuePolicy>
> </policyEntry>
> </policyEntries>
> </policyMap>
> </destinationPolicy>
> {code}
> If I send message to queue://TESTQ1 with an expiration of 1second, with an unreliable/slow receiver, the publisher eventually hangs sending to the queue. The underlying problem is that when the message is expired to the DLQ the MemoryUsage reference is left pointing the TESTQ1's memory limiter, instead of being reset to the DLQ limiter, and when it is added to the DLQ, TESTQ1's memory limiter is updated counteracting the decrement that is done by the TESTQ1 when the message is expired.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (AMQ-2487) MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.

2009-11-11T23:45:52Z

MemoryUsage not properly accounted for when expiring messages to DLQ: can lead to hang.
---------------------------------------------------------------------------------------

Key: AMQ-2487
URL: https://issues.apache.org/activemq/browse/AMQ-2487
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.0
Environment: N/A
Reporter: Colin MacNaughton
Fix For: 5.4.0

Given the following broker destination policy
{code:xml}
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="true"
memoryLimit="1mb">
<pendingSubscriberPolicy>
<vmCursor />
</pendingSubscriberPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="true"
memoryLimit="1mb">

<pendingQueuePolicy>
<vmQueueCursor />
</pendingQueuePolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
{code}

If I send message to queue://TESTQ1 with an expiration of 1second, with an unreliable/slow receiver, the publisher eventually hangs sending to the queue. The underlying problem is that when the message is expired to the DLQ the MemoryUsage reference is left pointing the TESTQ1's memory limiter, instead of being reset to the DLQ limiter, and when it is added to the DLQ, TESTQ1's memory limiter is updated counteracting the decrement that is done by the TESTQ1 when the message is expired.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQNET-205) Add support for Message Body Compression and Decompression

2009-11-11T13:28:44Z

[ https://issues.apache.org/activemq/browse/AMQNET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55321#action_55321 ]

Timothy Bish commented on AMQNET-205:
-------------------------------------

I've added ICompressionPolicy and a default implementation to the NMS.ActiveMQ project as well as modifying the Message commands to use that for their compression streams.

> Add support for Message Body Compression and Decompression
> ----------------------------------------------------------
>
> Key: AMQNET-205
> URL: https://issues.apache.org/activemq/browse/AMQNET-205
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.2.0
>
> Attachments: DefaultCompressionService.cs
>
>
> Add the framework in NMS.ActiveMQ to deal with Messages that are tagged as Compressed, as well as allowing messages to be sent with Compression.
> The Java based ActiveMQ client's ConnectionFactory allows a user to turn on Compression for the Connections it creates, this causes the client to send messages with the message body compressed using a Zlib compression algorithm. The client can uncompress messages that it receives that have the Openwire Compressed field set to true.
> .Net doesn't have support for Zlib compression / decompression built in but there are third-party libraries that can do this.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQCPP-265) The C++ ActiveMQ StreamMessage and the Java ActiveMQ StreamMessage are not compatible.

2009-11-11T11:33:52Z

[ https://issues.apache.org/activemq/browse/AMQCPP-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-265.
---------------------------------

Resolution: Fixed

Resolved in trunk.

The StreamMessage should now be fully compatible with Java and .NET clients.

> The C++ ActiveMQ StreamMessage and the Java ActiveMQ StreamMessage are not compatible.
> --------------------------------------------------------------------------------------
>
> Key: AMQCPP-265
> URL: https://issues.apache.org/activemq/browse/AMQCPP-265
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 3.0.1
> Reporter: Jeremy Judeaux
> Assignee: Timothy Bish
> Fix For: 3.1
>
>
> The C++ ActiveMQ StreamMessage and the Java ActiveMQ StreamMessage are not compatible.
> CMS uses a list to implement the StreamMessage, JMS does not. This list (de)serializes its size before (de)serializing its content.
> Tested with CMS 3.0.1 and JMS 5.2.0.
> May the both implementations work together ?
> PS : is there any specification about how a StreamMessage should be implemented ?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2324) Forwarded message cannot be distributed to the original broker

2009-11-11T11:11:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55317#action_55317 ]

Gary Tully commented on AMQ-2324:
---------------------------------

and even more context: http://www.pubbs.net/activemq/200910/12101/ from another user.

> Forwarded message cannot be distributed to the original broker
> --------------------------------------------------------------
>
> Key: AMQ-2324
> URL: https://issues.apache.org/activemq/browse/AMQ-2324
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: ying
> Assignee: Bruce Snyder
> Fix For: 5.4.0
>
>
> I have a simple cause which can cause dispatch problem:
> 1. setup a network of broker1, broker2, bridged by multicast discovery
> 2. make a producer send 5 msg to queueA to broker2
> 3. make a consumer to consume from broker1 queueA ( make it slow, so it only consumer 1 msg) but make sure all 5 msg from broker2 are forwared to broker1
> 4. stop the consumer to broke1, restart it to consume from broker2 queueA
> 5. the 4 msgs originally published to broker2 and forwarded to broker1 and has not yet been consumed will stuck on broker1 and will not forwarded to broker2 for the consumer to consume.
> Here is an solution: it checks forwarded to broker( eg, broker1) to see whether it has any active consumer, it will be able forward the message back to the original broker when there is no active consumer on the forwarded to broker.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2324) Forwarded message cannot be distributed to the original broker

2009-11-11T11:07:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55316#action_55316 ]

Gary Tully commented on AMQ-2324:
---------------------------------

some of the original context from the user list: http://old.nabble.com/Serious-dispatch-issue-tt23990060.html#a23996544

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2485) Pure Master Slave documentation should describe how to recover from slave failure

2009-11-11T10:57:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55315#action_55315 ]

Jörn Kottmann commented on AMQ-2485:
------------------------------------

Just looking again at the documentation, it says:

"A master broker doesn't need any special configuration - it's a normal broker until a slave broker attaches itself."

But thats not true, right ? Because a master must be configured to wait for a slave to be attached.

> Pure Master Slave documentation should describe how to recover from slave failure
> ---------------------------------------------------------------------------------
>
> Key: AMQ-2485
> URL: https://issues.apache.org/activemq/browse/AMQ-2485
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 5.3.0
> Reporter: Jörn Kottmann
> Priority: Minor
>
> The Pure Master Slave documentation should describe how to recover from a slave failure. The Master is still running, but the slave fails, how can the slave be reattached to the master ?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Improved ActiveMQ Initscript

2009-11-11T09:57:09Z

Hi,

Dejan Bosanac schrieb:
> Hi Marc,
>
> great work, thanks. Can you create Jira enhacement request with these files
> attached and description. It'll make sure it doesn't get lost in the emails.
>
It´s a bug, not a feature :-))

https://issues.apache.org/activemq/browse/AMQ-2453

Best regards
Marc Schöchlin

[jira] Commented: (AMQ-2452) Option to "activemq-admin" do not work properly

2009-11-11T09:55:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55312#action_55312 ]

Marc Schöchlin commented on AMQ-2452:
-------------------------------------

See also new initscript : AMQ-2453

> Option to "activemq-admin" do not work properly
> -----------------------------------------------
>
> Key: AMQ-2452
> URL: https://issues.apache.org/activemq/browse/AMQ-2452
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Marc Schöchlin
>
> All options of the start script "activemq-admin" except "start" do not work.
> (including no-option)
> activemq@host:~/bin> ./activemq-admin
> ./activemq-admin: line 132: [: =: unary operator expected
> Java Runtime: IBM Corporation 1.6.0 /usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre
> activemq@host:~/bin> ./activemq-admin stop
> Java Runtime: IBM Corporation 1.6.0 /usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre
> Heap sizes: current=4096k free=3150k max=524288k
> JVM args: -Xjcl:jclscar_24 -Dcom.ibm.oti.vm.bootstrap.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64 -Dsun.boot.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64 -Djava.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64:/usr/lib -Djava.home=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre -Djava.ext.dirs=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/ext -Duser.dir=/opt/apache-activemq-5.3.0/bin _j2se_j9=1119744 -Xdump -Djava.class.path=. -Dactivemq.classpath=/opt/apache-activemq/conf; -Dactivemq.home=/opt/apache-activemq -Dactivemq.base=/opt/apache-activemq -Djava.class.path=/opt/apache-activemq/bin/run.jar -Dsun.java.command=/opt/apache-activemq/bin/run.jar stop -Dsun.java.launcher=SUN_STANDARD -Dsun.java.launcher.pid=405 _port_library _org.apache.harmony.vmi.portlib
> ACTIVEMQ_HOME: /opt/apache-activemq
> ACTIVEMQ_BASE: /opt/apache-activemq
> Connecting to JMX URL: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> ERROR: java.lang.RuntimeException: Failed to execute stop task. Reason: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> java.lang.RuntimeException: Failed to execute stop task. Reason: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> at org.apache.activemq.console.command.ShutdownCommand.runTask(ShutdownCommand.java:106)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:292)
> at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:129)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:599)
> at org.apache.activemq.console.Main.runTaskClass(Main.java:251)
> at org.apache.activemq.console.Main.main(Main.java:107)
> ERROR: java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> at org.apache.activemq.console.command.ShutdownCommand.runTask(ShutdownCommand.java:107)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:292)
> at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:129)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:599)
> at org.apache.activemq.console.Main.runTaskClass(Main.java:251)
> at org.apache.activemq.console.Main.main(Main.java:107)
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:334)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:259)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:218)
> at org.apache.activemq.console.command.AbstractJmxCommand.createJmxConnector(AbstractJmxCommand.java:214)
> at org.apache.activemq.console.command.AbstractJmxCommand.createJmxConnection(AbstractJmxCommand.java:237)
> at org.apache.activemq.console.command.ShutdownCommand.runTask(ShutdownCommand.java:70)
> ... 11 more
> Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:113)
> at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:197)
> at javax.naming.InitialContext.lookup(InitialContext.java:455)
> at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1882)
> at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1852)
> at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:268)
> ... 16 more
> Caused by: java.rmi.ConnectIOException: non-JRMP server at remote endpoint
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:242)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:196)
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:334)
> at sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java:89)
> at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:109)
> ... 21 more

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2451) logging.properties are not found automatically by start-script

2009-11-11T09:55:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55313#action_55313 ]

Marc Schöchlin commented on AMQ-2451:
-------------------------------------

See also new initscript : AMQ-2453

> logging.properties are not found automatically by start-script
> --------------------------------------------------------------
>
> Key: AMQ-2451
> URL: https://issues.apache.org/activemq/browse/AMQ-2451
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Marc Schöchlin
>
> The "logging.properties" file was found automatically in version 5.4.2 - now i have
> to chdir to "conf" to find the file automatically.
> ----
> activemq@host:~> bin/activemq-admin start
> GNARF
> Java Runtime: IBM Corporation 1.6.0 /usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre
> Heap sizes: current=4096k free=3055k max=524288k
> JVM args: -Xjcl:jclscar_24 -Dcom.ibm.oti.vm.bootstrap.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64 -Dsun.boot.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64 -Djava.library.path=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64/default:/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/amd64:/usr/lib -Djava.home=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre -Djava.ext.dirs=/usr/lib64/jvm/java-1_6_0-ibm-1.6.0/jre/lib/ext -Duser.dir=/opt/apache-activemq-5.3.0 _j2se_j9=1119744 -Xdump -Djava.class.path=. -Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dcom.sun.management.jmxremote -Dactivemq.classpath=/opt/apache-activemq/conf; -Dactivemq.home=/opt/apache-activemq -Dactivemq.base=/opt/apache-activemq -Djava.class.path=/opt/apache-activemq/bin/run.jar -Dsun.java.command=/opt/apache-activemq/bin/run.jar start -Dsun.java.launcher=SUN_STANDARD -Dsun.java.launcher.pid=32694 _port_library _org.apache.harmony.vmi.portlib
> ACTIVEMQ_HOME: /opt/apache-activemq
> ACTIVEMQ_BASE: /opt/apache-activemq
> Loading message broker from: xbean:activemq.xml
> INFO | Using Persistence Adapter: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter@42da42da
> INFO | Replayed 1 operations from the journal in 0.015 seconds.
> INFO | ActiveMQ 5.3.0 JMS Message Broker (localhost) is starting
> INFO | For help or more information please see: http://activemq.apache.org/
> java.io.FileNotFoundException: logging.properties (No such file or directory)
> at java.io.FileInputStream.<init>(FileInputStream.java:112)
> at java.io.FileInputStream.<init>(FileInputStream.java:72)
> at java.util.logging.LogManager.readConfiguration(LogManager.java:464)
> at java.util.logging.LogManager$3.run(LogManager.java:226)
> at java.security.AccessController.doPrivileged(AccessController.java:202)
> at java.util.logging.LogManager.<clinit>(LogManager.java:212)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
> at java.util.logging.Logger.getLoggerWithRes(Logger.java:342)
> at java.util.logging.Logger.getLogger(Logger.java:372)
> at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:49)
> at javax.management.NotificationBroadcasterSupport.<clinit>(NotificationBroadcasterSupport.java:346)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
> at javax.management.MBeanServerDelegate.<init>(MBeanServerDelegate.java:69)
> at com.sun.jmx.mbeanserver.MBeanServerDelegateImpl.<init>(MBeanServerDelegateImpl.java:94)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.newMBeanServerDelegate(JmxMBeanServer.java:1338)
> at javax.management.MBeanServerBuilder.newMBeanServerDelegate(MBeanServerBuilder.java:60)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:313)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:224)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:185)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:599)
> at org.apache.activemq.broker.jmx.ManagementContext.findTigerMBeanServer(ManagementContext.java:349)
> at org.apache.activemq.broker.jmx.ManagementContext.findMBeanServer(ManagementContext.java:319)
> at org.apache.activemq.broker.jmx.ManagementContext.getMBeanServer(ManagementContext.java:169)
> at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:292)
> at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:54)
> at org.apache.activemq.broker.jmx.ManagedRegionBroker.registerDestination(ManagedRegionBroker.java:245)
> at org.apache.activemq.broker.jmx.ManagedRegionBroker.register(ManagedRegionBroker.java:151)
> at org.apache.activemq.broker.jmx.ManagedQueueRegion.createDestination(ManagedQueueRegion.java:57)
> at org.apache.activemq.broker.region.AbstractRegion.addDestination(AbstractRegion.java:120)
> at org.apache.activemq.broker.region.RegionBroker.addDestination(RegionBroker.java:268)
> at org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:142)
> at org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:142)
> at org.apache.activemq.advisory.AdvisoryBroker.addDestination(AdvisoryBroker.java:153)
> at org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:142)
> at org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBrokerFilter.java:149)
> at org.apache.activemq.broker.region.AbstractRegion.start(AbstractRegion.java:94)
> at org.apache.activemq.broker.region.RegionBroker.start(RegionBroker.java:178)
> at org.apache.activemq.broker.jmx.ManagedRegionBroker.start(ManagedRegionBroker.java:100)
> at org.apache.activemq.broker.TransactionBroker.start(TransactionBroker.java:112)
> at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.java:154)
> at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.java:154)
> at org.apache.activemq.broker.BrokerService$3.start(BrokerService.java:1668)
> at org.apache.activemq.broker.BrokerService.start(BrokerService.java:452)
> at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:56)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
> at java.security.AccessController.doPrivileged(AccessController.java:224)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
> at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
> at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)
> at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)
> at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:96)
> at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:52)
> at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)
> at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)
> at org.apache.activemq.console.command.StartCommand.startBroker(StartCommand.java:115)
> at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:74)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:129)
> at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
> at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:599)
> at org.apache.activemq.console.Main.runTaskClass(Main.java:251)
> at org.apache.activemq.console.Main.main(Main.java:107)
>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2453) start/control-script is not suitable for professional environments

2009-11-11T09:53:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marc Schöchlin updated AMQ-2453:
--------------------------------

Attachment: usage-example.txt
activemq

I wrote a new initscript for running standalone activemq installations
(see attached script).

This script is originally based on the scripts "activemq" and
"activemq-admin" located in
"assembly/src/release/bin/" and replaces both scripts.

Read "usage-examples.txt" for getting a first impression of the initscript.

Features of the new script:
- the script should be compatible with cygwin, macosx and most linux and
unix systems
To ensure compatibility to macosx and cygwin it does not utilize lsb
standard infrastructure for controlling daemons like
"start-stop-daemon".
(i tried to keep the shell-syntax compatible to most unix systems,
but only tested on SLES11 and Ubuntu 9.10)
- the complete functionality if "activemq-admin" is now included in
"activemq"
(list, query, browse, ...)
- all option not implemented by the initscript, are directly passed to
the java-call
- the configuration parameters can be located in
/etc/default/activemq.conf or $HOME/.activemqrc
- the script supports operation of multiple instances on the same system
(if the script is symlinked/renamed to
"activemq-instance-<INSTANCENAME>", the configuration
is searched on /etc/default/activemq-instance-<INSTANCENAME>.conf and
$HOME/.activemqrc-instance-<INSTANCENAME>)
- in case of syntax-errors in the configuration, the execution is stopped
- a template configuration for the script can be created by using the
"setup" option
- activemq configuration- and data-dir (e.g. kahadb, tmpstorage) are
configurable
- configuration hints for jmx (because of non-available
"VirtualMachine.attach(PID)", especially needed when using a ibm jvms)
- improved shutdown procedure: script invokes shutdown by a jmx-request,
if process does not disappear
after a configurable timeout, the process is killed by SIGKILL (-9)
- start activemq daemon as an background process : option "start"
- start activemq daemon without daemonizing the daemon: option "fgstart"
- usage of PID files to determine running activemq instances
- the "status" option, checks if there is a running activemq instance
(this is useful for using activemq with high-availability tools)
- the script outputs usage-information if it is invoked without any option
(usage of the java binary combined with the script-usage)

In my opinion it would be good/nice:
- if this script is will be tested on several unix-systems and on cygwin
- to provide the possibility to configure the entire jmx-setup in
activemq.xml or jetty.xml
(if jetty provides this)
- it would be nice if the java code supports daemonizing
- if this script will be part of activemq, we should adapt the wiki pages

Feedback and improvement ideas are very welcome :-)

> start/control-script is not suitable for professional environments
> ------------------------------------------------------------------
>
> Key: AMQ-2453
> URL: https://issues.apache.org/activemq/browse/AMQ-2453
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Marc Schöchlin
> Attachments: activemq, usage-example.txt
>
>
> The start-scripts "activemq" and "activemq-admin" do not seem to be ready for production use.
> Reasons:
> - Server does not run in background
> => this can be done by redirecting output to a file and run in background
> => in my opinion this should be implemented directly in java
> => the console log should be written by log4j to <install-root>/data/console.log
> - The process should be started on a non-root user
> => use 'su -c "$COMMAND" - $RUN_AS_USER'
> => this should be defined in /etc/activemq.conf
> - The script should support a "reload" feature to reload the configurartion
> (if activemq supports reloading)
> - The script should support a "status" option
> => this should show a quick overview about the state of activemq
> => this should return a value != 0 if the service is not working
> (this is important for cluster integration)
> Does anybody already working on these items?
> Do you have suggestions for a implementation?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-253) Problems with compiler aCC on HPUX

2009-11-11T07:43:52Z

[ https://issues.apache.org/activemq/browse/AMQCPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55310#action_55310 ]

Timothy Bish commented on AMQCPP-253:
-------------------------------------

The warnings could be of use but I don't think they are the cause of this error. This looks more like the compiler is having an issue with the member template dynamicCast in the Pointer class which is odd since the library uses this extensively. My first guess is that there is something not getting passed to the compiler for the exe that is getting passed to the compiler when building the lib, have you check the output of the call to aCC for a file in the lib vs a file in the examples build?

I don't know why you couldn't attach the file, the included amq_cpp_30.tar for this issue is 60KB so you are under that. Worse case you can send it to me via email but I'd verify those compiler settings first.

> Problems with compiler aCC on HPUX
> ----------------------------------
>
> Key: AMQCPP-253
> URL: https://issues.apache.org/activemq/browse/AMQCPP-253
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Affects Versions: 3.0
> Environment: HP-UX gemma1 B.11.23 U 9000/800
> aCC: HP ANSI C++ B3910B A.03.77
> Reporter: Wolfgang.Klein
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 3.1
>
> Attachments: amq_cpp_30.tar, TcpSocket.cpp
>
>
> compile errors with native HP compiler

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (AMQ-2486) systemExitOnShutdown="true" causes broker shutdown to hang

2009-11-11T07:41:52Z

systemExitOnShutdown="true" causes broker shutdown to hang
----------------------------------------------------------

Key: AMQ-2486
URL: https://issues.apache.org/activemq/browse/AMQ-2486
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac

To reproduce:

* add systemExitOnShutdown="true" to the <broker> tag
* start a broker
* try to stop the broker

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2485) Pure Master Slave documentation should describe how to recover from slave failure

2009-11-11T07:33:52Z

[ https://issues.apache.org/activemq/browse/AMQ-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55309#action_55309 ]

Jörn Kottmann commented on AMQ-2485:
------------------------------------

Yes thanks

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-253) Problems with compiler aCC on HPUX

2009-11-11T07:31:53Z

[ https://issues.apache.org/activemq/browse/AMQCPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55307#action_55307 ]

Brian McFarland commented on AMQCPP-253:
----------------------------------------

I'm trying to attach a build log, and keep getting this error from the website.

Errors
No files were attached. Please add your attachments again (lost during reload).

As a zip file, it's on 32KB.

Tim, do you think the aCC warnings in the log would be useful to you? If so is there an alternate method I can use to send them?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2485) Pure Master Slave documentation should describe how to recover from slave failure

2009-11-11T07:31:53Z

[ https://issues.apache.org/activemq/browse/AMQ-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55308#action_55308 ]

Gary Tully commented on AMQ-2485:
---------------------------------

The master needs to be restarted and the slave attached again. A slave cannot play catch up with an already started and active master. there is a waitForSlave option on a master that can facilitate the synchronized start of the master.

Would this suffice?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is back to stable: ActiveMQ #183

2009-11-11T06:24:00Z

See <http://hudson.zones.apache.org/hudson/job/ActiveMQ/183/changes>

[jira] Created: (AMQ-2485) Pure Master Slave documentation should describe how to recover from slave failure

2009-11-11T06:21:52Z

Pure Master Slave documentation should describe how to recover from slave failure
---------------------------------------------------------------------------------

Key: AMQ-2485
URL: https://issues.apache.org/activemq/browse/AMQ-2485
Project: ActiveMQ
Issue Type: Improvement
Components: Documentation
Affects Versions: 5.3.0
Reporter: Jörn Kottmann
Priority: Minor

The Pure Master Slave documentation should describe how to recover from a slave failure. The Master is still running, but the slave fails, how can the slave be reattached to the master ?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is back to stable: ActiveMQ » ActiveMQ :: Optional #183

2009-11-11T06:21:46Z

See <http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-optional/183/changes>

[jira] Created: (AMQ-2484) Avoid stuck messages in a network of brokers

2009-11-11T01:33:52Z

Avoid stuck messages in a network of brokers
--------------------------------------------

Key: AMQ-2484
URL: https://issues.apache.org/activemq/browse/AMQ-2484
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Environment: all
Reporter: Andreas Gies
Priority: Minor

In certain fail over scenarios messages can become "stuck" in a network of brokers. This would be the case if the message was forwarded to a broker because a consumer existed, but the consumer disconnects or dies before the message can be delivered. Th then the consumer reconnects to the network of brokers it might be, that it connects to another member of the NWOB alltogether.

If the message has already passed that other broker on its way, the message is stuck.

To solve this I was thinking along the lines of allowing a NWOB-redelivery policy. The default for this could be "NONE" and would represent the current behavior. On top of that it would be nice to configure a timeout, after which the message will be passed on even to nodes that it has already crossed. Perhaps some kind of backoffmultiplier would make sense here as well ?

Another way might be to simply "forget" the path the message came across, but I am not sure about the potential impacts regarding duplicate messages or similar issues.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (AMQ-2483) OOM due to build of of iterate executions during bulk message consumption - asyncWakeup called excessivly

2009-11-11T01:29:52Z

OOM due to build of of iterate executions during bulk message consumption - asyncWakeup called excessivly
---------------------------------------------------------------------------------------------------------

Key: AMQ-2483
URL: https://issues.apache.org/activemq/browse/AMQ-2483
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.0
Reporter: Gary Tully
Assignee: Gary Tully

when consuming a large of messages,the method:asyncWakeup() is invoked
crazily,so the executor has a great deal of runnable that callback Queue.iterate(), but
Queue.iterate() is much slower than the increasing of runnable in the
executor. this result in OOM.

avoid to invoke the method:asyncWakeup() frequently???

http://old.nabble.com/file/p26278228/oom.jpg

Context: http://old.nabble.com/Out-of-Memory-on-5.3-tp26064098p26297020.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Improved ActiveMQ Initscript

2009-11-11T01:13:31Z

Hi Marc,

great work, thanks. Can you create Jira enhacement request with these files
attached and description. It'll make sure it doesn't get lost in the emails.

Thanks
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net

2009/11/10 Marc Schöchlin <marc@...>

> Hello ActiveMQ developers,
>
> i wrote a new initscript for running standalone activemq installations
> (see attached script).
>
> This script is originally based on the scripts "activemq" and
> "activemq-admin" located in
> "assembly/src/release/bin/" and replaces both scripts.
>
> Read "usage-examples.txt" for getting a first impression of the
> initscript.
>
> Features of the new script:
> - the script should be compatible with cygwin, macosx and most linux and
> unix systems
> To ensure compatibility to macosx and cygwin it does not utilize lsb
> standard infrastructure for controlling daemons like
> "start-stop-daemon".
> (i tried to keep the shell-syntax compatible to most unix systems,
> but only tested on SLES11 and Ubuntu 9.10)
> - the complete functionality if "activemq-admin" is now included in
> "activemq"
> (list, query, browse, ...)
> - all option not implemented by the initscript, are directly passed to
> the java-call
> - the configuration parameters can be located in
> /etc/default/activemq.conf or $HOME/.activemqrc
> - the script supports operation of multiple instances on the same system
> (if the script is symlinked/renamed to
> "activemq-instance-<INSTANCENAME>", the configuration
> is searched on /etc/default/activemq-instance-<INSTANCENAME>.conf and
> $HOME/.activemqrc-instance-<INSTANCENAME>)
> - in case of syntax-errors in the configuration, the execution is stopped
> - a template configuration for the script can be created by using the
> "setup" option
> - activemq configuration- and data-dir (e.g. kahadb, tmpstorage) are
> configurable
> - configuration hints for jmx (because of non-available
> "VirtualMachine.attach(PID)", especially needed when using a ibm jvms)
> - improved shutdown procedure: script invokes shutdown by a jmx-request,
> if process does not disappear
> after a configurable timeout, the process is killed by SIGKILL (-9)
> - start activemq daemon as an background process : option "start"
> - start activemq daemon without daemonizing the daemon: option "fgstart"
> - usage of PID files to determine running activemq instances
> - the "status" option, checks if there is a running activemq instance
> (this is useful for using activemq with high-availability tools)
> - the script outputs usage-information if it is invoked without any option
> (usage of the java binary combined with the script-usage)
>
> In my opinion it would be good/nice:
> - if this script is will be tested on several unix-systems and on cygwin
> - to provide the possibility to configure the entire jmx-setup in
> activemq.xml or jetty.xml
> (if jetty provides this)
> - it would be nice if the java code supports daemonizing
> - if this script will be part of activemq, we should adapt the wiki pages
>
> Feedback and improvement ideas are very welcome :-)
>
> Best regards
> Marc Schoechlin
>
>
> #!/bin/sh
> # ------------------------------------------------------------------------
> # Licensed to the Apache Software Foundation (ASF) under one or more
> # contributor license agreements. See the NOTICE file distributed with
> # this work for additional information regarding copyright ownership.
> # The ASF licenses this file to You under the Apache License, Version 2.0
> # (the "License"); you may not use this file except in compliance with
> # the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> # ------------------------------------------------------------------------
> #
> # This script controls standalone Apache ActiveMQ service processes.
> # To ensure compatibility to macosx and cygwin we do not utilize
> # lsb standard infrastructure for controlling daemons like
> # "start-stop-daemon".
> #
> # See also
> http://activemq.apache.org/activemq-command-line-tools-reference.html
> # for additional commandline arguments
> #
> # Authors:
> # Marc Schoechlin <ms@...>
>
> # ------------------------------------------------------------------------
> # CONFIGURATION
> ACTIVEMQ_CONFIGS="/etc/default/activemq.conf $HOME/.activemqrc"
>
> # For using instances
> if ( basename $0 | grep -q "activemq-instance-" );then
> INST="$(basename $0|sed 's/^activemq-instance-//;s/\.sh$//')"
> ACTIVEMQ_CONFIGS="/etc/default/activemq-instance-${INST}.conf
> $HOME/.activemqrc-instance-${INST}"
> echo "INFO: using alternative activemq configuration files:
> $ACCTIVEMQ_CONFIGS"
> fi
>
> ## START:DEFAULTCONFIG
> # ------------------------------------------------------------------------
> # Configuration file for running Apache Active MQ as standalone provider
> #
> # This file overwrites the predefined settings of the sysv init-script
> #
> # Active MQ installation dir
> ACTIVEMQ_HOME="/opt/activemq"
>
> # Active MQ configuration directory
> ACTIVEMQ_CONFIG_DIR="$ACTIVEMQ_HOME/conf"
>
> # Active MQ configuration directory
> ACTIVEMQ_DATA_DIR="$ACTIVEMQ_HOME/data"
>
> # Location of the pidfile
> ACTIVEMQ_PIDFILE="$ACTIVEMQ_DATA_DIR/activemq.pid"
>
> # Location of the java installation
> # Specify the location of your java installation using JAVA_HOME, or
> specify the
> # path to the "java" binary using JAVACMD
> # (set JAVACMD to "auto" for automatic detection)
> #JAVA_HOME=""
> JAVACMD="auto"
>
> # Configure a user with non root priviledges, if no user is specified do
> not change user
> ACTIVEMQ_USER=""
>
> # Set jvm memory configuration
> ACTIVEMQ_OPTS_MEMORY="-Xms256M -Xmx256M"
>
> # Set jvm jmx configuration
> # This enables jmx access over a configured jmx-tcp-port.
> # You have to configure the first four settings if you run a ibm jvm,
> caused by the
> # fact that IBM's jvm does not support VirtualMachine.attach(PID).
> # JMX access is needed for quering a running activemq instance to gain data
> or to
> # trigger management operations.
> #
> # Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.access:
> # ---
> # # The "monitorRole" role has readonly access.
> # # The "controlRole" role has readwrite access.
> # monitorRole readonly
> # controlRole readwrite
> # ---
> #
> # Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.password:
> # ---
> # # The "monitorRole" role has password "abc123".
> # # # The "controlRole" role has password "abcd1234".
> # monitorRole abc123
> # controlRole abcd1234
> # ---
> #
> # ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=11099 "
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.ssl=false"
> ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote"
>
> # Set jvm jmx configuration for controlling the broker process
> # You only have to configure the first four settings if you run a ibm jvm,
> caused by the
> # fact that IBM's jvm does not support VirtualMachine.attach(PID)
> # (see also com.sun.management.jmxremote.port, .jmx.password.file and
> .jmx.access.file )
> #ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://
> 127.0.0.1:11099/jmxrmi --jmxuser controlRole --jmxpassword abcd1234"
> ACTIVEMQ_SUNJMX_CONTROL=""
>
> # Specify the queue manager URL for using "browse" option of sysv
> initscript
> ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"
>
> # Set additional JSE arguments
> ACTIVEMQ_SSL_OPTS=""
>
> # Uncomment to enable YourKit profiling
> #ACTIVEMQ_DEBUG_OPTS="-agentlib:yjpagent"
>
> # Uncomment to enable remote debugging
> #ACTIVEMQ_DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
>
> # ActiveMQ tries to shutdown the broker by jmx,
> # after a specified number of seconds send SIGKILL
> ACTIVEMQ_KILL_MAXSECONDS="300"
>
> ## END:DEFAULTCONFIG
>
> # ------------------------------------------------------------------------
> # LOAD CONFIGURATION
>
> # load activemq configuration
> CONFIG_LOAD="no"
> for ACTIVEMQ_CONFIG in $ACTIVEMQ_CONFIGS;
> do
> if [ -f "$ACTIVEMQ_CONFIG" ] ; then
> ( . $ACTIVEMQ_CONFIG >/dev/null 2>&1 )
> if [ "$?" != "0" ];then
> echo "ERROR: there are syntax errors in '$ACTIVEMQ_CONFIG'"
> exit 1
> else
> echo "INFO: loading '$ACTIVEMQ_CONFIG'"
> . $ACTIVEMQ_CONFIG
> CONFIG_LOAD="yes"
> fi
> fi
> done
>
> # inform user thagt no configuration was loaded
> if [ "$CONFIG_LOAD" != "yes" ];then
> if [ "$1" != "setup" ];then
> echo "INFO: using default configuration";
> echo "(you can configure options in one of these file:
> $ACTIVEMQ_CONFIGS)"
> echo
> echo "INFO: invoke the following command to create a configuration
> file"
> echo "$0 setup [ $(echo $ACTIVEMQ_CONFIGS|sed 's/[ ][ ]*/ | /') ]"
> echo
> fi
> fi
>
> # create configuration if requested
> if [ "$1" = "setup" ];then
> if [ -z "$2" ];then
> echo "ERROR: specify configuration file"
> exit 1
> fi
> echo "INFO: creating configuration file: $2"
> (
> P_STATE="0"
> while read LINE ;do
> if (echo "$LINE" | grep "START:DEFAULTCONFIG" >/dev/null );then
> P_STATE="1"
> continue;
> fi
> if (echo "$LINE" | grep "END:DEFAULTCONFIG" >/dev/null);then
> P_STATE="0"
> break;
> fi
> if [ "$P_STATE" -eq "1" ];then
> echo $LINE
> fi
> done < $0
> ) > $2
> echo "INFO: it's recommend to limit access to '$2' to the priviledged
> user"
> echo "INFO: (recommended: chown `whoami`:nogroup '$2'; chmod 600 '$2')"
> exit $?
> fi
>
> # ------------------------------------------------------------------------
> # OS SPECIFIC SUPPORT
>
> OSTYPE="unknown"
>
> case "`uname`" in
> CYGWIN*) OSTYPE="cygwin" ;;
> Darwin*)
> OSTYPE="darwin"
> if [ "$JAVACMD" = "auto" ];then
> JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home
> fi
> ;;
> esac
>
> # For Cygwin, ensure paths are in UNIX format before anything is touched
> if [ "$OSTYPE" = "cygwin" ]; then
> [ -n "$ACTIVEMQ_HOME" ] &&
> ACTIVEMQ_HOME="`cygpath --unix "$ACTIVEMQ_HOME"`"
> [ -n "$JAVA_HOME" ] &&
> JAVA_HOME="`cygpath --unix "$JAVA_HOME"`"
> [ -n "$CLASSPATH" ] &&
> CLASSPATH="`cygpath --path --unix "$CLASSPATH"`"
> fi
>
> # Detect the location of the java binary
> if [ -z "$JAVACMD" ] ; then
> if [ -n "$JAVA_HOME" ] ; then
> if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
> # IBM's JDK on AIX uses strange locations for the executables
> JAVACMD="$JAVA_HOME/jre/sh/java"
> else
> JAVACMD="$JAVA_HOME/bin/java"
> fi
> fi
> fi
>
> # Hm, we still do not know the location of the java binary
> if [ ! -x "$JAVACMD" ] ; then
> JAVACMD=`which java 2> /dev/null `
> if [ -z "$JAVACMD" ] ; then
> JAVACMD=java
> fi
> fi
> # Stopt here if no java installation is defined/found
> if [ ! -x "$JAVACMD" ] ; then
> echo "ERROR: configuration varaiable JAVA_HOME or JAVACMD is not defined
> correctly."
> echo " (JAVA_HOME='$JAVAHOME', JAVACMD='$JAVACMD')"
> exit 1
> fi
>
> echo "INFO: useing java '$JAVACMD'"
>
> if [ -z "$ACTIVEMQ_BASE" ] ; then
> ACTIVEMQ_BASE="$ACTIVEMQ_HOME"
> fi
>
> # For Cygwin, switch paths to Windows format before running java if [
> "$OSTYPE" = "cygwin" ]; then
> if [ "$OSTYPE" = "cygwin" ];then
> ACTIVEMQ_HOME=`cygpath --windows "$ACTIVEMQ_HOME"`
> ACTIVEMQ_BASE=`cygpath --windows "$ACTIVEMQ_BASE"`
> ACTIVEMQ_CLASSPATH=`cygpath --path --windows "$ACTIVEMQ_CLASSPATH"`
> JAVA_HOME=`cygpath --windows "$JAVA_HOME"`
> CLASSPATH=`cygpath --path --windows "$CLASSPATH"`
> CYGHOME=`cygpath --windows "$HOME"`
> if [ -n "$CYGHOME" ]; then
> ACTIVEMQ_CYGWIN="-Dcygwin.user.home=\"$CYGHOME\""
> fi
> fi
>
> # Set default classpath
> ACTIVEMQ_CLASSPATH="${ACTIVEMQ_CONFIG_DIR}/;${ACTIVEMQ_CLASSPATH}"
>
> # Backup invocation parameters
> COMMANDLINE_ARGS="$@"
>
> # ------------------------------------------------------------------------
> # HELPER FUNCTIONS
>
> # Start the ActiveMQ JAR
> #
> # This function uses a lot of globally defined variables
> invokeJar(){
> local PIDFILE="$1"
> local RET="1"
> local CUSER="$(whoami)"
>
> if ( ! [ -f "${ACTIVEMQ_HOME}/bin/run.jar" ] );then
> echo "ERROR: '${ACTIVEMQ_HOME}/bin/run.jar' does not exist"
> exit 1
> fi
>
> if ( [ -z "$ACTIVEMQ_USER" ] || [ "$ACTIVEMQ_USER" = "$CUSER" ] );then
> DOIT_PREFIX="sh -c "
> DOIT_POSTFIX=";"
> elif [ "$(id -u)" = "0" ];then
> DOIT_PREFIX="su -c "
> DOIT_POSTFIX=" - $ACTIVEMQ_USER"
> echo "INFO: changing to user '$ACTIVEMQ_USER' to invoke java"
> fi
> # Execute java binary
> if [ -n "$PIDFILE" ];then
> $DOIT_PREFIX "cd $ACTIVEMQ_CONFIG_DIR; $JAVACMD $ACTIVEMQ_OPTS
> $ACTIVEMQ_DEBUG_OPTS \
> -Dactivemq.classpath=\"${ACTIVEMQ_CLASSPATH}\" \
> -Dactivemq.home=\"${ACTIVEMQ_HOME}\" \
> -Dactivemq.base=\"${ACTIVEMQ_BASE}\" \
> $ACTIVEMQ_CYGWIN \
> -jar \"${ACTIVEMQ_HOME}/bin/run.jar\" $COMMANDLINE_ARGS
> >/dev/null 2>&1 &
> RET=\"\$?\"; APID=\"\$!\";
> echo \$APID > $PIDFILE;
> echo \"INFO: pidfile created : '$PIDFILE' (pid
> '\$APID')\";exit \$RET" $DOIT_POSTFIX
> RET="$?"
> else
> $DOIT_PREFIX "cd $ACTIVEMQ_CONFIG_DIR; $JAVACMD $ACTIVEMQ_OPTS
> $ACTIVEMQ_DEBUG_OPTS \
> -Dactivemq.classpath=\"${ACTIVEMQ_CLASSPATH}\" \
> -Dactivemq.home=\"${ACTIVEMQ_HOME}\" \
> -Dactivemq.base=\"${ACTIVEMQ_BASE}\" \
> $ACTIVEMQ_CYGWIN \
> -jar \"${ACTIVEMQ_HOME}/bin/run.jar\" $COMMANDLINE_ARGS"
> $DOIT_POSTFIX
> RET="$?"
> fi
> return $RET
> }
>
> checkRunning(){
> if [ -f "$ACTIVEMQ_PIDFILE" ]; then
> if [ -z "$(cat $ACTIVEMQ_PIDFILE)" ];then
> echo "ERROR: pidfile '$ACTIVEMQ_PIDFILE' exists but contains no pid"
> return 2
> fi
> if (ps -p $(cat $ACTIVEMQ_PIDFILE)|grep java >/dev/null);then
> return 0;
> else
> return 1;
> fi
> else
> return 1;
> fi
> }
>
> invoke_status(){
> if ( checkRunning );then
> echo "Activemq is running (pid '$(cat $ACTIVEMQ_PIDFILE)')"
> exit 0
> fi
> echo "Activemq not running"
> exit 1
> }
>
> invoke_start(){
> if ( checkRunning );then
> echo "INFO: process with pid '$(cat $ACTIVEMQ_PIDFILE)' is already
> running"
> exit 0
> fi
>
> if [ -z "$ACTIVEMQ_OPTS" ] ; then
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY
> -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> -Djava.util.logging.config.file=logging.properties"
> fi
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SUNJMX_START $ACTIVEMQ_SSL_OPTS"
> echo "INFO: starting - inspect logfiles specified in logging.properties
> and log4j.properties to get details"
> invokeJar $ACTIVEMQ_PIDFILE
> exit "$?"
> }
>
> invoke_fgstart(){
> if ( checkRunning );then
> echo "ERROR: activemq is already running"
> exit 1
> fi
> if [ -z "$ACTIVEMQ_OPTS" ] ; then
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY
> -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> -Djava.util.logging.config.file=logging.properties"
> fi
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SUNJMX_START $ACTIVEMQ_SSL_OPTS"
>
> COMMANDLINE_ARGS="start $(echo $COMMANDLINE_ARGS|sed 's,^fgstart,,')"
> echo "INFO: starting in foreeground, this is just for debugging purposes
> (stop process by pressing CTRL+c)"
> invokeJar
> exit "$?"
> }
>
>
> invoke_stop(){
> RET="1"
> if ( checkRunning );then
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
> COMMANDLINE_ARGS="$COMMANDLINE_ARGS $ACTIVEMQ_SUNJMX_CONTROL"
> invokeJar
> RET="$?"
> echo -n "INFO: waiting at least $ACTIVEMQ_KILL_MAXSECONDS seconds for
> regular process termination of pid '$(cat $ACTIVEMQ_PIDFILE)' : "
> FOUND="0"
> for i in `seq 0 $ACTIVEMQ_KILL_MAXSECONDS` ;do
> if (checkRunning);then
> sleep 1
> echo -n "."
> else
> echo " FINISHED"
> FOUND="1"
> break
> fi
> done
> if [ "$FOUND" -ne "1" ];then
> echo "INFO: regular shutdown not successful, sending SIGKILL to
> process with pid '$(cat $ACTIVEMQ_PIDFILE)'"
> kill -KILL $(cat $ACTIVEMQ_PIDFILE)
> RET="1"
> fi
> elif [ -f "$ACTIVEMQ_PIDFILE" ];then
> echo "ERROR: no or outdated process id in '$ACTIVEMQ_PIDFILE'"
> echo
> echo "INFO: removing $ACTIVEMQ_PIDFILE"
> else
> exit 0
> fi
> rm -f $ACTIVEMQ_PIDFILE >/dev/null 2>&1
> exit $RET
> }
>
> invoke_task(){
> # call task in java binary
> if ( checkRunning );then
> if [ "$1" = "browse" ] && [ -n "$ACTIVEMQ_QUEUEMANAGERURL" ];then
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
> COMMANDLINE_ARGS="$1 $ACTIVEMQ_QUEUEMANAGERURL $(echo
> $COMMANDLINE_ARGS|sed 's,^browse,,')"
> elif [ "$1" = "query" ] && [ -n "$ACTIVEMQ_QUEUEMANAGERURL" ];then
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
> COMMANDLINE_ARGS="$1 $ACTIVEMQ_SUNJMX_CONTROL $(echo
> $COMMANDLINE_ARGS|sed 's,^query,,')"
> else
> ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
> COMMANDLINE_ARGS="$COMMANDLINE_ARGS $ACTIVEMQ_SUNJMX_CONTROL"
> fi
> invokeJar
> exit $?
> else
> echo "INFO: activemq not running"
> exit 1
> fi
> }
>
> # ------------------------------------------------------------------------
> # MAIN
>
> # show help
> if [ -z "$1" ];then
> invokeJar
> RET="$?"
> cat << EOF
> Tasks provided by the sysv init script:
> restart - stop running instance (is there is one), start new
> instance
> fgstart - start daemon in foreground, usful for debugging
> purposes
> status - check if activemq process is running
> setup - create the specified configuration file for this init
> script
> (see next usage section)
>
> Configuration of this script:
> The configuration of this script can be placed on
> /etc/default/activemq.conf or $HOME/.activemqrc.
> To use addtional configurations for running multiple instances on the
> same operating system
> rename or symlink script to a name matching to
> activemq-instance-<INSTANCENAME>.
> This changes the configuration location to
> /etc/default/activemq-instance-<INSTANCENAME>.conf and
> \$HOME/.activemqrc-instance-<INSTANCENAME>. Configuration files in /etc
> have higher precedence.
> EOF
> exit $RET
> fi
>
> case "$1" in
> status)
> invoke_status
> ;;
> restart)
> if ( checkRunning );then
> $0 stop
> fi
> $0 status
> $0 start
> $0 status
> ;;
> start)
> invoke_start
> ;;
> fgstart)
> invoke_fgstart
> ;;
> stop)
> invoke_stop
> ;;
> *)
> invoke_task
> esac
>
> # vim:ai et ts=2 shiftwidth=2 expandtab tabstop=3:
>
> $ ./activemq start
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> INFO: starting - inspect logfiles specified in logging.properties and
> log4j.properties to get details
> INFO: pidfile created :
> '/home/mschoechlin/temp/apache-activemq-data/activemq.pid' (pid '11283')
>
> $ ./activemq restart
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Java Runtime: Sun Microsystems Inc. 1.6.0_16
> /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Heap sizes: current=59776k free=59151k max=886592k
> JVM args:
> -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> Stopping broker: localhost
> INFO: waiting at least 300 seconds for regular process termination of pid
> '11283' : FINISHED
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Activemq not running
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> INFO: starting - inspect logfiles specified in logging.properties and
> log4j.properties to get details
> INFO: pidfile created :
> '/home/mschoechlin/temp/apache-activemq-data/activemq.pid' (pid '11407')
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Activemq is running (pid '11407')
>
> $ ./activemq list
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Java Runtime: Sun Microsystems Inc. 1.6.0_16
> /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Heap sizes: current=59776k free=59151k max=886592k
> JVM args:
> -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> BrokerName = localhost
>
> $ ./activemq query
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Java Runtime: Sun Microsystems Inc. 1.6.0_16
> /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Heap sizes: current=59776k free=59151k max=886592k
> JVM args:
> -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> DequeueCount = 0
> Name = ddddddddd
> MinEnqueueTime = 0
> CursorMemoryUsage = 0
> MaxAuditDepth = 2048
> Destination = ddddddddd
> AverageEnqueueTime = 0.0
> InFlightCount = 0
> MemoryLimit = 1048576
> Type = Queue
> EnqueueCount = 0
> MaxEnqueueTime = 0
> MemoryUsagePortion = 0.0
> ProducerCount = 0
> UseCache = true
> MaxProducersToAudit = 32
> CursorFull = false
> BrokerName = localhost
> ConsumerCount = 0
> ProducerFlowControl = true
> Subscriptions = []
> QueueSize = 0
> MaxPageSize = 200
> CursorPercentUsage = 0
> MemoryPercentUsage = 0
> DispatchCount = 0
> ExpiredCount = 0
> ...
> ...
>
> $ ./activemq fgstart
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> ERROR: activemq is already running
>
> $ ./activemq stop
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> Java Runtime: Sun Microsystems Inc. 1.6.0_16
> /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Heap sizes: current=59776k free=59151k max=886592k
> JVM args:
> -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> Stopping broker: localhost
> INFO: waiting at least 300 seconds for regular process termination of pid
> '11407' : FINISHED
>
> $ ./activemq fgstart
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: useing java '/usr/bin/java'
> INFO: starting in foreeground, this is just for debugging purposes (stop
> process by pressing CTRL+c)
> Java Runtime: Sun Microsystems Inc. 1.6.0_16
> /usr/lib/jvm/java-6-sun-1.6.0.16/jre
> Heap sizes: current=251264k free=247327k max=251264k
> JVM args: -Xms256M -Xmx256M
> -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> -Djava.util.logging.config.file=logging.properties
> -Dcom.sun.management.jmxremote.port=11099
> -Dcom.sun.management.jmxremote.password.file=/home/mschoechlin/temp/apache-activemq-data/conf/jmx.password
> -Dcom.sun.management.jmxremote.access.file=/home/mschoechlin/temp/apache-activemq-data/conf/jmx.access
> -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote
> -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> Loading message broker from: xbean:activemq.xml
> INFO | Using Persistence Adapter:
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter@1cb1a4e2
> INFO | Replayed 1 operations from the journal in 0.019 seconds.
> INFO | ActiveMQ 5.3.0 JMS Message Broker (localhost) is starting
> INFO | For help or more information please see:
> http://activemq.apache.org/
> INFO | Listening for connections at: tcp://lt-msch:61616
> INFO | Connector openwire Started
> INFO | ActiveMQ JMS Message Broker (localhost,
> ID:lt-msch-37931-1257840732525-0:0) started
> INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via
> org.mortbay.log.Slf4jLog
> INFO | jetty-6.1.9
> INFO | ActiveMQ WebConsole initialized.
> INFO | Initializing Spring FrameworkServlet 'dispatcher'
> INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
> INFO | Initializing Spring root WebApplicationContext
> INFO | Connector vm://localhost Started
> INFO | Camel Console at http://0.0.0.0:8161/camel
> INFO | ActiveMQ Web Demos at http://0.0.0.0:8161/demo
> INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
> INFO | Started SelectChannelConnector@...:8161
> ^C INFO | ActiveMQ Message Broker (localhost,
> ID:lt-msch-37931-1257840732525-0:0) is shutting down
> INFO | Connector openwire Stopped
> INFO | Connector vm://localhost Stopped
> INFO | ActiveMQ JMS Message Broker (localhost,
> ID:lt-msch-37931-1257840732525-0:0) stopped
>
> $ ./activemq setup /tmp/test.config
> INFO: loading '/home/mschoechlin/.activemqrc'
> INFO: creating configuration file: /tmp/test.config
> INFO: it's recommend to limit access to '/tmp/test.config' to the
> priviledged user
> INFO: (recommended: chown mschoechlin:nogroup '/tmp/test.config'; chmod 600
> '/tmp/test.config')
>
> $ cat /tmp/test.config
> # ------------------------------------------------------------------------
> # Configuration file for running Apache Active MQ as standalone provider
> #
> # This file overwrites the predefined settings of the sysv init-script
> #
> # Active MQ installation dir
> ACTIVEMQ_HOME="/opt/activemq"
>
> # Active MQ configuration directory
> ACTIVEMQ_CONFIG_DIR="$ACTIVEMQ_HOME/conf"
>
> # Active MQ configuration directory
> ACTIVEMQ_DATA_DIR="$ACTIVEMQ_HOME/data"
>
> # Location of the pidfile
> ACTIVEMQ_PIDFILE="$ACTIVEMQ_DATA_DIR/activemq.pid"
>
> # Location of the java installation
> # Specify the location of your java installation using JAVA_HOME, or
> specify the
> # path to the "java" binary using JAVACMD
> # (set JAVACMD to "auto" for automatic detection)
> #JAVA_HOME=""
> JAVACMD="auto"
>
> # Configure a user with non root priviledges, if no user is specified do
> not change user
> ACTIVEMQ_USER=""
>
> # Set jvm memory configuration
> ACTIVEMQ_OPTS_MEMORY="-Xms256M -Xmx256M"
>
> # Set jvm jmx configuration
> # This enables jmx access over a configured jmx-tcp-port.
> # You have to configure the first four settings if you run a ibm jvm,
> caused by the
> # fact that IBM's jvm does not support VirtualMachine.attach(PID).
> # JMX access is needed for quering a running activemq instance to gain data
> or to
> # trigger management operations.
> #
> # Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.access:
> # ---
> # # The "monitorRole" role has readonly access.
> # # The "controlRole" role has readwrite access.
> # monitorRole readonly
> # controlRole readwrite
> # ---
> #
> # Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.password:
> # ---
> # # The "monitorRole" role has password "abc123".
> # # # The "controlRole" role has password "abcd1234".
> # monitorRole abc123
> # controlRole abcd1234
> # ---
> #
> # ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=11099 "
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
> # ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote.ssl=false"
> ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START
> -Dcom.sun.management.jmxremote"
>
> # Set jvm jmx configuration for controlling the broker process
> # You only have to configure the first four settings if you run a ibm jvm,
> caused by the
> # fact that IBM's jvm does not support VirtualMachine.attach(PID)
> # (see also com.sun.management.jmxremote.port, .jmx.password.file and
> .jmx.access.file )
> #ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://
> 127.0.0.1:11099/jmxrmi --jmxuser controlRole --jmxpassword abcd1234"
> ACTIVEMQ_SUNJMX_CONTROL=""
>
> # Specify the queue manager URL for using "browse" option of sysv
> initscript
> ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"
>
> # Set additional JSE arguments
> ACTIVEMQ_SSL_OPTS=""
>
> # Uncomment to enable YourKit profiling
> #ACTIVEMQ_DEBUG_OPTS="-agentlib:yjpagent"
>
> # Uncomment to enable remote debugging
> #ACTIVEMQ_DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
>
> # ActiveMQ tries to shutdown the broker by jmx,
> # after a specified number of seconds send SIGKILL
> ACTIVEMQ_KILL_MAXSECONDS="300"
>
>
>

Dejan Bosanac

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net

Hudson build is unstable: ActiveMQ #182

2009-11-10T18:18:10Z

See <http://hudson.zones.apache.org/hudson/job/ActiveMQ/182/changes>

Hudson build is unstable: ActiveMQ » ActiveMQ :: Optional #182

2009-11-10T18:17:54Z

See <http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-optional/182/>

[jira] Commented: (AMQCPP-253) Problems with compiler aCC on HPUX

2009-11-10T15:57:52Z

[ https://issues.apache.org/activemq/browse/AMQCPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55284#action_55284 ]

Brian McFarland commented on AMQCPP-253:
----------------------------------------

Before seeing this post, I decided to try the replacing the whole thing with a literal zero which did the trick:

socketHandle( 0 )

NULL might be more appropriate, but 0 should have the same end result.

Once that made all the compiler errors go away, I started getting duplicate symbol errors from the linker for INVALID_SOCKET_HANDLE.

The following generates an error:

------------------------------------------------------------------
Socket.h
------------------------------------------------------------------
class Socket{
...
static apr_socket_t* INVALID_SOCKET_HANDLE = 0;
...
}
------------------------------------------------------------------

One solution is to drop the "= 0;" and initialize the value outside of the class declaration.

However, the fix posted by Wolfgang also causes an error. In other words, when adding the following line to the header file, you get duplicate instances of INVALID_SOCKET_HANDLE.

apr_socket_t* Socket::INVALID_SOCKET_HANDLE = 0;

To avoid the duplicate symbol problem, that line needs to go in a cpp file. However, Socket is a purely abstract class (i.e. only pure virtual functions), so no cpp file existed. I created a Socket.cpp with the following content:

------------------------------------------------------------------
Socket.cpp
------------------------------------------------------------------
#include "Socket.h"
#include <apr_network_io.h>

namespace decaf{
namespace net{
apr_socket_t* Socket::INVALID_SOCKET_HANDLE = 0;
}}
------------------------------------------------------------------

Everything now builds & links in the main library. On to the example and test directories..... This is the latest round of errors:

Error 19: "advisories/TempDestinationAdvisoryConsumer.cpp", line 77 # Unexpected '>'.
amqMessage->getDataStructure().dynamicCast<DestinationInfo>();
^
Error 902: "advisories/TempDestinationAdvisoryConsumer.cpp", line 77 # Template deduction failed to find a
match for the call to 'operator <' with signature 'void (void (),activemq::commands::DestinationInfo)'.
amqMessage->getDataStructure().dynamicCast<DestinationInfo>();
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error 226: "advisories/TempDestinationAdvisoryConsumer.cpp", line 76 # No appropriate function found for
call of 'Pointer::Pointer'. Last viable candidate was
"decaf::lang::Pointer<activemq::commands::DestinationInfo,decaf::lang::AtomicRefCounter>::Pointer(const
decaf::lang::Pointer<activemq::commands::DestinationInfo,decaf::lang::AtomicRefCounter> &)"
["./../main/decaf/lang/Pointer.h", line 129]. Argument of type 'int' could not be converted to 'const
decaf::lang::Pointer<activemq::commands::DestinationInfo,decaf::lang::AtomicRefCounter> &'.
Pointer<DestinationInfo> info =

It would be nice to be able to run "make check" to get a sanity check, but since libactivemq-cpp.so is built w/o running the unit tests, it might not be 100% necessary.

It's probably also worth notiing that I see several warnings during the compilation. I'm rebuilding from scratch right now with all the output sent to a log file.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-253) Problems with compiler aCC on HPUX

2009-11-10T13:35:52Z

[ https://issues.apache.org/activemq/browse/AMQCPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55282#action_55282 ]

Timothy Bish commented on AMQCPP-253:
-------------------------------------

The cleanest solution is to remove the INVALID_SOCKET_HANDLE entirely which is what I committed to trunk today. It was used back when we didn't use APR for the socket code. Its not needed any longer and a NULL suffices to set the socket pointer to a default state.

A quick fix might be to just remove the static_cast and just go with a blind cast:

{noformat}

socketHandle( (apr_socket_t*)INVALID_SOCKET_HANDLE )

{noformat}

This is what is done in the ServerSocket class, so if that's compiling for you then you should be golden.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Improved ActiveMQ Initscript

2009-11-10T13:15:32Z

Hello ActiveMQ developers,

i wrote a new initscript for running standalone activemq installations
(see attached script).

This script is originally based on the scripts "activemq" and
"activemq-admin" located in
"assembly/src/release/bin/" and replaces both scripts.

Read "usage-examples.txt" for getting a first impression of the initscript.

Features of the new script:
- the script should be compatible with cygwin, macosx and most linux and
unix systems
To ensure compatibility to macosx and cygwin it does not utilize lsb
standard infrastructure for controlling daemons like
"start-stop-daemon".
(i tried to keep the shell-syntax compatible to most unix systems,
but only tested on SLES11 and Ubuntu 9.10)
- the complete functionality if "activemq-admin" is now included in
"activemq"
(list, query, browse, ...)
- all option not implemented by the initscript, are directly passed to
the java-call
- the configuration parameters can be located in
/etc/default/activemq.conf or $HOME/.activemqrc
- the script supports operation of multiple instances on the same system
(if the script is symlinked/renamed to
"activemq-instance-<INSTANCENAME>", the configuration
is searched on /etc/default/activemq-instance-<INSTANCENAME>.conf and
$HOME/.activemqrc-instance-<INSTANCENAME>)
- in case of syntax-errors in the configuration, the execution is stopped
- a template configuration for the script can be created by using the
"setup" option
- activemq configuration- and data-dir (e.g. kahadb, tmpstorage) are
configurable
- configuration hints for jmx (because of non-available
"VirtualMachine.attach(PID)", especially needed when using a ibm jvms)
- improved shutdown procedure: script invokes shutdown by a jmx-request,
if process does not disappear
after a configurable timeout, the process is killed by SIGKILL (-9)
- start activemq daemon as an background process : option "start"
- start activemq daemon without daemonizing the daemon: option "fgstart"
- usage of PID files to determine running activemq instances
- the "status" option, checks if there is a running activemq instance
(this is useful for using activemq with high-availability tools)
- the script outputs usage-information if it is invoked without any option
(usage of the java binary combined with the script-usage)

In my opinion it would be good/nice:
- if this script is will be tested on several unix-systems and on cygwin
- to provide the possibility to configure the entire jmx-setup in
activemq.xml or jetty.xml
(if jetty provides this)
- it would be nice if the java code supports daemonizing
- if this script will be part of activemq, we should adapt the wiki pages

Feedback and improvement ideas are very welcome :-)

Best regards
Marc Schoechlin

#!/bin/sh
# ------------------------------------------------------------------------
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ------------------------------------------------------------------------
#
# This script controls standalone Apache ActiveMQ service processes.
# To ensure compatibility to macosx and cygwin we do not utilize
# lsb standard infrastructure for controlling daemons like
# "start-stop-daemon".
#
# See also http://activemq.apache.org/activemq-command-line-tools-reference.html
# for additional commandline arguments
#
# Authors:
# Marc Schoechlin <ms@...>

# ------------------------------------------------------------------------
# CONFIGURATION
ACTIVEMQ_CONFIGS="/etc/default/activemq.conf $HOME/.activemqrc"

# For using instances
if ( basename $0 | grep -q "activemq-instance-" );then
INST="$(basename $0|sed 's/^activemq-instance-//;s/\.sh$//')"
ACTIVEMQ_CONFIGS="/etc/default/activemq-instance-${INST}.conf $HOME/.activemqrc-instance-${INST}"
echo "INFO: using alternative activemq configuration files: $ACCTIVEMQ_CONFIGS"
fi

## START:DEFAULTCONFIG
# ------------------------------------------------------------------------
# Configuration file for running Apache Active MQ as standalone provider
#
# This file overwrites the predefined settings of the sysv init-script
#
# Active MQ installation dir
ACTIVEMQ_HOME="/opt/activemq"

# Active MQ configuration directory
ACTIVEMQ_CONFIG_DIR="$ACTIVEMQ_HOME/conf"

# Active MQ configuration directory
ACTIVEMQ_DATA_DIR="$ACTIVEMQ_HOME/data"

# Location of the pidfile
ACTIVEMQ_PIDFILE="$ACTIVEMQ_DATA_DIR/activemq.pid"

# Location of the java installation
# Specify the location of your java installation using JAVA_HOME, or specify the
# path to the "java" binary using JAVACMD
# (set JAVACMD to "auto" for automatic detection)
#JAVA_HOME=""
JAVACMD="auto"

# Configure a user with non root priviledges, if no user is specified do not change user
ACTIVEMQ_USER=""

# Set jvm memory configuration
ACTIVEMQ_OPTS_MEMORY="-Xms256M -Xmx256M"

# Set jvm jmx configuration
# This enables jmx access over a configured jmx-tcp-port.
# You have to configure the first four settings if you run a ibm jvm, caused by the
# fact that IBM's jvm does not support VirtualMachine.attach(PID).
# JMX access is needed for quering a running activemq instance to gain data or to
# trigger management operations.
#
# Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.access:
# ---
# # The "monitorRole" role has readonly access.
# # The "controlRole" role has readwrite access.
# monitorRole readonly
# controlRole readwrite
# ---
#
# Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.password:
# ---
# # The "monitorRole" role has password "abc123".
# # # The "controlRole" role has password "abcd1234".
# monitorRole abc123
# controlRole abcd1234
# ---
#
# ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=11099 "
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.ssl=false"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote"

# Set jvm jmx configuration for controlling the broker process
# You only have to configure the first four settings if you run a ibm jvm, caused by the
# fact that IBM's jvm does not support VirtualMachine.attach(PID)
# (see also com.sun.management.jmxremote.port, .jmx.password.file and .jmx.access.file )
#ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11099/jmxrmi --jmxuser controlRole --jmxpassword abcd1234"
ACTIVEMQ_SUNJMX_CONTROL=""

# Specify the queue manager URL for using "browse" option of sysv initscript
ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"

# Set additional JSE arguments
ACTIVEMQ_SSL_OPTS=""

# Uncomment to enable YourKit profiling
#ACTIVEMQ_DEBUG_OPTS="-agentlib:yjpagent"

# Uncomment to enable remote debugging
#ACTIVEMQ_DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"

# ActiveMQ tries to shutdown the broker by jmx,
# after a specified number of seconds send SIGKILL
ACTIVEMQ_KILL_MAXSECONDS="300"

## END:DEFAULTCONFIG

# ------------------------------------------------------------------------
# LOAD CONFIGURATION

# load activemq configuration
CONFIG_LOAD="no"
for ACTIVEMQ_CONFIG in $ACTIVEMQ_CONFIGS;
do
if [ -f "$ACTIVEMQ_CONFIG" ] ; then
( . $ACTIVEMQ_CONFIG >/dev/null 2>&1 )
if [ "$?" != "0" ];then
echo "ERROR: there are syntax errors in '$ACTIVEMQ_CONFIG'"
exit 1
else
echo "INFO: loading '$ACTIVEMQ_CONFIG'"
. $ACTIVEMQ_CONFIG
CONFIG_LOAD="yes"
fi
fi
done

# inform user thagt no configuration was loaded
if [ "$CONFIG_LOAD" != "yes" ];then
if [ "$1" != "setup" ];then
echo "INFO: using default configuration";
echo "(you can configure options in one of these file: $ACTIVEMQ_CONFIGS)"
echo
echo "INFO: invoke the following command to create a configuration file"
echo "$0 setup [ $(echo $ACTIVEMQ_CONFIGS|sed 's/[ ][ ]*/ | /') ]"
echo
fi
fi

# create configuration if requested
if [ "$1" = "setup" ];then
if [ -z "$2" ];then
echo "ERROR: specify configuration file"
exit 1
fi
echo "INFO: creating configuration file: $2"
(
P_STATE="0"
while read LINE ;do
if (echo "$LINE" | grep "START:DEFAULTCONFIG" >/dev/null );then
P_STATE="1"
continue;
fi
if (echo "$LINE" | grep "END:DEFAULTCONFIG" >/dev/null);then
P_STATE="0"
break;
fi
if [ "$P_STATE" -eq "1" ];then
echo $LINE
fi
done < $0
) > $2
echo "INFO: it's recommend to limit access to '$2' to the priviledged user"
echo "INFO: (recommended: chown `whoami`:nogroup '$2'; chmod 600 '$2')"
exit $?
fi

# ------------------------------------------------------------------------
# OS SPECIFIC SUPPORT

OSTYPE="unknown"

case "`uname`" in
CYGWIN*) OSTYPE="cygwin" ;;
Darwin*)
OSTYPE="darwin"
if [ "$JAVACMD" = "auto" ];then
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home
fi
;;
esac

# For Cygwin, ensure paths are in UNIX format before anything is touched
if [ "$OSTYPE" = "cygwin" ]; then
[ -n "$ACTIVEMQ_HOME" ] &&
ACTIVEMQ_HOME="`cygpath --unix "$ACTIVEMQ_HOME"`"
[ -n "$JAVA_HOME" ] &&
JAVA_HOME="`cygpath --unix "$JAVA_HOME"`"
[ -n "$CLASSPATH" ] &&
CLASSPATH="`cygpath --path --unix "$CLASSPATH"`"
fi

# Detect the location of the java binary
if [ -z "$JAVACMD" ] ; then
if [ -n "$JAVA_HOME" ] ; then
if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
# IBM's JDK on AIX uses strange locations for the executables
JAVACMD="$JAVA_HOME/jre/sh/java"
else
JAVACMD="$JAVA_HOME/bin/java"
fi
fi
fi

# Hm, we still do not know the location of the java binary
if [ ! -x "$JAVACMD" ] ; then
JAVACMD=`which java 2> /dev/null `
if [ -z "$JAVACMD" ] ; then
JAVACMD=java
fi
fi
# Stopt here if no java installation is defined/found
if [ ! -x "$JAVACMD" ] ; then
echo "ERROR: configuration varaiable JAVA_HOME or JAVACMD is not defined correctly."
echo " (JAVA_HOME='$JAVAHOME', JAVACMD='$JAVACMD')"
exit 1
fi

echo "INFO: useing java '$JAVACMD'"

if [ -z "$ACTIVEMQ_BASE" ] ; then
ACTIVEMQ_BASE="$ACTIVEMQ_HOME"
fi

# For Cygwin, switch paths to Windows format before running java if [ "$OSTYPE" = "cygwin" ]; then
if [ "$OSTYPE" = "cygwin" ];then
ACTIVEMQ_HOME=`cygpath --windows "$ACTIVEMQ_HOME"`
ACTIVEMQ_BASE=`cygpath --windows "$ACTIVEMQ_BASE"`
ACTIVEMQ_CLASSPATH=`cygpath --path --windows "$ACTIVEMQ_CLASSPATH"`
JAVA_HOME=`cygpath --windows "$JAVA_HOME"`
CLASSPATH=`cygpath --path --windows "$CLASSPATH"`
CYGHOME=`cygpath --windows "$HOME"`
if [ -n "$CYGHOME" ]; then
ACTIVEMQ_CYGWIN="-Dcygwin.user.home=\"$CYGHOME\""
fi
fi

# Set default classpath
ACTIVEMQ_CLASSPATH="${ACTIVEMQ_CONFIG_DIR}/;${ACTIVEMQ_CLASSPATH}"

# Backup invocation parameters
COMMANDLINE_ARGS="$@"

# ------------------------------------------------------------------------
# HELPER FUNCTIONS

# Start the ActiveMQ JAR
#
# This function uses a lot of globally defined variables
invokeJar(){
local PIDFILE="$1"
local RET="1"
local CUSER="$(whoami)"

if ( ! [ -f "${ACTIVEMQ_HOME}/bin/run.jar" ] );then
echo "ERROR: '${ACTIVEMQ_HOME}/bin/run.jar' does not exist"
exit 1
fi

if ( [ -z "$ACTIVEMQ_USER" ] || [ "$ACTIVEMQ_USER" = "$CUSER" ] );then
DOIT_PREFIX="sh -c "
DOIT_POSTFIX=";"
elif [ "$(id -u)" = "0" ];then
DOIT_PREFIX="su -c "
DOIT_POSTFIX=" - $ACTIVEMQ_USER"
echo "INFO: changing to user '$ACTIVEMQ_USER' to invoke java"
fi
# Execute java binary
if [ -n "$PIDFILE" ];then
$DOIT_PREFIX "cd $ACTIVEMQ_CONFIG_DIR; $JAVACMD $ACTIVEMQ_OPTS $ACTIVEMQ_DEBUG_OPTS \
-Dactivemq.classpath=\"${ACTIVEMQ_CLASSPATH}\" \
-Dactivemq.home=\"${ACTIVEMQ_HOME}\" \
-Dactivemq.base=\"${ACTIVEMQ_BASE}\" \
$ACTIVEMQ_CYGWIN \
-jar \"${ACTIVEMQ_HOME}/bin/run.jar\" $COMMANDLINE_ARGS >/dev/null 2>&1 &
RET=\"\$?\"; APID=\"\$!\";
echo \$APID > $PIDFILE;
echo \"INFO: pidfile created : '$PIDFILE' (pid '\$APID')\";exit \$RET" $DOIT_POSTFIX
RET="$?"
else
$DOIT_PREFIX "cd $ACTIVEMQ_CONFIG_DIR; $JAVACMD $ACTIVEMQ_OPTS $ACTIVEMQ_DEBUG_OPTS \
-Dactivemq.classpath=\"${ACTIVEMQ_CLASSPATH}\" \
-Dactivemq.home=\"${ACTIVEMQ_HOME}\" \
-Dactivemq.base=\"${ACTIVEMQ_BASE}\" \
$ACTIVEMQ_CYGWIN \
-jar \"${ACTIVEMQ_HOME}/bin/run.jar\" $COMMANDLINE_ARGS" $DOIT_POSTFIX
RET="$?"
fi
return $RET
}

checkRunning(){
if [ -f "$ACTIVEMQ_PIDFILE" ]; then
if [ -z "$(cat $ACTIVEMQ_PIDFILE)" ];then
echo "ERROR: pidfile '$ACTIVEMQ_PIDFILE' exists but contains no pid"
return 2
fi
if (ps -p $(cat $ACTIVEMQ_PIDFILE)|grep java >/dev/null);then
return 0;
else
return 1;
fi
else
return 1;
fi
}

invoke_status(){
if ( checkRunning );then
echo "Activemq is running (pid '$(cat $ACTIVEMQ_PIDFILE)')"
exit 0
fi
echo "Activemq not running"
exit 1
}

invoke_start(){
if ( checkRunning );then
echo "INFO: process with pid '$(cat $ACTIVEMQ_PIDFILE)' is already running"
exit 0
fi

if [ -z "$ACTIVEMQ_OPTS" ] ; then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties"
fi
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SUNJMX_START $ACTIVEMQ_SSL_OPTS"
echo "INFO: starting - inspect logfiles specified in logging.properties and log4j.properties to get details"
invokeJar $ACTIVEMQ_PIDFILE
exit "$?"
}

invoke_fgstart(){
if ( checkRunning );then
echo "ERROR: activemq is already running"
exit 1
fi
if [ -z "$ACTIVEMQ_OPTS" ] ; then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties"
fi
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SUNJMX_START $ACTIVEMQ_SSL_OPTS"

COMMANDLINE_ARGS="start $(echo $COMMANDLINE_ARGS|sed 's,^fgstart,,')"
echo "INFO: starting in foreeground, this is just for debugging purposes (stop process by pressing CTRL+c)"
invokeJar
exit "$?"
}

invoke_stop(){
RET="1"
if ( checkRunning );then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
COMMANDLINE_ARGS="$COMMANDLINE_ARGS $ACTIVEMQ_SUNJMX_CONTROL"
invokeJar
RET="$?"
echo -n "INFO: waiting at least $ACTIVEMQ_KILL_MAXSECONDS seconds for regular process termination of pid '$(cat $ACTIVEMQ_PIDFILE)' : "
FOUND="0"
for i in `seq 0 $ACTIVEMQ_KILL_MAXSECONDS` ;do
if (checkRunning);then
sleep 1
echo -n "."
else
echo " FINISHED"
FOUND="1"
break
fi
done
if [ "$FOUND" -ne "1" ];then
echo "INFO: regular shutdown not successful, sending SIGKILL to process with pid '$(cat $ACTIVEMQ_PIDFILE)'"
kill -KILL $(cat $ACTIVEMQ_PIDFILE)
RET="1"
fi
elif [ -f "$ACTIVEMQ_PIDFILE" ];then
echo "ERROR: no or outdated process id in '$ACTIVEMQ_PIDFILE'"
echo
echo "INFO: removing $ACTIVEMQ_PIDFILE"
else
exit 0
fi
rm -f $ACTIVEMQ_PIDFILE >/dev/null 2>&1
exit $RET
}

invoke_task(){
# call task in java binary
if ( checkRunning );then
if [ "$1" = "browse" ] && [ -n "$ACTIVEMQ_QUEUEMANAGERURL" ];then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
COMMANDLINE_ARGS="$1 $ACTIVEMQ_QUEUEMANAGERURL $(echo $COMMANDLINE_ARGS|sed 's,^browse,,')"
elif [ "$1" = "query" ] && [ -n "$ACTIVEMQ_QUEUEMANAGERURL" ];then
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
COMMANDLINE_ARGS="$1 $ACTIVEMQ_SUNJMX_CONTROL $(echo $COMMANDLINE_ARGS|sed 's,^query,,')"
else
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS $ACTIVEMQ_SSL_OPTS"
COMMANDLINE_ARGS="$COMMANDLINE_ARGS $ACTIVEMQ_SUNJMX_CONTROL"
fi
invokeJar
exit $?
else
echo "INFO: activemq not running"
exit 1
fi
}

# ------------------------------------------------------------------------
# MAIN

# show help
if [ -z "$1" ];then
invokeJar
RET="$?"
cat << EOF
Tasks provided by the sysv init script:
restart - stop running instance (is there is one), start new instance
fgstart - start daemon in foreground, usful for debugging purposes
status - check if activemq process is running
setup - create the specified configuration file for this init script
(see next usage section)

Configuration of this script:
The configuration of this script can be placed on /etc/default/activemq.conf or $HOME/.activemqrc.
To use addtional configurations for running multiple instances on the same operating system
rename or symlink script to a name matching to activemq-instance-<INSTANCENAME>.
This changes the configuration location to /etc/default/activemq-instance-<INSTANCENAME>.conf and
\$HOME/.activemqrc-instance-<INSTANCENAME>. Configuration files in /etc have higher precedence.
EOF
exit $RET
fi

case "$1" in
status)
invoke_status
;;
restart)
if ( checkRunning );then
$0 stop
fi
$0 status
$0 start
$0 status
;;
start)
invoke_start
;;
fgstart)
invoke_fgstart
;;
stop)
invoke_stop
;;
*)
invoke_task
esac

# vim:ai et ts=2 shiftwidth=2 expandtab tabstop=3:

$ ./activemq start
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
INFO: starting - inspect logfiles specified in logging.properties and log4j.properties to get details
INFO: pidfile created : '/home/mschoechlin/temp/apache-activemq-data/activemq.pid' (pid '11283')

$ ./activemq restart
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Java Runtime: Sun Microsystems Inc. 1.6.0_16 /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Heap sizes: current=59776k free=59151k max=886592k
JVM args: -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/; -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0 -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
Stopping broker: localhost
INFO: waiting at least 300 seconds for regular process termination of pid '11283' : FINISHED
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Activemq not running
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
INFO: starting - inspect logfiles specified in logging.properties and log4j.properties to get details
INFO: pidfile created : '/home/mschoechlin/temp/apache-activemq-data/activemq.pid' (pid '11407')
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Activemq is running (pid '11407')

$ ./activemq list
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Java Runtime: Sun Microsystems Inc. 1.6.0_16 /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Heap sizes: current=59776k free=59151k max=886592k
JVM args: -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/; -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0 -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
BrokerName = localhost

$ ./activemq query
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Java Runtime: Sun Microsystems Inc. 1.6.0_16 /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Heap sizes: current=59776k free=59151k max=886592k
JVM args: -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/; -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0 -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
DequeueCount = 0
Name = ddddddddd
MinEnqueueTime = 0
CursorMemoryUsage = 0
MaxAuditDepth = 2048
Destination = ddddddddd
AverageEnqueueTime = 0.0
InFlightCount = 0
MemoryLimit = 1048576
Type = Queue
EnqueueCount = 0
MaxEnqueueTime = 0
MemoryUsagePortion = 0.0
ProducerCount = 0
UseCache = true
MaxProducersToAudit = 32
CursorFull = false
BrokerName = localhost
ConsumerCount = 0
ProducerFlowControl = true
Subscriptions = []
QueueSize = 0
MaxPageSize = 200
CursorPercentUsage = 0
MemoryPercentUsage = 0
DispatchCount = 0
ExpiredCount = 0
...
...

$ ./activemq fgstart
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
ERROR: activemq is already running

$ ./activemq stop
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
Java Runtime: Sun Microsystems Inc. 1.6.0_16 /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Heap sizes: current=59776k free=59151k max=886592k
JVM args: -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/; -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0 -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
Stopping broker: localhost
INFO: waiting at least 300 seconds for regular process termination of pid '11407' : FINISHED

$ ./activemq fgstart
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: useing java '/usr/bin/java'
INFO: starting in foreeground, this is just for debugging purposes (stop process by pressing CTRL+c)
Java Runtime: Sun Microsystems Inc. 1.6.0_16 /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Heap sizes: current=251264k free=247327k max=251264k
JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dcom.sun.management.jmxremote.port=11099 -Dcom.sun.management.jmxremote.password.file=/home/mschoechlin/temp/apache-activemq-data/conf/jmx.password -Dcom.sun.management.jmxremote.access.file=/home/mschoechlin/temp/apache-activemq-data/conf/jmx.access -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/; -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0 -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
Loading message broker from: xbean:activemq.xml
INFO | Using Persistence Adapter: org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter@1cb1a4e2
INFO | Replayed 1 operations from the journal in 0.019 seconds.
INFO | ActiveMQ 5.3.0 JMS Message Broker (localhost) is starting
INFO | For help or more information please see: http://activemq.apache.org/
INFO | Listening for connections at: tcp://lt-msch:61616
INFO | Connector openwire Started
INFO | ActiveMQ JMS Message Broker (localhost, ID:lt-msch-37931-1257840732525-0:0) started
INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
INFO | jetty-6.1.9
INFO | ActiveMQ WebConsole initialized.
INFO | Initializing Spring FrameworkServlet 'dispatcher'
INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
INFO | Initializing Spring root WebApplicationContext
INFO | Connector vm://localhost Started
INFO | Camel Console at http://0.0.0.0:8161/camel
INFO | ActiveMQ Web Demos at http://0.0.0.0:8161/demo
INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
INFO | Started SelectChannelConnector@...:8161
^C INFO | ActiveMQ Message Broker (localhost, ID:lt-msch-37931-1257840732525-0:0) is shutting down
INFO | Connector openwire Stopped
INFO | Connector vm://localhost Stopped
INFO | ActiveMQ JMS Message Broker (localhost, ID:lt-msch-37931-1257840732525-0:0) stopped

$ ./activemq setup /tmp/test.config
INFO: loading '/home/mschoechlin/.activemqrc'
INFO: creating configuration file: /tmp/test.config
INFO: it's recommend to limit access to '/tmp/test.config' to the priviledged user
INFO: (recommended: chown mschoechlin:nogroup '/tmp/test.config'; chmod 600 '/tmp/test.config')

$ cat /tmp/test.config
# ------------------------------------------------------------------------
# Configuration file for running Apache Active MQ as standalone provider
#
# This file overwrites the predefined settings of the sysv init-script
#
# Active MQ installation dir
ACTIVEMQ_HOME="/opt/activemq"

# Active MQ configuration directory
ACTIVEMQ_CONFIG_DIR="$ACTIVEMQ_HOME/conf"

# Active MQ configuration directory
ACTIVEMQ_DATA_DIR="$ACTIVEMQ_HOME/data"

# Location of the pidfile
ACTIVEMQ_PIDFILE="$ACTIVEMQ_DATA_DIR/activemq.pid"

# Location of the java installation
# Specify the location of your java installation using JAVA_HOME, or specify the
# path to the "java" binary using JAVACMD
# (set JAVACMD to "auto" for automatic detection)
#JAVA_HOME=""
JAVACMD="auto"

# Configure a user with non root priviledges, if no user is specified do not change user
ACTIVEMQ_USER=""

# Set jvm memory configuration
ACTIVEMQ_OPTS_MEMORY="-Xms256M -Xmx256M"

# Set jvm jmx configuration
# This enables jmx access over a configured jmx-tcp-port.
# You have to configure the first four settings if you run a ibm jvm, caused by the
# fact that IBM's jvm does not support VirtualMachine.attach(PID).
# JMX access is needed for quering a running activemq instance to gain data or to
# trigger management operations.
#
# Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.access:
# ---
# # The "monitorRole" role has readonly access.
# # The "controlRole" role has readwrite access.
# monitorRole readonly
# controlRole readwrite
# ---
#
# Example for ${ACTIVEMQ_CONFIG_DIR}/jmx.password:
# ---
# # The "monitorRole" role has password "abc123".
# # # The "controlRole" role has password "abcd1234".
# monitorRole abc123
# controlRole abcd1234
# ---
#
# ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=11099 "
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
# ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.ssl=false"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote"

# Set jvm jmx configuration for controlling the broker process
# You only have to configure the first four settings if you run a ibm jvm, caused by the
# fact that IBM's jvm does not support VirtualMachine.attach(PID)
# (see also com.sun.management.jmxremote.port, .jmx.password.file and .jmx.access.file )
#ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11099/jmxrmi --jmxuser controlRole --jmxpassword abcd1234"
ACTIVEMQ_SUNJMX_CONTROL=""

# Specify the queue manager URL for using "browse" option of sysv initscript
ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"

# Set additional JSE arguments
ACTIVEMQ_SSL_OPTS=""

# Uncomment to enable YourKit profiling
#ACTIVEMQ_DEBUG_OPTS="-agentlib:yjpagent"

# Uncomment to enable remote debugging
#ACTIVEMQ_DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"

# ActiveMQ tries to shutdown the broker by jmx,
# after a specified number of seconds send SIGKILL
ACTIVEMQ_KILL_MAXSECONDS="300"

[jira] Resolved: (AMQNET-209) Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.

2009-11-10T12:17:52Z

[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-209.
------------------------------

Resolution: Fixed

> Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.
> --------------------------------------------------------------------------------------------
>
> Key: AMQNET-209
> URL: https://issues.apache.org/activemq/browse/AMQNET-209
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: NMS
> Affects Versions: 1.1.0
> Environment: .NET 3.5, MONO
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.2.0
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> .NET 3.5 and MONO support extension methods. Extension methods, if used carefully, can seamlessly extend the API in a type-safe way. There are several utility functions that are prime candidates for this type of re-factoring. The readability gains in the client code are quite significant. Any extension methods will need to be isolated with
> {{#ifdef NET_3_5 || MONO}}
> since this is a new feature for the .NET platform.
> See the following link for more information on extension methods:
> http://msdn.microsoft.com/en-us/library/bb383977.aspx

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.