Topic
1 reply Latest Post - ‏2013-01-22T14:28:44Z by bpaskin
SystemAdmin
SystemAdmin
37422 Posts
ACCEPTED ANSWER

Pinned topic Issues in deploying App in WAS 8.5

‏2013-01-18T21:24:30Z |
Hi,
I am trying to deploy an application on 8.5 version of WAS. I am following all the steps of deployment and the installation seems successful and when I load the home page which is a static JSP it loads correctly but when I click on a menu option on the home page, the request goes to a servlet and all I am seeing is a blank page on the browser, no errors or messages in the log.
I am hoping someone can guide me as to how to debug this. I can provide more details as needed.

The web.xml looks like below:

<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app id="WebApp_ID" version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

<!-- ********************************* Filters ********************************* -->
<filter>
<filter-name>HibernateFilter</filter-name>
<filter-class>fission.ui.servlet.HibernateFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>HibernateFilter</filter-name>
<servlet-name>RequestManager</servlet-name>
</filter-mapping>

<!-- ********************************* Servlets ********************************* -->
<!-- Bootup -->
<servlet>
<servlet-name>
Bootup
</servlet-name>
<servlet-class>
fission.ui.servlet.Bootup
</servlet-class>
<init-param>
<param-name>EDITServicesConfigFileName</param-name>
<param-value>EDITServicesConfig.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>
RequestManager
</servlet-name>
<servlet-class>
fission.ui.servlet.RequestManager
</servlet-class>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet>
<servlet-name>CheckServlet</servlet-name>
<servlet-class>fission.ui.servlet.CheckServlet</servlet-class>
</servlet>

<!-- ********************************* Servlet Mappings ********************************* -->
<!-- EDITSolutions -->
<servlet-mapping>
<servlet-name>
RequestManager
</servlet-name>
<url-pattern>
/servlet/RequestManager/*
</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>CheckServlet</servlet-name>
<url-pattern>/CheckServlet</url-pattern>
</servlet-mapping>

<!-- ********************************* Other ********************************* -->
<session-config>
<session-timeout>500</session-timeout>
</session-config>
<error-page>
<exception-type>
java.lang.Throwable
</exception-type>
<location>
/common/jsp/error.jsp
</location>
</error-page>

<!-- ********************************* Taglibs ********************************* -->
<!-- <taglib>
<taglib-uri>/WEB-INF/taglibs-input.tld</taglib-uri>
<taglib-location>/WEB-INF/taglibs-input.tld</taglib-location>
</taglib>
-->
<!-- **************************** Resource References **************************** -->
<resource-ref>
<description>
Resource reference to a factory for java.sql.Connection instances that may be used for talking to EDITSolutions
database that is configured in the Context configurartion for the web application.
</description>
<res-ref-name>
jdbc/EDITSOLUTIONS
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
<resource-ref>
<description>
Resource reference to a factory for java.sql.Connection instances that may be used for talking to
database that is configured in the Context configurartion for the web application.
</description>
<res-ref-name>
jdbc/PRASE
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
<resource-ref>
<description>
Resource reference to a factory for java.sql.Connection instances that may be used for talking to Security
database that is configured in the Context configurartion for the web application.
</description>
<res-ref-name>
jdbc/SECURITY
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
<distributable />
</web-app>
Updated on 2013-01-22T14:28:44Z at 2013-01-22T14:28:44Z by bpaskin
  • bpaskin
    bpaskin
    3762 Posts
    ACCEPTED ANSWER

    Re: Issues in deploying App in WAS 8.5

    ‏2013-01-22T14:28:44Z  in response to SystemAdmin
    Hi,

    usually a blank page indicates a internal server error (HTTP 500). You should see some error from the Servlet in the SystemOut or SystemErr log, unless the code is swallowing the error. You may want to add some debug code to your JSP and Servlet. Also, you may want to use the Servlet 3.0 specification and do away with the web.xml for most processing.

    Regards,
    Brian