THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block |
|---|
Loading ServiceMix from file: C:\exist\servicemix\servicemix-1.0.1\examples\jms-binding\servicemix.xml
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from file [C:\exist\servicemix\servicemix-1.0.1\examples\jms-binding\servicemix.xml]
[INFO] FileSystemXmlApplicationContext - -Bean factory for application context
[org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=1102920]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans
[jencks,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy
[INFO] FileSystemXmlApplicationContext - -5 beans defined in application context org.springframework.context.support. FileSystemXmlApplicationContext;hashCode=1102920]
[INFO] CollectionFactory - -JDK 1.4+ collections available
[INFO] CollectionFactory - -Commons Collections 3.x available
[INFO] FileSystemXmlApplicationContext - -Unable to locate MessageSource with name 'messageSource': using default
[org.springframework.context.support.DelegatingMessageSource@1971afc]
[INFO] FileSystemXmlApplicationContext - -Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster':
using default [org.springframework.context.event.SimpleApplicationEventMulticaster@cdedfd]
[INFO] DefaultListableBeanFactory - -Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory
defining beans [jencks,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy]
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean'jencks'
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean'broker'
[INFO] SpringBrokerContainerFactory - -Loading ActiveMQ broker from configuration: class path resource [activemq.xml]
[INFO] ActiveMQBeanDefinitionReader - -Loading XML bean definitions from class path resource [activemq.xml]
[INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'broker'
[INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'memoryManager'
[INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'derby-ds'
[INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'mysql-ds'
[INFO] BrokerContainerImpl - -ActiveMQ 3.1-M6 JMS Message Broker (ID:el2tong-3108-1131439169538-0:0) is starting
[INFO] BrokerContainerImpl - -For help or more information please see: http://www.logicblaze.com
[INFO] JDBCPersistenceAdapter - -Database driver recognized: [apache_derby_embedded_jdbc_driver]
[INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARC
HAR(250), MSGID VARCHAR(250), MSG BLOB, PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in Schema 'APP'. SQLState: X0Y32 Vendor code: 20000
[INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist.
Failure was: CREATE TABLE ACTIVEMQ_TXS(XID VARCHAR(250) NOT NULL, PRIMARY KEY ( XID )) Message: Table/View 'ACTIVEMQ_TXS' already exists in Schema 'APP'. S
QLState: X0Y32 Vendor code: 20000
[INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: CREATE TABLE ACTIVEMQ_ACKS(SUB VARCHAR(250) NOT NULL, CONTAINER
VARCHAR(250) NOT NULL, LAST_ACKED_ID INTEGER, SE_ID INTEGER, SE_CLIENT_ID VARCHAR(250), SE_CONSUMER_NAME VARCHAR(250), SE_SELECTOR VARCHAR(250), PRIMARY KEY (
SUB, CONTAINER )) Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState: X0Y32 Vendor code: 20000
[INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: ALTER TABLE ACTIVEMQ_MSGS ADD EXPIRATION BIGINT Message:
Column 'EXPIRATION' already exists in Table/View 'APP.ACTIVEMQ_MSGS'. SQLState: X0Y32 Vendor code: 20000
[INFO] JournalPersistenceAdapter - -Opening journal.
[INFO] JournalPersistenceAdapter - -Opened journal: Active Journal: using 2 x 20.0 Megs at: ..\var\journal
[INFO] JournalPersistenceAdapter - -Journal Recovery Started.
[INFO] JournalPersistenceAdapter - -Journal Recovered: 1 message(s) in transactions recovered.
[INFO] TcpTransportServerChannel - -Listening for connections at: tcp://el2tong:61616
[INFO] BrokerConnectorImpl - -ActiveMQ connector started: TcpTransportServerChannel@tcp://el2tong:61616
[INFO] BrokerContainerImpl - -ActiveMQ JMS Message Broker (ID:el2tong-3108-1131439169538-0:0) has started
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'transactionManager'
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jmsFactory'
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi'
[INFO] JCAConnector - -Activating endpoint for activationSpec: ActiveMQActivationSpec{acknowledgeMode='Auto-acknowledge', destinationType='javax.jms.Topic', mes
sageSelector='null', destination='demo.org.servicemix.source', clientId='null',
subscriptionName='null', subscriptionDurability='NonDurable'} using endpointFact
ory: org.jencks.SingletonEndpointFactory@2803d5[transactionManager=null]
[INFO] ActiveMQConnection - -channel status changed: Channel: TcpTransportChannel: Socket[addr=localhost/127.0.0.1,port=61616,localport=3109] has connected
[INFO] BrokerContainerImpl - -Adding new client: ID:el2tong-3108-1131439169538-6:0
on transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=3109,localport=61616]
[INFO] SpringInitialContextFactory - -Loading JNDI context from: class path resource [jndi.xml]
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from class path resource [jndi.xml]
[INFO] XmlBeanFactory - -Creating shared instance of singleton bean 'jndi'
[INFO] JBIContainer - -ServiceMix JBI Container (http://servicemix.org/) name: defaultJBI running version: ServiceMix.
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=inputReceiver,id=inputReceiver] with service: {http://servicemix.org/demo/}inputRece
iver component: org.servicemix.components.jms.JmsInUsingJCABinding@98f192
[INFO] ComponentContextImpl - -Component: inputReceiver activated endpoint: {http://servicemix.org/demo/}inputReceiver : inputReceiver
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=outputSender,id=outputSender] with service: {http://servicemix.org/demo/}outputSende
r component: org.servicemix.components.jms.JmsSenderComponent@1d5b89c
[INFO] ComponentContextImpl - -Component: outputSender activated endpoint: {http://servicemix.org/demo/}outputSender : outputSender
[INFO] JCAContainer - -Jencks JCA Container (http://jencks.org/) has started running version: 1.0-M1
[INFO] BrokerContainerImpl - -Adding new client: ID:el2tong-3114-1131439189647-1:0 on transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=3115,localport=61616]
[INFO] DeliveryChannel - -default destination serviceName for inputReceiver = {http://servicemix.org/demo/}outputSender
[INFO] ActiveMQConnection - -channel status changed: Channel: TcpTransportChannel: Socket[addr=localhost/127.0.0.1,port=61616,localport=3116] has connected
[INFO] BrokerContainerImpl - -Adding new client: ID:el2tong-3108-1131439169538-17:0 on
transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=3116,localport=61616]
[INFO] BrokerContainerImpl - -Removing client: ID:el2tong-3114-1131439189647-1:0 on transport:
TcpTransportChannel: Socket[addr=/127.0.0.1,port=3115,localport=61616]
|
Details
The following table provides more details about the function of each component and bean in the servicemix.xml file.
Component or Bean ID | Description | ||
|---|---|---|---|
jbi | jbi is the "id" of the JBI container and provides the basic infrastructure services for the following components: timer, inputSender, inputReceiver, and outputSender, jmsTrace, and trace. During initialization, several singletons are instantiated: transactionManager, broker, jencks, jmsFactory, and jbi. After initialization, the components in the jbi container are activated, starting with the timer component.timer | ||
inputReceiver | The timer component shows the use of the QuartzComponent class. Every 5 seconds, until the program is terminated, the timer component kicks off an instance of a SimpleTrigger, which is associated with an instance of JobDetail. The job has a property called "name" with a value of "My Example Job" and another property called "group" with a value of "ServiceMix." The resulting message is converted to a normalized message and routed through the NMR. | ||
inputSender | This is a component inside the JBI container. It receives the normalized message (the message from the trigger), converts it to a JMS message, and publishes it to the topic called demo.org.servicemix.source. It uses the jmsTemplate(1) bean to handle the publish. | ||
inputReceiver | This component uses jencks , the JCA container, to listen on port 61616 for a JMS message on the topic called "demo.org.servicemix.source." inputReceiver subscribes to the demo.org.servicemix.source topic. It takes the message, normalizes it, and routes it to outputSender via the NMR. This component combined with outputSender and supporting beans creates a JMS bridge between two topics. | ||
outputSender | This component receives a normalized message from the NMR, marshals it into a JMS message using jmsTemplate, then publishes it on the ActiveMQ (JMS) topic called This component uses jencks , the JCA container, to listen on port 61616 for a JMS message on the topic called "demo.org.servicemix.resultsource." | jmsTrace | This component uses jencks to subscribe inputReceiver subscribes to the " demo.org.servicemix.result" source topic and get messages. It then marshals takes the message into a normalized message , normalizes it, and routes it via the NMR to the trace component.to outputSender via the NMR. This component combined with outputSender and supporting beans creates a JMS bridge between two topics. |
outputSender | This component receives a normalized message from the NMR, marshals it into a JMS message using jmsTemplate, then publishes it on the ActiveMQ (JMS) topic called "demo.org.servicemix.result." | trace | Receives normalized messages from jmsTrace via the NMR. It transforms the normalized message into a string and logs it to the console. |
jencks | The jencks bean defines a JCA container. The JCA container allows you to configure thread pool size, configure a transaction manager, and configure a resource adapter. In this example, the resource adapter is an ActiveMQ adapter, however, another JMS listener could be configured instead. This adapter listens on port 61616 for JMS messages. | ||
broker | The broker bean uses the | ||
transactionManager | This bean is configured to be the default transaction manager for the jbi container. jencks is configured to use the default transaction manager. This transaction manager provides transactional services between the resource adapter (in this case the ActiveMQ resource adapter provided by the jencks JCA container) and components the jbi container. | ||
jmsFactory | This bean listens on port 61616 and provides a pooled ActiveMQ connection. |
...