SOAP unable to create a socket after OS upgrade OS/400 V5R4 to V7R1

[matthias_sander]

Hello,

after we upgraded our OS from System i V5R4 to V7R1 we have problems with our SOAP adapters.

In the runtime workbench and also in the SXMB_MONI the following error occured:

SOAP: call failed: java.io.IOException: unable to create a socket

Message-Verarbeitung fehlgeschlagen. Grund: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket

Before the OS upgrade the adapter rans without any errors and we tested the connection to the partner

with an system running V5R4 with success. So it seems to be an error that came with the OS upgrade.

Any idea? Had any one the same error after migration to V7R1? Thanks for your help.

Best regards,

Matthias

[rajasekhar_reddy14]

Hi,

it looks network issue. could you please check with network team like port opened or not.after OS upgrade there was some influence on network settings.

Regards,

Raj

[matthias_sander]

Hi,

that is what I expected too, but i can't find any informations in the log which port can't bind.

Is there any possibility to find out which port effected the error?

Matthias

[matthias_sander]

Hello,

we found out that the error is attached to DNS and Java stack. Our ABAP stack can set the url to the correct IP adress, if we configure a entry in SM59. Also the java stack calls our partner over SOAP with IP adress, but not with url. The urls are stored in the local host table, so we suppose that the java stack doesn't use the local dns table and doesn't ask our dns server for the right ip adress.

Does anybody know this issue? The only change we did is upgrade OS/400 from V4R4 to V7R1. If a mod see this, I think it make sence to move this thread into the forum SAP on DB2 UDB for i5/OS (DB4). Thank's.

Matthias

[matthias_sander]

Hello,

the problem is connected to the SAP JVM and IPv6. The IPv6 stack was active, but only with the standard parameters and no further configuration. With the new release V7R1 and SAP JVM 5 patch 41 (I know this is an old patch) the DNS resolving doesn't work correctly. In consequence of this no SOAP adapter works, because we using host names and no ip adresses in the configuration.

After deactivating the IPv6 stack the problem doesn't occured any more. In the future we plan to patch the SAP JVM at the most current level and test the JVM with IPv6 again. Problem is solved.

[matthias_sander]

Has nobody an idea?