I am trying to use EmbeddedCassandraService to instantiate a Cassandra server in my unit tests. But I am getting this error. Any idea what can be causing this?
ERROR org.apache.cassandra.config.DatabaseDescriptor - Fatal error:
null; Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=No
single argument constructor found for class
org.apache.cassandra.config.Config Bad configuration; unable to start
server
I used a configuration which is working in a standalone installation.
This thread and bug report from the Cassandra users mailing list may help, as it reports the same error message - what version of Cassandra are you using? (The bug report is against 0.7 beta 2)
Related
I think this will only be relevant to people who have also tried installing Sitecore so I’m not going to write every step of the process.
After running the ./up.ps1 command, I get this error message shown in the image
sitecore error message
The 2nd error can’t be correct because I am logged into docker so it could only be the first error of “The virtual machine could not be started because a required feature is not installed”
Any ideas as to what’s causing this error?
I was following the instructions given by sitecore and was expecting their sitecore environment to start running
I downloaded the installation pack for TestLink from SourceForge, and I attempted to install it on the server.
When the installation is trying to connect to the database, I get this message:
TestLink setup will now attempt to setup the database:
Creating connection to Database Server:OK!
Connecting to database `testlink`:OK!
==============================================================================
DB Access Error - debug_print_backtrace() OUTPUT START
ATTENTION: Enabling more debug info will produce path disclosure weakness (CWE-200)
Having this additional Information could be useful for reporting
issue to development TEAM.
==============================================================================
#0 database->exec_query() called at [/home/galigeo/testlink/install/installUtils.php:100]
#1 getUserList() called at [/home/galigeo/testlink/install/installUtils.php:267]
#2 create_user_for_db() called at [/home/galigeo/testlink/install/installNewDB.php:420]
Does anybody know how I should proceed from here?
We also tried to download another pack for 1.9.20 from Github, however that one is also stalling.
I got the problem like you and fixed like this:
Access link like https://yourtestlink.com/install
Done anything in these step.
I get the following error:Service Invocation Exeption i am working with Version 8.7 IBM InfoSphere DataStage and QualityStage Designer and using a server job and there, i have 1 sequential file, web service, sequential file.
Any idea what could be the reason of this error ?
Make sure you have chosen proper DataStage job type and your stage that operates on web service is configured properly.
You should also check the DataStage logs to get more information about root cause of the error.
I have download WSO2 MB 2.1.0 and run it with the built-in Cassandra server in Windows 7 64bit.
But the start-up procedure failed with the following error message.
[2013-12-14 11:27:03,371] ERROR {org.apache.cassandra.service.AbstractCassandraD
aemon} -
Exception in thread Thread[Thread-21,5,main]
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:713)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1371)
at org.apache.cassandra.thrift.CustomTThreadPoolServer.serve(CustomTThre
adPoolServer.java:103)
at org.apache.cassandra.thrift.CassandraDaemon$ThriftServer.run(Cassandr
aDaemon.java:213)
[2013-12-14 11:27:03,396] INFO {me.prettyprint.cassandra.service.JmxMonitor} -
Registering JMX me.prettyprint.cassandra.service_ClusterOne:ServiceType=hector,
MonitorType=hector
I found a related bug issue: https://wso2.org/jira/browse/MB-210
Does anyone know if the next release will really fix this bug?
Or I have to use standalone deployment with external Cassandra server as this suggestion?
http://udarakr.blogspot.tw/2013/09/how-to-overcome-wso2-message-broker.html
This issue is something to do with Cassandra,In Linux i faced the same issue and once i increased the max user processes Everything went fine, Please refer the article written on this topic Unable to create new native thread and max user processes. Since this issue is occurring in Windows, Better to Run Cassandra externally and fine tune the Cassandra on it!
I'm trying to develop a system service, so I use the echo service as a test.
I developed the service by following the directions on the CF doc.
Now the echo node can be running, but the echo gateway failed with the error "echo_gateway - pid=15040 tid=9321 fid=290e ERROR -- Exiting due to NATS error: Could not connect to server on nats://localhost:4222/"
I got into this issue and struck for almost a week finally someone helped me to resolve it. The underlying problemn is something else and since errors are not trapped properly it gives a wrong message. You need to goto github and get the latest code base. The fix for this issue is http://reviews.cloudfoundry.org/#/c/8891 . Once you fix this issue, you will most likely encounter a timeout field issue. the solution for that is to define the timeout field gateway.yml
A few additional properties became required in the echo_gateway.yml.erb file - specifically, the latest were default_plan and timeout, under the service group. The properties have been added to the appropriate file in the vcap-services-sample-release repo.
Looks like the fix for the misleading error has been merged into github. I haven't updated and verified this myself just yet but the gerrit comments indicate the solution is the same as what the node base has had for some time. I did previously run into that error handling and it was far more helpful.