java - Quartz RMI remote server returning invalid hostname -
i have 2 processes on separate servers. 1 running quartz scheduler , want connect other manage triggers.
on scheduler server config is:
org.quartz.scheduler.rmi.export = true org.quartz.scheduler.rmi.createregistry = org.quartz.scheduler.rmi.registryhost = localhost org.quartz.scheduler.rmi.registryport = 1099 org.quartz.scheduler.rmi.serverport = 1100
on remote server config is:
org.quartz.scheduler.rmi.proxy = true org.quartz.scheduler.rmi.registryhost = ip-172-16-5-11.eu-west-1.compute.internal org.quartz.scheduler.rmi.registryport = 1099
when try , connect remote scheduler following error in log:
error [2016-07-28 09:10:23,017] xxxx: error communicating remote scheduler. ! java.net.connectexception: connection refused ! ... 83 common frames omitted ! causing: java.rmi.connectexception: connection refused host: log-emea-1; nested exception is: ! java.net.connectexception: connection refused
although host host on our network have no idea why being returned remote registry.
there no connectivity issues. if run tcpdump on remote machine can see connecting scheduler. it's scheduler returning invalid host:
09:19:02.047589 ip 172.16.5.11.1099 > 172.16.0.81.54065: flags [p.], seq 19:235, ack 105, win 210, options [nop,nop,ts val 1231389006 ecr 562121102], length 216 e.....@.@..........q.k.1}.z... ......c..... ie.n!.i.q....w..9.e2...v0.|...sr.$org.quartz.core.quartzscheduler_stub...........pxr..java.rmi.server.remotestub......e....pxr..java.rmi.server.remoteobject.a...a3....pxpw3. unicastref. log-emea-1...l/8. .a.69.e2...v0.|....x
where quartz rmi registry getting hostname from? there no clues in hosts file or dns. appears random.
you start scheduler following jvm-flag
java -djava.rmi.server.hostname=...
(see rmi-faq or why java rmi keep connecting 127.0.1.1. when ip 192.168.x.x?)
Comments
Post a Comment