Hi Kai, the problem is a workaround for 5.3.1 that now instructs camel and camel web console to use tcp connector to talk to the broker.
Just add something like <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent" > <property name="connectionFactory"> <bean class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="vm://localhost?create=false&waitForStart=10000" /> <property name="userName" value="${activemq.username}"/> <property name="password" value="${activemq.password}"/> </bean> </property> </bean> in webapps/camel/WEB-INF/applicationContext.xml and conf/camel.xml (if you use camel) and you should be fine. We'll fix it for the next release. Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Mar 30, 2010 at 10:39 AM, kaiontour <kai.schae...@mcs-ag.de> wrote: > > Hello, > > I changed the port from 61616 to 23000 in activemq.xml: > > <transportConnectors> > <transportConnector name="openwire" > uri="tcp://localhost:23000"/> > </transportConnectors> > > When I then start activemq.bat it starts normally but does go throught the > "Initializing Spring root WebApplicationContext" process. It just stops. > When going to 61616 again, it works. > > It does not work with any other port then 61616. > > It is working in 5.3.0. > > Any suggestions or is this a bug? > > Thx > Kai > > -- > View this message in context: > http://old.nabble.com/ActiveMQ-5.3.1-WebApplicationContext-does-not-start-with-port-different-to-61616-tp28078490p28078490.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >