topic Re: tWebService component to work on the jobServer in Talend Studio

tWebService component to work on the jobServer

Philippe_Gagnon_-_RTC — Sat, 16 Nov 2024 11:43:14 GMT

Hello

We are trying to get the tWebService component to work on the jobServer version 5.3.1
https://help.talend.com/search/all?query=tWebService&content-lang=en

we found the solution for the desktop client (change the use of the jre to jdk)
https://jira.talendforge.org/browse/TDI-25565

but we are unable to configure the JobServer side

our JobServer starts D:\Talend\5.3.1\JobServer\conf\jsl_static64.exe
The JDK is installed
the JAVA_HOME variable links the JDK
then jsl_static.ini file seems to be well configured (joined to the email)
could you please help us

thank you

Philippe
www.rtcquebec.ca

======

;This section defines variables, which can be used elsewhere in the ini file
;A variable refenrencing itself e.g. "PATH=%PATH%;c:\java\test" will result in an import from the environment.
;JSL will first look in the normal environment then in the system environment of the registry as a fallback.
;Any variable not in the defines section will result in a environment lookup as well.
;Variable substitution is possible in any value in the ini file
;% is escaped by %%
PATH= %PATH%
JAVA = %JAVA_HOME%
P1 = d:\java\test
P2 = %P1%

;Comma seperated list of variables to be exported to the environment
;Supersedes the "path" parameter further down.
;Do not use the path parameter if you also set "PATH"in the export parameter as precedence is undefined.
export = CLASSPATH,PATH

