Hi,
I am working for starting connetware driver in back ground.
I am able to successfully start the driver by running unix shell program bnddc.sh and able to do the transactions. But the problem here is:


when I start Driver in back ground:

1. I start the function server and do some successful transactions.
2. I do transaction to get timeout error.
3. after I do successful transactions and it works ok!
4. If I do any unsuccessful transaction (such as which returns a message to connetware back like "Location blocked for warehouse" etc..) Connectware hangs.


But when I start Driver in foreground (through baan): everything works fine.

Is there any issue like this with anybody before.

I examined the logs : Baan sending response correctly.

I forcebly need to restart the drivers again.


My environment is : Baan Vc and Connetware 2.1.1

Rajsekhar,

I found this info our latest porting set - 7.3.a.04

MaintReger: # 19327 (BDUX12452): DF212605

Date: Thu, 10 Jul 2003 15:24:34 +0200

Created on: MaintReger
Type: bugfix

Problem Description (Customer terms)
DDC server stops processing transactions after a while when running in background mode (i.e. started from ddc driver via ddc_start_bshell.

Problem Description (Technical terms)
While the bshell is running in background mode, data is still being written to ds_outstream and/or ds_instream. Since a data is not being picked up off of these, the limit is reached on that stream and no more processing is done.

Workaround
Run DDC in foreground mode.

Test Procedure
Ran ddc in background mode processing many more transactions than were previously processed.

Motive source
DF:212605

You would have to contact BaaN support and get the latest porting set for your BaaN Version.

Hi Prasanth,
I already verified that issue. But my problem is not stopping all transactions. After timeout error, all successful transactions are going fine. Only first unsuccessful transaction making driver to hang up. But when I ran in foreground mode it works fine. Only difference I observered is: DDC_LIST_START. Logs from Baan side are same for successful and unsuccessful transactions.


Fore ground:

Driver: Send Msg Type : 21
Driver: Send Msg String :
Driver: Wait for Receive.



Driver: Rcv Msg Type : 8
Driver: Rcvd Msg Type : 8
Driver: Rcvd Msg String: bnddc510,DDC_INIT,0,0

Driver: Send Msg Type : 9
Driver: Send Msg String : bnddc510,DDC_LIST_START,grp_lst,0
Driver: Wait for Receive.

Driver: Rcv Msg Type : 6
Driver: Rcvd Msg Type : 6
Driver: Rcvd Msg String: bnddc510,DDC_ACK


Driver: Send Msg Type : 10
Driver: Send Msg String : bnddc510,DDC_LIST_ELEM,grp_lst,A,Connectware
Driver: Send Msg Type : 11
Driver: Send Msg String : bnddc510,DDC_LIST_END,grp_lst
Driver: Wait for Receive.


Driver: Rcv Msg Type : 6
Driver: Rcvd Msg Type : 6
Driver: Rcvd Msg String: bnddc510,DDC_ACK
Driver: Wait for Receive.


Driver: Rcv Msg Type : 9
Driver: Rcvd Msg Type : 9
Driver: Rcvd Msg String: bnddc510,DDC_LIST_START,grp_sel,0,1,0


Driver: Send Msg Type : 6
Driver: Send Msg String : bnddc510,DDC_ACK
Driver: Wait for Receive.



Driver: Rcv Msg Type : 0
Driver: Rcvd Msg Type : 10
Driver: Rcvd Msg String: bnddc510,DDC_LIST_ELEM,grp_sel,A,Connectware
Driver: Wait for Receive.


Driver: Rcv Msg Type : 0
Driver: Rcvd Msg Type : 11
Driver: Rcvd Msg String: bnddc510,DDC_LIST_END,grp_sel,1,0,0


Driver: Send Msg Type : 6
Driver: Send Msg String : bnddc510,DDC_ACK
Driver: Send Msg Type : 6


Driver: Send Msg String : bnddc510,DDC_ACK
Driver: Rcv Msg Type : 9
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Rcv Msg Type : 19
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Wait for Receive.
Driver: Rcv Msg Type : -19
Driver: Rcvd Msg Type : 7
Driver: Rcvd Msg String: DDC_EXECUTE
Driver: Wait for Receive.


Back ground logs:

Connecting with bshell...
Connection established.
Driver: Wait for Receive.
Driver: Rcv Msg Type : 21
Driver: Rcvd Msg Type : 21
Driver: Rcvd Msg String: bnddc510,DDC_START_UP,0,0
Driver: Wait for Receive.




Driver: Rcv Msg Type : 8
Driver: Rcvd Msg Type : 8
Driver: Rcvd Msg String: bnddc510,DDC_INIT,0,0



Driver: Send Msg Type : 6
Driver: Send Msg String : bnddc510,DDC_ACK


Driver: Rcv Msg Type : 9
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Rcv Msg Type : 19
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Wait for Receive.
Driver: Rcv Msg Type : -19
Driver: Rcvd Msg Type : 7
Driver: Rcvd Msg String: DDC_EXECUTE
Driver: Wait for Receive.


except this everything I saw in back ground and fore ground are same. Environmental variables , DDC variables etc..

I also checked error logs and the events are going fine, responses going fine. Here is the differece between failed transaction and successful transaction:

Failed transaction:
Driver: Wait for Receive.
Driver: Rcv Msg Type : -19
Driver: Rcv Msg Type : 19
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Send Msg Type : 1
Driver: Send Msg String : termid,DDC_REQUEST,1,20040213142308,user,KMG,2hyoo40y,,,,,functionservername,functionname,arguments
Driver: Rcvd Msg Type : 1
Driver: Rcvd Msg String: termid ,DDC_REPLY,1,1,0,2hyoo40y,,,,,functionservername,functionname,arguments,error message.
Driver: Send Msg Type : 19

Successful transaction:

Driver: Wait for Receive.
Driver: Rcv Msg Type : -19
Driver: Rcv Msg Type : 19
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Send Msg Type : 1
Driver: Send Msg String : termid,DDC_REQUEST,1,20040213141857,user,,2hyoh51y,,,,,functionservername,functionname,arguments
Driver: Rcvd Msg Type : 1
Driver: Rcvd Msg String: termid,DDC_REPLY,1,1,0,2hyoh51y,,,,,functionservername,functionname,arguments,error message
Driver: Rcv Msg Type : 9
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Rcv Msg Type : 19
Driver: Rcvd Msg Type : -1
Driver: Rcvd Msg String:
Driver: Wait for Receive.