Web service fails with HTTP 503 error

Issue description

After installing and starting the xMatters web server, the \webserver\webapps\axis2\WEB-INF\logs\errors.log file contains the following stack trace:

ERROR context.ContextLoader - Context initialization failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'excludeAllDeletedEntitiesInterceptor' defined in class path resource [resources/spring/integration/webServiceContext.xml]: Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [resources/spring/integration/dataApplicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/commons/collections/SequencedHashMap

Caused by:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [resources/spring/integration/dataApplicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/commons/collections/SequencedHashMap

Caused by:

java.lang.NoClassDefFoundError: org/apache/commons/collections/SequencedHashMap

at org.hibernate.mapping.Table.(Table.java:33)

at org.hibernate.cfg.Mappings.addTable(Mappings.java:165)

......

Caused by: java.lang.ClassNotFoundException: org.apache.commons.collections.SequencedHashMap

at java.net.URLClassLoader$1.run(Unknown Source)

......

... 55 more

Attempting to access the xMatters web services (for example, accessing the WSDL or attempting to use the ping service) results in the following error:

HTTP ERROR: 503  
SERVICE_UNAVAILABLE  
RequestURI=/api/services/AlarmPointWebService/pingService  

Cause

This issue is caused by a bug in the xMatters 4.1 installer. The issue has been repaired in the latest installer files and will be addressed permanently in the next patch release.

Resolution

To address this issue, do one of the following:

  • Download the latest installer file and reinstall your xMatters deployment.
  • Download one of the hotfixes attached to this article (41-Installer-hotfix.zip for Windows or 41-Installer-hotfix.tar.gz for Unix) and extract it to the <xMHOME> folder. After the hotfix has finished extracting, restart your xMatters web server.

Further information

This issue was addressed permanently in xMatters engine 4.1 patch 007.

xMatters Reference

DTN-2571, JDN-1907

Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk