maxThreads reached

Dear Orbeon community,

I've integrated the orbeon pipelines with a job scheduler in Tomcat 5.5.16. So I have a server that periodically launches 4 pipelines to retrieve information from web pages and databases. Basically it launces 4 pipelines every 5 minutes that connects to external sources and retrieves information.

My problem is that after few hours all the processes stop, so the pipelines are not executed anymore. I've got this message from Tomcat:

12-Aug-2006 02:33:11 org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase
maxThreads (150) or check the servlet status

Somehow I've reached the maxThreads, and I think that's because some pipeline threads are not killed. This may happen because the source is not available or is changing at the moment that the scheduler launches the pipeline.

My question is how I can solve this issue. Is there a way to control that an error has ocurred and kill the threads associated to the pipeline? Or there is a way to reset all threads associated to the pipelines so I can schedule this cleanup mechanism periodically?

Thanks again,
Jordi




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Hi,

I've solved my problem. I just set a timeout for the sessions in orbeon
web.xml

    <session-config>
        <session-timeout>10</session-timeout>
    </session-config>

And now if any pipeline thread is not completed after 10 minutes it will be
stopped.

Jordi

-----Mensaje original-----
De: [hidden email] [mailto:[hidden email]]
Enviado el: sábado, 12 de agosto de 2006 15:48
Para: [hidden email]
Asunto: [ops-users] maxThreads reached

Dear Orbeon community,

I've integrated the orbeon pipelines with a job scheduler in Tomcat 5.5.16.
So I have a server that periodically launches 4 pipelines to retrieve
information from web pages and databases. Basically it launces 4 pipelines
every 5 minutes that connects to external sources and retrieves information.

My problem is that after few hours all the processes stop, so the pipelines
are not executed anymore. I've got this message from Tomcat:

12-Aug-2006 02:33:11 org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase
maxThreads (150) or check the servlet status

Somehow I've reached the maxThreads, and I think that's because some
pipeline threads are not killed. This may happen because the source is not
available or is changing at the moment that the scheduler launches the
pipeline.

My question is how I can solve this issue. Is there a way to control that an
error has ocurred and kill the threads associated to the pipeline? Or there
is a way to reset all threads associated to the pipelines so I can schedule
this cleanup mechanism periodically?

Thanks again,
Jordi






--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws