Hello,

We are trying to post transactions using HTTPS with DNS Entry, We are facing below issue

when using pub.client.http service, its giving this error as - com.wm.app.b2b.server.ServiceException: org.apache.axis2.AxisFault: java.net.UnknownHostException:

soapClient and http client both has same issue

Things that are checked -

1. Host Entry is properly done
2. No firewall blocking/port is open, we are able to post using IP but not using DNS.

This issue is not only for particular partner system but for all HOST ENTRIES/DNS. -

AIX Server - We found some discrepancies with procfiles being created with 0 bytes with interactions of IS with Server which are related to Cache/repository pileup.

So we tried clearing the folders as IS has the ability to regenerate the files which might resolve the issue, but no luck as issue still persists.

Folders cleared - under Instance
1.db
2.cacheStore
3.WmRepository4
4.DocumentStore

Can someone please provide some insides on how to resolve this issue?

Hi Sai,

have you tried to check the dns resolution with “nslookup”?
Eventually you have to check with your OS Admin, if the nslookup.conf, resolv.conf etc. are configured properly.

Regards,
Holger

Hello Holger,

yes DNS resolution works fine. We are getting proper/correct IP

Previously this issue can be resolved by restarting IS, but now even after restart issue still persists.

note - this is not only for 1 entry but for multiple DNS Entries.

Hi Sai,

when it works locally outside IS but not from inside IS, this needs to be investigated further.
But this is not possible with the informations currently provided in this thread.

You might want to check to increase the log level for certain IS Log Factories to get more informations why looking up the adresses fails.

See IS Administrators Guide for further informations.

Regards,
Holger

Hello,

We have tried enabling Logs with trace and below are the details.

Logs

2024-07-17 00:54:03.700 GMT+05:30 [ISS.0015.0005D] Invoking service pub.client:http.
2024-07-17 00:54:03.700 GMT+05:30 [ISS.0014.0016T] Invoking service pub.client:http
2024-07-17 00:54:03.700 GMT+05:30 [ISS.0007.0004T] ACLManager: allow check for user “local/Administrator” on ACL “Internal” is returning true.
2024-07-17 00:54:03.701 GMT+05:30 [ISC.0064.0015T] Opening Socket https://[URL]
2024-07-17 00:54:03.771 GMT+05:30 [ISU.0000.9999D] InfraDC: Service Error Event pub.client:http
2024-07-17 00:54:03.772 GMT+05:30 [ISS.0142.0002D] Unregistered Lifecycle Listener com.wm.app.b2b.server.HTTPMessageLifecycleListener@373db42e is true
2024-07-17 00:54:03.772 GMT+05:30 [ISC.0038.0002D] → HTTP/1.1 403 Service Error
2024-07-17 00:54:03.772 GMT+05:30 [ISC.0038.0002D] → Content-Type: text/html; charset=UTF-8
2024-07-17 00:54:03.773 GMT+05:30 [ISC.0038.0002D] → Content-Length: 9058
2024-07-17 00:54:03.773 GMT+05:30 [ISS.0048.9999D] Servername
2024-07-17 00:54:03.773 GMT+05:30 [ISU.0000.9999D] InfraDC: ISDCNotificationQueue sending isextdc.logmessage to queue
2024-07-17 00:54:03.773 GMT+05:30 [ISU.0000.9999D] InfraDC: Service Error Event null
2024-07-17 00:54:03.773 GMT+05:30 [ISU.0000.9999D] InfraDC: ISDCNotificationQueue sending isextdc.logmessage to queue

Exception

INFO | jvm 1 | 2024/07/17 00:21:54 | java.net.UnknownHostException: [DNS]
INFO | jvm 1 | 2024/07/17 00:21:54 | at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:214)
INFO | jvm 1 | 2024/07/17 00:21:54 | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
INFO | jvm 1 | 2024/07/17 00:21:54 | at java.net.Socket.connect(Socket.java:666)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.ext.jsse.JSSESecureSocketFactory.newSocket(JSSESecureSocketFactory.java:539)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.ext.jsse.JSSESecureSocketFactory.createSocket(JSSESecureSocketFactory.java:468)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.socket.pool.SocketPool.getSocketWrapper(SocketPool.java:197)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.socket.pool.SocketPoolManager._getSocketWrapper(SocketPoolManager.java:129)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.socket.pool.SocketPoolManager.getSocketWrapper(SocketPoolManager.java:111)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.NetURLConnection.getSocket(NetURLConnection.java:980)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.NetURLConnection.openDirectConnection(NetURLConnection.java:958)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.NetURLConnection.connect(NetURLConnection.java:173)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.HttpURLConnection.getOutputStream(HttpURLConnection.java:439)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.HttpContext.getOutputStream(HttpContext.java:927)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.HttpContext.getOutputStream(HttpContext.java:903)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.net.HttpContext.post(HttpContext.java:531)
INFO | jvm 1 | 2024/07/17 00:21:54 | at pub.clientimpl.http(clientimpl.java:959)
INFO | jvm 1 | 2024/07/17 00:21:54 | at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source)
INFO | jvm 1 | 2024/07/17 00:21:54 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
INFO | jvm 1 | 2024/07/17 00:21:54 | at java.lang.reflect.Method.invoke(Method.java:508)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:404)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:748)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:50)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:299)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:377)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:626)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:441)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:397)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:252)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:120)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:156)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:181)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:397)
INFO | jvm 1 | 2024/07/17 00:21:54 | at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
INFO | jvm 1 | 2024/07/17 00:21:54 | at java.lang.Thread.run(Thread.java:785)

Please do let us know if we are able to find the resolution with this logs.

Hello Team,

We found the issue with OS trying to fetch details from resolv.conf instead of /etc/hosts.
When we removed permission to invoke resolv.conf, We can see that procfiles of OS are reduced and host resolution started working.

Thanks to all for your inputs.

Hi,

additionally check the nsswitch.conf and nslookup.conf in the /etc directory (there might be some other conf-files starting with ns*, check these as well) for the order in which the different dns a queried for resolution.
Usually you would like to check the real dns server before reverting back to the hosts file.

Remember, that these files can be updated automatically by a central configuration repository tool (like i.e. Puppet) depending on how your company is handling this. If this is the case, make sure that repository is updated correctly and it replicates this data correctly to the physical hosts.

Regards,
Holger