D:\projet\testjms\smx>bin\servicemix
servicemix.bat: Enabling Java debug options: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server
=y,suspend=n,address=5005
Listening for transport dt_socket at address: 5005
Starting Apache ServiceMix ESB: 3.1.1-incubating-SNAPSHOT
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - CollectionFactory - JDK 1.4+ collections available
INFO - CollectionFactory - Commons Collections 3.x available
INFO - PropertyPlaceholderConfigurer - Loading properties file from class path resource [servicemix.properties]
INFO - DefaultListableBeanFactory - Pre-instantiating singletons in factory [org.springframework.beans.factory.supp
ort.DefaultListableBeanFactory defining beans [org.apache.servicemix.jbi.util.SystemProperties,propertyConfigurer,authen
ticationService,keystoreManager,authorizationMap,rmiRegistry,jmxServer,org.apache.servicemix.jbi.jmx.ConnectorServerFact
oryBean,jmxConnectorEnvironment,transactionManager,workManager,bootstrapContext,connectionTracker,poolingSupport,connect
ionManager,jndi,jndiEntries,activemqMCF,activemqRA,activemqCF,jbi,org.apache.servicemix.jbi.audit.jdbc.JdbcAuditor,org.a
pache.servicemix.jbi.view.DotViewService,org.apache.servicemix.jbi.logging.LogService]; root of BeanFactory hierarchy]
INFO - JtaTransactionManager - Using JTA UserTransaction: org.jencks.GeronimoPlatformTransactionManager@25b72a
INFO - JtaTransactionManager - Using JTA TransactionManager: org.jencks.GeronimoPlatformTransactionManager@25b
72a
INFO - ConnectorServerFactoryBean - JMX connector server started: javax.management.remote.rmi.RMIConnectorServer@13
c3b45
INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://192.168.80.96:1090/jm
xrmi
INFO - JBIContainer - ServiceMix 3.1.1-incubating-SNAPSHOT JBI Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please see: http://incubator.apache.org/servicemi
x/
INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started
INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-http-3.1.1-incubatin
g-SNAPSHOT-installer.zip ...
WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicem
ix-http installation is suspended and will be resumed once the listed shared libraries are installed
INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-http-3.1.1-in
cubating-SNAPSHOT-installer.zip
INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-jms-3.2-incubating-S
NAPSHOT-installer.zip ...
WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicem
ix-jms installation is suspended and will be resumed once the listed shared libraries are installed
INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-jms-3.2-incub
ating-SNAPSHOT-installer.zip
INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-lwcontainer-3.1.1-in
cubating-SNAPSHOT-installer.zip ...
WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicem
ix-lwcontainer installation is suspended and will be resumed once the listed shared libraries are installed
INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-lwcontainer-3
.1.1-incubating-SNAPSHOT-installer.zip
INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-shared-3.1.1-incubat
ing-SNAPSHOT-installer.zip ...
INFO - JDBCAdapterFactory - Database driver recognized: [apache_derby_embedded_jdbc_driver]
INFO - jetty - Logging to org.apache.servicemix.http.jetty.JCLLogger@10e468f via org.apache.se
rvicemix.http.jetty.JCLLogger
INFO - ComponentMBeanImpl - Starting component: servicemix-http
INFO - ComponentMBeanImpl - Initializing component: servicemix-http
INFO - ComponentMBeanImpl - Starting component: servicemix-jms
INFO - ComponentMBeanImpl - Initializing component: servicemix-jms
INFO - ComponentMBeanImpl - Starting component: servicemix-lwcontainer
INFO - ComponentMBeanImpl - Initializing component: servicemix-lwcontainer
INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-shared-3.1.1-
incubating-SNAPSHOT-installer.zip
INFO - LogTask - log4j system reconfigured
INFO - AutoDeploymentService - Directory: deploy: Archive changed: processing SA-1.0-SNAPSHOT.jar ...
INFO - DefaultListableBeanFactory - Pre-instantiating singletons in factory [org.springframework.beans.factory.supp
ort.DefaultListableBeanFactory defining beans [org.apache.servicemix.http.HttpEndpoint]; root of BeanFactory hierarchy]
INFO - DefaultListableBeanFactory - Pre-instantiating singletons in factory [org.springframework.beans.factory.supp
ort.DefaultListableBeanFactory defining beans [org.apache.servicemix.jms.endpoints.JmsProviderEndpoint,jndiTemplate,inte
rnalJmsQueueConnectionFactory]; root of BeanFactory hierarchy]
DEBUG - JndiTemplate - Looking up JNDI object with name [JQCF]
INFO - ConfigurationRepository - No protocols were defined for property 'carol.protocols', trying with default p
rotocol = 'jrmp'.
DEBUG - JndiObjectFactoryBean - Located object with JNDI name [JQCF]
INFO - DefaultListableBeanFactory - Pre-instantiating singletons in factory [org.springframework.beans.factory.supp
ort.DefaultListableBeanFactory defining beans [jbi]; root of BeanFactory hierarchy]
INFO - ServiceAssemblyLifeCycle - Starting service assembly: SA
INFO - ServiceUnitLifeCycle - Initializing service unit: HTTP
INFO - ServiceUnitLifeCycle - Initializing service unit: JMS
INFO - ServiceUnitLifeCycle - Initializing service unit: LWC
INFO - ServiceUnitLifeCycle - Starting service unit: HTTP
INFO - jetty - jetty-6.0.1
INFO - jetty - Started SelectChannelConnector @ 0.0.0.0:9988
INFO - ServiceUnitLifeCycle - Starting service unit: JMS
INFO - ServiceUnitLifeCycle - Starting service unit: LWC
INFO - ComponentMBeanImpl - Initializing component: receiver
INFO - ComponentMBeanImpl - Starting component: receiver
INFO - AutoDeploymentService - Directory: deploy: Finished installation of archive: SA-1.0-SNAPSHOT.jar
[Fatal Error] :-1:-1: Premature end of file.
ERROR - JmsComponent - Error processing exchange InOnly[
id: ID:192.168.80.96-11348128d6d-2:0
status: Active
role: provider
service: {http://www.etnic.be/test}jmsIn
endpoint: endpoint
in: Unable to display: org.xml.sax.SAXParseException: Premature end of file.
]
org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly identified desti
nation: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDestinationException: P
roxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentException: denjms: ba
d id
Caused by:
javax.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly identified destination: java.l
ang.IllegalArgumentException: denjms: bad id
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.route(RequestMultiplexer.java:304)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.access$200(RequestMultiplexer.java:51)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer$DemultiplexerDaemon.run(RequestMultiplexer.java:
474)
at java.lang.Thread.run(Thread.java:595)
WARN - jetty - EXCEPTION
javax.servlet.ServletException: Failed to process request: java.lang.Exception: org.springframework.jms.InvalidDestinati
onException: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentExcepti
on: denjms: bad id; nested exception is javax.jms.InvalidDestinationException: Proxy could not forward the request to in
correctly identified destination: java.lang.IllegalArgumentException: denjms: bad id
at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
WARN - jetty - Nested in javax.servlet.ServletException: Failed to process request: java.lang.
Exception: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly ident
ified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDestinationE
xception: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentException:
denjms: bad id:
java.lang.Exception: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorre
ctly identified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDe
stinationException: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgument
Exception: denjms: bad id
at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:222)
at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly ident
ified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDestinationE
xception: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentException:
denjms: bad id
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:229)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:432)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:485)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:471)
at org.apache.servicemix.jms.endpoints.JmsProviderEndpoint.processInOnly(JmsProviderEndpoint.java:316)
at org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly identified destinat
ion: java.lang.IllegalArgumentException: denjms: bad id
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.route(RequestMultiplexer.java:304)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.access$200(RequestMultiplexer.java:51)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer$DemultiplexerDaemon.run(RequestMultiplexer.java:
474)
... 1 more
WARN - jetty - /test/:
java.lang.Exception: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorre
ctly identified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDe
stinationException: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgument
Exception: denjms: bad id
at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:222)
at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly ident
ified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDestinationE
xception: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentException:
denjms: bad id
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:229)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:432)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:485)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:471)
at org.apache.servicemix.jms.endpoints.JmsProviderEndpoint.processInOnly(JmsProviderEndpoint.java:316)
at org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly identified destinat
ion: java.lang.IllegalArgumentException: denjms: bad id
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.route(RequestMultiplexer.java:304)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.access$200(RequestMultiplexer.java:51)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer$DemultiplexerDaemon.run(RequestMultiplexer.java:
474)
... 1 more
WARN - jetty - /test/
java.lang.Exception: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorre
ctly identified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDe
stinationException: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgument
Exception: denjms: bad id
at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:222)
at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: org.springframework.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly ident
ified destination: java.lang.IllegalArgumentException: denjms: bad id; nested exception is javax.jms.InvalidDestinationE
xception: Proxy could not forward the request to incorrectly identified destination: java.lang.IllegalArgumentException:
denjms: bad id
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:229)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:432)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:485)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:471)
at org.apache.servicemix.jms.endpoints.JmsProviderEndpoint.processInOnly(JmsProviderEndpoint.java:316)
at org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.InvalidDestinationException: Proxy could not forward the request to incorrectly identified destinat
ion: java.lang.IllegalArgumentException: denjms: bad id
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.route(RequestMultiplexer.java:304)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer.access$200(RequestMultiplexer.java:51)
at org.objectweb.joram.client.jms.connection.RequestMultiplexer$DemultiplexerDaemon.run(RequestMultiplexer.java:
474)
... 1 more