Failed Deploy to WAS - Websphere

This is a discussion on Failed Deploy to WAS - Websphere ; Hi, I am receiving an error when deploying to WAS v6. When developing on my pc and deploying to local WAS from RAD everything works fine and no errors encountered. I have searched forums and web but have found nothing ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Failed Deploy to WAS

  1. Failed Deploy to WAS

    Hi,

    I am receiving an error when deploying to WAS v6. When developing on my pc and deploying to local WAS from RAD everything works fine and no errors encountered. I have searched forums and web but have found nothing that helps. When deploying to test or prod WAS on Solaris box following error is returned:



    /u01/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr # more SystemOut.log



    3/11/08 8:05:59:632 SAST 00000072 SystemOut O In NLSActionServlet



    3/11/08 8:06:06:816 SAST 00000072 ArchiveDeploy W ADMA0142W: Trying to close the archive that is already closed.



    3/11/08 8:06:12:559 SAST 00000072 ArchiveDeploy W ADMA0091E: The resource WEB-INF/ibm-web-bnd.xmi that is defined in URI WEB-INF



    /ibm-web-bnd.xmi for module WesBank-Fleet-War.war is not valid. The resource has a cross reference WEB-INF/web.xml#WebApp_ID that c



    annot be resolved.



    3/11/08 8:06:14:645 SAST 00000071 SystemOut O In NLSActionServlet



    /u01/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr # more SystemErr.log



    3/11/08 8:06:15:926 SAST 00000071 SystemErr R com.ibm.etools.j2ee.commonarchivecore.exception.De ploymentDescriptorLoadExceptio



    n: IWAE0022E Exception occurred loading deployment descriptor for module "WesBank-Fleet-War.war" in EAR file "/u01/opt/IBM/WebSphere



    /AppServer/profiles/Dmgr01/wstemp/514564614/upload/WesBank-Fleet.ear"



    !Stack_trace_of_nested_exce!



    com.ibm.etools.j2ee.commonarchivecore.exception.De ploymentDescriptorLoadException: WEB-INF/web.xml



    web.xml is as follows:

    <?xml version="1.0" encoding="UTF-8"?>

    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">

    <!-- ENVIRONMENT VARS S -->



    <!-- Logger settings -->

    <env-entry>

    <env-entry-name>propertiesFile</env-entry-name>

    <env-entry-type>java.lang.String</env-entry-type>

    <env-entry-value>/u01/wesbank/props/auto/wesbank_fleet.properties</env-entry-value>

    </env-entry>

    <!-- ENVIRONMENT VARS E -->



    <!-- CONTEXT PARAMS S -->

    <context-param>

    <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>

    <param-value>com.sun.facelets.FaceletViewHandler</param-value>

    </context-param>

    <context-param>

    <param-name>com.sun.faces.verifyObjects</param-name>

    <param-value>false</param-value>

    </context-param>

    <context-param>

    <param-name>com.sun.faces.validateXml</param-name>

    <param-value>true</param-value>

    </context-param>

    <context-param>

    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>

    <param-value>client</param-value>

    </context-param>

    <context-param>

    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>

    <param-value>.jspx</param-value>

    </context-param>

    <context-param>

    <param-name>facelets.DEVELOPMENT</param-name>

    <param-value>true</param-value>

    </context-param>

    <context-param>

    <param-name>facelets.SKIP_COMMENTS</param-name>

    <param-value>true</param-value>

    </context-param>

    <!-- CONTEXT PARAMS E -->



    <!-- LISTENERS S -->

    <listener>

    <listener-class>za.co.fleet.web.listeners.InitilisationListe ner</listener-class>

    </listener>

    <listener>

    <listener-class>org.apache.myfaces.webapp.StartupServletCont extListener</listener-class>

    </listener>

    <listener>

    <listener-class>com.sun.faces.config.ConfigureListener</listener-class>

    </listener>

    <!-- LISTENERS E -->



    <!-- SERVLETS S -->

    <servlet>

    <servlet-name>Faces Servlet</servlet-name>

    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>

    </servlet>

    <servlet>

    <description>Generates PDF for printing/saving</description>

    <servlet-name>PdfPrinter</servlet-name>

    <servlet-class>za.co.fleet.web.servlets.PdfPrinter</servlet-class>

    </servlet>

    <servlet-mapping>

    <servlet-name>Faces Servlet</servlet-name>

    <url-pattern>/faces/*</url-pattern>

    </servlet-mapping>

    <servlet-mapping>

    <servlet-name>PdfPrinter</servlet-name>

    <url-pattern>/pdfPrinter</url-pattern>

    </servlet-mapping>

    <!-- SERVLETS E -->



    <!-- FILTERS S -->

    <filter>

    <display-name>Ajax4jsf Filter</display-name>

    <filter-name>ajax4jsf</filter-name>

    <filter-class>org.ajax4jsf.Filter</filter-class>

    <init-param>

    <param-name>forceparser</param-name>

    <param-value>false</param-value>

    </init-param>

    </filter>

    <filter-mapping>

    <filter-name>ajax4jsf</filter-name>

    <servlet-name>Faces Servlet</servlet-name>

    <dispatcher>REQUEST</dispatcher>

    <dispatcher>FORWARD</dispatcher>

    <dispatcher>INCLUDE</dispatcher>

    </filter-mapping>



    <filter>

    <filter-name>MyFacesExtensionsFilter</filter-name>

    <filter-class>org.apache.myfaces.webapp.filter.ExtensionsF ilter</filter-class>

    <init-param>

    <param-name>maxFileSize</param-name>

    <param-value>20m</param-value>

    </init-param>

    </filter>

    <!-- extension mapping for adding <script/>, <link/>, and other resource tags to JSF-pages -->

    <filter-mapping>

    <filter-name>MyFacesExtensionsFilter</filter-name>

    <servlet-name>Faces Servlet</servlet-name>

    </filter-mapping>

    <filter-mapping>

    <filter-name>MyFacesExtensionsFilter</filter-name>

    <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>

    </filter-mapping>



    <filter>

    <filter-name>AuthFilter</filter-name>

    <filter-class>za.co.fleet.web.security.AuthFilter</filter-class>

    </filter>

    <filter-mapping>

    <filter-name>AuthFilter</filter-name>

    <url-pattern>sec/*</url-pattern>

    </filter-mapping>

    <!-- FILTERS E -->



    <!-- ERROR PAGES S -->

    <error-page>

    <exception-type>java.lang.Exception</exception-type>

    <location>/faces/error/throwable.jspx</location>

    </error-page>

    <error-page>

    <error-code>401</error-code>

    <location>/faces/error/auth.jspx</location>

    </error-page>

    <error-page>

    <error-code>403</error-code>

    <location>/faces/error/auth.jspx</location>

    </error-page>

    <error-page>

    <error-code>404</error-code>

    <location>/faces/error/404.jspx</location>

    </error-page>

    <error-page>

    <error-code>500</error-code>

    <location>/faces/error/500.jspx</location>

    </error-page>

    <!-- ERROR PAGES S -->



    <!-- SECURITY S -->

    <!-- Cert auth -->

    <login-config>

    <auth-method>CLIENT-CERT</auth-method>

    <realm-name>Site</realm-name>

    </login-config>

    <login-config>

    <auth-method>CLIENT-CERT</auth-method>

    <realm-name>Members</realm-name>

    </login-config>



    <security-constraint>

    <web-resource-collection>

    <web-resource-name>Site</web-resource-name>

    <description>Encrypt with SSL</description>

    <url-pattern>/faces/*</url-pattern>

    <url-pattern>/*</url-pattern>

    </web-resource-collection>

    <user-data-constraint>

    <transport-guarantee>CONFIDENTIAL</transport-guarantee>

    </user-data-constraint>

    </security-constraint>

    <security-constraint>

    <web-resource-collection>

    <web-resource-name>Members</web-resource-name>

    <description>Restrict access to the following resources to only authenticated users</description>

    <url-pattern>/faces/sec/*</url-pattern>

    <url-pattern>/sec/*</url-pattern>

    <!--

    <http-method>GET</http-method>

    <http-method>POST</http-method>

    <http-method>PUT</http-method>

    <http-method>TRACE</http-method>

    <http-method>DELETE</http-method>

    <http-method>HEAD</http-method>

    -->

    </web-resource-collection>

    <auth-constraint>

    <role-name>client</role-name>

    <role-name>staff</role-name>

    <role-name>admin</role-name>

    <role-name>system</role-name>

    </auth-constraint>

    <user-data-constraint>

    <transport-guarantee>CONFIDENTIAL</transport-guarantee>

    </user-data-constraint>

    </security-constraint>



    <security-role>

    <role-name>client</role-name>

    </security-role>

    <security-role>

    <role-name>staff</role-name>

    </security-role>

    <security-role>

    <role-name>admin</role-name>

    </security-role>

    <security-role>

    <role-name>system</role-name>

    </security-role>

    <!-- SECURITY E -->



    <!-- APP SETTINGS S -->

    <session-config>

    <session-timeout>30</session-timeout>

    </session-config>

    <welcome-file-list>

    <welcome-file>index.jsp</welcome-file>

    </welcome-file-list>

    <!-- APP SETTINGS E -->



    <!-- RESOURCE REFERENCES S -->

    <resource-ref id="ResourceRef_1199883113673">

    <res-ref-name>defDb</res-ref-name>

    <res-type>javax.sql.DataSource</res-type>

    <res-auth>Container</res-auth>

    <res-sharing-scope>Shareable</res-sharing-scope>

    </resource-ref>

    <resource-ref id="ResourceRef_1199883187555">

    <res-ref-name>oemDb</res-ref-name>

    <res-type>javax.sql.DataSource</res-type>

    <res-auth>Container</res-auth>

    <res-sharing-scope>Shareable</res-sharing-scope>

    </resource-ref>

    <resource-ref id="ResourceRef_1199883187565">

    <res-ref-name>wfsDb</res-ref-name>

    <res-type>javax.sql.DataSource</res-type>

    <res-auth>Container</res-auth>

    <res-sharing-scope>Shareable</res-sharing-scope>

    </resource-ref>

    <!-- RESOURCE REFERENCES E -->

    </web-app>



    Please could someone assist.



    Regards and thanks is advance

    Byron

  2. Re: Failed Deploy to WAS

    btymvios@wesbank.co.za wrote:
    > Hi,
    > I am receiving an error when deploying to WAS v6. When developing on my pc and deploying to local WAS from RAD everything works fine and no errors encountered. I have searched forums and web but have found nothing that helps. When deploying to test or prod WAS on Solaris box following error is returned:
    >
    > /u01/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr # more SystemOut.log
    >
    > 3/11/08 8:05:59:632 SAST 00000072 SystemOut O In NLSActionServlet
    >
    > 3/11/08 8:06:06:816 SAST 00000072 ArchiveDeploy W ADMA0142W: Trying to close the archive that is already closed.
    >
    > 3/11/08 8:06:12:559 SAST 00000072 ArchiveDeploy W ADMA0091E: The resource WEB-INF/ibm-web-bnd.xmi that is defined in URI WEB-INF
    >
    > /ibm-web-bnd.xmi for module WesBank-Fleet-War.war is not valid. The resource has a cross reference WEB-INF/web.xml#WebApp_ID that c
    >
    > annot be resolved.
    >
    > 3/11/08 8:06:14:645 SAST 00000071 SystemOut O In NLSActionServlet
    >
    > /u01/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr # more SystemErr.log
    >
    > 3/11/08 8:06:15:926 SAST 00000071 SystemErr R com.ibm.etools.j2ee.commonarchivecore.exception.De ploymentDescriptorLoadExceptio
    >
    > n: IWAE0022E Exception occurred loading deployment descriptor for module "WesBank-Fleet-War.war" in EAR file "/u01/opt/IBM/WebSphere
    >
    > /AppServer/profiles/Dmgr01/wstemp/514564614/upload/WesBank-Fleet.ear"
    >
    > !Stack_trace_of_nested_exce!
    >
    > com.ibm.etools.j2ee.commonarchivecore.exception.De ploymentDescriptorLoadException: WEB-INF/web.xml
    >
    > web.xml is as follows:
    >
    >

    [snip]
    > Please could someone assist.
    >
    > Regards and thanks is advance
    > Byron
    >

    Byron,
    Looks like the deployment descriptors are incorrect. If you built your
    EAR by exporting it from RAD and then deploying it, there may be
    something wrong in RAD. Try editing the source for web.xml (make some
    trivial change like adding an empty line) and saving it to force a rebuild.

    Ken

  3. Re: Failed Deploy to WAS

    Hi Ken,



    Thanks for your reply, I have found the problem, it was because I had duplicate <login-config> declared in the web.xml.



    Thanks Again, Keep well

    Byron

+ Reply to Thread