An issue of deploying war file on tomcat 5.5

Hi,
I know the regular process to deply a war file is like this - stop tomcat server, remove your previous war file and directory, say abc.war and dir abc, copy your new version abc.war into webapps and restart tomcat server.
However, I found an interesting issue today - I was deploying a new release war file as described. While I stopped tomcat, removed all previous version direcotry, and restarted tomcat server, I got an http 404 error saying that the resource /abc/ is not available. I noticed that the org folder was not generated at work/Catalina/locahost/abc.
I stuck there for a long time to try to fix but did not find a solution. I am pretty sure the war file should be ok since it works fine on my local machine. This only happened in the unix box. Later, occasionally, I removed the director abc without stopping the tomcat server. In another word, I removed the war file while tomcat is still running. A new abc directory was created soon and now it works.
Anyone has any idea about that? Thanks!
Michael

Any thoughts? Thanks

Similar Messages

How to deploy WAR file in tomcat.?

Can anybody please provide step by step information of deploying war file to Jakarta tomcat without IDE.
I am working on Windows XP with jakarta tomcat 4.1.30.
Thanks in advance.
Regards,
Aman Aggarwal

See if tomcat runs as a service in your operating system. If you can locate it, you can set the start type to automatic. A very crud way is to run the tomcat startup file from autoexe.bat.
I don't know how to do this in Linux. Here is a link for tomcat 6. Maybe it is the same in tomcat 4
[http://tomcat.apache.org/tomcat-6.0-doc/setup.html]
Edited by: nirvan on Dec 29, 2008 9:15 AM

Deploying .war file on Tomcat 4.1?

Hi,
I would like to know whether anyone know how to deploy a .war file onto Tomcat 4.1? Or can this be done?
And what about web.xml? Is it different from a web.xml written for BEA's Weblogic Server?
Thanks

hmm.. ic
The .war file when drop in the webapps dir and u restart tomcat, it auto create a dir with your .war filename and the content of .war file is copied to there.
Am i rite to say so?
And wat about the web.xml?
If i need to add users and password how can I accomplished it in tomcat web.xml?
Last but not least, thanks for taking the time to reply. :D

Web Service cannot be Started when we deploy war file in Tomcat

Hello every one,
We made a webservice in Netbeans 6. and we created the war file
and ist is workign fine with netbeans. when we tried to deploy to tomcat
it is showing error as given below:
**FAIL - Application at context path /WebApplication3 could not be started**
please help me to sort out this problem as early as possible.
Thanks in advance
Vishnu

Any one has any idea on this. I am stuck up with this. Help!
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pragashj:
OS : Windows NT 4.0 SP 5
OAS : 4.0.8.2
Issue : Listner failed to start asking me to start OAS service first. But the OAS service is already started. When I tried starting the Listner service from Windows - Services (In control panel) still it failed. OAS Service though active does not show as active in the Service Control(This issue is listed in the Release note). The svwww.err gives oracle_adp_init returned ADI_FATALINIT.
Any one had the same issue? How do I work around to get my Web Listner started?
Thanks<HR></BLOCKQUOTE>
null

Deploying war file on Tomcat: file path problem

Hello all,
i am using my eclipse ide for automatically deploy my webapplication to Tomcat. For Database connectivity i configured hibernate. To configure hibernate i am using the following code:
package de.wfm.hibernate.hibernateUtil;
import org.hibernate.HibernateException;
import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;
public class ESDBFactory {
     private static SessionFactory sf;
     private static Session session = null;
     private static String pathToCfgFile = "de\\"
                         + "wfm\\hibernate\\hibernateUtil\\esdb.cfg.xml";
     public static synchronized Session getSession() throws HibernateException {
          if (session==null) {
               if (sf==null) {
                    sf = new Configuration()
                         .configure(pathToCfgFile).
                         buildSessionFactory();
          session = sf.openSession();
          return session;
}When i use this in the ide all is fine. But when i export my application to a war file and deploy it on Tomcat i got the exception:
2006-07-28 10:06:10 StandardWrapperValve[Urlaubsplanung Servlet]: Servlet.service() for servlet Urlaubsplanung Servlet threw exception
javax.faces.FacesException: #{User.doLogin}: javax.faces.el.EvaluationException: org.hibernate.HibernateException: de\wfm\hibernate\hibernateUtil\esdb.cfg.xml not foundHow to avoid this? What do i have to do to set the file path correctly?
Regards,
ak

hmm.. ic
The .war file when drop in the webapps dir and u restart tomcat, it auto create a dir with your .war filename and the content of .war file is copied to there.
Am i rite to say so?
And wat about the web.xml?
If i need to add users and password how can I accomplished it in tomcat web.xml?
Last but not least, thanks for taking the time to reply. :D

Deploying WAR files in Tomcat

I placed cdmanagersample.war file under c:/tomcat5.0/webapps directory and restarted Tomcat. Then I went to web browser and typed http://127.0.0.1/cdmanagersample. I get the following error.
HTTP Status 404 - /cdmanagerSample
Shouldn't Tomcat extract the war file and deploy it as it should. Any reason why it didn't?

Here's my server.xml file now:

<Context path="/cdmanagersample " docBase="../webapps/cdmanagersample " debug="0" reloadable="true" >

<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
</Context>
When I try strating Tomcat by saing catalina run, I get following:
C:\Program Files\Apache Software Foundation\Tomcat 5.0>cd bin
C:\Program Files\Apache Software Foundation\Tomcat 5.0\bin>catalina run
Using CATALINA_BASE: C:\Program Files\Apache Software Foundation\Tomcat 5.0
Using CATALINA_HOME: C:\Program Files\Apache Software Foundation\Tomcat 5.0
Using CATALINA_TMPDIR: C:\Program Files\Apache Software Foundation\Tomcat 5.0\
mp
Using JAVA_HOME: C:\j2sdk1.4.2_03
Jan 28, 2004 11:21:52 AM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use: JVM_Bind:8080
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndp
nt.java:302)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:18
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnecto
java:1366)
at org.apache.catalina.core.StandardService.initialize(StandardService
ava:633)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.j
a:2413)
at org.apache.catalina.startup.Catalina.load(Catalina.java:532)
at org.apache.catalina.startup.Catalina.load(Catalina.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:397)
Jan 28, 2004 11:21:52 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException: Protocol handler initialization failed: java.net.BindExce
ion: Address already in use: JVM_Bind:8080
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnecto
java:1368)
at org.apache.catalina.core.StandardService.initialize(StandardService
ava:633)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.j
a:2413)
at org.apache.catalina.startup.Catalina.load(Catalina.java:532)
at org.apache.catalina.startup.Catalina.load(Catalina.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:397)
Jan 28, 2004 11:21:52 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2453 ms
Jan 28, 2004 11:21:53 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 28, 2004 11:21:53 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.16
Jan 28, 2004 11:21:53 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jan 28, 2004 11:21:53 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Jan 28, 2004 11:21:53 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:C:\Program Files\Apache S
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\admin.xml
Jan 28, 2004 11:21:54 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=t
e
Jan 28, 2004 11:21:54 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='org.apache.struts.action.ActionResources', returnN
l=true
Jan 28, 2004 11:21:55 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', ret
nNull=true
Jan 28, 2004 11:21:58 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:C:\Program Files\Apache S
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\balancer.xml
Jan 28, 2004 11:21:59 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:C:\Program Files\Apache S
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\manager.xml
Jan 28, 2004 11:21:59 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /cdmanagersample from URL fil
C:/Program Files/Apache Software Foundation/Tomcat 5.0/webapps/cdmanagersample
Jan 28, 2004 11:22:00 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=t
e
Jan 28, 2004 11:22:00 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='org.apache.struts.action.ActionResources', returnN
l=true
Jan 28, 2004 11:22:00 AM org.apache.struts.util.PropertyMessageResources <init
INFO: Initializing, config='cdmanager.ApplicationResources', returnNull=true
Jan 28, 2004 11:22:00 AM org.apache.struts.action.ActionServlet initApplicatio
ataSources
SEVERE: Initializing application data source org.apache.struts.action.DATA_SOU
E
java.sql.SQLException: Cannot load JDBC driver class 'org.gjt.mm.mysql.Driver'
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataS
rce.java:529)
at org.apache.commons.dbcp.BasicDataSource.setLogWriter(BasicDataSourc
java:381)
at org.apache.struts.util.GenericDataSource.setLogWriter(GenericDataSo
ce.java:345)
at org.apache.struts.action.ActionServlet.initApplicationDataSources(A
ionServlet.java:942)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:457)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrappe
java:1044)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:
7)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardCont
t.java:3948)
at org.apache.catalina.core.StandardContext.start(StandardContext.java
271)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBa
.java:866)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
0)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:63
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostD
loyer.java:316)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:859
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:6
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:4
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1002)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.ja
:393)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecy
eSupport.java:166)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:113
at org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:112
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:5
at org.apache.catalina.core.StandardService.start(StandardService.java
19)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2
3)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
Jan 28, 2004 11:22:00 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL file:C
Program Files\Apache Software Foundation\Tomcat 5.0\webapps\jsp-examples
Jan 28, 2004 11:22:01 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path from URL file:C:\Program Fil
\Apache Software Foundation\Tomcat 5.0\webapps\ROOT
Jan 28, 2004 11:22:01 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL f
e:C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\servlets-exam
es
Jan 28, 2004 11:22:01 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tomcat-docs from URL file:C:
rogram Files\Apache Software Foundation\Tomcat 5.0\webapps\tomcat-docs
Jan 28, 2004 11:22:01 AM org.apache.coyote.http11.Http11Protocol start
SEVERE: Error starting endpoint
java.net.BindException: Address already in use: JVM_Bind:8080
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndp
nt.java:302)
at org.apache.tomcat.util.net.PoolTcpEndpoint.startEndpoint(PoolTcpEnd
int.java:319)
at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:2
at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.jav
1436)
at org.apache.catalina.core.StandardService.start(StandardService.java
28)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2
3)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
Jan 28, 2004 11:22:01 AM org.apache.catalina.startup.Catalina start
SEVERE: Catalina.start:
LifecycleException: Protocol handler start failed: java.net.BindException: Ad
ess already in use: JVM_Bind:8080
at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.jav
1438)
at org.apache.catalina.core.StandardService.start(StandardService.java
28)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2
3)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
Jan 28, 2004 11:22:01 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 9224 ms
StandardServer.await: create[8005]: java.net.BindException: Address already in
se: JVM_Bind
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
at java.net.ServerSocket.bind(ServerSocket.java:318)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:5
at org.apache.catalina.startup.Catalina.await(Catalina.java:637)
at org.apache.catalina.startup.Catalina.start(Catalina.java:599)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398)
Jan 28, 2004 11:22:01 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jan 28, 2004 11:22:01 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stoping http11 protocol on 8080 Catalina:type=ThreadPool,name=http8080
Jan 28, 2004 11:22:01 AM org.apache.coyote.tomcat5.CoyoteConnector stop
SEVERE: Coyote connector has not been started
Jan 28, 2004 11:22:01 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /admin
C:\Program Files\Apache Software Foundation\Tomcat 5.0\bin>