appname = TalendJobServer
servicename = TalendJobServer
displayname = Talend JobServer
;Size of internal buffer for string handling
;increase if you use very long command line parameters e.g. a very long classpath
stringbuffer = 16000
;port used to communicate stop command to JVM
;Must be unique for each JSL instance installed
;This option is ignored if a stop method is defined further down
;stopport = 8465
;delay n milliseconds to start the Java VM
;Default is no start delay
;startdelay = 10000
;service dependencies can be added
;as a comma separated string "dep1,dep2"
;dependencies=depend2
;service start type
;auto demand disabled
;default is auto
starttype=auto
;Allow interaction with desktop
;This is a service configuration flag; default is false
;interactwithdesktop = false
;load ordering group
loadordergroup=someorder
;account under which service runs
;default is system
;account=mroescht-PC\mroescht
;password for above account
;system need not provide a password
;obfuscation of password is not supported. It is actually not needed.
;The password specified here is ONLY used during the jsl -install command. It can (and should) be deleted after installation.
;password=somepwd
;Allocate a console and register a console event handler to catch shutdown events.
;Default is true; options are FALSE TRUE false true YES NO yes no
;This option has two effects:
;1. If active it catches the logoff events and prevents the service from erroneously stopping in this case.
;2. It creates a console window if interaction with the desktop is allowd.
;Effect 1 can be achieved in Java 1.3.1 and higher by using the -Xrs option.
;Effect 2 may or may not be desired.
useconsolehandler=false
;Call <stopclass>.<stopmethod> through JNI so stop the JVM.
;This can be used an alternative to the ServiceStopper
;When all three parameters are defined the JSL will try to use JNI to stop the service.
;If not it will use a tcp/ip connection to the stopport.
;The simplest way to use this functionality is to use the Systen.exit() call as specified below.
;Nevertheless you can call any static method in your code.
;The method called is expected to terminate the JVM one way or the other. It can directly
;call System.exit() or make another Thread do it make the main method return.
;The method can return imediately if desired. If the JVM doesn't stop another attempt can be made to
;stop the service at a later time.
stopclass=java/lang/System
stopmethod=exit
;Take care to specify the right signature for your method. void System.exit( int code ) has
;the sifnature specified below. void myMethod() has the signature ()V. Please refer to the
;JNI documentation for details.
stopsignature=(I)V
;Parameters can be passed in "stopparam".
;Note that parameter passing is only implemented for the special case that the signature of the
;method is (String[]). Generic parameter passing is cumbersome to implement in C so I choose
;to implement only the most common case.
;stopsignature=(
;Path to the java runtime used
;If this option is not used the default from the registry will be used
;jrepath=c:\java\jdk16x32
;jrepath=..\..\..\jdk16
jrepath=C:\Program Files\Java\jdk1.7.0_45
;Type of jvm to be used. Alternative mechanism to specifiying -client or -server on the command line.
;Can use any JVM name, which is diffrent from the command line which will only allow -client and -server
;Useful when using a JVM diffrent from Suns implementation.
jvmtype=server
;working directory
;If the working directory path starts with a "." it will be replaced with the .ini directory path
;This is neccessary because a service does not inherit a working directory from the shell. Therefore "." would be meaningless.
;This logic is only required here because all other paths will resolve a "." against the working dir once it is set.
;wrkdir=c:\java\test\jsl_0_9_9j\release
;wrkdir=.
;the number of paramters passed to the java application
;parameters must be named param00, param01 ...
;Please note that each command line parameter has to go on it's own parameter value here!
;The way the JVM is called in JSL, the JVM expects a preparsed array of parameters.
;Everything seperated by whitespace on a java command line is broken down into a parameter here.
;You don't need to care about quotes
;around strings containing spaces here. e.g.
;java.exe -cp "c:\program files\test\lib.jar" com.test.Java "test.>"
;becomes
;params = 6
;param00 = -cp
;param01 = c:\jobserver;c:\jobserver\lib\jmxremote_optional.jar;c:\jobserver\lib\log4j-1.2.15.jar;c:\jobserver\lib\commons-io-1.3.2.jar;c:\jobserver\lib\jsl.jar
;param02 = -Djava.library.path=c:\jobserver\jsysmon-20061229\native\windows\
;param03 = -Dcom.sun.management.jmxremote
;param04 = -Dtalend_props=c:\jobserver\conf\TalendJobServer.properties
;param05 = org.talend.remote.jobserver.service.WindowsJobServer
params = 6
param00 = -cp
param01 = D:\Talend\5.3.1\JobServer;D:\Talend\5.3.1\JobServer\lib\jmxremote_optional.jar;D:\Talend\5.3.1\JobServer\lib\log4j-1.2.15.jar;D:\Talend\5.3.1\JobServer\lib\commons-io-1.3.2.jar;D:\Talend\5.3.1\JobServer\lib\jsl.jar;D:\Talend\5.3.1\JobServer\sigar-bin\lib\sigar.jar
;param02 = -Djava.library.path=D:\Talend\5.3.1\JobServer\jsysmon-20061229\native\windows\
param02 = -Djava.library.path=D:\Talend\5.3.1\JobServer\sigar-bin\lib\
param03 = -Dcom.sun.management.jmxremote
param04 = -Dtalend_props=D:\Talend\5.3.1\JobServer\conf\TalendJobServer.properties
param05 = org.talend.remote.jobserver.service.WindowsJobServer

Re: tWebService component to work on the jobServer

Anonymous — Tue, 18 Mar 2014 15:25:33 GMT

Hi,
In your jsl_static64.ini i am seing this: jrepath=C:\Program Files\Java\jdk1.7.0_45, your jobserver seems using JDK.
Can you please follow up these step and let me know your feedback:
1) Stop the jobserver services
2) Open the start_rs.bat script and update set MY_JAVA=java with set MY_JAVA="C:\Program Files\Java\jdk1.7.0_45\bin\java"
3) Restart the jobserver
And test if your job will work as expected.
HTH,

Re: tWebService component to work on the jobServer

Philippe_Gagnon_-_RTC — Tue, 18 Mar 2014 16:38:27 GMT

Hello

I change the start_rs.bat file and restart everything but it doesn't solve the issue

I'm not sure if this file is use because my windows service start this file when lauched.
D:\Talend\5.3.1\JobServer\conf\jsl_static64.exe

Here is a copy of the start_rs.bat file

Thank you
Philippe

