Openfire Error: "...rejected from java.util.concurrent.ThreadPoolExecutor..." - openfire

I Just installed Openfire 3.9.3 (Ubuntu 12.04), and it works great in Pidgin, but when trying to log in via the Candy client, it fails and firebug returns the following:
500 Task
org.jivesoftware.openfire.http.HttpSessionManager$HttpPacketSender#58b901
rejected from
java.util.concurrent.ThreadPoolExecutor#8aeebf[Terminated, pool size =
0, active threads = 0, queued tasks = 0, completed tasks = 0]
The only attempt at a solution I could find is at:
openfire error when try to connect via http-bind
I logged into hxxp://127.0.0.1:9090/server-properties.jsp , but there were no xmpp.httpbind.worker.threads or xmpp.client.processing properties listed. So I added both and assigned each a value of 16. Then restarted the openfire service. But there was absolutely no change.
openfire warning log:
java.util.concurrent.RejectedExecutionException: Task org.jivesoftware.openfire.http.HttpSessionManager$HttpPacketSender#3ea82c
rejected from
java.util.concurrent.ThreadPoolExecutor#8aeebf[Terminated, pool size =
0, active threads = 0, queued tasks = 0, completed tasks = 0]
Any suggestions please?

Related

Azure Redis Cache Service Timeout Issue

