Eclipse + Tomcat 7 + Audit Trial DataSource - Server Failed to start - java

I want to create stardust application.
When I configure tomcat server and Audit Trial DataSource (using documentation http://help.eclipse.org/luna/topic/org.eclipse.stardust.docs.wst/html/wst-integration/configuration.html?cp=60_7_4_2) and start server I get:
lis 20, 2014 10:15:54 PM org.apache.tomcat.util.digester.Digester startElement
SEVERE: Begin event threw exception
java.lang.ClassNotFoundException: org.eclipse.stardust.ide.wst.server.tomcat.EmbeddedDerbyLifecycleListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:360)...
I use Eclipse Luna, Tomcat 7, java 8 and ArchLinux.
I've installed all Eclipse Process Manager plugins.
What could cause that problem ?

I switched from java 8 to java 7 and now it works.

Related

Sonar Runner execution error on IssueListener?

I have a job that I run on a monthly basis at this time. Lately, I'm encounting an Issue that I don't get when running sonar-runner (version 2.5.1):
INFO: Scanner configuration file:
/var/lib/jenkins/tools/hudson.plugins.sonar.SonarRunnerInstallation/SonarQube_Scanner_2.5.1/conf/sonar-runner.properties
INFO: Project configuration file:
/var/lib/jenkins/workspace/tpk-extra-package/tpx-extra-tools/tpk-extra-tools_build/sonar-project.properties
INFO: SonarQube Scanner 2.5.1 INFO: Java 1.8.0_121 Oracle Corporation
(64-bit) INFO: Linux 4.4.0-98-generic amd64 INFO: Error stacktraces
are turned on. INFO: User cache: /var/lib/jenkins/.sonar/cache
Exception in thread "main" java.lang.NoClassDefFoundError:
org/sonar/batch/bootstrapper/IssueListener at
org.sonar.runner.batch.DefaultBatchFactory.createBatch(DefaultBatchFactory.java:44)
at
org.sonar.runner.batch.BatchIsolatedLauncher.start(BatchIsolatedLauncher.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.sonar.runner.impl.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:61)
at com.sun.proxy.$Proxy0.start(Unknown Source) at
org.sonar.runner.api.EmbeddedRunner.doStart(EmbeddedRunner.java:251)
at org.sonar.runner.api.EmbeddedRunner.start(EmbeddedRunner.java:187)
at org.sonar.runner.api.EmbeddedRunner.start(EmbeddedRunner.java:182)
at org.sonarsource.scanner.cli.Main.execute(Main.java:76) at
org.sonarsource.scanner.cli.Main.main(Main.java:66) Caused by:
java.lang.ClassNotFoundException:
org.sonar.batch.bootstrapper.IssueListener at
java.net.URLClassLoader.findClass(URLClassLoader.java:381) at
org.sonar.runner.impl.IsolatedClassloader.loadClass(IsolatedClassloader.java:82)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
The host where I run this command did not change over the last month (since the last successful run): same kernel, same java 1.8 version, ...
I've checked using strace/ltrace but couldn't find what is the issue.
I try to run the same sonar-runner on a different system (another linux distro with different kernel and java - but yet 1.8), still the same stacktrace.
Do you have any idea ?
Thanks for your help.

Trying to run the RSA SDK under Tomcat 8

Java newbie here.
Working on a some java App that uses the RSA SDK 8.2. All applications work fine when run as a console application. We're need to put a Web front end on it but we error out as shows below.
We've tried running it on both Wildfly 10 and Tomcat 8.0. Using Java 1.8
Below is error received when running on Tomcat. The error of NoSuchMethodException below from org.glassfish.tyrus.server.TyrusServerConfiguration.()
This exists in one of the Jars provided in the SDK. If we remove the jar Tomcat will serve up the page but will fail when a call to the SDK is made. If we include the jar, we get the error below.
SEVERE: Error during ServletContainerInitializer processing<br>
javax.servlet.ServletException: java.lang.InstantiationException: org.glassfish.tyrus.server.TyrusServerConfiguration<br>
at org.apache.tomcat.websocket.server.WsSci.onStartup(WsSci.java:88)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5303)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.InstantiationException: org.glassfish.tyrus.server.TyrusServerConfiguration
at java.lang.Class.newInstance(Class.java:427)
at org.apache.tomcat.websocket.server.WsSci.onStartup(WsSci.java:74)
... 8 more
Caused by: java.lang.NoSuchMethodException: org.glassfish.tyrus.server.TyrusServerConfiguration.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at java.lang.Class.newInstance(Class.java:412)
... 9 more
Sep 26, 2017 3:00:39 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/tomcattest3] startup failed due to previous errors
I was able to duplicate this problem using Tomcat 9. I added websocket-ri-bundle-1.1.jar to Tomcat's lib without realizing that it already contained websocket-api-jar. When I removed the ri bundle I no longer got the error.

How to solve GRAVE: Unable to process Jar entry

On every server startup I get the following error:
GRAVE: Unable to process Jar entry
Mai 15, 2017 10:39:31 AM org.apache.catalina.startup.ContextConfig processAnnotationsJar
GRAVE: Unable to process Jar entry [fr/package/model/someClass.class] from Jar [jar:file:/C:/Folder-dev/work/eclipse/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/web/WEB-INF/lib/package-model-0.0.1-SNAPSHOT.jar!/] for annotations
java.io.EOFException
This was a well known error that was caused by some incompatibility issues between TOMCAT 7 & JDK <= 6.
In my case I'm working with this configurations:
Server number: 8.0.9.0
Server version: Apache Tomcat/8.0.9
Architecture: amd64
JVM Version: 1.8.0_131-b11
Can anyone help me to solve this issue ?
I upgraded to tomcat 8.5 and everything works fine.