======================================
@echo off
rem S. Correia
rem Date: 2007 09 26
rem This script executes the Talend Agent
rem Edit the environment variables containing the token MY_ according to the target environment.
rem put the full path to the java executable if the default is not the required one
set MY_JAVA="C:\Program Files\Java\jdk1.7.0_45\bin\java"
rem the root path
set MY_ROOT_PATH=%~dp0
rem The main class to run
set MY_CLASS=org.talend.remote.jobserver.server.TalendJobServerMain
rem for local test with Jconsole:
rem set MY_CLASS=org.talend.monitoring.jmx.api.OSInformationAgent
rem The properties configuration file
set MY_CONF_PROP="%MY_ROOT_PATH%conf\TalendJobServer.properties"
rem set the different classpaths here
set MY_CLASSPATH=%MY_ROOT_PATH%
set MY_CLASSPATH=%MY_CLASSPATH%;%MY_ROOT_PATH%lib\log4j-1.2.15.jar
set MY_CLASSPATH=%MY_CLASSPATH%;%MY_ROOT_PATH%lib\jmxremote_optional.jar
set MY_CLASSPATH=%MY_CLASSPATH%;%MY_ROOT_PATH%lib\commons-io-1.3.2.jar
set MY_CLASSPATH=%MY_CLASSPATH%;%MY_ROOT_PATH%sigar-bin\lib\sigar.jar
rem set the path to the native Sigar library (OS dependent)
set MY_SIGAR_LIB_DIR=%MY_ROOT_PATH%sigar-bin\lib\
rem set the JVM arguments here
set MY_JMV_ARGS=-Dcom.sun.management.jmxremote -Djava.library.path="%MY_ROOT_PATH%sigar-bin\lib>"
rem set MY_JMV_ARGS="-Xms256M -Xmx512M "
rem set the program arguments here
set MY_PROG_ARGS=
REM ##### DO NOT EDIT AFTER THIS LINE #########
set CONF_PROP_ARG="-Dtalend_props=%MY_CONF_PROP%"
rem concatenate all classpaths
set ALL_CLASSPATH=
set ALL_CLASSPATH=%MY_CLASSPATH%
echo %ALL_CLASSPATH%
rem concatenate all jvm arguments
set ALL_JVM_ARGS=
set ALL_JVM_ARGS=%ALL_JVM_ARGS% %MY_JMV_ARGS%
set ALL_JVM_ARGS=%ALL_JVM_ARGS% %CONF_PROP_ARG%
set ALL_JVM_ARGS=%ALL_JVM_ARGS% -Djava.library.path=%MY_SIGAR_LIB_DIR%

rem Java command line
%MY_JAVA% %ALL_JVM_ARGS% -classpath "%ALL_CLASSPATH%" %MY_CLASS% %MY_PROG_ARGS%
http://www.talendforge.org/forum/img/members/152288/mini_130114_2014-03-18 12_26_50-Remote Desktop Manager [srvxatal2 - Serveur d\'ex

Re: tWebService component to work on the jobServer

Anonymous — Tue, 18 Mar 2014 17:37:41 GMT

If you are using Java 1.7 on Windows please update your jsl_static64.exe to a more recent version. This has been reported already to development as a problem with the packaged version:
https://jira.talendforge.org/browse/TUP-1715
Let us know if this helps. Thanks!

Re: tWebService component to work on the jobServer

Philippe_Gagnon_-_RTC — Tue, 18 Mar 2014 19:19:04 GMT

hello

I installed the latest jsl version (try with Release 0.99m and latest 0.99o)
doesn't seem to work either
thank you for your help
Philippe
rtcquebec.ca

here is the log when I start it in debug mode : jsl_static64.exe -debug
:1395169418: Start loading params
Module name decomposed 😧 \Talend\5.3.1\JobServer\conf\ jsl_static64 .exe
Ini file path final D:\Talend\5.3.1\JobServer\conf\jsl_static64.ini
Final ini file decomposed 😧 \Talend\5.3.1\JobServer\conf\ jsl_static64 .ini
Ini file: cmdline =
Finally: cmdline =
:1395169418: Loaded module path
Ini file: jrepath = C:\Program Files\Java\jdk1.7.0_45
Finally: jrepath = C:\Program Files\Java\jdk1.7.0_45
Ini file: jvmtype = server
Finally: jvmtype = server
Ini file: dependencies =
Finally: dependencies =
Ini file: starttype = auto
Finally: starttype = auto Ini fil

To see the whole post, download it here
OriginalPost.pdf

Re: tWebService component to work on the jobServer

Philippe_Gagnon_-_RTC — Tue, 18 Mar 2014 19:25:51 GMT

Hello

additional information

We also have same problem with development workstation.
If we launch the job within talend studio it works fine (screenshot #1)
But if we export the job (run with batch file or run on the target server) the tWebService component give us the same error. (screenshot #2)

thank you
Philippe
rtcquebec.ca

Re: tWebService component to work on the jobServer

Anonymous — Thu, 20 Mar 2014 18:31:25 GMT

Confirmed fix: Remove the JRE and only leave the JDK installed.

Re: tWebService component to work on the jobServer

Anonymous — Mon, 04 Apr 2016 10:12:00 GMT

How to write the fatal error to file in talend using log4j