Deploying War file in Weblogic 9.2

Hi Nipun,
Thanks for replying.
I checked my connector. It seemed to be properly set up.
Here is the console display when I started Weblogic Server 9.2:

<24-Aug-2007 1:25:38 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\bea921\weblogic92\platform\lib\p13n\p13n-schemas.jar;C:\bea921\weblogic92\platform\lib\p13n\p13n_common.jar;C:\bea921\weblogic92\platform\lib\p13n\p13n_system.jar;C:\bea921\weblogic92\platform\lib\wlp\netuix_common.jar;C:\bea921\weblogic92\platform\lib\wlp\netuix_schemas.jar;C:\bea921\weblogic92\platform\lib\wlp\netuix_system.jar;C:\bea921\weblogic92\platform\lib\wlp\wsrp-common.jar>
<24-Aug-2007 1:25:40 o’clock PM ADT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_06-b05 from Sun Microsystems Inc.>
<24-Aug-2007 1:25:42 o’clock PM ADT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308 >
<24-Aug-2007 1:25:46 o’clock PM ADT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : C:\bea921\license.bea>
<24-Aug-2007 1:25:46 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<24-Aug-2007 1:25:46 o’clock PM ADT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<24-Aug-2007 1:25:47 o’clock PM ADT> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea921\user_projects\domains\base_domain921\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<24-Aug-2007 1:25:51 o’clock PM ADT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<24-Aug-2007 1:25:56 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<24-Aug-2007 1:25:56 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<24-Aug-2007 1:26:11 o’clock PM ADT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
<24-Aug-2007 1:26:12 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<24-Aug-2007 1:26:12 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<24-Aug-2007 1:26:13 o’clock PM ADT> <Notice> <Server> <BEA-002613> <Channel “Default[1]” is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, http.>
<24-Aug-2007 1:26:13 o’clock PM ADT> <Notice> <Server> <BEA-002613> <Channel “Default” is now listening on 142.139.122.98:7001 for protocols iiop, t3, ldap, http.>
<24-Aug-2007 1:26:13 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server “AdminServer” for domain “base_domain921” running in Development Mode>
<24-Aug-2007 1:26:13 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<24-Aug-2007 1:26:13 o’clock PM ADT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<WSEE>Warning: JMS queue ‘weblogic.wsee.DefaultQueue’ is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>
<24-Aug-2007 1:28:02 o’clock PM ADT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<24-Aug-2007 1:28:23 o’clock PM ADT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal.>

Mike

Yes, I am using Weblogic install JDK which is jdk1.5.0_06. After I removed all the paths settings and restart Weblogic Server, the console displayed the following messages:

<SNIP, same as above, just using that one for reference>

Hi Riyad,

The XML validation was on. I turned them all off and redeploy the application. The console displayed the similars error as before.

……
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:229)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:216)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
…..

I deployed the war file in the domain I created in Weblogic Server directory
“c:\bea921\user_projects\domains\base_domain921\autodeploy\FotoProject.war”
The url I used is “http://localhost:7001/FotoProject/home.html&#8221;. When I typed this
url the browser diplayed “Error 404-Not Found”. In Tomcat, when I typed
“http://localhost:8090/FotoProject/home.html&#8221;, I received the initial home page as expected.

There are no errors or markers in my web.xml file. Attached is the web.xml

<web-app>
<display-name>Photo Project</display-name>
<description>Photo Project</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<welcome-file-list>home.htm</welcome-file-list>

<servlet><servlet-name>LogOn</servlet-name><init-param><param-name>url</param-name><param-value>VldteAndProceedLogOn</param-value></init-param>
<servlet-class>com.gnb.ca.LogOn</servlet-class><display-name>LogOn</display-name><description></description></servlet>

<servlet><servlet-name>VldteAndProceedLogOn</servlet-name>
<init-param><param-name>poolName</param-name><param-value>psdmvdevpool</param-value></init-param>
<init-param><param-name>service</param-name><param-value>QMVS_Generic3</param-value></init-param>
<init-param><param-name>ttssService</param-name><param-value>QMVS_Sgnver3</param-value></init-param>
<init-param><param-name>trxnCode</param-name><param-value>T00773</param-value></init-param>
<init-param><param-name>appId</param-name><param-value>2</param-value></init-param>
<init-param><param-name>url1</param-name><param-value>LogOn</param-value></init-param>
<init-param><param-name>url2</param-name><param-value>PasswordToExp</param-value></init-param>
<init-param><param-name>url3</param-name><param-value>ChangePassword</param-value></init-param>
<init-param><param-name>propsLocn</param-name><param-value>c:\Jolt-Jars\joltpool.properties</param-value></init-param>
<servlet-class>com.gnb.ca.VldteAndProceedLogOn</servlet-class><display-name>VldteAndProceedLogOn</display-name><description></description></servlet>

