f.martel
9th February 2016, 17:09
Iorana !

My actions :
- Read XML file
- Receipt purchase with AFS (thread (http://www.baanboard.com/baanboard/showthread.php?t=15618&highlight=tdpur4120m000))
- Update personal table

With some item (1 item, 1 purchase order, 1 position => 1 line in XML file) everything is good
With some item (1 item, 1 purchase order, 1 position => X lines in XML file for each lot number):
- Sometime, First receipt is good , the following receptions are bad: Set serial number
- Sometime, First receipt is good then error CORE DUMPED

I don't know how solved the core dumped message (bshell.log) :
log message called from /view/port.6.1c.07.17/vobs/tt/lib/al-1/al_sig: #157 keyword: CORE DUMPED
pid 6667 Uid 208 Euid 208 Gid 125 Egid 125

WARNING:
- We can't update our porting set
- We don't have ILC

Thanks

François

bhushanchanda
9th February 2016, 19:57
Hi,

You can check this thread (http://www.baanboard.com/baanboard/showthread.php?t=13280). Will give you some hints on how you can tackle the creation of the dump core files though have never faced this.

Ajesh
10th February 2016, 05:17
Please Check Your bshell Log, I once faced a Core Dump Issue when there were too many transactions going for commit. It might have a Clue.

mark_h
10th February 2016, 16:20
There was a couple of function servers I used to have that would dump after so many records. These sessions deleted hundreds or thousands of records. After so many runs it would abort and on occasion core dump. Not sure that is the case here - but with SP and upgrades I do not recall having this issue anymore.

I think the first thing you need to do is maybe make sure all the sessions close after each transaction. You might also want to try a pause(or suspend) before starting a new transactions. I know those two things have helped some of my sessions in the past. Think of the pause as giving the chance for the session to complete one transaction, before you start the next.