Deploy war file to Tomcat

Hi all,
i have this problem:
i've created a web application with Sun Studio Creator 2 with connectione to DB Oracle 10.1.3
i've exported war file to deploy it under Tomcat but when i try to lunch the application i get the following error:
com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: java.lang.RuntimeException: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null'
     com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.destroy(ViewHandlerImpl.java:601)
     com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:316)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)Could you help me plese?
Thank's,
Ciro.

hi Ciro,
You have not created the context of your database in context.xml of your tomat (path for context.xml tomcat folder/conf/context.xml)
Unless and until you don't create context you will get same error.
regards,
Joshmachine
Edited by: joshmachine on Mar 27, 2008 3:46 PM

Error while deploying WAR file in TOMCAT

hi.
I have put my SEA.WAR (test WAR file) into /webapps of TOMCAT.
I checked the server.xml and put:
<Context path="/SEA" docBase="SEA" debug="0"/>
I restarted TOMCAT and tried to execute the file:
http://localhost:8080/SEA/index.jsp
But I got error message:
Apache Tomcat/4.0.3 - HTTP Status 404 - /SEA/index.jsp
What was happenning?
Anyone can help me?
Thank you.

what happens when you just hit http://localhost:8080/SEA/ ?

Issue after deploying war file???

We are moving from a windows box to a unix box...
We had installed jdeveloper - jdev11113install.exe (along with weblogic server and adf libraries) earlier version on the windows box and deployed a ADF application war file on that box which worked fine.
Now i have installed jdevloper -jdev11115install.jar (along with weblogic server and adf libraries) a newer version. Now if i deploy my adf war file on this weblogic server its not fully functional. I have some bars and charts which dont load on one tab but loads on the other.
Here are my logs :
AdminServer-Diagnostic .log
[2011-05-13T00:59:05.835-07:00] [AdminServer] [WARNING] [J2EE JMX-46041] [oracle.as.jmx.framework.MessageLocalizationHelper] [tid: JMX FRAMEWORK Domain Runtime MBeanServer pooling thread] [userId: <anonymous>] [ecid: 0000IzcNPGiEGRG5yz_AiW1DnEIq000002,0] The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
[2011-05-13T01:00:11.288-07:00] [AdminServer] [ERROR] [] [org.apache.beehive.netui.pageflow.internal.AdapterManager] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IzcNfGTEGRG5yz_AiW1DnEIq000003,0] [APP: consoleapp] ServletContainerAdapter manager not initialized correctly.
[2011-05-13T01:14:04.821-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:14:05.208-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:15:17.280-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:15:19.989-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:15:26.200-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:17:22.266-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp already exists
[2011-05-13T01:17:22.275-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp deregistered
[2011-05-13T01:17:22.278-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:17:42.347-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:17:42.598-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:17:46.568-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:20:34.868-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:20:35.142-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:21:07.963-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:21:08.177-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:21:11.460-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:23:52.056-07:00] [AdminServer] [NOTIFICATION] [] [oracle.jbo.uicli.mom.CpxUtils$Visitor] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] zip:/usr/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/STUsageApp/aszvbi/war/WEB-INF/lib/_wl_cls_gen.jar!/st/view/DataBindings.cpx
[2011-05-13T01:23:53.108-07:00] [AdminServer] [NOTIFICATION] [ADFC-54008] [oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] ADFc: Initializing ADF Page Lifecycle for the JSF environment, LifecycleContextBuilder is 'oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
[2011-05-13T01:23:58.753-07:00] [AdminServer] [WARNING] [] [oracle.adf.share.jndi.ReferenceStoreHelper] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004c,0] [APP: STUsageApp] Incomplete connection reference object for connection:oc
[2011-05-13T01:25:08.181-07:00] [AdminServer] [WARNING] [] [org.apache.myfaces.trinidad.webapp.ResourceServlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-00000000000000d2,0] [APP: STUsageApp] ResourceServlet._setHeaders(): Content type for /bi/jsLibs/engine_20110409.swf is NULL![[
Cause: Unknown file extension
]]

