DVIPA monitoring during logon shows an almost equal number of packets going to both the ASYS and BSYS LPARs.

Why is the updated WebSphere service pack level (WebSphere level 8.5.5.16 and later) triggering what appears to be a persistence problem between DVIPA, IDS, and the WebSphere servers HTTPS communications from the 12.1 Web Viewer application when the Load Balancing is being used?

Trace: 2020/06/18 10:26:49.549 02 t=8A5C68 c=UNK key=P8 tag= (13007004)

SourceId: com.ibm.ws.runtime.component.ThreadMonitorImpl

ExtendedMessage: BBOO0221W: WSVR0605W: Thread "WebSphere WLM Dispatch Thread t=008aae88" (00000093) has been active for 691977 mil

liseconds and may be hung. There is/are 2 thread(s) in total in the server that may be hung.

at com.ca.erm.webviewer.data.RepositoryBean.isConnected(RepositoryBean.java:852)

at com.ca.erm.webviewer.control.RepositoryDetailBean.isShowFileUpload(RepositoryDetailBean.java:725)

at sun.reflect.GeneratedMethodAccessor346.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

at java.lang.reflect.Method.invoke(Method.java:508)

at com.sun.faces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:79)

at com.sun.faces.el.impl.ArraySuffix.evaluate(ArraySuffix.java:167)

at com.sun.faces.el.impl.ComplexValue.evaluate(ComplexValue.java:151)

at com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)

at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)