Re: Communication link failure -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Communication link failure
From: Thorbjoern Ravn Andersen <ravn@xxxxxxxxxx>
Date: Thu, 05 Mar 2009 18:05:04 +0100
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Glenn Holmer skrev:

Is anyone familiar with this type of exception? We had a whole storm of
them over a couple days, but our iSeries tech guys can't figure out what
might have caused it. How to diagnose and/or prevent something like
this?

What network equipment is between the Tomcat instance and the AS/400?

This could be a silently dropped connection due to inactivity over the TCP/IP connection. If so, your database pool must either keep pooled connections alive or implement some "drop when inactive" mechanism itself.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.