2 of 2 people found this helpful
i've never seen this error before..
...but with the newer ARS versions there is a Service Failover mechanism and if you have more than one AR Server (aka Server Group) you can split the load (if you have different Incoming and Outgoing mailboxes) to different AR Servers.
You only have to change the ranking in the form "AR System Service Failover Ranking"
good luck ;-)
Have you tried checking with network team since this seems to be a problem or latency with Remedy Email to Exchange communication.
Since this is being the Solaris environment which also has the local send mail service.
1 of 1 people found this helpful
So a “read“ time-out has nothing to do with sending or connecting to the mail server. The “read” means your remedy system cannot read What it needs to in order to complete the transaction for the java plugin.
typically this is due to a lack of resources And/or limitations. Version 9 versus version 8 does use more java memory, was that tuned correctly? Do you have enough threads? Have you ran thread logs and looked at that? In the java lib directory there is a logging.properties file can you look at the level of logging you’re doing? Default is typically set to severe so you won’t get much detail. here is documentation on the logging Debugging options for the BMC Remedy Email Engine - Documentation for Remedy Action Request System 9.1 - BMC Documentati…
Another point is if your plugin is crashing and armonitor is restarting it, it may not have all the environment variables set correctly like when remedy starts up. Validate the CLASSPATH, JRE_HOME and PATH are correct and that each java process in armonitor has the correct java version and CLASSPATH.
there were features in the old java versions which were sunset and in java 8 there are completely new parameters to use to fine tune the performance , were those set?