HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Internal DCE thread problem
HPE 9000 and HPE e3000 Servers
1827288
Members
1840
Online
109717
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2001 08:59 PM
07-22-2001 08:59 PM
Internal DCE thread problem
I've been facing this problem with HP-UX 10.2. Whenever I try to stop a running process with Ctrl-C, I'll get the following error messsage:
%Internal DCE Threads problem (version CMA BL10+), terminating execution.
% Reason: dispatch: no available VP (uniprocessor)
% See 'cma_dump.log' for state information.
After tracing the code, I found that the error message always comes out after this particular line of the code:
bytes_read = in_sock->read( temp_buf, RPC_INT_SIZE);
And 'in_sock' is defined as below:
os_tcp_socket* in_sock /* Read into the packet from the specified socket */
os_tcp_sock is the standard function in object space.
// DESCRIPTION:
An `os_tcp_socket` allows reliable connection-oriented communication between a server socket and a client socket. The server process constructs a TCP connection server and binds it to an address that is known to its client. It then waits for an incoming connection request using `accept()`. A client process creates a stream socket and connects it to the server socket using `connect_to()`. When the connection is made, the server's `accept()` function connects its socket argument to the client socket. Any data written to the server socket will appear as input to the client socket, and visa-versa.
TCP sockets may be bound to a UNIX file system path, although this is only useful for TCP connections between processes that have access to the same file system.
In cma_dump.log, there is one statement stated that the DCEthreads scheduling database is locked. Below is one piece of the error message from the log file:
%Internal DCE Threads problem (version CMA BL10+), terminating execution.
% Reason: dispatch: no available VP (uniprocessor)
The current thread is 2 (address 0x00083628)
DECthreads scheduling database is locked.
Is this the kernel setting problem setting e.g. ulimit or others?
Fyi, the process I run is a software developed internally in command line mode.
%Internal DCE Threads problem (version CMA BL10+), terminating execution.
% Reason: dispatch: no available VP (uniprocessor)
% See 'cma_dump.log' for state information.
After tracing the code, I found that the error message always comes out after this particular line of the code:
bytes_read = in_sock->read( temp_buf, RPC_INT_SIZE);
And 'in_sock' is defined as below:
os_tcp_socket* in_sock /* Read into the packet from the specified socket */
os_tcp_sock is the standard function in object space.
// DESCRIPTION:
An `os_tcp_socket` allows reliable connection-oriented communication between a server socket and a client socket. The server process constructs a TCP connection server and binds it to an address that is known to its client. It then waits for an incoming connection request using `accept()`. A client process creates a stream socket and connects it to the server socket using `connect_to()`. When the connection is made, the server's `accept()` function connects its socket argument to the client socket. Any data written to the server socket will appear as input to the client socket, and visa-versa.
TCP sockets may be bound to a UNIX file system path, although this is only useful for TCP connections between processes that have access to the same file system.
In cma_dump.log, there is one statement stated that the DCEthreads scheduling database is locked. Below is one piece of the error message from the log file:
%Internal DCE Threads problem (version CMA BL10+), terminating execution.
% Reason: dispatch: no available VP (uniprocessor)
The current thread is 2 (address 0x00083628)
DECthreads scheduling database is locked.
Is this the kernel setting problem setting e.g. ulimit or others?
Fyi, the process I run is a software developed internally in command line mode.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2001 05:29 AM
07-23-2001 05:29 AM
Re: Internal DCE thread problem
You need to post this to the HPUX forum under system administration.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP