java.io.FileNotFoundException JspServlet.service

[Joly Mathew]

Hi,
We are trying to run a web application moduled deployed in Websphere 5.0 app server.Application installed successfully with no errors.But while trying to access the index.jsp page we are getting a 404-FileNotFound Exception.
SystemOut.log file shows no errors but server1_Exception.log shows the following error attached.
It will be great help if some one can advice me the cause of this exception.
Thanks in Advance,
Joly Mathew
================
Index Occur Time of last Occurence Exception SourceId ProbeId
ences
-----------------------------------------------------------------------
1 4 03.10.16 12:30:15:547 GMT+05:30 java.io.FileNotFoundException com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service 344
2 1 03.10.16 12:23:56:906 GMT+05:30 java.lang.ClassNotFoundException com.ibm.ws.runtime.component.MessageListenerImpl.initialize 83
3 1 03.10.16 12:24:01:266 GMT+05:30 java.io.FileNotFoundException com.ibm.ejs.jms.DurableSubscriptionManagerImpl.readDurableSubscriptionFile 236
4 5 03.10.16 12:24:27:875 GMT+05:30 com.ibm.ws.naming.jcache.CacheEntryNotFoundException com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal 367
5 1 03.10.16 12:24:00:406 GMT+05:30 java.lang.NullPointerException com.ibm.ws.utils.VUTrace.initialisation 584
6 2 03.10.16 12:23:59:781 GMT+05:30 org.omg.CosNaming.NamingContextPackage.AlreadyBound com.ibm.ws.naming.jndicos.CNContextImpl.doCreateSubcontext 2155
7 5 03.10.16 12:41:37:453 GMT+05:30 java.io.FileNotFoundException com.ibm.ws.webcontainer.jsp.servlet.JspServlet.loadJSP 794
8 1 03.10.16 12:24:30:609 GMT+05:30 java.util.ConcurrentModificationException com.ibm.ejs.util.am._Alarm.run 75
9 3 03.10.16 12:24:20:031 GMT+05:30 javax.naming.NameAlreadyBoundException com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_bind_new_corba_context 1042
10 1 03.10.16 12:23:58:031 GMT+05:30 java.lang.ClassNotFoundException com.ibm.ws.activity.ActivityServiceInterceptor.loadMigrationImpls 424
11 4 03.10.16 12:24:00:750 GMT+05:30 javax.naming.NameNotFoundException com.ibm.ws.naming.urlbase.UrlContext.lookup 1226
12 2 03.10.16 12:23:59:781 GMT+05:30 javax.naming.NameAlreadyBoundException com.ibm.ws.naming.jndicos.CNContextImpl.createSubcontext 756
13 2 03.10.16 12:24:00:750 GMT+05:30 javax.naming.NameNotFoundException com.ibm.ws.naming.urlbase.UrlContext.lookup 1252
14 989 03.10.16 12:34:59:781 GMT+05:30 java.lang.ClassNotFoundException com.ibm.ws.classloader.CompoundClassLoader.loadClass 248
15 1 03.10.16 12:24:20:031 GMT+05:30 org.omg.CosNaming.NamingContextPackage.AlreadyBound com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.executeBatchedOperations 1497
16 1 03.10.16 12:24:13:438 GMT+05:30 java.util.MissingResourceException com.ibm.ejs.sm.client.ui.NLS.NLS 166
17 1 03.10.16 12:23:56:953 GMT+05:30 java.io.FileNotFoundException com.ibm.ejs.jms.listener.AsyncMessageLog.readRequestLogFile 128
18 1 03.10.16 12:24:01:250 GMT+05:30 java.lang.ClassNotFoundException com.ibm.ejs.jms.listener.MDBListenerManagerImpl.initializeMQJMSConnectionPooling 705
-----------------------------------------------------------------------

[Hinrich Boog]

Did you find any solution to this problem ? I encountered the same and it is hard to track down.

[Andee Weir]

Also started getting the same problem here. It was all working fine & then the Windows server was restarted & WS now won't start, getting the same error as mentioned above. I've tried uninstalling & reinstalling but with no joy. Also noticed in the startup log the following error:-

Component-managed authentication alias not specified for connection factory or datasource JMS$SampleJMSTopicConnectionFactory.
[25/08/04 10:16:35:453 BST] 641fd451 ConnectionFac I J2CA0107I: Component-managed authentication alias not specified for connection factory or datasource JMS$SampleJMSTopicConnectionFactory$JMSManagedConnection@1663702143.
[25/08/04 10:16:36:906 BST] 641fd451 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$SampleJMSTopicConnectionFactory. The exception which was received is Broker command failed: 3157 Reason code 3157
[25/08/04 10:16:36:922 BST] 641fd451 MDBListenerIm W WMSG0019E: Unable to start MDB Listener PSSampleMDB, JMSDestination Sample/JMS/listen : com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3157 Reason code 3157
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:1208)
at com.ibm.mq.jms.MQConnectionConsumer.pubSubSetup(MQConnectionConsumer.java:318)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:192)
at com.ibm.mq.jms.MQTopicConnection.createCC(MQTopicConnection.java:852)
at com.ibm.mq.jms.MQTopicConnection.createDurableConnectionConsumer(MQTopicConnection.java:817)
at com.ibm.ejs.jms.JMSTopicConnectionHandle.createDurableConnectionConsumer(JMSTopicConnectionHandle.java:186)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:327)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:404)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:437)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:144)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:660)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:631)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:139)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:371)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:726)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:139)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:135)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:542)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:254)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:232)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:117)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

[ August 25, 2004: Message edited by: Andee Weir ]

[Andee Weir]

Found a solution to my problem :-

In my case I also had WAS4.0 cohabiting on the same server. I found that if I started WAS5.0 before WAS4.0 it worked but the other way around didn't. Haven't yet found out why (presume it's a conflicting port) but at least it's a step in the right direction.