wiremock standalone server not starting using --print-all-network-traffic - wiremock

I am trying to run wiremock stand along server using command .
java -jar wiremock-1.57-standalone.jar --port=9090 --verbose --print-all-network-traffic
But it always give me exception .
Exception in thread "main"
Exception: java.util.MissingResourceException thrown from the
UncaughtExceptionHandler in thread "main"
But after removing network command it starts fine.
Could you pleas help me with this.
Thanks

It was issue of old versions i updated jar file from 1.5 to 2.6

Related

Skyve on Wildfly wont restart with StateTransitionException

On restart of Wildfly I get the following error:
java.lang.RuntimeException: org.ehcache.StateTransitionException: Persistence directory already locked by this process: C:\bizhub\workspace\content\SKYVE_CACHE
Shutdown Wildfly if it is running, in the directory named in the exception (in this case C:\bizhub\workspace\content\SKYVE_CACHE) there will be a file called .lock, if this file is removed and wildfly is restarted this should resolve the issue.

Getting following error in console while solr connection to Mongo . No error in solr log

Exception in thread "Thread-14" java.lang.NoSuchMethodError: com.mongodb.ReadPreference.secondaryPreferred()Lcom/mongodb/ReadPreference;
at org.apache.solr.handler.dataimport.MongoDataSource.init(MongoDataSource.java:51)
at org.apache.solr.handler.dataimport.DataImporter.getDataSourceInstance(DataImporter.java:397)
at org.apache.solr.handler.dataimport.ContextImpl.getDataSource(ContextImpl.java:100)
at org.apache.solr.handler.dataimport.MongoEntityProcessor.init(MongoEntityProcessor.java:33)
at org.apache.solr.handler.dataimport.EntityProcessorWrapper.init(EntityProcessorWrapper.java:77)
at org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:434)
at org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:415)
at org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:330)
at org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:233)
at org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:424)
at org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:483)
at org.apache.solr.handler.dataimport.DataImporter.lambda$runAsync$0(DataImporter.java:466)
at java.lang.Thread.run(Thread.java:745)
There are jar files interdependent (though I took all latest was not compatible). Finally the combination worked is listed below.
solr-dataimporthandler-8.3.0.jar
solr-mongo-importer-1.0.0.jar
mongo-java-driver-2.13.2.jar
It was frustrating.

org.neo4j.kernel.lifecycle.LifecycleException in Neo4j

I've been using neo4j 1.9 RC1 for the past two months. Yesterday, after an eclipse crash I started having this this exception:
Exception in thread "main" java.lang.RuntimeException: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.TxManager#bf5743' was successfully initialized, but failed to start. Please see attached cause exception.
at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:282)
at org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:90)
at org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:75)
at org.neo4j.kernel.EmbeddedGraphDatabase.<init>(EmbeddedGraphDatabase.java:60)
at fr.inria.atlanmod.neo4emf.drivers.impl.PersistenceService.<init>(PersistenceService.java:44)
at fr.inria.atlanmod.neo4emf.drivers.impl.PersistenceServiceFactory.createPersistenceService(PersistenceServiceFactory.java:27)
at fr.inria.atlanmod.neo4emf.drivers.impl.PersistenceManager.<init>(PersistenceManager.java:80)
at fr.inria.atlanmod.neo4emf.impl.Neo4emfResource.<init>(Neo4emfResource.java:58)
at fr.inria.atlanmod.neo4emf.impl.Neo4emfResourceFactory.createResource(Neo4emfResourceFactory.java:58)
at main.JDTASTMain.main(JDTASTMain.java:35)
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.TxManager#bf5743' 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:260)
... 9 more
Caused by: org.neo4j.graphdb.TransactionFailureException: Unable to start TM, no active tx log file found but found either tm_tx_log.1 or tm_tx_log.2 file, please set one of them as active or remove them.
at org.neo4j.kernel.impl.transaction.TxManager.openLog(TxManager.java:738)
at org.neo4j.kernel.impl.transaction.TxManager.start(TxManager.java:138)
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:491)
... 11 more
I am running it with Java 1.7. Any ideas?
It seems that your data directory is corrupt. There is already a suggestion printed to the log to fix that issue:
Unable to start TM, no active tx log file found but found either
tm_tx_log.1 or tm_tx_log.2 file, please set one of them as active or
remove them.

Unable to start Eclipse RSE Server, java.lang.NullPointerException

I have the problem with Eclipse RSE Server. I'm unable to start it on CentOS 6.4 (AMD64). This is the error messages.
Exception in thread "main" java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:542)
at java.util.Properties.setProperty(Properties.java:161)
at java.lang.System.setProperty(System.java:786)
at org.eclipse.dstore.internal.core.server.ServerAttributes.getHostName(ServerAttributes.java:97)
at org.eclipse.dstore.core.server.ServerLauncher.init(ServerLauncher.java:643)
at org.eclipse.dstore.core.server.ServerLauncher.<init>(ServerLauncher.java:486)
at org.eclipse.dstore.core.server.ServerLauncher.main(ServerLauncher.java:779)
I'm using daemon.pl with the root user. Tried server.pl. but, the same error occurred.
Thanks for advance.
I just came across the same problem and it was solved after adding my server name to the /etc/hosts file with loopback IP.

jena ExceptionInInitializerError

i'm jena newbie and I have this error:
Exception in thread "AWT-EventQueue-0" java.lang.ExceptionInInitializerError
at com.hp.hpl.jena.rdf.model.impl.RDFReaderFImpl.<clinit>(RDFReaderFImpl.java:74)
at com.hp.hpl.jena.rdf.model.impl.ModelCom.<clinit>(ModelCom.java:54)
at com.hp.hpl.jena.rdf.model.ModelFactory.createDefaultModel(ModelFactory.java:142)
at com.hp.hpl.jena.rdf.model.ModelFactory.createDefaultModel(ModelFactory.java:136)
at com.hp.hpl.jena.vocabulary.OWL.<clinit>(OWL.java:37)
at com.hp.hpl.jena.ontology.ProfileRegistry.<clinit>(ProfileRegistry.java:47)
at com.hp.hpl.jena.ontology.OntModelSpec.<clinit>(OntModelSpec.java:53)
at myprogram.Connection.<init>(Connection.java:46)
Where the code part that jumps into this exception is this (Connection.java:46):
m = ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM, null );
The userlibrary I defined contains:
commons-codec-1.5.jar
httpclient-4.1.2.jar
httpcore-4.1.3.jar
jcl-over-slf4j-1.6.4
jena-arq-2.9.4.jar
jena-core-2.7.4.jar
jena-iri-0.9.4.jar
jena-tdb-0.9.4.jar
log4j-1.2-16.jar
slf4j-api-1.7.2.jar
slf4j-log4j12-1.6.4.jar
xercesimpl-2.10.0.jar
xml-apis-1.4.01.jar
Java version is jdk1.7.0_11
Anyone can help me?
AWT-EventQueue-0 -- what environment are you running in?
One possibility is that there is another version of Jena around because stacktrace does not quite align with the 2.7.4 codebase.