Running ActiveMQ under Harmony!
Hey, Just wanted to let you guys know that I tried running ActiveMQ using the Harmony JVM and here are the results: Harmon: latest from tonight Platform: Linux SUSE 10 ActiveMQ: 4.0.2 RC6 Using default config it bombed with: [EMAIL PROTECTED]:~/Desktop/incubator-activemq-4.0.2/bin> ./activemq ACTIVEMQ_HOME: /home/chirino/Desktop/incubator-activemq-4.0.2 Loading message broker from: xbean:activemq.xml Created MBeanServer with ID: UID[-6822e1e4:10e87cde34a:-8000]:dualcoreamd:1 INFO BrokerService - ActiveMQ 4.0.2 JMS Message Broker (localhost) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ WARN ManagementContext - Failed to start jmx connector: javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [EMAIL PROTECTED] [Root exception is java.lang.ClassNotFoundException: class not found] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver] java: /home/chirino/sandbox/harmony/enhanced/drlvm/trunk/vm/vmcore/src/object/object_handles.cpp:100: void GcFrame::add_object(ManagedObject**): Assertion `__null == *p || (*p >= vm_heap_base_address() && *p < vm_heap_ceiling_address())' failed. SIGABRT in VM code. Stack trace: addr2line: '[vdso]': No such file [EMAIL PROTECTED]:~/Desktop/incubator-activemq-4.0.2/bin> But if you disable persistence in ActiveMQ, it runs great! See: [EMAIL PROTECTED]:~/Desktop/incubator-activemq-4.0.2/bin> ./activemq ACTIVEMQ_HOME: /home/chirino/Desktop/incubator-activemq-4.0.2 Loading message broker from: xbean:activemq.xml Created MBeanServer with ID: UID[-68563ba8:10e87cea873:-8000]:dualcoreamd:1 INFO BrokerService - ActiveMQ 4.0.2 JMS Message Broker (localhost) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ WARN ManagementContext - Failed to start jmx connector: javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [EMAIL PROTECTED] [Root exception is java.lang.ClassNotFoundException: class not found] INFO TransportServerThreadSupport - Listening for connections at: tcp://dualcoreamd:61616 WARN MulticastDiscoveryAgent- brokerName not set INFO TransportConnector - Connector default Started INFO TransportServerThreadSupport - Listening for connections at: stomp://dualcoreamd:61613 INFO TransportConnector - Connector stomp Started INFO NetworkConnector - Network Connector default Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:dualcoreamd-27697-1161919638290-0:0) started Kudos to the Harmony team! Great work! -- Regards, Hiram Blog: http://hiramchirino.com
XMPP support (Jabber) available in the main trunk
Just a heads up, I've added XMPP support back into ActiveMQ (we had some experimental support a long time go that's been sitting in the sandbox for a while). This allows any Jabber application (or GoogleTalk) to communicate with the ActiveMQ broker. Currently all names in XMPP map to Topics; am sure we can figure out a way to support queues as well later on. There's some documentation and a demo walk through available here... http://activemq.org/site/xmpp.html The nice thing about the XMPP support is you can use your Jabber client as a quick way to test out your installation & watch things happening in development etc. -- James --- http://radio.weblogs.com/0112098/
[jira] Commented: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[
https://issues.apache.org/activemq/browse/AMQ-734?page=comments#action_37294 ]
Eric Wood commented on AMQ-734:
---
We can reproduce this issue using the current build of 4.0.2. We are running a
distributed queue between two embedded brokers over an unreliable network
(wireless). We had been using 4.0.1, but the brokers did not reestablish the
bridge when it was stopped due to inactivity timeout. We tried 4.0.2 and it
worked great for a while, but eventually one of the reconnect attempts failed.
On the receiver side broker (called CTSServer) we see in the logs wire format
negotiation taking place, but on the send side broker (called CTSClient) we get
the following in the log:
[java] 12:42:12,236 DEBUG DurableConduitBridge:69 - Forwarding messages
for durable destination: queue://TEST.FOO
[java] 12:42:12,237 DEBUG DemandForwardingBridge:289 - stopping CTSClient
bridge to CTSServer is disposed already ? false
[java] 12:42:12,240 DEBUG DemandForwardingBridge:308 - CTSClient bridge to
CTSServer stopped
[java] 12:42:12,241 DEBUG DemandForwardingBridge:289 - stopping CTSClient
bridge to CTSServer is disposed already ? true
[java] 12:42:12,242 DEBUG DemandForwardingBridge:308 - CTSClient bridge to
CTSServer stopped
[java] 12:42:12,244 INFO NetworkConnector:96 - Establishing network
connection between from vm://CTSClient?network=true to tcp://10.134.0.1:61616
[java] 12:42:15,986 DEBUG WireFormatNegotiator:65 - Sending:
WireFormatInfo { version=1, properties={TightEncodingEnabled=true,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[java] 12:42:15,987 DEBUG TcpTransport:133 - TCP consumer thread starting
[java] 12:42:18,957 DEBUG WireFormatNegotiator:95 - Received WireFormat:
WireFormatInfo { version=1, properties={StackTraceEnabled=true,
TightEncodingEnabled=true, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
MaxInactivityDuration=3, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
[java] 12:42:18,957 DEBUG WireFormatNegotiator:102 -
tcp:///10.134.0.1:61616 before negotiation: OpenWireFormat{version=1,
cacheEnabled=false, stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
[java] 12:42:18,958 DEBUG WireFormatNegotiator:113 -
tcp:///10.134.0.1:61616 after negotiation: OpenWireFormat{version=1,
cacheEnabled=true, stackTraceEnabled=true, tightEncodingEnabled=true,
sizePrefixDisabled=false}
[java] 12:42:21,838 DEBUG Service:221 - Async error occurred:
javax.jms.InvalidClientIDException: Broker: CTSClient - Client:
NC_CTSServer_inboundCTSClient already connected
[java] javax.jms.InvalidClientIDException: Broker: CTSClient - Client:
NC_CTSServer_inboundCTSClient already connected
[java] at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:180)
[java] at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:70)
[java] at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:70)
[java] at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:70)
[java] at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:83)
[java] at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:633)
[java] at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:120)
[java] at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:237)
[java] at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:61)
[java] at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92)
[java] at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67)
[java] at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:77)
[java] at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:45)
[java] at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:59)
[java] at
org.apache.activemq.network.DemandForwardingBridgeSupport.startLocalBridge(DemandForwardingBridgeSupport.java:225)
[java] at
org.apache.activemq.network.DemandForwardingBridgeSupport$3.run(DemandForwardingBridgeSupport.java:191)
[java] 12:42:21,840 INFO DemandForwardingBridge:230 - Network connection
between vm://CTSClient#728 and tcp:///10.134.0.1:61616(CTSServer) has been
established.
[java] 12:42:21,851 INFO DemandForwardingBridge:432 - Network connection
between vm://CTSClient#728 and tcp:///10.134.0.1:61616 shutdown due to a local
error: javax.jms.InvalidClientIDException: Broker: CTSClient - Client:
NC_CTSServer_
[jira] Commented: (AMQ-40) jabber support as client & server
[ https://issues.apache.org/activemq/browse/AMQ-40?page=comments#action_37289 ] james strachan commented on AMQ-40: --- FWIW in 4.1 its now via xmpp://host:port For more details see http://activemq.org/site/xmpp.html > jabber support as client & server > - > > Key: AMQ-40 > URL: https://issues.apache.org/activemq/browse/AMQ-40 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan >Priority: Minor > Fix For: 3.1 > > > we now support a new transport > jabber://localhost:61606 > which allows a Jabber client to connect to ActiveMQ and talk Jabber (XMPP) to > the ActiveMQ broker. This allows any Jabber client in any language to talk > natively to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-506) Jabber transport missing
[ https://issues.apache.org/activemq/browse/AMQ-506?page=all ] james strachan resolved AMQ-506. Fix Version/s: 4.1 (was: 4.2) Resolution: Fixed Now back as activemq-xmpp > Jabber transport missing > > > Key: AMQ-506 > URL: https://issues.apache.org/activemq/browse/AMQ-506 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport >Affects Versions: 4.0 M4 >Reporter: Guillaume Nodet > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages
[ https://issues.apache.org/activemq/browse/AMQ-1007?page=all ] james strachan resolved AMQ-1007. - Resolution: Fixed The activemq-xmpp module provides the functionality, for documentation see http://activemq.org/site/xmpp.html > XMPP support (Jabber support) so existing Jabber clients can be used to > interact with and monitor ActiveMQ messages > --- > > Key: AMQ-1007 > URL: https://issues.apache.org/activemq/browse/AMQ-1007 > Project: ActiveMQ > Issue Type: New Feature > Components: Transport >Reporter: james strachan > Assigned To: james strachan > Fix For: 4.1 > > > This is particularly useful for demos or testing things out in development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages
XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages --- Key: AMQ-1007 URL: https://issues.apache.org/activemq/browse/AMQ-1007 Project: ActiveMQ Issue Type: New Feature Components: Transport Reporter: james strachan Assigned To: james strachan Fix For: 4.1 This is particularly useful for demos or testing things out in development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
