I have a situation where if I start the slave agent using the jnlp, sikuli 
runs from my test architecture (java based calling older rc3 sikuli) just 
fine.  If i start the same agent in headless mode then there is a linking 
issue that the sikluli dlls cannot be found.  Clearly my path statement and 
all that are setup correctly because if I use the jnlp it works just fine.  

This is my jnlp:
<jnlp spec="1.0+" 
codebase="http://cmfalgadwts1v.comfin.ge.com:8083/computer/CMF-TL50W71/";><information><title>Slave
 
Agent for CMF-TL50W71</title><vendor>Jenkins project</vendor><homepage 
href="https://jenkins-ci.org/"/></information><security><all-permissions/></security><resources><j2se
 
version="1.5+"/><jar 
href="http://cmfalgadwts1v.comfin.ge.com:8083/jnlpJars/remoting.jar"/><property 
name="hudson.showWindowsServiceInstallLink" 
value="true"/></resources><application-desc 
main-class="hudson.remoting.jnlp.Main"><argument>24cb861434e134376984c8c8d72bedf85c9f981581a170675cfe9b1a51194fdd</argument><argument>CMF-TL50W71</argument><argument>-url</argument><argument>http://cmfalgadwts1v.comfin.ge.com:8083/</argument></application-desc></jnlp>

This is my batch file to start the headless agent:
"%JAVA_HOME%\bin\java.exe" -Dhudson.util.ProcessTreeKiller.disable=true 
-jar C:\Jenkins\slave.jar -jnlpUrl 
http://cmfalgadwts1v.comfin.ge.com:8083/computer/CMF-TL50W71/slave-agent.jnlp 
-secret 24cb861434e134376984c8c8d72bedf85c9f981581a170675cfe9b1a51194fdd

JAVA_HOME is pointing to the jdk1.7.0_45 directory

The jnlp is associated with the javaws from the jdk bin folder as well.

Thoughts?  Something must be different in how java is processing these 2 
for it to not be able to find the dlls properly.  I have tried many things 
including adding the sikuli libs folder as a -Djava.library.path= in my 
batch file, still doesnt work.  Thanks for the help.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to