I am running the application in load balancer and using shared Azure Redis Cache service with connection pool of 50, but I am getting following timeout exception very frequently, Anyone please guide me what to do:
RedisTimeoutException
Timeout performing EXISTS (60000ms), next: GET vstfs:///Classification/TeamProject/b81283a0-baf4-46df-a616-fbdd9d387034##CheckOutFiles, inst: 6, qu: 0, qs: 0, aw: False, bw: Inactive, rs: ReadAsync, ws: Idle, in: 0, serverEndpoint: mr4devops.redis.cache.windows.net:6380, mc: 1/1/0, mgr: 10 of 10 available, clientName: inteGREAT.Web.UI.v2_IN_1(SE.Redis-v2.6.66.47313), IOCP: (Busy=0,Free=1000,Min=4,Max=1000), WORKER: (Busy=151,Free=32616,Min=4,Max=32767), v: 2.6.66.47313 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)   
at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor`1 processor, ServerEndPoint server, T defaultValue) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 1867   
at StackExchange.Redis.RedisDatabase.KeyExists(RedisKey key, CommandFlags flags) in /_/src/StackExchange.Redis/RedisDatabase.cs:line 811
As per my understanding you are facing a time out error when running application in load balancer using shared Azure Redis Cache with connection pool of 50.
The answer is in that link included in the exception message. The number of busy worker threads is greater than the min, so you will need to increase the min.
Hope that helps

Websphere application server LDAP connection pool

We are using websphere application server 8.5.0.0. we have a requirement where we have to query a LDAP server to get the customer details. I tried to configure the connection pool as described here and here.
I passed the below JVM arguments
-Dcom.sun.jndi.ldap.connect.pool.maxsize=5
-Dcom.sun.jndi.ldap.connect.pool.timeout=60000
-Dcom.sun.jndi.ldap.connect.pool.debug=all
Below is a sample code snippet
Hashtable<String,String> env = new Hashtable<String,String>();
...
...
env.put("com.sun.jndi.ldap.connect.pool", "true");
env.put("com.sun.jndi.ldap.connect.timeout", "5000");
InitialDirContext c = new InitialDirContext(env);
...
...
c.close();
I have two issues here
When I am calling the service for the 6th time, I am getting javax.naming.ConnectionException: Timeout exceeded while waiting for a connection: 5000ms. I checked the connection pool debug logs and I noticed the connections are not returning back to the pool immediately despite closing the context safely in a finally block. The connections are released after some time and expired after sometime after the release. There after if I call the service again, it connects to the LDAP server but new connections are being created.
I tried to execute the code and I am able to see the connection pool debug logs. But the logs are being logged in System.Err log. Is this an issue? Can I ignore it?
But when I run the code as a standalone application(multithreaded with loop of 50 times), the connections are returned/released immediately.
Can anyone please let me know what am I doing wrong?

How should I investigate a cause of crash on Bluemix?

I got the following error messages when I pushed an app of Liberty for Java into Bluemix.
[Console]
an instance of the app crashed: failed to start exit status: -1, CRASHED
[cf events APPNAME]
index: 1, reason: CRASHED, exit_description: failed to start, exit_status: -1
index: 2, reason: CRASHED, exit_description: failed to start, exit_status: -1
a) Is there exit status code list? I can not find it.
b) This error, exit status = -1, sometimes occurred. What is it? How should I investigate this cause?
On bluemix, you can use cf logs appName command to investigate the logs.
You can also use Monitoring and analytics for investigating the logs.
Read this article to get an idea of logging mechanism on bluemix -
https://www.ibm.com/blogs/bluemix/2014/10/accessing-application-logs-bluemix/
Try cf events appname to see if there's any more crash related info. Ensure that you deployed the app with enough memory, as insufficient memory will cause a crash on startup.

unknown SSL error -12218 (SSL_ENCRYPTION_FAILURE) while launching upwork application on debian stretch

Recently I've been installing upwork application on my debian system.It has installed fine.But when I try to launch it from cli typing: upwork
a bunch of errors happen.
[1008/213534:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[1008/213535:ERROR:renderer_main.cc(200)] Running without renderer sandbox
[1008/213542:ERROR:renderer_main.cc(200)] Running without renderer sandbox
[1008/213542:WARNING:channel.cc(549)] Failed to send message to ack remove remote endpoint (local ID 1, remote ID 1)
[1008/213542:WARNING:channel.cc(549)] Failed to send message to ack remove remote endpoint (local ID 2147483648, remote ID 2)
[1008/213542:ERROR:channel.cc(300)] RawChannel read error (connection broken)
[1008/213542:ERROR:renderer_main.cc(200)] Running without renderer sandbox
[1008/213543:WARNING:channel.cc(549)] Failed to send message to ack remove remote endpoint (local ID 1, remote ID 1)
[1008/213543:WARNING:nss_ssl_util.cc(370)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[1008/213600:WARNING:nss_ssl_util.cc(370)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[1008/213600:WARNING:nss_ssl_util.cc(370)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[1008/214550:WARNING:channel.cc(549)] Failed to send message to ack remove remote endpoint (local ID 1, remote ID 1)
[
How to overcome this errors?
After online searching the decision was found on upwork site forum
unknown ssl error
The problem was how to use the 2 versions of libnss3 packet simultaneously.Libnss3 goes as a security related packet so instead of downgrading it on the system you can simply download the old version of libnss3 compatible with upwork app and then dynamically add a path to this old version to the linker when you need to use upwork app, while the system will have the newest one.

The sandboxed code execution request was refused because the Sandboxed Code Host Service was too busy to handle the request

I am working with SharePoint 2010 server. I have deployed a sandboxed solution to the sharepoint server. But while adding the webpart to page it shows the error like below.
"The sandboxed code execution request was refused because the Sandboxed Code Host Service was too busy to handle the request"
I found below article and followed all the work around, but the error is still persisting.
http://blogs.msdn.com/b/sharepointdev/archive/2011/02/08/error-the-sandboxed-code-execution-request-was-refused-because-the-sandboxed-code-host-service-was-too-busy-to-handle-the-request.aspx
Can anyone tell me what am I missing or what I have to do in order to get rid of this exception?
We've had to do this, too:
$uc = [Microsoft.SharePoint.Administration.SPUserCodeService]::Local
$uc.WorkerProcessExecutionTimeout = 5000
$uc.Update()
$tier = $uc.Tiers[""] # default Tier has no Name
$tier.MaximumWorkerProcesses = 2 # number of CPU Cores + 1
$tier.Update()