Re: JDBC woes
Re: JDBC woes
- Subject: Re: JDBC woes
- From: Chuck Hill <email@hidden>
- Date: Wed, 04 Jun 2003 14:43:06 -0700
Seems to be the day for this problem...
The wo adaptor (the one the websever talks to) will only wait for a
specified amount of time for a response. After that it hangs up on the app
and tries another instance (if there is one). When the app processing the
original request goes to return the response it finds that the adaptor is
no longer listening hence it can not send the response. What you get in
this case is a java.io.IOException: Broken pipe, meaning "Hey! The adaptor
is not listening to me anymore!" You can either make the request process
faster (maybe not an option) or ask the adaptor to wait longer. The latter
is done by setting the connect and receive timeouts in JavaMonitor. This
won't happen in developement mode if you are using Direct Connect as the
adaptor is not involved.
HTH
Chuck
At 05:31 PM 04/06/2003 -0400, Rob Caljouw wrote:
>Hi List,
>
>We're trying to deploy a D2JC application on an Xserver running 10.2.6 and
>WO 5.2.1.
>
>The app was developed on 10.2.6 and WO 5.2.1. Everything works well in the
>development environment but in production deployment there is a problem with
>one of the JDBC connections.
>
>We are connecting to an AS400 using the IBM JDBC driver from the development
>machines and the Xserver.
>
>When the application runs on the server it throws the following exception:
>
>Exception while sending response: java.io.IOException: Broken pipe
>
>We have made sure the JDBC jar files are the same in both environments.
>
>We have turned on debugging in development and production and everything is
>the same with respect to the SQL that is generated. The database on the 400
>contains about 480,000 rows and calls take about 15 - 20 seconds to return
>in the development environment. The time between the initial SQL generation
>and the exception on the server seems to be about the same. It is as though
>the connection to the client is broken. We have set the WOSessionTimeOut on
>the application to 24 hours and it seems to work fine.
>
>Any suggestions would be greatly appreciated.
>
>Thanks in advance,
>
>--
>R.J. (Rob) Caljouw, P.Eng.
>President
>Bennett Technology Group, LLC.
>Phone: 770-957-1866 (537)
>
>_______________________________________________
>WebObjects-dev mailing list
>email@hidden
>http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >JDBC woes (From: Rob Caljouw <email@hidden>) |