| Author |
Message |
 Topic: Cluster workload exit intermittant SIGSEGV |
lorenmcc
Replies: 15
Views: 48108
|
 Forum: User Exits Posted: Wed Dec 12, 2012 8:06 am Subject: Cluster workload exit intermittant SIGSEGV |
It does look like it is the localtime function not being thread safe as the problem. I have converted to localtime_r and I am running some test cases to see if I can break it.
Thanks everyone for ... |
| Topic: Cluster workload exit intermittant SIGSEGV |
lorenmcc
Replies: 15
Views: 48108
|
Forum: User Exits Posted: Tue Dec 11, 2012 11:54 am Subject: Cluster workload exit intermittant SIGSEGV |
| you were lucky on the ESQL, but I guess that is on usage of something they support. I guess it depends on who you get. I opened a PMR asking specific questions on writing the exits and I was told fl ... |
| Topic: Cluster workload exit intermittant SIGSEGV |
lorenmcc
Replies: 15
Views: 48108
|
Forum: User Exits Posted: Tue Dec 11, 2012 10:47 am Subject: Cluster workload exit intermittant SIGSEGV |
I agree on the risk, but this is the decision that was made.
As for IBM's involvement, it stops as soon as you write the exit. They will not debug user code or give advice on how to write it, even ... |
| Topic: Cluster workload exit intermittant SIGSEGV |
lorenmcc
Replies: 15
Views: 48108
|
Forum: User Exits Posted: Tue Dec 11, 2012 10:02 am Subject: Cluster workload exit intermittant SIGSEGV |
| We have several hundred integrated apps (WebSphere AS and mainframe), across about 50 qmgrs and several thousand queues involved. I don't need a debate about whether this should have been done. This ... |
| Topic: Cluster workload exit intermittant SIGSEGV |
lorenmcc
Replies: 15
Views: 48108
|
Forum: User Exits Posted: Tue Dec 11, 2012 8:46 am Subject: Cluster workload exit intermittant SIGSEGV |
| I am receiving a SIGSEGV (address not mapped) intermittantly in an exit I wrote for Cluster WLM exit. The purpose of the exit is to logically split our cluster so applications can test an implementat ... |
