× 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.




Hi Dick,

The database is "not ready",

Interesting. Are you using the Toolbox or native JDBC driver? Just trying to relate to something to do with TCP/IP.


Joe Sam

Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400

----- Original Message ----- From: "Dick Balaska" <dick@xxxxxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400" <java400-l@xxxxxxxxxxxx>
Sent: Tuesday, June 10, 2008 1:43 PM
Subject: Re: java.net.SocketException: The protocol required to support thespecified address family is not available at this time.


I've seen this message. When tomcat comes up during the IPL, my webapp
throws this. The database is "not ready", although i'm not sure why
since the database comes up waaay before tomcat. I wrap the getConfig
query in my serlvet's init which sleeps on the error.
I always thought that it was interesting that this message is deceptive
to the actual problem.

I've never seen it while the system is actually running.

Dick Balaska

On 6/9/2008 11:19 AM also sprach Thorbjørn Ravn Andersen :
I had an interesting problem today, namely that I had the following in
my log, in the process of getting an AS400 connection to the local machine.

java.net.SocketException: The protocol required to support the specified
address family is not available at this time.
at
java.lang.Throwable.<init>(Throwable.java:195)

at
java.lang.Exception.<init>(Exception.java:41)

at
java.io.IOException.<init>(IOException.java:40)

at
java.net.SocketException.<init>(SocketException.java:29)

at
java.net.SocketInputStream.read(SocketInputStream.java:129)

at
com.ibm.as400.access.ClientAccessDataStream.construct(ClientAccessDataStream.java:46)

at
com.ibm.as400.access.AS400ThreadedServer.run(AS400ThreadedServer.java:321)

at
java.lang.Thread.run(Thread.java:534)



I could only find a single hit on google which said that TCP/IP had
vanished for the subsystem and that it was recommended to restart the
subsystem.

Has anybody ever seen this message before?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.