tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Herschke (JIRA)" <>
Subject [jira] [Created] (TOMEE-2044) threadPool-queue (in ServicePool) from ejbd-Service is never processed
Date Thu, 01 Jun 2017 16:07:04 GMT
Lars Herschke created TOMEE-2044:

             Summary: threadPool-queue (in ServicePool) from ejbd-Service is never processed

                 Key: TOMEE-2044
             Project: TomEE
          Issue Type: Bug
          Components: TomEE Core Server
    Affects Versions: 1.7.4
         Environment: FreeBSD 10.3-STABLE amd64 
            Reporter: Lars Herschke

If you have many requests to your ejbd-service the queue from the threadPool in
is filled. This queue is never processed depending on your server config. If you have only
ejbd-service enabled and the services admin, ejbds and httpejbd are disabled all is fine.
If you have two or more of these services enabled the issue could occur. The reason is the
following. has the following line to get the queue.
final ServicePool incoming = SystemInstance.get().getComponent(ServicePool.class); hold components in a HahMap with the class type as key. On server-startup
the above named services are initalized in ServiceManager.manage(...). This method instances
new ServicePool for this services. Each ServicePool-instance calls in his constructor
SystemInstance.get().setComponent(ServicePool.class, this);.
Every other call of setComponent replace the old entry in the components HashMap. So KeepAliveServer
gets always the queue of the last initalized service.

Use only one of the four above named services
set threadsCore for your services at least as high, that the queue is never used.

This message was sent by Atlassian JIRA

View raw message