|
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
owensjim
Joined: 08 Aug 2011 Posts: 49
|
|
mix matching versions - is this a problem? |
|
We built a VM linux server.
installed java 1.5
downloaded the most recent version of job scheduler from the website and have the 30 day trail version
unzipped the package
copied the members to Linux server
installed job scheduler per instructions
When trying to connect the agent from our old version of JS 4.1 build 255 to your most current version which we have the 30day trial version
Are we running into a key conflict?
Can we mix-match versions and continue processing?
Do we need to run the older JS source?
We are receiving the following message in the debug log on job scheduler:
java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at com.softtreetech.jscheduler.business.agent.remote.RemoteAgentImpl_Stub.checkLicense(Unknown Source)
at com.softtreetech.jscheduler.business.runner.RemoteJobRunner.runJob(Unknown Source)
at com.softtreetech.jscheduler.business.runner.AbstractJobRunner.oO0000(Unknown Source)
at com.softtreetech.jscheduler.business.runner.AbstractJobRunner.Object(Unknown Source)
at com.softtreetech.jscheduler.business.runner.AbstractJobRunner.execute(Unknown Source)
at com.softtreetech.jscheduler.business.runner.JobExecutorImpl.execute(Unknown Source)
at com.softtreetech.jscheduler.business.runner.JobExecutorImpl$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
... 12 more
|
|
Wed Aug 31, 2011 10:20 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
|
|
The agent and scheduler should have the same significant version 4.4, the build number is not important.
Also, please verify you are connecting scheduler to the agent, not the other way around. In other words, in the scheduler settings you need to setup remote agent profile and specify connection properties for the agent.
|
|
Wed Aug 31, 2011 1:06 pm |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|