basedomain.log
n.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
     at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
     at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
     at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:17:50 o'clock AM PDT> <Error> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002c> <1305274670833> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670836> <BEA-149004> <Failures were detected while initiating start task for application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670837> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
     at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
     at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
     at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:18:32 o'clock AM PDT> <Warning> <netuix> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000030> <1305274712736> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppDeploymentsControlPage.>
####<13-May-2011 1:19:47 o'clock AM PDT> <Warning> <Socket> <server_name> <AdminServer> <ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000011> <1305274787906> <BEA-000450> <Socket 21 internal data record unavailable (probable closure due idle timeout), event received -32>
####<13-May-2011 1:20:34 o'clock AM PDT> <Warning> <J2EE> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038> <1305274834453> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application STUsageApp is not versioned.>
####<13-May-2011 1:21:22 o'clock AM PDT> <Notice> <HTTP> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000042> <1305274882683> <BEA-101352> <There are no active sessions. The webapp module STUsage-ViewController-context-root of application STUsageApp is ready to go into admin mode.>

[Deploy WAR File with Tomcat] Blank page after login to DSCC

i installed Sun Java System Directory Server Enterprise Edition 6.3 ( Zip Distro) in SuSe Linux 10 sp2 (64bit )
and I've deployed DSCC web console in tomcat with following installation guide
http://docs.sun.com/app/docs/doc/820-2761/6nebf1543?a=view
open browser , go to http://hostname:8080/dscc, The Directory Service Manager Login page displays.
i entered username/password , after that, nothing come up in the page...
Anyone got idea ?
Edited by: ikcat on Jan 16, 2009 12:06 AM

