startcp not starting the web server and cptool list sessions giving an error

0
No votes yet

When i do a cptool list sessions, i get this error message:

ERROR: Event notification subsystem initialization failed. This is most likely because the JMS provider is not accepting connections. Aborting command.

Also when i start up the server using startcp command, it fails. it says it cannot start the messagebroker component of the web server. It gives an error message saying that the JMS validator timed out.

Any ideas how to fix the error?

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Message Broker

It probably has something to do with messages being queued up. You may want to run this command (in one line):

mbtool update adminobj -rdn="cn=MBInternalTopicConnectionFactory" -property=sctHeartbeatConsumerIsEnabled:false

Here is how you can debug the "jms provider validation timeout" error:

1) Run “configman -g messaging.jms.provider.configfile” to determine where the JMS provider configuration file is located.
2) Edit the JMS provider configuration file (as determined in step 1): change imq.log.level from INFO to DEBUG.
3) Then try starting the jms provider manually by running this command: /etc/init.d/mq start
4) Monitor the mb-broker.log in $CP_ROOT/logs for detailed debugging information

The issue god resolved

Hello Vikram,
Thank you for your suggestion. We had shifted our production server on a load balancer which also was responsible for the SSL on campus. Because of this the networking team made a lot of changes and changed the host file as well as closing many ports.

Since most of the scripts in luminis run based on the host name and not the IP address, most of the processes failed and it looked as if the system broke.

But we resolved teh issue successfully. Thank you very much fo ryour help and support.

ask0500

How to pause or purge Active messages?

Message broker is loaded with calendar transactions which are processing extremely slowly and preventing LDI messages from being processed.

How can we change the subscription state to INACTIVE to allow LDI messages to process?

[cpadmin]$ mbtool list subscriptions -dest=CPInternalDispatch

Number Of Messages: 71202
Subscription State: ACTIVE
Durable Subscription Name: cp$calendar
Client ID: CPUser.WebServlet_0

Can we give cp$cpincoming a higher priority than cp$calendar?