cancel
Showing results for 
Search instead for 
Did you mean: 

Mail: error occured: java.net.ConnectException: Connection timed out

Former Member
0 Kudos

Hi Experts,

we have encounterd following error for Mail interface in Production Server and message is in System Erro status in Seeburger Adapter Engine,

2011-02-10 13:31:42 Error Mail: error occured: java.net.ConnectException: Connection timed out

2011-02-10 13:31:42 Error Mail: error occured: com.sap.aii.af.lib.mp.module.ModuleException

2011-02-10 13:31:42 Error Adapter Framework caught exception: Failed to call the endpoint

2011-02-10 13:31:42 Error Delivering the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint [null "null"]; nested exception caused by: java.net.ConnectException: Connection timed out.

2011-02-10 13:31:42 Error The message status was set to NDLV.

Please advise what can be done.

Regards,

Nitin

Accepted Solutions (0)

Answers (3)

Answers (3)

Shabarish_Nair
Active Contributor
0 Kudos

com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint null \"null\"; nested exception caused by: java.net.ConnectException: Connection timed out.

this is predominantly a connectivity issue.

have you basis team check if your PI server is able to ping the mail server.

You might have to open some ports to have this connection established

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>>2011-02-10 13:31:42 Error Mail: error occured: java.net.ConnectException: Connection timed out

>>2011-02-10 13:31:42 Error Mail: error occured: com.sap.aii.af.lib.mp.module.ModuleException

>>2011-02-10 13:31:42 Error Adapter Framework caught exception: Failed to call the endpoint

The above error is due to network connectivity. This issue might be due to firewall does not allow the server to connect or proxy issues or invalid endpoint such as server/port details... Anything has changed recently that is causing this error?

shweta_walaskar2
Contributor
0 Kudos

Hi Nitin,

Following link addresses the same issue:

Regards,

Shweta