• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • ct_cmd_alloc(): user api layer: external error: The connection has been marked dead.

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved ct_cmd_alloc(): user api layer: external error: The connection has been marked dead.

  1. Issue
0
Votes
Undo
  1. Brindha Duraisingh
    Brindha Duraisingh
  2. PowerBuilder
  3. Monday, 22 March 2021 16:53 PM UTC

Hi All,

below error is being thrown when the powerbuilder 2019 application is left idle in WIN10.

ct_cmd_alloc(): user api layer: external error: The connection has been marked dead.

we didn't face this problem with PB12.9. 

my application has a timeout defined as 90 mins, but this DB connection failure makes the application session to disconnect in less than an hour.

 

does anyone else has faced similar DB disconnection issue? please suggest a sollution.

Error Calling External Object Function loadfile??
DLL que se instalan para el Run Time
Responses (2)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Thursday, 19 September 2024 14:07 PM UTC
  2. PowerBuilder
  3. # 1

Hi, Santhosh -

I've not used it in almost 15 years, but because of the "ct_cmd_alloc" name in the error, I am led to conclude you are using a Sybase Adaptive Server Enterprise (ASE) database and you are connected to it via the PowerBuilder ASE database interface, which in turn utilizes Sybase Open Client.

You need to work with your Sybase DBA to determine if they have set any connection timeout values in the database. If so, those will override any setting you configure from the PB/Open Client side. Please refer to the note included in the explanation of the setting "value" in the following PB help topics regarding DBParm settings:

    https://docs.appeon.com/pb2022r3/connection_reference/Sec_Cred_Timeout.html

    https://docs.appeon.com/pb2022r3/connection_reference/Sec_Sess_Timeout.html

You might also consider using/testing the "KeepAlive" DBParm setting that is applicable to ASE connections, to see if that helps:

    https://docs.appeon.com/pb2022r3/connection_reference/KeepAlive.html

Best regards, John

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 22 March 2021 19:50 PM UTC
  2. PowerBuilder
  3. # 2

Hi Brindha;

   This error normally (AFAIK) occurs when the Database / DBMS connection has been broken. This  error can also be caused when a long running DML request has been executed and the DBMS times out. Depending on the DBMS server type and its settings, it may just truncate the session.

   My advise would be to check the DBMS server logs and see if there is a corresponding log entry in the DBMS Server logs around the time that your PB App(s) get this error. If so, you might have to have your DBA team "tweak" the server settings.

HTH

Regards ... Chris

Comment
SANTHOSH S
  1. SANTHOSH S
  2. Thursday, 19 September 2024 08:41 AM UTC
Hi Chris,

Good day!!

For the above response , please let us know which DB parameter need to tweak now. Please advise
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. Thursday, 19 September 2024 09:53 AM UTC
Hi.

You don't mention which database you are connecting on. Neither the interface you are using to connect. It's a kind difficult to anyone to give a specific answer/advise to your question.

Andreas.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.