• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1130
  • Last Modified:

ExecuteThread: '1' for queue

Hi experts

I have a Java Program, the platforms are:
1)       JConnect 5.5.
2)       Driver: Sybase’s Driver (Type 4) Versions: 5.X
(jconn2.jar, com.sybase.jdbc2.jdbc.SybDriver)
3)       Weblogic 8.1 ServicePack 3 y ServicePack5*

The Program is working, but sometimes it stop, my administrator server said me the problem is because the ExecuteThread: ‘N’ for queue are full. He send me an email with the status, like to:

ExecuteThread: ‘1’ for queue:      Http Request:
‘Arcoweb.Execute.Queue’               /Arcoweb/consultas/ConsultaTemporal

I don´t have idea What is the problem?
1 Solution
Requests to a WebLogic Server instance are placed in an execute queue. Each request is assigned to a thread within the queue that performs the work. By default, a new WebLogic Server instance is configured with a default execute queue, weblogic.kernel.default, that contains 15 threads. In addition, WebLogic Server provides two other pre-configured queues: weblogic.admin.HTTP and weblogic.admin.RMI. Because these queues are reserved for communicating with the Administration Console and for administrative traffic, you cannot reconfigure them. Unless you configure additional execute queues and assign applications to them, Web applications and RMI objects use weblogic.kernel.default. This page allows you to configure a new, user-defined execute queue for use with applications on this server, or to edit an existing execute queue.

Could you please check your current Execute Queue setup from WebLogic Administrative Console:

From WebLogic Administrative console,

Domain>Servers>[your server name]>Configuration>General>Advanced Option>Configure Execute Queues

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now