Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: Aquidneck
-
Fix Version/s: 2.0.0, sprint 14: 12-05-2012, Aquidneck
-
Component/s: None
-
Labels:None
-
Environment:
QA Env. BidMgr 734, JBOSS 709,
-
Sprint:Sprint 14
Description
I have recently updated the QA Environment with BidMgr 734 and JBOSS 709 and ran the JBoss Messenger service upgrade scripts. Since the upgrade, the admax listener will not start properly. After initial deployment, I experienced what you see in the listener.log file attached to this JIRA. After that, I stopped everything and restarted JBOSS and the listener.
I used nohup /usr/local/tsa/bidmgr/jmslistener.sh 3 2> /tmp/listener.log & to start the listener and it does the following in the listener.log and then stops:
2012-11-30 19:43:57.335 (3) [AdMaxListener]: Starting in 3...
2012-11-30 19:43:58.335 (3) [AdMaxListener]: Starting in 2...
2012-11-30 19:43:59.336 (3) [AdMaxListener]: Starting in 1...
2012-11-30 19:44:00.336 (3) [AdMaxListener]: Connecting to: localhost:1100
I can attempt to deploy campaigns that are picked up in the jboss logs but not in listener.
If I start the listner by /etc/init.d/tsa-admax-jmslistener.sh start, the /var/local/tsa/log/tsa-admax-jmslistener/tsa-admax-jmslistener.log file only contains one line "standard in must be a tty"
