<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Internal DCE Thread Problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/internal-dce-thread-problem/m-p/2556072#M28763</link>
    <description>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: &lt;BR /&gt;&lt;BR /&gt;%Internal DCE Threads problem (version CMA BL10+), terminating execution. &lt;BR /&gt;% Reason: dispatch: no available VP (uniprocessor) &lt;BR /&gt;% See 'cma_dump.log' for state information. &lt;BR /&gt;&lt;BR /&gt;After tracing the code, I found that the error message always comes out after this particular line of the code: &lt;BR /&gt;bytes_read = in_sock-&amp;gt;read( temp_buf, RPC_INT_SIZE); &lt;BR /&gt;&lt;BR /&gt;And 'in_sock' is defined as below: &lt;BR /&gt;os_tcp_socket* in_sock /* Read into the packet from the specified socket */ &lt;BR /&gt;&lt;BR /&gt;os_tcp_sock is the standard function in object space. &lt;BR /&gt;// DESCRIPTION: &lt;BR /&gt;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. &lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;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: &lt;BR /&gt;&lt;BR /&gt;%Internal DCE Threads problem (version CMA BL10+), terminating execution. &lt;BR /&gt;% Reason: dispatch: no available VP (uniprocessor) &lt;BR /&gt;The current thread is 2 (address 0x00083628) &lt;BR /&gt;DECthreads scheduling database is locked. &lt;BR /&gt;&lt;BR /&gt;I'm using signal() system call to handle the interuption. Does HP DCE Threads support this? Or should I use sigaction() or other signal handling function instead.&lt;BR /&gt;&lt;BR /&gt;Is this the kernel setting problem setting e.g. ulimit or others? &lt;BR /&gt;&lt;BR /&gt;Fyi, the process I run is a software developed internally in command line mode.</description>
    <pubDate>Tue, 24 Jul 2001 01:22:55 GMT</pubDate>
    <dc:creator>ivy_1</dc:creator>
    <dc:date>2001-07-24T01:22:55Z</dc:date>
    <item>
      <title>Internal DCE Thread Problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/internal-dce-thread-problem/m-p/2556072#M28763</link>
      <description>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: &lt;BR /&gt;&lt;BR /&gt;%Internal DCE Threads problem (version CMA BL10+), terminating execution. &lt;BR /&gt;% Reason: dispatch: no available VP (uniprocessor) &lt;BR /&gt;% See 'cma_dump.log' for state information. &lt;BR /&gt;&lt;BR /&gt;After tracing the code, I found that the error message always comes out after this particular line of the code: &lt;BR /&gt;bytes_read = in_sock-&amp;gt;read( temp_buf, RPC_INT_SIZE); &lt;BR /&gt;&lt;BR /&gt;And 'in_sock' is defined as below: &lt;BR /&gt;os_tcp_socket* in_sock /* Read into the packet from the specified socket */ &lt;BR /&gt;&lt;BR /&gt;os_tcp_sock is the standard function in object space. &lt;BR /&gt;// DESCRIPTION: &lt;BR /&gt;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. &lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;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: &lt;BR /&gt;&lt;BR /&gt;%Internal DCE Threads problem (version CMA BL10+), terminating execution. &lt;BR /&gt;% Reason: dispatch: no available VP (uniprocessor) &lt;BR /&gt;The current thread is 2 (address 0x00083628) &lt;BR /&gt;DECthreads scheduling database is locked. &lt;BR /&gt;&lt;BR /&gt;I'm using signal() system call to handle the interuption. Does HP DCE Threads support this? Or should I use sigaction() or other signal handling function instead.&lt;BR /&gt;&lt;BR /&gt;Is this the kernel setting problem setting e.g. ulimit or others? &lt;BR /&gt;&lt;BR /&gt;Fyi, the process I run is a software developed internally in command line mode.</description>
      <pubDate>Tue, 24 Jul 2001 01:22:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/internal-dce-thread-problem/m-p/2556072#M28763</guid>
      <dc:creator>ivy_1</dc:creator>
      <dc:date>2001-07-24T01:22:55Z</dc:date>
    </item>
  </channel>
</rss>

