[
https://issues.apache.org/jira/browse/CAMEL-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated CAMEL-6276:
------------------------------------
Fix Version/s: 2.12.0
2.11.1
> camel-example-spring-jms failed
> -------------------------------
>
> Key: CAMEL-6276
> URL: https://issues.apache.org/jira/browse/CAMEL-6276
> Project: Camel
> Issue Type: Bug
> Reporter: Christian Müller
> Fix For: 2.11.1, 2.12.0
>
>
> Client and Server using different port numbers:
> Server:
> {noformat}
> 2013-04-14 12:54:55,416 [ing.Main.main()] INFO BrokerService
> - Using Persistence Adapter: MemoryPersistenceAdapter
> 2013-04-14 12:54:55,431 [JMX connector ] INFO ManagementContext
> - JMX consoles can connect to
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> 2013-04-14 12:54:55,560 [ing.Main.main()] INFO BrokerService
> - Apache ActiveMQ 5.8.0 (myBroker,
> ID:christians-macbook-pro.fritz.box-56795-1365936895431-0:1) is starting
> 2013-04-14 12:54:55,567 [ing.Main.main()] INFO TransportConnector
> - Connector vm Started
> 2013-04-14 12:54:55,575 [ing.Main.main()] INFO TransportServerThreadSupport
> - Listening for connections at: tcp://localhost:1101
> 2013-04-14 12:54:55,575 [ing.Main.main()] INFO TransportConnector
> - Connector tcp Started
> {noformat}
> Client
> {noformat}
> cmueller$ mvn exec:java -PCamelClient
> ...
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java
> (default-cli) on project camel-example-spring-jms: An exception occured while
> executing the Java class. null: InvocationTargetException: Exception occurred
> during execution on the exchange: Exchange[Message: 22]: Uncategorized
> exception occured during JMS processing; nested exception is
> javax.jms.JMSException: Error while attempting to add new Connection to the
> pool; nested exception is javax.jms.JMSException: Could not connect to broker
> URL: tcp://localhost:61610. Reason: java.net.ConnectException: Connection
> refused -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
