Hi there..!!

I was trying out CMS OPENWIRE C++ APIs on SUSE Linux 10.0(Kernel release 2.6.13-15.8-default) Whenever I try to execute TestMain.cpp it gives the following and goes into sleep mode.

Connecting to ActiveMQ broker...
Opening socket to: 127.0.0.1 on port 61666
Sending command: cmd.id = 1, corr.id = -1, type = CONNECTION_INFO
Received command: cmd.id = 0, corr.id = -1, type = WIRE_FORMAT_INFO
Received command: cmd.id = 1, corr.id = -1, type = BROKER_INFO







My AMQ Server is running as :
ACTIVEMQ_HOME: /home/nrawat/incubator-activemq-4.0
Loading message broker from: xbean:activemq.xml
Created MBeanServer with ID: da6bf4:10c2b32b38c:-8000:kuwix:1
INFO BrokerService - ActiveMQ 4.0 JMS Message Broker (localhost) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ RMIConnectorServer started at: service:jmx:rmi://kuwix/jndi/rmi://localhost:1099/jmxrmi INFO ManagementContext - JMX consoles can connect to service:jmx:rmi://kuwix/jndi/rmi://localhost:1099/jmxrmi INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: /home/nrawat/incubator-activemq-4.0/activemq-data/journal INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered. INFO TransportServerThreadSupport - Listening for connections at: tcp://kuwix:61666
WARN  MulticastDiscoveryAgent        - brokerName not set
INFO  TransportConnector             - Connector default Started
INFO TransportServerThreadSupport - Listening for connections at: tcp://kuwix:61633?wireFormat=stomp
INFO  TransportConnector             - Connector stomp Started
INFO  NetworkConnector               - Network Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:kuwix-2163-1151775977128-1:0) started






Hearty Regards,
Naveen Rawat

Reply via email to