Re: java.net.SocketException: The protocolrequired tosupport thespecifiedaddress family is not available at this time.

Hi Dick,

I agree with you. I missed at first that you mentioned it happened at
IPL time. I still believe it's TCP/IP related (although I may be led down
the wrong path by the error,) but now think that DB2 may take some time to
be ready for connections via TCP/IP. It does have to start up a server to
listen on port 8471 (default,) and I would expect that to be about the last
thing to run in the database start up process.

I doubt any of us have the time, but it might be interesting to try the
native driver (doesn't use TCP/IP) to see if the same result occurs. But
your solution (sleep and retry) sounds right to me for start up. Bis
später,


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: Thursday, June 12, 2008 3:12 AM
Subject: Re: java.net.SocketException: The protocolrequired tosupport
thespecifiedaddress family is not available at this time.

It does imply that tomcat isn't ready. Except that if i start tomcat by
hand with the CMD QSH string (however it is, i'm a 'nix and 'doze guy
swimming in os/400) then it lights up without errors. It's only during
IPL that i see this anomaly. catalina.out reveals nothing significant.

I have another webapp that does an sFTP out as soon as it comes up, so
TCP/IP is ok. It smells like the database just doesn't want to talk to
me for another couple of minutes.

Tchus!

On 6/10/2008 2:55 PM also sprach Joe Sam Shirah :

Hi Dick,

<string value="jdbc:as400://MYMACHINE/MYDATABASE"/>

That's the connection URL, not the driver. But, since the subprotcol
is
"as400", that tells me it's the Toolbox driver. As a Type 4, "thin"
driver,
it does use TCP/IP.

In your case, given your solution, it seems to apply to Tomcat
initialization not being complete when access is attempted. Don't know
if
that applies to the OP. Vielen Dank!