I am currently trying to deploy a GWT web app to a tomcat instance, and the program isn't running correctly. On close examination of the tomcat logs, it looks like Tomcat is running into a AccessDeniedException.
SEVERE: Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type
'java.nio.file.AccessDeniedException' was not included in the set of
types which can be serialized by this SerializationPolicy or its Class
object could not be loaded. For security purposes, this type will not
be serialized.: instance = java.nio.file.AccessDeniedException:
/luceneIndex
I am perplexed however, as the folder should be easily accessible to tomcat.
drwxrwxrwx 4 tomcat tomcat 4096 Mar 14 20:32 SearchTest
-rwxrwxrwx 1 tomcat tomcat 602 Mar 12 20:14 SearchTest.css
-rwxrwxrwx 1 tomcat tomcat 3038 Mar 13 23:13 SearchTest.html
drwxrwxrwx 5 tomcat tomcat 4096 Mar 14 20:24 WEB-INF
-rwxrwxrwx 1 tomcat tomcat 1082 Mar 12 20:14 favicon.ico
drwxrwxrwx 2 tomcat tomcat 4096 Mar 14 20:24 luceneFiles
drwxrwxrwx 2 tomcat tomcat 4096 Mar 14 20:24 luceneIndex
What could be causing this issue?
Are you using 'java.nio.file.AccessDeniedException' in your client-side code? The GWT compiler translates all the client-side Java code into JavaScript. Since not all Java functionalities are available in a web browser, GWT only supports a subset of the Java runtime library.
You can take a look at these two page JRE Compatablity and JRE Emulation.
As far as I can tell, none of the classes within java.nio package are emulated. That might be the reason you got your error.
Related
I work on a very old system : OSGi Framework with Jetty.
Java command is launch inside a screen with -DmS parameters.
At the end, console give me this :
osgi> Sep 14, 2021 9:17:43 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
Sep 14, 2021 9:28:32 AM org.mortbay.util.Container start
INFO: Started org.eclipse.equinox.http.jetty.internal.Servlet25Handler#90832e
Sep 14, 2021 9:28:32 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
Sep 14, 2021 9:28:32 AM org.mortbay.util.FileResource <clinit>
INFO: Checking Resource aliases
Sep 14, 2021 9:28:33 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:[port]
Sep 14, 2021 9:28:33 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer#142bece
Experimental: JNI_OnLoad called.
And :
ss
Framework is launched.
id State Bundle
0 ACTIVE org.eclipse.osgi_3.4.2.R34x_v20080826-1230
1 ACTIVE javax.servlet_2.4.0.v200806031604
2 ACTIVE org.apache.commons.logging_1.1.1.v20080605-1935
3 ACTIVE org.eclipse.equinox.http.jetty_1.1.0.v20080425
4 ACTIVE org.eclipse.equinox.http.servlet_1.0.100.v20080427-0830
5 ACTIVE org.eclipse.osgi.services_3.1.200.v20071203
6 ACTIVE org.mortbay.jetty_5.1.14.v200806031611
7 ACTIVE org.apache.log4j_1.2.13.v200806030600
Fragments=14
8 ACTIVE Jamod_0.0.0
9 ACTIVE org.openscada.opc.dcom_0.5.0
10 ACTIVE Comm Linux RXTX Bundle_0.0.0
11 ACTIVE org.apache.commons.io_1.4.0
12 ACTIVE org.apache.commons.fileupload_1.2.1
13 ACTIVE org.apache.commons.lang3_3.1.0
14 RESOLVED InterpreterLog4JProperties_0.0.0
Master=7
15 ACTIVE EmailManager_1.0.0
16 ACTIVE Interpreter_1.0.0
17 ACTIVE InterpreterServlet_1.0.0
But during 10 minutes, I have only this :
osgi> Sep 14, 2021 10:16:06 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
ss
Framework is launched.
id State Bundle
0 ACTIVE org.eclipse.osgi_3.4.2.R34x_v20080826-1230
1 ACTIVE javax.servlet_2.4.0.v200806031604
2 ACTIVE org.apache.commons.logging_1.1.1.v20080605-1935
3 STARTING org.eclipse.equinox.http.jetty_1.1.0.v20080425
4 RESOLVED org.eclipse.equinox.http.servlet_1.0.100.v20080427-0830
5 RESOLVED org.eclipse.osgi.services_3.1.200.v20071203
6 RESOLVED org.mortbay.jetty_5.1.14.v200806031611
7 RESOLVED org.apache.log4j_1.2.13.v200806030600
Fragments=14
8 RESOLVED Jamod_0.0.0
9 RESOLVED org.openscada.opc.dcom_0.5.0
10 RESOLVED Comm Linux RXTX Bundle_0.0.0
11 RESOLVED org.apache.commons.io_1.4.0
12 RESOLVED org.apache.commons.fileupload_1.2.1
13 RESOLVED org.apache.commons.lang3_3.1.0
14 RESOLVED InterpreterLog4JProperties_0.0.0
Master=7
15 RESOLVED EmailManager_1.0.0
16 RESOLVED Interpreter_1.0.0
17 RESOLVED InterpreterServlet_1.0.0
I don't want to modify java code (too old, too long), I just want to start it correctly...
Finally someone have notice that if I plug a screen and a keyboard on this server, and log in, jetty start at once ?
(Whereas this doesn't work with ssh log in...?)
I think in my case, the simplest way (not perfect and clean I agree), would be to simulate a "real log in" (but I don't understand what is the difference between "real/local" log in and ssh log in).
Jetty 5.1.14 was EOL (End of Life) back in the year 2009 - https://www.eclipse.org/jetty/download.php#version-table
There has literally been over 1 million commits on Jetty over the past 12 years (I just checked)
For success with this old of a version of Jetty ...
You MUST run it with Java 1.4 (ONLY) and nothing newer. Newer JVMs have various things disabled that Jetty of that era require to run. (You could eke out Java 1.5, but only if you have SSL/TLS disabled, and don't use that specific version of OSGi, which only supported Java 1.2)
You MUST run it on an OS that wasn't upgraded in the past 12 years. Newer OSs have updated to support the feature-set of newer JVMs and dropped support for the quirks of older JVMs and will not run older JVMs reliably.
You MUST NOT use SSL (it's impossible for you to use it now). SSL/TLS has evolved extremely rapidly since 2009, and you have a featureset in the Java 1.4 JVM that is 100% not supported on modern web browsers. This means even if you turned it on, your modern browser has a minimum TLS 1.2 and a Cipher Suite that Java 1.4 doesn't even support on it's high end / non-export configurations.
So in short, you cannot upgrade Jetty (your choice), so you cannot upgrade the JVM (consequence of your first choice), and you cannot upgrade the OS (if you expect to run Java 1.4) for success.
If you have upgraded your JVM or your OS you have basically screwed yourself. I cannot even find a docker image with that old of a OS or JVM for you to limp along with.
I am trying to change the client_max_body_size property of my Elastic Beanstalk NGINX reverse-proxy in order to allow uploads for larger JPEG files. Therefore, I added the folder ".ebextensions" to the root directory of my WAR file (the WAR file is also including a Spring Boot application) and added a file ".ebextensions/01_files.config" with the following content:
files:
"/etc/nginx/conf.d/proxy.conf" :
mode: "000755"
owner: root
group: root
content: |
client_max_body_size 20M;
I deploy the WAR file via Travis-CI to Elastic Beanstalk. However, it seems that the file is beeing ignored by Elastic Beanstalk since uploads with a filesize e.g. 2MB do not work and when connecting with SSH to the instance and looking for "/etc/nginx/conf.d/proxy.conf" the file does not exist.
I already successfully validated above content with an YAML validator. I know, there exists plenty of related questions but non of those seem to fix my problem. I also checked if ".ebextensions/01_files.config" is included in the WAR file in root directory. And when I check "/tmp/eb_extracted_jar", the file ".ebextensions/01_files.config" also exists with the correct content. I can't even find any errors in the "/var/log/cfn-init.log". I noticed that, just for some seconds, the file "proxy.conf" appeared in "/etc/nginx/conf.d/" during deployment but then it has been removed.
Can this problem occure because of the deployment to Elastic Beanstalk via Travis-CI? Or did I miss something else that is important?
EDIT:
I just recognized that the "proxy.conf" file is created every time for a few seconds when the application is deployed but after a few seconds it disappears (checked with ls -lsa in "/etc/nginx/conf.d/", see the timestamps with 13:34 for "elasticbeanstalk" directory and "healthd_http.conf" and 13:43 for "proxy.conf")
4 drwxr-xr-x 3 root root 4096 6. Dec 13:43 .
4 drwxr-xr-x 4 root root 4096 6. Dec 13:34 ..
4 drwxr-xr-x 2 root root 4096 6. Dec 13:34 elasticbeanstalk
4 -rw-r--r-- 1 root root 148 6. Dec 13:34 healthd_http.conf
4 -rwxr-xr-x 1 root root 26 6. Dec 13:43 proxy.conf
And after a few seconds ls -lsa "/etc/nginx/conf.d/":
4 drwxr-xr-x 3 root root 4096 6. Dec 13:44 .
4 drwxr-xr-x 4 root root 4096 6. Dec 13:44 ..
4 drwxr-xr-x 2 root root 4096 6. Dec 13:44 elasticbeanstalk
4 -rw-r--r-- 1 root root 148 6. Dec 13:44 healthd_http.conf
After hours of reading docs, I found out that I missed some important parts of the official AWS docs for the Elastic Beanstalk Java SE Platform (see http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-platform.html).
Definitely my mistake: I used the wrong file extension, the file extension in the folder ".ebextensions" has to be ".conf" but not ".config".
At least for the Java SE Platform: one can directly add NGINX config files within the ".ebextensions" directory without using the "files: ..." syntax to generate a file with a specific content, i.e. to create the proxy file in "/etc/nginx/conf.d/proxy.conf" just add ".ebextension/nginx/conf.d/proxy.conf" with the content client_max_body_size 20M; directly. Subsequently, "proxy.conf" will then be deployed to "/etc/nginx/conf.d/proxy.conf" and automatically included by the default NGINX config.
Hope this answer saves someone else the time it took me to figure that out.
I'm deploying a war file (Thingworx Iot Software) on tomcat with elastic beanstalk. The software is trying to create some folders/files under Several folders (at server root) I've given tomcat permissions to write to.
drwxrwxr-x 3 tomcat tomcat 4096 Jan 12 22:41 ThingworxBackupStorage
drwxr-xr-x 2 tomcat tomcat 4096 Jan 13 20:47 ThingworxPlatform
drwxrwxr-x 9 tomcat tomcat 4096 Jan 12 22:41 ThingworxStorage
Heres the error I'm getting:
Caused by: java.io.IOException: THINGWORX WARNING: could not create directory: /ThingworxStorage/database
at com.thingworx.common.utils.PathUtilities.createPath(PathUtilities.java:39)
at com.thingworx.system.configuration.PlatformSettings.prepareLocation(PlatformSettings.java:302)
... 20 more
I'm running Java 8 and Tomcat 8 on an AWS EB setup.
Seams like it should just be a simple permissions thing, but from what I can tell I've already done all that properly. What am I missing?
I'm having an issue very strange in my enviroment wich is
jboss-5.1.0.GA
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
It was completely functional until I update a version of some jar (wich was tested in 6 enviroments before this one without the error) in the context.
before the error i had this files:
server/default/deploy/myfolder
-rw-r--r-- 1 jboss users 808430 May 16 17:29 s-c-core-2.38.6.0.jar
-rw-r--r-- 1 jboss users 555328 May 16 17:29 s-c-dao-2.38.6.0.jar
drwxr-xr-x 9 jboss users 4096 Jun 3 20:11 s-c-web.war
-rw-r--r-- 1 jboss users 199259 May 2 16:58 s-com-core-2.38.5.0.jar
-rw-r--r-- 1 jboss users 202086 May 2 16:58 s-com-dao-2.38.5.0.jar
-rw-r--r-- 1 jboss users 1333612 May 2 16:58 s-com-domain-2.38.5.0.jar
-rw-r--r-- 1 jboss users 86526 May 2 16:58 s-com-util-2.38.5.0.jar
-rw-r--r-- 1 jboss users 660621 May 11 13:01 s-fin-core-2.38.6.0.jar
-rw-r--r-- 1 jboss users 559292 May 11 13:01 s-fin-dao-2.38.6.0.jar
drwxr-xr-x 8 jboss users 4096 May 15 21:41 s-fin-web.war
-rw-r--r-- 1 jboss users 108444 May 7 07:29 s-geio-engine-2.38.5.0.jar
drwxr-xr-x 8 jboss users 4096 May 15 21:24 s-geio-web.war
-rw-r--r-- 1 jboss users 71975 Jun 14 2012 s-o-core-1.1.4.0.jar
-rw-r--r-- 1 jboss users 66516 Jun 14 2012 s-o-dao-1.1.4.0.jar
-rw-r--r-- 1 jboss users 53532 Jun 14 2012 s-o-domain-1.1.4.0.jar
-rw-r--r-- 1 jboss users 16347 Jun 14 2012 s-o-util-1.1.4.0.jar
drwxr-xr-x 5 jboss users 4096 Jun 14 2012 s-o-web.war
-rw-r--r-- 1 jboss users 54588 Apr 10 11:29 s-p-core-2.38.2.0.jar
-rw-r--r-- 1 jboss users 35784 Apr 10 11:29 s-p-dao-2.38.2.0.jar
drwxr-xr-x 8 jboss users 4096 Apr 10 19:20 s-p-web.war
-rw-r--r-- 1 jboss users 69140 Jun 14 2012 s-s-se-1.1.0.jar
-rw-r--r-- 1 jboss users 594214 May 13 13:36 s-ser-core-2.38.6.1.jar
-rw-r--r-- 1 jboss users 530903 May 13 13:36 s-ser-dao-2.38.6.1.jar
drwxr-xr-x 9 jboss users 4096 May 15 21:58 s-ser-web.war
drwxr-xr-x 6 jboss users 4096 May 28 08:27 s-te-me.war
-rw-r--r-- 1 jboss users 155639 May 15 22:06 s-uni-core-2.38.5.0.jar
-rw-r--r-- 1 jboss users 145944 May 15 22:05 s-uni-dao-2.38.5.0.jar
drwxr-xr-x 7 jboss users 4096 May 15 21:20 s-uni-web.war
then I stop my jboss (/etc/init.d/jbossd stop) and update just theese three files/folder (deleting the old ones and putting the new ones)
-rw-r--r-- 1 jboss users 808430 May 16 17:29 s-c-core-2.38.7.0.jar
-rw-r--r-- 1 jboss users 555328 May 16 17:29 s-c-dao-2.38.7.0.jar
drwxr-xr-x 9 jboss users 4096 Jun 3 20:11 s-c-web.war
after server start with the user root and with the command "/etc/init.d/jbossd start"
at some point the users start to use applications and on the log file server/default/log/server.log start to appear some strange errors like this:
2013-06-04 00:01:30,615 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] (http-0.0.0.0-80-3) Servlet.service() for servlet HtmlAdaptor threw exception
javax.management.InstanceNotFoundException: jboss.j2ee:jar=s-c-core-2.38.6.0.jar,name=ApCarBusinessImpl,service=EJB3 is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526)
at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:675)
at org.jboss.jmx.adaptor.control.Server.getMBeanData(Server.java:98)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$1.run(HtmlAdaptorServlet.java:357)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$1.run(HtmlAdaptorServlet.java:354)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.getMBeanData(HtmlAdaptorServlet.java:353)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.inspectMBean(HtmlAdaptorServlet.java:224)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:383)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Saying that the EJBs are not instantiated (lots of then)
but nothing happens to the user, the application keep working normally
So I start to verify if the file s-c-core-2.38.6.0.jar wasn't left behind in some folder inside my jboss and NO it didn't. So I start to think that is some kind of cache that the jboss was reading so I stop the service and delete the folders server/default/tmp and server/default/work and restart the server but the error keep going on the log.
My run.conf is with this configuration:
JAVA_OPTS="-DSB_BASE=$SB_BASE -Dmodulo.context.file=s-o-core-context.xml;s-com-core-context.xml;s-ser-core-context.xml;s-geio-core-context.xml;s-fin-core-context.xml;s-c-core-context.xml;s-uni-core-context.xml;s-p-core-context.xml -Xmx3072m -Xms768m -XX:MaxPermSize=256m -Xss1024k -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+UseConcMarkSweepGC -Djava.awt.headless=true"
I tried a lot of things like user permissions, folder permissions, memory configurations (xmx xms) and the error keep appearing in the log file.
When I came back to the files that I changed ( s-c--2.38.6.0 ) the application stop to show this error, so I obviously though that the erro is with that package then I applyed it on a mirror server and the error does'nt show up.
So I am without options right now. The application is working fine for the user but the error keep appearing in the log and this is very annoying.
Has someone here experienced something like this?
I've posted this question on community.jboss.org 2 days ago with no help:
Thanks in advance,
sorry about my english.
The error basically implies that JBoss was unable to find the service MBean in its tree. Do you see that service deployed in the jmx-console?
You are seeing the InstanceNotFoundException: jboss.j2ee:jar=s-c-core-2.38.6.0.jar,name=ApCarBusinessImpl,service=EJB3 is not registered because:
Some external service/tool/app or your own application is trying to invoke that particular service (name=ApCarBusinessImpl,service=EJB3). Since JBoss cant find it deployed anywhere (as a result of you updating the deployed JAR), it simply logs the message that it couldn't find the MBean that it was asked to invoke.
To resolve the issue you will need to find out who is making the request on the old service name (jboss.j2ee:jar=s-c-core-2.38.6.0.jar) and have it updated to point to the new service name. This should resolve seeing those exception log messages.
Edit by Jorge Campos:
As #Coolbeans said it was indeed a external service that was calling my beans started on JBoss. I found out that in the installed jboss was a security issue that was not properly configured (jmx-console). So, there was a worm that was making requests to a previosly installed beans in my application server (some kind of cache). After some digging inside the jboss installation I find this war iesvc.war which is a worm as stated in this thread
https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-security-threat-to-jboss-application-server
The worm is JAVA_JBOSSPY.A identified by a trend micro office scan.
So thank you for the answer #Coolbeans you were right it was a "Some external service/tool/app" as you said.
This is sometimes caused by the PU name. Try to change the PU name to another name, clean and build and deploy.
Regards
Let me start with what I use:
- ubuntu 11.04
- apache-tomcat-6.0.33
some details on my java:
adam#adam-1215N:~$ java -version
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1)
OpenJDK Server VM (build 20.0-b11, mixed mode)
adam#adam-1215N:~$ ll /usr/lib/jvm
total 84
drwxr-xr-x 3 root root 4096 2011-08-28 10:09 ./
drwxr-xr-x 229 root root 69632 2011-08-28 13:13 ../
lrwxrwxrwx 1 root root 14 2011-08-27 21:03 default-java -> java-6-openjdk/
lrwxrwxrwx 1 root root 14 2011-08-27 21:03 java-1.6.0-openjdk -> java-6-openjdk/
drwxr-xr-x 7 root root 4096 2011-08-27 21:11 java-6-openjdk/
-rw-r--r-- 1 root root 2164 2011-06-11 11:07 .java-6-openjdk.jinfo
How I deploy an application:
I build it using mvn clean install. Then I extract the content of created .war file and copy it to my directory in webapps in tomcat. It worked initially.
Now, the meritum:
Project that I try to deploy is quite simple. Everything worked until I wanted one method to return Set of objects. When building I got error that generics are not supported in java 1.3. I googled, and found that I need to add maven-compiler-plugin to my pom.xml pointing which java I want to use. So I added, pointing at 1.6. And here it comes:
Aug 28, 2011 6:25:50 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Reloading context [/myproject]
Aug 28, 2011 6:25:50 PM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Aug 28, 2011 6:25:50 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/myproject] startup failed due to previous errors
Now the bad news
I tried to return to initial maven configuration, deleted generics that made me use java 1.6 and problem still exists... I was messing with jdk, installing and removing different versions, that is why I gave you same details on what I have in the beginning.
Tomcat also gives one more warning, I thought it is irrelevant but I didn't see it before (or didn't notice) so I'm putting it here:
Aug 28, 2011 6:15:13 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
I'm confused and tired, after fighting with it almost 2 days. Any help appreciated.
Edit
I have found reason: I have changed name of class that was referenced in web.xml and "Refactor" tool in Eclipse didn't change it.
Leaving it here in case someone find it useful :)
I have looked up in logs/localhost.2011-08-28.log and found java.lang.ClassNotFoundException which led me to web.xml containing reference to class that I had renamed
I was getting this error when deploying a spring mvc app from eclipse. The maven build included all the dependent jars for spring under WEB-INF/lib and that worked fine when deployed to Tomcat. The eclipse Indigo export-war functionality was not exporting the dependent spring jars presumably because of the maven directory structure, even though it was in the build path and all the jars were displayed under the Libraries tag.