Absent Member.. Absent Member..
Absent Member..

The connection between DataFlow Probe and UCMDB is not stable because of F5?

Issue: The connection between DataFlow Probe and UCMDB is not stable, is it because of F5?


OS details:

UCMDB DataFlow Probe(V10.10) Server: win2008 standard SP2(64bit)

UCMDB Server(V10.10): win2008 enterprise R2(64bit)


Deployment info:

2 UCMDB Servers with 1 UCMDB Writer Float IP which is configured in F5(V10) Load Balancer.

2 UCMDB DataFlow Probe Servers on another 2 machines


Issue details:

1.The Probe status in "DataFlow Probe Setup" Pannel, switch between "disconnect" and "connected" frequently.

2.If configure 1st  DDM with float UCMDB IP, the connection is still un-stable; 2nd  DDM with static UCMDB IP the connection seems OK.

3.And in Probe log, I can see such error info which shows the communications between DDM and UCMDB Float IP is bad:


Connection reset by peer: socket write error


   I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: socket write error


   Failed sending results to the server, will retry later


   java.net.SocketException: Software caused connection abort: recv failed


   java.net.SocketTimeoutException: Read timed out



1. Does any one have some similiar experience or give some suggestion?

2. It seems the F5 not working very properly, hope for some F5 expertise.

Very appreciated for that!!!



Have a good day!


Thanks& BRs


email: yuanji.xuan@hp.com





2 Replies
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: The connection between DataFlow Probe and UCMDB is not stable because of F5?

This error can occur when the local network system aborts a connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).

Please work with F5 support, it most probably will end up there.

-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
Absent Member.
Absent Member.

Re: The connection between DataFlow Probe and UCMDB is not stable because of F5?

Thanks a lot! I also considered whether F5 is wrong.


So I checked the communication between F5 and UCMDB Writer Server, it seems F5 working fine, but the UCMDB Writer Server can't update timestamp and caused the response timeout.

I don't know how to move on, is anyone has some idea?



Check details:

1. I checked F5 local traffic, The heal monitor result told the UCMDB Writer Server down:


Sat Apr 26 04:09:31 MMT 2014 notice local/YGNDC-F5-01 mcpd[5072] 01070638 Pool member monitor status down.

Sat Apr 26 04:09:37 MMT 2014 notice local/YGNDC-F5-01 mcpd[5072] 01070727 Pool member monitor status up. 



2. I also used the WireShark to monitor the TCP Packages on UCMDB Writer Server, when such issue occured, there is no response from UCMDB Writer Server to F5.


3. And I check the UCMDB HA Log, it seems UCMDB Writer faced some issue and failed to update timestamp& response:


2014-04-25 14:41:47,107 [INFO ] This server (BOTITSAPPV1015_1398442176699) is going to be the writer, because the writer (BOTITSAPPV1015_1398333093189) did not update its timestamp for more than: 164 seconds

2014-04-25 14:41:47,107 [INFO ]                (current DB time: 1398413507, writer timestamp was:1398413343, writer inactivity period threshold:120)

2014-04-25 14:41:47,107 [INFO ] serverId:BOTITSAPPV1015_1398442176699 is now the writer.

2014-04-25 14:41:47,200 [INFO ] HA sync model: URM_customerId_-2147483648 started to load from revision: 351




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.