If you ever get an exception deploying a large WAR file on WebSphere here's the error, and how to fix it.
EJPPH0036I: Timeout reached after 300 seconds.
Explanation: A timeout was received prior to the expected notification event.
User Response: Increase the value of the property was.notification.timeout in DeploymentService.properies.
The stack trace may contain the exception com.ibm.wps.pe.mgr.exceptions.AppServerWarInstallException:
DeploymentService.properties is located in
shared/app/config/services under your websphere install root.
Need to list the contents of a jar file? You need to specify the options
tf to the jar command, for example:
jar tf any.jar
If you use
jar --help it may mislead you to think you need to specify a dash, or that you don't need the
Note you could also use this to list the contents of a zip file if you have java's
jar command installed.
Looking for the portlet-api jar file containing the IBM WebSphere Portlet API?
Try looking in the
PortalServer/shared/app/ folder for the file:
wp.pe.api.legacy.jar this contains the classes for the
Here are some links that you will find handy when migrating to the JSR168 portlet api from the IBM WebSphere Portlet API.
WebSphere portal server disabled deployment of JSR168 portlets by default. You can enabled it by setting
portal.enable.jsr168 = true in the file
ConfigService.properties in the directory