<servlet><servlet-name>RequestFoto</servlet-name>
<init-param><param-name>url1</param-name><param-value>VldteRequestFoto</param-value></init-param>
<init-param><param-name>url2</param-name><param-value>LogOn</param-value></init-param>
<servlet-class>com.gnb.ca.RequestFoto</servlet-class><display-name>RequestFoto</display-name><description></description></servlet>

<servlet><servlet-name>VldteRequestFoto</servlet-name>
<servlet-class>com.gnb.ca.VldteRequestFoto</servlet-class><display-name>VldteRequestFoto</display-name><description></description></servlet>

<servlet><servlet-name>PasswordToExp</servlet-name>
<init-param><param-name>poolName</param-name><param-value>psdmvdevpool</param-value></init-param>
<init-param><param-name>service</param-name><param-value>QMVS_Generic3</param-value></init-param>
<init-param><param-name>trxnCode</param-name><param-value>T00773</param-value></init-param>
<init-param><param-name>appId</param-name><param-value>2</param-value></init-param>
<init-param><param-name>url1</param-name><param-value>LogOn</param-value></init-param>
<init-param><param-name>url2</param-name><param-value>ChangePassword</param-value></init-param>
<servlet-class>com.gnb.ca.PasswordToExp</servlet-class><display-name>PasswordToExp</display-name><description></description></servlet>

<servlet><servlet-name>ChangePassword</servlet-name>
<init-param><param-name>poolName</param-name><param-value>psdmvdevpool</param-value></init-param>
<init-param><param-name>service</param-name><param-value>QMVS_Generic3</param-value></init-param>
<init-param><param-name>trxnCode</param-name><param-value>T00773</param-value></init-param>
<init-param><param-name>appId</param-name><param-value>2</param-value></init-param>
<init-param><param-name>url</param-name><param-value>LogOn</param-value></init-param>
<servlet-class>com.gnb.ca.ChangePassword</servlet-class><display-name>ChangePassword</display-name><description></description></servlet>

<servlet><servlet-name>ToChangePassword</servlet-name>
<init-param><param-name>trxnCode</param-name><param-value>T00773</param-value></init-param>
<init-param><param-name>appId</param-name><param-value>2</param-value></init-param>
<init-param><param-name>url1</param-name><param-value>LogOn</param-value></init-param>
<init-param><param-name>url2</param-name><param-value>ChangePassword</param-value></init-param>
<servlet-class>com.gnb.ca.ToChangePassword</servlet-class><display-name>ToChangePassword</display-name><description></description></servlet>

<servlet><servlet-name>CheckSecurity</servlet-name>
<init-param><param-name>poolName</param-name><param-value>psdmvdevpool</param-value></init-param>
<init-param><param-name>service</param-name><param-value>QMVS_Generic3</param-value></init-param>
<init-param><param-name>appId</param-name><param-value>2</param-value></init-param>
<init-param><param-name>url</param-name><param-value>LogOn</param-value></init-param>
<init-param><param-name>propsLocn</param-name><param-value>c:\Jolt-Jars\joltpool.properties</param-value></init-param>
<servlet-class>com.gnb.ca.CheckSecurity</servlet-class><display-name>CheckSecurity</display-name><description></description></servlet>

<servlet><servlet-name>LogOff</servlet-name><init-param><param-name>url</param-name><param-value>LogOn</param-value></init-param>
<servlet-class>com.gnb.ca.LogOff</servlet-class><display-name>LogOff</display-name><description></description></servlet>

<servlet-mapping><url-pattern>/LogOn</url-pattern><servlet-name>LogOn</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/RequestFoto</url-pattern><servlet-name>RequestFoto</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/VldteRequestFoto</url-pattern><servlet-name>VldteRequestFoto</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/VldteAndProceedLogOn</url-pattern><servlet-name>VldteAndProceedLogOn</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/PasswordToExp</url-pattern><servlet-name>PasswordToExp</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/ChangePassword</url-pattern><servlet-name>ChangePassword</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/ToChangePassword</url-pattern><servlet-name>ToChangePassword</servlet-name></servlet-mapping>
<servlet-mapping><url-pattern>/LogOff</url-pattern><servlet-name>LogOff</servlet-name></servlet-mapping>