How can I changed tomcat app server to version 8 with jdk 1.7 and spring 3.0.4?

My project used tomcat 7 ,jdk 1.6 and spring 3.0.4. I changed tomcat version to 8, jdk to 1.7. It works perfectly in Luna IDE with tomcat installer.(Of course I changed servlet.jar to javax.servlet-api-3.1.0.jar because of an error)
My project is running perfectly with the tomcat8 (binary version) for windows, but the war file is not running with tomcat 8 (linux binary version) at linux server and its error is:
Jun 14, 2015 5:32:47 PM org.apache.catalina.core.StandardContext
listenerStart SEVERE: Exception sending context initialized event to
listener instance of class utils.SysParams
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Failed to import bean definitions from relative
location [hibernate-beans.xml] Offending resource: ServletContext
resource [/WEB-INF/applicationContext.xml]; nested exception is
org.springframework.beans.factory.BeanDefinitionStoreException:
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/hibernate-beans.xml]; nested exception is
java.lang.NoSuchMethodError:
org.springframework.beans.MutablePropertyValues.add(Ljava/lang/String;Ljava/lang/Object;)Lorg/springframework/beans/MutablePropertyValues;
Its a Spring 3.0 method which should work in your case as it works on localhost. I guess your linux tomcat has pre-3.0 Spring versions somewhere in classpath- which could be from this project or legacy project. On linux tomcat check your classpath, search for spring 2* jars and try deleting work/temp folders..

Neo4j Server Startup Exception

Iam unable to start the neo4j server..iam using java 1.7 and neo4j 2.0.0 when i run the sample java with maven example, iam getting this problem. Here is the log file
Oct 09, 2013 8:49:14 AM org.neo4j.server.logging.Logger log
INFO: Setting startup timeout to: 120000ms based on -1
Oct 09, 2013 8:49:15 AM org.neo4j.server.logging.Logger log
SEVERE:
org.neo4j.server.ServerStartupException: Starting Neo4j Server failed: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.XaDataSourceManager#ce8273' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:211)
at org.neo4j.server.Bootstrapper.start(Bootstrapper.java:86)
at org.neo4j.server.Bootstrapper.main(Bootstrapper.java:49)
Caused by: java.lang.RuntimeException: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.XaDataSourceManager#ce8273' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:280)
at org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:106)
at org.neo4j.graphdb.factory.GraphDatabaseFactory$1.newDatabase(GraphDatabaseFactory.java:88)
at org.neo4j.graphdb.factory.GraphDatabaseBuilder.newGraphDatabase(GraphDatabaseBuilder.java:207)
at org.neo4j.kernel.impl.recovery.StoreRecoverer.recover(StoreRecoverer.java:114)
at org.neo4j.server.preflight.PerformRecoveryIfNecessary.run(PerformRecoveryIfNecessary.java:59)
at org.neo4j.server.preflight.PreFlightTasks.run(PreFlightTasks.java:70)
at org.neo4j.server.AbstractNeoServer.runPreflightTasks(AbstractNeoServer.java:276)
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:162)
... 2 more
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.XaDataSourceManager#ce8273' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:497)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:104)
at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:258)
... 10 more
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.nioneo.xa.NeoStoreXaDataSource#1f5329f' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:497)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:104)
at org.neo4j.kernel.impl.transaction.XaDataSourceManager.start(XaDataSourceManager.java:128)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:491)
... 12 more
Caused by: org.neo4j.kernel.impl.storemigration.UpgradeNotAllowedByConfigurationException: Failed to start Neo4j with an older data store version. To enable automatic upgrade, please set configuration parameter "allow_store_upgrade=true"
at org.neo4j.kernel.impl.storemigration.ConfigMapUpgradeConfiguration.checkConfigurationAllowsAutomaticUpgrade(ConfigMapUpgradeConfiguration.java:39)
at org.neo4j.kernel.impl.storemigration.StoreUpgrader.attemptUpgrade(StoreUpgrader.java:66)
at org.neo4j.kernel.impl.nioneo.store.StoreFactory.tryToUpgradeStores(StoreFactory.java:113)
at org.neo4j.kernel.impl.nioneo.store.StoreFactory.newNeoStore(StoreFactory.java:96)
at org.neo4j.kernel.impl.nioneo.xa.NeoStoreXaDataSource.start(NeoStoreXaDataSource.java:240)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:491)
... 15 more
Oct 09, 2013 8:49:15 AM org.neo4j.server.logging.Logger log
SEVERE: Failed to start Neo Server on port [7474]
How to clear this?
According to the documentation,
set the Neo4j configuration parameter "allow_store_upgrade=true" in your neo4j.properties or embedded configuration
Hope that helps.
In general with Neo4j, a database can be upgraded from a minor version to the next, e.g. 1.7 → 1.8, and 1.8 → 1.9, but you can not jump directly from 1.7 → 2.0.
You have two options:
upgrade to each minor version in succession setting the Neo4j configuration parameter "allow_store_upgrade=true" as in #Vidya's answer, or
re-import your data into the new 2.0 version of Neo4j.

Categories

Resources