karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prithviraj <meetra...@gmail.com>
Subject Problem in stopping Karaf sever on Unix machine
Date Tue, 03 Feb 2015 10:33:23 GMT
Hi ,

We have using Apache Karaf on unix  machine.
We have deployed our application on different 2 instaces(unix machines)
Each instance is having its own broker url configured .
the borker.xml  file  on each instance looks like as below 
on 10.50.51.92 machine 
	<broker:broker useJmx="true" persistent="true"	brokerName="localbroker"
schedulerSupport="false">
	        <broker:transportConnectors>
	            <broker:transportConnector
uri="activeMQ.url=tcp://10.50.51.92:61616" />
	        </broker:transportConnectors> 
			......

on 10.50.51.93 machine 
	<broker:broker useJmx="true" persistent="true"	brokerName="localbroker"
schedulerSupport="false">
	        <broker:transportConnectors>
	            <broker:transportConnector
uri="activeMQ.url=tcp://10.50.51.93:61616" />
	        </broker:transportConnectors> 
			......

			
Both instances are pointing sharing  same Database credentials. 
In bean.xml file we have configued
org.apache.activemq.ActiveMQConnectionFactory as below 

<bean id="jmsConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
		<property name="brokerURL"
value="failover://(tcp://10.50.51.93:61616,tcp://10.50.51.92:61616)" />		
		<property name="useAsyncSend" value="true" />
	</bean>
	
Due to this 10.50.51.93 became primary and 10.50.51.92 became  secondary .
So when we started 10.50.51.93 first in sequence all bundle get started
properly  and when we  start 10.50.51.92 afterword, broker bundle goes to
starting mode  since *.93 is running state.
When we  stop 10.50.51.93 , broker bundle from 10.50.51.92  goes to running
state  and everything is working as expected.
Now  when we trying to stop 10.50.51.92 by  ./stop  script , karaf server
not getting stop  properly and  it  get  running in the back ground .
we need to kill karaf process  manully by kill commannd .

what could be reason for this ?
Are we missed anything in configuration  ?
Thanks in advance.




--
View this message in context: http://karaf.922171.n3.nabble.com/Problem-in-stopping-Karaf-sever-on-Unix-machine-tp4038249.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Mime
View raw message