</web-app>

I will check BEA forum and hopefully I will find some answers. Thanks for the help. I will update the thread when I got an answer from Bea.

I looked at one of the web.xml in BEA examples. It has two extra statements at the beginning of the web.xml file:

<?xml version=”1.0″ encoding=”UTF-8″?>
<web-app xmlns:j2ee=”http//java.sun.com/xml/ns/j2ee”>

I added these two statments to my web.xml and redeployed my web application.
Wa-Lah! The application was deployed and I could invoke the web application
successfully. But I don’t understand why. Could someone explain please?

Mike

Hi Riyad,
Didn’t mean to mislead you. I went over my changes to web.xml file and tested it carefully. The problem is not due to the two statements which I mentioned I added and/or changed. All in all there is only one <web-app> element.
What made the deployment work was that I changed the sequence of the elements and removed <display-name> and <description> within <servlet> and </servlet>. I also
changed the sequence of the elements within <servlet-mapping> and </servlet-mapping>.

Here is the partial of the Before and After of my web.xml:

Before:

<web-app>
<display-name>Photo Project</display-name>
<description>Photo Project</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<welcome-file-list>home.htm</welcome-file-list>

<servlet><servlet-name>LogOn</servlet-name><init-param><param-name>url</param-name><param-value>VldteAndProceedLogOn</param-value></init-param>
<servlet-class>com.gnb.ca.LogOn</servlet-class><display-name>LogOn</display-name><description></description></servlet>
…..
…..
<servlet-mapping><url-pattern>/LogOn</url-pattern><servlet-name>LogOn</servlet-name></servlet-mapping>
</web-app>

After:

<web-app>
<display-name>Photo Project</display-name>
<description>Photo Project</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>home.html</welcome-file>
</welcome-file-list>

<servlet>
<servlet-name>LogOn</servlet-name>
<servlet-class>com.gnb.ca.LogOn</servlet-class>
<init-param>
<param-name>url</param-name>
<param-value>VldteAndProceedLogOn</param-value>
</init-param>
</servlet>
……
……
<servlet-mapping>
<servlet-name>LogOn</servlet-name>
<url-pattern>/LogOn</url-pattern>
</servlet-mapping>
</web-app>

Although I can invoke my web application, there are some warnings and errors showing in the console after I deployed the war file. However, the application seemed to be working fine. Just wonder will these errors and warnings cause problem down the road. Here is what showed up in the console:

<14-Sep-2007 11:29:36 o’clock AM ADT> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID ‘1189780171912’ for task ’12’. Error is: ‘weblogic.management.DeploymentException: ‘
weblogic.management.DeploymentException:
at weblogic.management.deploy.internal.MBeanConverter.reconcile81MBeans(MBeanConverter.java:302)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.compatibilityProcessor(RedeployOperation.java:182)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:117)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
Truncated. see log file for complete stacktrace
java.util.zip.ZipException: Error opening file – C:\bea921\user_projects\domains\base_domain921\servers\AdminServer\stage\_appsdir_FotoProject_war\FotoProject.war Message – error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:65)
at weblogic.servlet.utils.WarUtils.isWar(WarUtils.java:44)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:54)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.reconcileMBeans(MBeanFactoryImpl.java:157)
Truncated. see log file for complete stacktrace
>
<14-Sep-2007 11:29:36 o’clock AM ADT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application ‘_appsdir_FotoProject_war’.>
<14-Sep-2007 11:29:36 o’clock AM ADT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException:
at weblogic.management.deploy.internal.MBeanConverter.reconcile81MBeans(MBeanConverter.java:302)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.compatibilityProcessor(RedeployOperation.java:182)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:117)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
Truncated. see log file for complete stacktrace
java.util.zip.ZipException: Error opening file – C:\bea921\user_projects\domains\base_domain921\servers\AdminServer\stage\_appsdir_FotoProject_war\FotoProject.war Message – error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:65)
at weblogic.servlet.utils.WarUtils.isWar(WarUtils.java:44)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:54)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.reconcileMBeans(MBeanFactoryImpl.java:157)
Truncated. see log file for complete stacktrace
>

Thanks

Mike

This message has not been recovered.