Use this information for troubleshooting problems that occur when starting an application.
What kind of error do you see when you start an application?
If your HTTP server appears to be functioning correctly, and the Application Server also works on its own, but browser requests sent to the HTTP server for pages are not being served, a problem exists in the WebSphere Application Server plug-in.
In this case:
For further details on troubleshooting plug-in-related problems, see Web server plug-in troubleshooting tips.
If text output appears on your JSP- or servlet-supported Web page, but image files do not:
Typically this directory
will be found in the install_root/installedApps/nodename/appname.ear directory or install_root/installedApps/nodename/appnameNetwork.ear directory.
If the files are in a subdirectory of the document root, verify that the reference to the file reflects that. That is, if the invoices.html file is stored in Windows directory Web_module_name.war\invoices, then links from other pages in the Web application to display it should read "invoices\invoices.html", not "invoices.html".
View the file serving property of the hosting Web module by browsing the source .war file in an assembly tool. If necessary, update the property and redeploy the module.
The
file typically is found in the install_root/config/cells/nodename or nodenameNetwork/applications/application_name/deployments/application name/Web_module_name/web-inf directory.
If text output appears on your JSP- or -servlet-supported Web page, but image files do not:
Typically, this directory
is found in the install_root/installedApps/nodename/appname.ear directory
or install_root/installedApps/nodename/appnameNetwork.ear directory.
If the graphics files are in a subdirectory of the document root, verify that the reference to the graphic reflects that; for example, if the banner.gif file is stored in Windows directory Web_module_name.war/images, the tag to display it should read: <img SRC="images/banner.gif">, not <img SRC="banner.gif">.
View the file serving property of the hosting Web module by browsing the source .war file in an assembly tool. If necessary, update the property and re-deploy the module.
The
file typically is found in the install_root/config/cells/nodename or nodenameNetwork/applications/application_name/deployments/application name/Web_module_name/web-inf directory.
If this error appears in a browser when trying to access a new or modified .jsp file for the first time, the most likely cause is that the JSP file Java source failed (was incorrect) during the javac compilation phase.
Check
the log files for a compiler error message.
C:\WASROOT\temp\ ... test.war\_myJsp.java:14: \
Duplicate variable declaration: int myInt was int myInt
int myInt = 122;
String myString = "number is 122";
static int myStaticInt=22;
int myInt=121;
^
Fix the problem in the JSP source file, save the source and request the JSP file again.
Undefined variable or class name: MyClassThis error indicates that a supporting class or jar file is not copied to the target server, or is not on the class path. Find the MyClass.class file, and place it on the Web module WEB-INF/classes directory, or place its containing .jar file in the Web module WEB-INF/lib directory.
Verify that the URL used to access the resource is correct by doing the following:
JSP serving is enabled by default. File serving for HTML and image files must be enabled as a property of the Web module, in an assembly tool, or by setting the fileServingEnabled property to true in the ibm-web-ext.xmi file of the installed Web application and restarting the application.
For example, to access myCom.myServlet.class, located
in c:\WebSphere\ApplicationServer\installedApps\ myEntApp.ear\myWebApp.war\WEB-INF\classes,
and assuming the context root for the myWebApp module is "myApp", the URL
would be http://myhost.mydomain.com/myApp/servlet/myCom.MyServlet.
Serving servlets by class name must be enabled as a property of the Web module, and is enabled by default. File serving for HTML and image files must be enabled as a property of the Web application, in an assembly tool, or by setting the fileServingEnabled property to true in the ibm-web-ext.xmi file of the installed Web application and restarting the application.
Correct the URL in the "from" HTML file, servlet or JSP file. An HREF with no leading slash (/) inherits the calling resource context. For example:
It is probable that the Web application is not configured for servlet reloading, or the reload interval is too high.
To correct this problem, in an assembly tool, check the Reloading Enabled flag and the Reload Interval value in the IBM Extensions for the Web module in question. Enable reloading, or if it is already enabled, then set the Reload Interval lower.
It is probable that the JSP file failed during the translation to Java phase. Specifically, a JSP directive, in this case an Include statement, was incorrect or referred to a file that could not be found.
To correct this problem, fix the problem in the JSP source, save the source and request the JSP file again.
It is probable that the JSP processor is not configured to keep generated Java source.
In an assembly tool, check the JSP Attributes under Assembly Property Extensions for the Web module in question. Make sure the keepgenerated attribute is there and is set to true. If not, set this attribute and restart the Web application. To see the results of this operation, delete the class file from the temp directory to force the JSP processor to translate the JSP source into Java source again.
It is probable that the full enterprise application path and name, starting with the .ear subdirectory that resides in the applications directory is expected as an argument to the JspBatchCompiler tool, not just the display name.
The directory path is install_root\config\cells\node_nameNetwork\applications.
For example:
req.setCharacterEncoding("gb2312");before any req.getParameter method calls.
This problem affects servlets and jsp files ported from earlier versions of WebSphere Application Server, which converted characters automatically based upon the locale of the WebSphere Application Server.
In some browsers, tree or list type items that extend beyond their allotted windows do not have scroll bars to permit viewing of the entire list.
To correct this problem, right-click on the browser window and click Reload from the menu.
This error can occur when an HTTP timeout causes the servant to be brought down and restarted. To correct this problem, increase the ConnectionIOTimeOut value:
If an application server on which the application is deployed synchronizes configuration with the deployment manager during server startup, then the application might not start and a DeploymentDescriptorLoadException might be written to the server SystemErr.log file. Stop and restart the server, and then try starting the application again.