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!
Related
CF 2016 on windows10 with IIS
I've checked other threads on similar issues and they don't appear to apply.
My laptop has needed to be crash-started on a number of occasions recently due to the laptop not waking up from sleep mode. A couple of times ColdFusion 2016 didn't start automatically and needed to be manually started. Now, ColdFusion appears to be starting automatically, but now I'm getting an error:
HTTP Error 500.0 - The Security service is not available.
I'm afraid I have no idea where to start on this or even what additional information to provide. So, I would really appreciate any hints.
The remainder of the error has the following information:
Detailed Error Information:
Module: IsapiModule Notification: ExecuteRequestHandler
Handler: ISAPI-dll
Error Code: 0x00000000
Requested URL: http://zbay_sys:80/jakarta/isapi_redirect.dll
Physical Path : C:\ColdFusion2016\config\wsconfig\1\isapi_redirect.dll
Logon Method: Anonymous
Logon User : Anonymous
I really hope I don't have to re-install CF
Glad, that you are sorted.
The error message says, "The Security service is not available." Thus IIS is showing http based error 500. If the service is not starting, there could likely be a problem at ColdFusion end.
Please try the following, if you face the similar issue in future:–
Stop ColdFusion service (if not already)
Launch Command prompt as Administrator
Browse to cf_root\cfusion\bin and run the following
command coldfusion.exe -start console
Try to access the CF Admin, once the services are started.
In case it gives an error message, please share the same.
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.
What does "Pending Restart" mean? I have stopped and restarted my WebJob numerous times and that doesn't seem to fix it. Does it mean I have to restart my website? What caused my job to get in this state in the first place? Is there any way I can prevent this from happening in the future?
Usually, it means that the job fails to start (an exception?). Look in the jobs dashboard for logs.
Also, make sure that if the job is continuous, you actually have an infinite loop that keeps the process alive.
To add to Victor's answer, the continuous WebJob states are:
Initializing - The site was just started and the WebJob is doing it's initialization process.
Starting - The WebJob is starting up the process/script.
Running - The WebJob's process is running.
PendingRestart - The WebJob's process exited (for any good or bad reason) in less than 2 minutes since it started, for a continuous WebJob it's considered that something was probably not right with it (some exception during start-up probably as mentioned by Victor), at this point the system is waiting for 60 seconds before it'll restart the WebJob process (hence the name "pending restart").
Stopped - The WebJob was stopped (usually from the Azure portal) and is currently not running and will not be running until it is started again, best way to see this is as disabled.
Also, take a look at the webjob log, it should hold cue to what's been happening.
if the JOB is set to run continuously, once the process exits (say you are polling a queue and it's empty) the job shuts down and status changes to "pending restart". Azure Scheduler will typically restart the process in 60 seconds.
Try changing the target framework to .NET 4.5. This same issue was fixed for me when I changed the target framework from 4.6.1 to 4.5.
Had the same problem, found out that i need to keep my webjob alive, so I put a continous loop to keep it alive.
It means that application is failing after start. Check the App Service Application setting might have some problem. .. In my case i am passing date as a configuration and i entered wrong date like 20160431
This is just because Webjobs is failing or giving exception.
Make sure the Webjobs is continuous and you can check that in the log where it failing and can make the changes.
Process went down, waiting for 60 seconds
Status changed to Pending Restart
In my case, we got the deployment package prepared through the Visual Studio folder publish and deployed along with WebApp. Package created through 'Folder publish' lacked 'run.cmd' file in which command to invoke the console application (.exe) is available; this file is automatically created when we directly publish to Azure WebJob from Visual Studio.
After manually adding this to a package folder, the issue got fixed.
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)
I am running an application in WebSphere Portal Server 6.1 and WAS 7. In the native_stderr.log , I am getting the following error message :
<JNI GetStringCritical: buffer=0x000000004D810988>
<JNI ReleaseStringCritical: buffer=000000004D810988>
These messages fill up the log rapidly and the size of the log increases rapidly and grows up to 1 GB in about 5 minutes.
This does not seem to be related to our deployed application since even when the application is not in use the logs keep getting generated.
Can anyone please help me on this issue. Thanks in advance.
The messages are from -verbose:jni. Turn that off to remove the messages. From the admin console:
Servers > (Server Types) > WebSphere application servers > server1 > (Java and Process Management) > Process Definition > (Additional Properties) > Java Virtual Machine
There is an option "Verbose JNI". Alternatively, you have -verbose:jni specified manually in the "Generic JVM Arguments" argument.
You got to provide additional info besides this for folks to help.
What is the JNI Stuff that you have in your application?
Notice the call here - GetStringCritical() would likely be blocking GC on the JVM.
Try and turn off the JNI component of the application and see how your servers behave
Manglu
You can also turn this off in the config files:
(You will have to modify this path to your own setup)
../WAS-7.0/WebSphere/AppServer/profiles/AppSrv01/config/cells/localhostNode01Cell/nodes/localhostNode01/servers/server1/server.xml
Look for the tag, you will see it has there:
verboseModeClass="false"
verboseModeGarbageCollection="false"
verboseModeJNI="false"
etc