Usually restarting Tomcat will help. Do the Tomcat logs have anything of interest?

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
     Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
     Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

Tomcat error when deploying WAR file

Hi
I have written my first program using Creator 2. It runs with no problems when i use the sun appserver. however I wanted it to run on tomcat and having deplowed the war file on tomcat when i run the program I get the following error message which i will add at the end of the message.
Is this because tomcat is using java \jre1.5.0_06 library and Creator 2 deploy using j2ee1.4 ?
ERROR MESSAGE:
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
     com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
root cause
java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:123)
     com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:311)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs.

hi Marco
Thanks for the advice. I have made some progress but still getting an error when i deploy on tomcat but not on the bundeled server. I will add the error at the end and hope you may be able to directly me again. There is another Q regarding the page you adviced me to look at . It suggests in step 2 copying two .jar files but fails to indicate copying them to which directory. Can u help?
ERROR:
Cannot read USERS database: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'users' at line 1)
Thanks
zak

Deploy war file developed by rational to tomcat 5.5

i've developed an application using rational application developer then exported it to war file
then i want to deploy this war file to tomcat server
could someone help me!!!
thanx in advance

If it's a standard WAR file, properly done, just drop it in the Tomcat /webapps directory and start up Tomcat. Use the WAR file name as the context.
%

Deploying war files with JBuilder 5 to Tomcat 4

