I have a setup with Titan 0.5.2 running with Rexster. When I use the rexster console to run some code on the Titan side and exception happens, I get only short message like:
==>An error occurred while processing the script for language [groovy]. All transactions across all graphs in the session have
been concluded with failure: java.util.concurrent.ExecutionException:
javax.script.ScriptException: javax.script.ScriptException:
groovy.lang.MissingPropertyException: No such property: a for class:
Script8
And no output from the script (that is produced with println or such) is visible. Is it possible to make the rexster console produce the exception backtraces (e.g. like Titan's gremlin console does) and see the output from the script?
You can't get much more out of Rexster Console. If you look at server logs for Rexster though, you should see a bit more output. Of course, I wouldn't expect the trace to tell you too much more in the specific case of a "No such property" type of error.
Related
I have setup the stormcrawler project using this medium story https://medium.com/analytics-vidhya/web-scraping-and-indexing-with-stormcrawler-and-elasticsearch-a105cb9c02ca, but when I tried to submit the es-injector.flux, then I recevied this error:
Exception in thread "main" java.lang.IllegalArgumentException: Couldn't find a suitable
constructor for class 'com.digitalpebble.stormcrawler.util.StringTabScheme' with
arguments '[DISCOVERED]'.
at org.apache.storm.flux.FluxBuilder.buildObject(FluxBuilder.java:358)
at org.apache.storm.flux.FluxBuilder.buildComponents(FluxBuilder.java:421)
at org.apache.storm.flux.FluxBuilder.buildTopology(FluxBuilder.java:101)
at org.apache.storm.flux.Flux.runCli(Flux.java:158)
at org.apache.storm.flux.Flux.main(Flux.java:103)
The command that I run is:
storm jar target/project-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --local es-
injector.flux
Can someone please tell me what does it mean and how can I get rid of this error?
The latest ES tutorial is probably a better starting point, I'd recommend that you use it instead.
I am learning Jmeter use id=2172797 appid=b6907d289e10d714a6e88b30761fae22
and now Unable to read data from uploaded .csv file getting error message like ; Response code: Non HTTP response code: java.net.URISyntaxException under Jmeter.
Added screen for your reference.
Please help me.
Thanks
Double check your ${id} and ${appid} variable values using Debug Sampler and View Results Tree listener combination, the error you're getting most probably indicates that both variables are not resolved into their values and $ is an illegal character in the HTTP Request URL Path
Check out How to Debug your Apache JMeter Script article to learn more about troubleshooting JMeter tests
While running UploadJars utility after giving all the parameters, utility is failing with following exception:
Logging configuration class "oracle.core.ojdl.logging.LoggingConfiguration" failed
java.lang.ClassNotFoundException: oracle.core.ojdl.logging.LoggingConfiguration
Error occurred in performing the operation:
Exception in thread "main" java.lang.NullPointerException
at oracle.iam.platformservice.utils.JarUploadUtility.main(JarUploadUtility.java:232)
Any help will be appreciated :)
We had the same problem.
We added
ORACLE_COMMON/modules/oracle.odl_11.1.1/ojdl.jar
(where ORACLE_COMMON is your oracle_common directory) to the start of our CLASSPATH and the error went away.
I think UploadJars.sh worked anyway, it was just writing out a problem with logging what it was doing.
btw, Note you might need to use UpdateJars.sh if an earlier version of the file already exists. You can check if the upload/update was successful by looking at the date in OIMHOME_JARS.UPDATED_ON.
Cassandra stopped.
when i restart Cassandra using "service cassandra start" or "service cassandra restart", i get the following error(from "/var/log/cassandra/system.log"):
ERROR [main] 2014-11-14 02:08:52,379 CommitLogReplayer.java (line 304) Unexpected error deserializing mutation; saved to /tmp/mutation3145492124947244713dat and ignored. This may be caused by replaying a mutation against a table with the same name but incompatible schema. Exception follows:
org.apache.cassandra.serializers.MarshalException: Expected 8 or 0 byte long for date (7)
at org.apache.cassandra.serializers.TimestampSerializer.validate(TimestampSerializer.java:118)
at org.apache.cassandra.db.marshal.AbstractType.validate(AbstractType.java:171)
at org.apache.cassandra.db.marshal.AbstractType.validateCollectionMember(AbstractType.java:289)
at org.apache.cassandra.db.marshal.AbstractCompositeType.validate(AbstractCompositeType.java:282)
at org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:274)
at org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:95)
at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:151)
at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:131)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:336)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
now i cannot start cassandra.
cqlsh is also not available.
I also encounter this problem. I'd like to share how I resolve the problem.
Change the debug mode
The default debug mode is INFO, the output is too less to track the error. You should change the debug mode from INFO to DEBUG. This is is determined by the following line in the log4j-server.properties file:
log4j.rootLogger=INFO,stdout,R
rerun the cassandra
From the output, I find the error appears when replay the commit log file. I think there are something wrong in the log file. But the log file is binary, I don't know how to read it. So I try to delete the log file that results in the error, then restart cassandra. And it works!
Maybe the root problem is different from mine, but you can try to find it in this way. Hope this can help.
I am trying to track down a problem with GWT. I get an error which I want to track down to the source but log4j truncates the stacktrace by indicating something like "... 26 more" hence I cannot determine the exact location for the problem. I tried finding out if there is anyway to prevent that truncation but have been unable to find any option that will accomplish that. Is this truncation a configurable feature?
I am running Tomcat 6.0.31, Spring 3.0 (for backend), GWT 2.1.0.
Thanks
It isn't log4j truncating the stack trace, it's standard Java. And it's actually only making the trace more readable because those lines that were omitted were already output by the 'enclosing' exception. See Throwable javadoc.