Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1483 Starting external PLSTAF service hanging

All
open
Sharon Lucas
5
2014-08-17
2013-03-14
Manoj Kumar
No

When i try to start an external perl service from staf it hangs and no response from staf server to the staf client . I found the root cause for the problem. it's because of the perlnterpreterlog file which exceeds 1 mb, then this problem occurs , since MAXLOGSIZE is 1 mb , I doubt if it could be an problem in creating backup logs. So i tried increasing the MAXLOGSIZE , the problem is not seen till the log file reaches the MAXLOGSIZE . I tried with MAXLOGSIZE OPTION in the cmd , but it sucks.

Staf example command :

add SERVICE SWAT LIBRARY PLSTAF EXECUTE ConsoleDaemon OPTION MAXLOGSIZE=1048576000 OPTION USELIB=c:\swat\tools\ConsoleDaemon.pm

Can anyone help me in it.

My e-mail id is c_mthan@qti.qualcomm.com

Discussion

  • Sharon Lucas
    Sharon Lucas
    2013-03-14

    • assigned_to: nobody --> slucas
     
  • Sharon Lucas
    Sharon Lucas
    2013-03-14

    I need more information.

    What Windows version are you running this STAF Perl service on?

    What is the output from: STAF local MISC LIST PROPERTIES

    What version of Perl are you using?

    The Perl interpreter log files are stored in the {STAF/DataDir}/lang/perl/<serviceName> directory. So, if you installed STAF to the default location of C:\STAF and are using the default STAF_INSTANCE_NAME of STAF, the Perl interpreter log files for a service named SWAT would be stored in C:\STAF\data\STAF\lang\perl\SWAT. Does the user that was logged on when STAFProc was started have the right permissions to be able to create files in this directory?

    Section "4.4.3 PLSTAF service proxy library" in the STAF User's Guide describes the MAXLOGSIZE option as follows:

    MAXLOGSIZE=<Number> specifies the maximum size, in bytes, for the Perl interpreter log file(s). The default is 1048576 (1M). This option determines when to create a new Perl interpreter log file. When the Perl interpreter is started, if the size of a Perl interpreter log file exceeds the maximum size specified by this option, a new Perl interpreter log file will be created.

    You said you tried increasing the maximum log size by specifying "OPTION MAXLOGSIZE=1048576000" when submitting a ADD SERVICE request. Did that not work? If it didn't work, what was the return code and error message that STAF provided?

    Note that the USELIB option should be set to the directory that contains the .pm file (not set to the name of the .pm file as your example showed). Try using the following STAF command to add your SWAT Perl service after first removing the service:

    STAF local SERVICE REMOVE SERVICE SWAT

    STAF local SERVICE ADD SERVICE SWAT LIBRARY PLSTAF EXECUTE ConsoleDaemon OPTION MAXLOGSIZE=1048576000 OPTION USELIB=C:\\swat\\tools

    If it didn't work, what was the return code and error message that STAF returned?

    What are the line(s) in your STAF.cfg file that you use the register the SWAT Perl service?