Hello,
An ASE session initiates a CIS call to a remote server (EAServer 6.3 application server in this case).
For some reasons, the remote server needs to be restarted.
This results in the ASE client sessions that already has a CIS connection "open" to this server getting corrupted and the next CIS call to that remote server results in an error. A second call to the same external server works ok, so it seems that the error is captured and CIS reinitiates the session, but not the "first time".
The remote server is defined like this:
|name |network_name |class |status |id|cost|
+----------+---------------+------------+--------------------------------------------------------------------------------------------------+--+----+
|EA_SERVER |JAGUAR_ISUTV02 |ASEnterprise|timeouts, no net password encryption, writable , rpc security model A, enable login redirection |25|1000|
+----------+---------------+------------+--------------------------------------------------------------------------------------------------+--+----+
The remote call is made to a "stored procedure (EJB in this case)" and looks like this example:
set cis_rpc_handling on
set transactional_rpc on
exec @iRetStatus = EA_SERVER.SIMBaseMail.Mail.sendMailFromDBBoxen
@vcFelText output,
@nLopNr
set transactional_rpc off
set cis_rpc_handling off
The error message from the CIS call is (ISUTV02 is in this example the ASE server that initiates the call to the remote server):
Cannot read from site 'ISUTV02'. <Server> = ISUTV02, <MsgNo> = 7223, <MsgState> = 12, <Severity> = 16, <Line> = 18
Error indicated when reading the result from a SQL command execution
Normally, that shouldn't really affect the calling ASE in this way: CIS should be able to recognize that the session isn't working and repair this without this error situation. This error gets thrown to the ASE clients that interpret this as a fatal error.
Is this due to some misconfiguration of our ASE or are there any other solution to this problem?
For example a command that will reinitiate all CIS connections after a restart of the external server