Inbound connection shows connection refused on sender

[Bill Rambo]

I have an odd interface issue. I have an inbound connection from Acudose that sends CHGS to the interface engine. I can see the message coming into the engine and the ACK being sent back to the Acudose server. On the Acudose server, I can see the ACK received and the next message queued up to be sent to the interface engine. But the Acudose server shows connection down. On the Cloverleaf network monitor the connection shows up and according to the log, the engine is ready to receive the next message. The Acudose support tech says the Acudose server is being refused connection. All I do is stop the connection via the Cloverleaf network monitor and restart and the messages begin flowing into cloverleaf. It does not happen on every message just every once in a while. The odd thing is it happens at around 8 minutes after the hour but not at every 8 minutes after the hour. Sometimes it is around 38 minutes after the hour.

This just started happening after we upgraded from 3.7.1P to 5.3 on a new server (HPUX 11.11) using a 1 gig network card. Old server was an IBM AIX running a 100 mb card.

Has anyone else seen this situation?

Thanks,

Bill Rambo

Self Regional Healthcare

Greenwood, SC

Topic

[Anonymous]

Bill,

without looking at the process log it is not easy to say what may have caused this issue.

What you may want to do is that turn on enable_all on in EO config and apply the eo config for both inbound and outboud threads. Stop and start the threads and processes. If a panick occurs, cut and paste the lines contain errors and few lines above into this forum.

Thx

Reggie

[Bill Rambo]

Reggie,

I have done that on the inbound connection. I can see the CHG message come into Cloverleaf and the ACK message go out to the sending server. The problem is the sending server then stops sending because it thinks the Cloverleaf connection is down and not responding. So the sending system continues to poll the connection until I stop and restart the Cloverleaf inbound connection. The Cloverleaf connection always shows UP status and according to the log it is ready to receive the next message. This does not happen on every transmission, just every now and then.

[Traci Zee]

I’m experiencing a similar issue with my first Multi-Server configuration on AIX 5.3, Cloverleaf 5.4 Rev 1.  Have you had any solutions for it?  Any known problems?

TIA,

Traci Zee

[Traci Zee]

Solution found – the sending system was not using the right port.  The confusion was added to because the error was ‘write failed’, instead of no connection.

[Mark Perschbacher]

Just to throw in my two cents, I went round and round with one of our business partners on a similar problem with a result interface.  I loaded a network sniffer, and what I saw was that  with the Cloveleaf box in client mode, the port number on the TCP stack that it was using to acknowledge the ACK from the foreign host kept incrementing up, which is normal.  The issue was that their firewall was allowing these incremeted port packets in, but not back out.  This is a security feature some firewalls have built in to blocking malicious port scanning.  The business partner had to load a new firmware version, and create a firewall entry such that for our address, it would pass any port number coming back out of their network.

[Kevin Scantlan]

It sounds like a firewall issue to me, also.

[Author]

Replies