Topic
  • 7 replies
  • Latest Post - ‏2012-12-10T13:30:41Z by hnasgaard
SystemAdmin
SystemAdmin
1245 Posts

Pinned topic Problem with running standalone job

‏2012-12-07T03:17:01Z |
Hi, I tried to write a SPL composite which read files from specific directory and collaborate with Java program.
When I ran it as standalone, I got some messages from the console of StreamStudio as following.
Could anyone give me some suggestion to resolve the problem?

Thanks for your help first.

============================ SIGNAL SIGSEGV ============================
/opt/ibm/InfoSphereStreams/lib/libstreams-apputils.so.0(Distillery::BacktraceDumper::dump(int, bool, int)+0x39) 0x2b12d831cbb9
/opt/ibm/InfoSphereStreams/lib/../lib/libstreams-runtime.so.0(Distillery::DistilleryApplication::faultHandler(int)+0x4d) 0x2b12d9641b1d
/opt/ibm/InfoSphereStreams/lib/../lib/libstreams-runtime.so.0(Distillery::DistilleryApplication::errorSignalHandler(int)+0x63) 0x2b12d9642ab3
/lib64/libc.so.6 0x3152830280
/opt/ibm/InfoSphereStreams/lib/libstreams-spl-runtime.so.0 0x2b12d7c220e0
/opt/ibm/InfoSphereStreams/lib/libstreams-spl-runtime.so.0 0x2b12d7e88172
/opt/ibm/InfoSphereStreams/lib/libstreams-spl-runtime.so.0(SPL::StandaloneApplicationImpl::createPE()+0x143) 0x2b12d7eabf43
/opt/ibm/InfoSphereStreams/lib/libstreams-spl-runtime.so.0(SPL::StandaloneApplicationImpl::run(std::vector<std::string, std::allocator<std::string> > const&)+0x18e) 0x2b12d7eaca4e
/opt/ibm/InfoSphereStreams/lib/../lib/libstreams-runtime.so.0(Distillery::DistilleryApplication::runSafeCatchDst(std::vector<std::string, std::allocator<std::string> > const&)+0x2e9) 0x2b12d964da19
/opt/ibm/InfoSphereStreams/lib/../lib/libstreams-runtime.so.0(Distillery::DistilleryApplication::runSafeCatchall(std::vector<std::string, std::allocator<std::string> > const&)+0x24) 0x2b12d9654224
/opt/ibm/InfoSphereStreams/lib/../lib/libstreams-runtime.so.0(Distillery::DistilleryApplication::main(int, char**, char**)+0x3dd) 0x2b12d9647eed
/opt/ibm/Eclipse/StreamsStudio/workspace/CombineJava/output/main.EntryPoint/Standalone/bin/standalone(main+0x23) 0x400a0b
/lib64/libc.so.6(__libc_start_main+0xf4) 0x315281d974
/opt/ibm/Eclipse/StreamsStudio/workspace/CombineJava/output/main.EntryPoint/Standalone/bin/standalone(__gxx_personality_v0+0x89) 0x400939
=============================================================================
  • hnasgaard
    hnasgaard
    200 Posts

    Re: Problem with running standalone job

    ‏2012-12-07T15:57:36Z  
    From the traceback it appears that there was a seg fault (invalid memory access) during startup. Can you provide code to reproduce the problem? Without that it is hard to say what the problem might be. What version of Streams are you running? What OS are you running on?
  • SystemAdmin
    SystemAdmin
    1245 Posts

    Re: Problem with running standalone job

    ‏2012-12-07T17:30:58Z  
    • hnasgaard
    • ‏2012-12-07T15:57:36Z
    From the traceback it appears that there was a seg fault (invalid memory access) during startup. Can you provide code to reproduce the problem? Without that it is hard to say what the problem might be. What version of Streams are you running? What OS are you running on?
    Hi hnasgaard. Thanks for your reply first.

    The attachment is the zipped project.

    My environment information is:
    Streams: 3.0.0.0
    OS : RedHat5 64bit
    JAVA : IBM Java SDK 1.6.0

    I tried to run it at distribute mode, it ran correctly.
  • hnasgaard
    hnasgaard
    200 Posts

    Re: Problem with running standalone job

    ‏2012-12-07T18:47:22Z  
    Hi hnasgaard. Thanks for your reply first.

    The attachment is the zipped project.

    My environment information is:
    Streams: 3.0.0.0
    OS : RedHat5 64bit
    JAVA : IBM Java SDK 1.6.0

    I tried to run it at distribute mode, it ran correctly.
    Hi
    The tar file you provided does not seem to have the SPL code so I really can't see much of what's going on. Is it possible to get the SPL code?
  • SystemAdmin
    SystemAdmin
    1245 Posts

    Re: Problem with running standalone job

    ‏2012-12-08T08:24:59Z  
    • hnasgaard
    • ‏2012-12-07T18:47:22Z
    Hi
    The tar file you provided does not seem to have the SPL code so I really can't see much of what's going on. Is it possible to get the SPL code?
    Hi
    You could get the SPL code in the main folder or see the attachment.

    Thanks for your help.
  • hnasgaard
    hnasgaard
    200 Posts

    Re: Problem with running standalone job

    ‏2012-12-08T13:43:01Z  
    Hi
    You could get the SPL code in the main folder or see the attachment.

    Thanks for your help.
    Hi,
    I realized this morning that the tar file I downloaded was corrupt. A new download cleared up that problem; I now see the SPL and Java code. In fact I can build and execute the standalone version of the code without problem. At this point I would suggest setting both Trace output level and Log output level to info via the run configuration and then see what output you get in the Studio console.
  • SystemAdmin
    SystemAdmin
    1245 Posts

    Re: Problem with running standalone job

    ‏2012-12-09T14:54:18Z  
    • hnasgaard
    • ‏2012-12-08T13:43:01Z
    Hi,
    I realized this morning that the tar file I downloaded was corrupt. A new download cleared up that problem; I now see the SPL and Java code. In fact I can build and execute the standalone version of the code without problem. At this point I would suggest setting both Trace output level and Log output level to info via the run configuration and then see what output you get in the Studio console.
    Thanks hbasgaard very much.

    It works ! I don't modify the SPL code, I just change the trace level.
  • hnasgaard
    hnasgaard
    200 Posts

    Re: Problem with running standalone job

    ‏2012-12-10T13:30:41Z  
    Thanks hbasgaard very much.

    It works ! I don't modify the SPL code, I just change the trace level.
    That is not what I expected. Changing the trace level should not have made it work. It only should have provided more information about where it fails. If you change the trace/log levels back to what they were originally, does it fail again? If so, what is trace/log level set to when it fails?