com.sap.smd.server.util.concurrent.TimeoutException

[Former Member]

Hi,

I am getting the above TIme Out Exception and the Agents get disconnected.

Although I have updated the below Parameters :

smdserver.connection.interval=120000 in the runtime.properties of the Agent.

smd.asio.remote.time.out.ms in the Service.properties.

Anything else I need to update since my Agents are still reading the limit as 30000 ms.

Error Ping failed (com.sap.smd.server.exec.asio.TimeoutError) com.sap.smd.server.util.concurrent.TimeoutException [EXCEPTION] Time out occured when calling method 'ping' on object [com.sap.smd.api.ISMDServerHandle_Stub@7774c29a] after 30001 ms.possible cause:

com.sap.smd.server.util.concurrent.TimeoutException

at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:140)

Regards,

Kaustubh.

[Former Member]

Hello,

Please increase parameter smd.asio.remote.time.out.ms to 100000 as was said in note.

1751496 - Agent is showing intermittently in the Agent Administration

BR,

Kamil

[Former Member]

Hi Kamil,

I have already applied the parameter as per the Note suggested by you. The default value was 60000 and I have increased it to 600000. DO you mean I have to increase it further ?

I took hint from the Note which says to add a Zero to the existing value.

Regards,

Kaustubh.

[Former Member]

Hi,

Have you restarted the SMD agents

Please follow all the steps of the below note.

• Restart the SMD Agent to apply the new value
• Delete all log files of these agent before restart them
• Monitor the log the validate if this new timeout value solve the issue and then could be applied to the all other diagnostics agents

1842840  - Diagnostics Agent disconnecting from Solution Manager System

Thanks

Rishi abrol

[Former Member]

Hi Rishi,

I have already gone through the note Mentioned and applied the parameters as above in my post.

But still I am getting the time out issue.

I have followed the stop- delete logs -- re-run smdsetup.bat and then start cycle with all the agents involved.

Regards,

Kaustubh.

[Former Member]

Hi,

When this issues start. have you recently patched the kernel of your solution manager.

Can you please check that the below url shows you the P4 port

http://<solmal_msg_server_host>:<j2ee_msg_server_http_port>/msgserver/text/logon

Please try the below stesp.

1. Go to agent admin and enable Maintenance Mode
2. Go to tab advanced settings
3. Increase the value as follows
   smd.asio.remote.time.out.long.ms = 1800000
   smd.asio.remote.time.out.ms = 60000
4. Go to NWA page and restart the service
   tc~smd~server~service
5. Go to agent admin and disable Maintenance Mode
6. Restart smd agent

For more info read note this.

1870702  - "Agent Registration failed " "Registration REJECTED" appear in Diagnostics Agent logs - ...

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

Thanks for the suggestions.

P4 Port is visible.

I had only upgraded the Kernel as per SAP note 1878116. But, the issues have been seen before and after.

I had already increased the parameters for timeouts.

smd.asio.remote.time.out.long.ms = 1000000

smd.asio.remote.time.out.ms = 600000

Regards,

Kaustubh.

[Former Member]

Hi,

I think you might have to still increase it to 1800000 as per the not still it doesn't fixes than might be better to check with sap.

Sap also says

If the issue is not solved, you must check your network performance by using commands such as ping and traceroute.

If no network performance issue is found, open a message in SV-SMG-DIA-SRV-AGT

More information regarding the handling of agents on the server side.
SMD server uses some key to identify an agent.
We distinguish 2 cases:

1. The agent does not have a server name. The keys to lookup the
   agent are the host name, the agent FQN, the agent ID, and the IP.
2. The agent has a server name: only this value is used as a key in
   a unique way

Can you also check what is the kernel version of your SMD agents.

Note 1707141 - Diagnostics Agent - How to upgrade SAP Kernel

Hope it helps.

Just wanted to to know your initial and target kernel version.

Thanks

Rishi abrol