Re: LifecycleProcessor exception

2017-05-11 Thread Hidekazu
sage in context: http://activemq.2283324.n4.nabble.com/LifecycleProcessor-exception-tp4725380p4725958.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: LifecycleProcessor exception

2017-05-09 Thread Tim Bain
stall # add "-Dmaven.test.skip=true" if tests are failing on > your system (should not happen) > > However, I just put activemq package in /opt/apache-activemq directory. > I said to you that I did clean install before. > I'm sorry if I misunderstood the meaning of clean

Re: LifecycleProcessor exception

2017-05-09 Thread Hidekazu
View this message in context: http://activemq.2283324.n4.nabble.com/LifecycleProcessor-exception-tp4725380p4725818.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: LifecycleProcessor exception

2017-05-07 Thread Tim Bain
ake sense? > Java version for activemq is 1.7.0_25 > > Thanks. > Kawai > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/LifecycleProcessor-exception-tp4725380p4725730.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >

Re: LifecycleProcessor exception

2017-05-07 Thread Hidekazu
? Java version for activemq is 1.7.0_25 Thanks. Kawai -- View this message in context: http://activemq.2283324.n4.nabble.com/LifecycleProcessor-exception-tp4725380p4725730.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: LifecycleProcessor exception

2017-05-01 Thread Tim Bain
ce when restarted it by > executing “activemq restart” command. > Here are the exceptions in activemq.log. > I found there were several posts about this LifecycleProcessor exception in > the forum, however, none of them didn’t seem to be the reason which caused > my resta

LifecycleProcessor exception

2017-05-01 Thread Hidekazu
Hi, Dear All I have an ActiveMQ ver 5.14.3 and had a problem once when restarted it by executing “activemq restart” command. Here are the exceptions in activemq.log. I found there were several posts about this LifecycleProcessor exception in the forum, however, none of them didn’t seem to be the