Hi,
I'm developing a webapp in JBuilder 5. When I copy my war file to tomcat 3.2 webapps directory and start tomcat it works just fine, but when I copy my war file to the webapps directory in tomcat 4 I have the following error when I start tomcat 4:
ERROR reading java.io.ByteArrayInputStream@33f8f6
At Line 15 /web-app/servlet/
All the examples in Tomcat 4 works just fine, and if I create a war file from the command prompt it also works, but the war file generated with JBuilder 5 doesn't work.
does this sound familiar?
please help

Hi Lilja,
ran into this myself, and had to do a full web search to find the answer.
JBuilder5 will let you change the Tomcat version a certain project uses, but it won't necessarily like it.
Creating a new project with Tomcat 4 as the default server, and then putting your existing files into it seems to work.
Dodgy, I know, but blame Borland. ;-)
Ta,
Martin Hughes

Deploying War file in Weblogic 9.2

Hi,
          I have a web application packaged as war file. The servlets are compiled using jdk1.5.0_06. I deployed the
          war file in Tomcat 5.5 successfully and I can invoke the
          application via url http://localhost:8090/FotoProject/home.html
          On the other hand I installed Weblogic Server 9.2. Started the Examples Server and dropped my "FotoProject.war" in "\weblogic92"\samples\domains\wl_server\autodeploy" directory. When I entered url "http://localhost:7001/FotoProject/home.html", I got
          "Error 404-Not Found".
          Could some one help and tell me what is wrong? Thanks in advance.
          Mike

Restart the server and see if you get any deployment error in log files. Do you see proper deployment msg in the logs? May be there is some issue in weblogic.xml which is not allowing app to deploy properly. How does the app appear in Admin console under deployments?

An issue of deploying war file on tomcat 5.5

Similar Messages

Maybe you are looking for