Originally posted by: Kepa_Screen

Hi:

We are running an Event Server with DataStage 6.7.1. The system works well, but sometimes, it goes to Not Responding.

We have looked at the logs, and we can see this :

" /merc671/mantenimiento/tmp/launcher_78958 -> more crash.log
AIX -> inside stack trace
Received signal: 11
Registers: IAR=0xd613667c CR=0x82004041 LR=0xd6136670 CTR=0xd0019780 MSR=0xd0b2
0: is ???:0xd6136508+0x164
1: is ???:0xd612f68c+0x80
2: is ???:0xd6180628+0x98
3: is MercatorThread:0x10012248+0x1588
4: is _pthread_body:0xd0007ff8+0xd0
5: is ???:0x0+0x0
6: is ???:0x0+0x0
AIX -> stack trace end
+ uname -a
+ echo OS=AIX X70001 3 4 000002604C00
OS=AIX X70001 3 4 000002604C00
+ date
+ echo DATE = Wed Oct 10 13:48:04 DFT 2007
DATE = Wed Oct 10 13:48:04 DFT 2007
+ echo PID = 78958
PID = 78958
+ echo ThreadNo = 86
ThreadNo = 86
+ echo \nSystem limits report

System limits report
+ ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) unlimited
memory(kbytes) 32768
coredump(blocks) unlimited
nofiles(descriptors) 6000
+ echo \nTrying to start dbx debbuger ...\n

Trying to start dbx debbuger ...

+ echo thread current 86; where ; thread; detach
+ dbx -a 78958
Waiting to attach to process 78958 ...
Successfully attached to launcher.
warning: Directory containing launcher could not be determined.
Apply 'use' command to initialize source path.

Type 'help' for help.
reading symbolic information ...warning: no source compiled with -g

stopped in evt._pthread_ksleep [/usr/lib/libpthreads.a] at 0xd0011b6c ($t2)
0xd0011b6c (_pthread_ksleep+0x9c) 80410014 lwz r2,0x14(r1)
wait.waitpid(0x30953750, 0x0, 0xffffffff) at 0xd01b79c0
system.system(??) at 0xd01b6970
system.system(??) at 0xd01b6970
mercStackTrace(??, ??, ??) at 0x10045480
mercExceptHandler(??, ??, ??, ??) at 0x10044844
sigSegvHandler(??, ??, ??) at 0x10044d84
Unload__15CMpiMapSetCacheFP10CMpiMapSet() at 0xd613667c
__dt__7CMpiMapFv() at 0xd612f70c
mpiObjectDestroy() at 0xd61806c0
MercatorThread(??) at 0x100137d0
pthread._pthread_body(??) at 0xd00080c8
thread state-k wchan state-u k-tid mode held scope function
$t1 wait running 123847 k no pro main

*$t2 run blocked 109503 k no sys _pthread_ksleep

$t3 wait running 122557 k no pro create_atomlist

$t4 wait running 110707 k no pro _ptrgl

$t5 terminated u no pro

$t6 run running 117141 k no pro create_atomlist

$t7 terminated u no pro

$t8 wait running 124105 k no sys mercReadyToRead

$t9 wait running 124363 k no sys mercReadyToRead

$t10 wait running 124621 k no sys mercReadyToRead

$t11 run running 123605 k no sys $PTRGL

$t12 run running 101837 k no sys $PTRGL

$t13 run running 91425 k no sys $PTRGL

$t14 run running 115861 k no sys $PTRGL

>$t86 wait running 225747 k no sys waitpid

$t16 blocked u no pro _usched_swtch

$t17 blocked u no pro _usched_swtch

$t27 wait running 104037 k no sys mercSocketReady

$t19 blocked u no pro _usched_swtch

$t20 blocked u no pro _usched_swtch

$t21 blocked u no pro _usched_swtch

$t22 blocked u no pro _usched_swtch

$t23 blocked u no pro _usched_swtch

$t24 blocked u no pro _usched_swtch

$t25 blocked u no pro _usched_swtch

$t26 blocked u no pro _usched_swtch

+ echo \nEnd of Mercator crash report

End of Mercator crash report
"

We don't know exactly why the ES is "crashing"... Could anybody help in some manner ??

Thanks in advance.

#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: GerryCullen

I suggest you contact IBM Support to see if this is a know problem. Version 6.7.1 is pretty old...
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

Event server usually only crashes when there is a resource conflict. Have you changed any systems?
Check file names, log file names etc. Have you got 2 maps trying to delete the same file? 2 maps trying to write to a log file of the same name.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: Kepa_Screen

Thank you for your replies.
I forget to say that we are getting this issue only on a Development Box, not at Production one, so is very possible that the problem is something about resource conflicts as said by you.

We are doing some tests with DSTX 8.0.1 in order to migrate our boxes, and couldn't reproduce the error, so we will upgrade soon.

Thank you very much for your suggestions.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender