Rohan,
This message shows that the RMI call is unable to connect to
https://mts.toll.com.au. Knowing a little bit about your architecture, this may be due to a couple of things:
1) Since reverse-proxies are in place ahead of the OTM application, they may not be handling the redirects correctly -- for instance the link
https://mts.toll.com.au/images/spacer.gif should have an associated URL prefix that allows the reverse-proxy to identify the correct back-end system.
2) There may be a bug in the OTM software, that is causing it not to correctly "reverse-proxy enable" this action.
3) It may be that https is not enabled internally and that http needs to be used. For instance, I know that you use https coming into the reverse-proxy, but use http for everything behind that. As a result, I'm not sure if your basic OTM instance is https enabled.
Thanks,
Chris