WASP module does not start

Document ID : KB000007118
Last Modified Date : 03/08/2018
Show Technical Document Details
Issue:

The probe wasp will not start, reporting the error:
INFO  [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] Initializing Spring root WebApplicationContext

Environment:
Any environment with probe wasp
Cause:

When you start the probe wasp the probe don't get the ip address and the port number

On the wasp log you are not able to see any error just info like this

jun 19 13:42:16:337 INFO  [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] Initializing Spring root WebApplicationContext
jun 19 13:43:04:051 INFO  [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] Initializing Spring FrameworkServlet 'Remoting Servlet'

On the portal log also you are not able to see errors

19 jun 2017 13:29:34,878 INFO  [PortletHotDeployListener:295] Registering portlets for relationshipviewer
19 jun 2017 13:29:34,966 INFO  [PortletHotDeployListener:454] 1 portlet for relationshipviewer is available for use
19 jun 2017 13:29:59,214 INFO  [PortalInitAction:109] Setting metadata.hibernate.dialect=com.jaspersoft.ji.hibernate.dialect.SQLServerJICustomDialect for jasperserver-pro

 

 

Resolution:

Open the wasp.cfg change load_on_startup = true to load_on_startup = false except for root and usm

and make sure the probe start and get ip address and port, if gets, you have some portlet with an issue.

Based on the last line for the portal log maybe will be a issue with the portlet that the portal show on the last line.

On this case jasperserver-pro was the issue.

After you disabled all start one by one to check with one is causing the issue.