Re^3: Soap calls using multithreading running out of memory

Some more info on this....

I am running perl program with Threads and which uses Soap::Lite also. This is running good in my windows 7(perl 5, version 24, subversion 0 (v5.24.0) built for MSWin32-x64-multi-thread) strawberry perl. While I run the same program in my DEV( HP-UX XXXXXXXX B.11.31 U ia64 2666145408 unlimited-user license ) environment( perl, v5.8.8 built for IA64.ARCHREV_0-thread-multi ) It is throwing "Memory fault(coredump)" Did anyone face similar situation / Do anyone have any suggetion to resolve this?

Comment on Re^3: Soap calls using multithreading running out of memory

Replies are listed 'Best First'.
Re^4: Soap calls using multithreading running out of memory by marto (Cardinal) on Feb 14, 2017 at 14:32 UTC
5.8.8. is over 10 years old, your dev and production platforms are very different. Are you running the same version of SOAP::Lite and it's dependency trees (their dependencies etc)? I suspect that this will be very different. You were told that SSL modules aren't thread safe. My suggestion would be to try and isolate the problem. Ensure your dev environment is the same (or as close as possible) to production, otherwise you'll spend a lot of time developing something that need to be completely retested on the production platform which may look nothing like the one you built it for, you'll waste a lot of time chasing bugs in differences in the stacks.	[reply]

Replies are listed 'Best First'.

Re^4: Soap calls using multithreading running out of memory
by marto (Cardinal) on Feb 14, 2017 at 14:32 UTC

5.8.8. is over 10 years old, your dev and production platforms are very different. Are you running the same version of SOAP::Lite and it's dependency trees (their dependencies etc)? I suspect that this will be very different. You were told that SSL modules aren't thread safe. My suggestion would be to try and isolate the problem. Ensure your dev environment is the same (or as close as possible) to production, otherwise you'll spend a lot of time developing something that need to be completely retested on the production platform which may look nothing like the one you built it for, you'll waste a lot of time chasing bugs in differences in the stacks.

[reply]