Cain
Posts: 86
|
| Posted: 11/11/2004, 12:57 PM |
|
I am a big newbie to codecharge, but I am liking it so far.
I got a call recently from our server guy who advised me that I had a bunch of idle connections to our database.
As I used codecharge to autogenerate as much as possible, I am not sure what the problem is.
I read somewhere that for oracle there was an issue with Persistent Connections which I did select for this project.
Any ideas how I can correct this?
Other than that I am liking code charge so far.
|
 |
 |
peterr
Posts: 5971
|
| Posted: 11/11/2004, 4:14 PM |
|
I am not sure what the problem is, but if you don't see other responses on the forum please contact http://support.yessoftware.com for help.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
klw
|
| Posted: 11/11/2004, 5:17 PM |
|
Cain, are you using persistent connections? That may be the problem.
This brings up an issue I came across with persistent connections.
I found out I needed them when submitting a record form, otherwise
the state of some of the fields (when posting back to the same form)
were lost.
Has anyone else seen this problem, and how did you resolve it? 
|
|
|
|
Cain
Posts: 86
|
| Posted: 11/12/2004, 8:46 AM |
|
I am using persistent connections. I have since turned them off but still waiting for word if I am getting the same connection issue. Will let you know if it clears up.
|
|
|
|
NR
|
| Posted: 11/16/2004, 5:44 PM |
|
Caim, Persistent connections are supposed to speed up things.
What I found in environments using PHP/PostgreSQL (RH9/AS3.0) is that connections are not reused unless for exactly similar transactions.
If you have a 'form' for intensive data input, for instance same kind of repetitive insert, persistent connections will work fine. For a more common use, with a lot of different transactions (different insert/update/delete code from a lot of 'forms') then database idle connections will 'pile up' without beeing reutilized, untill the point you ran out of processes.
For this particular environment I found the only solution to be deactivate persistent connections (if you use PHP you can do it in php.ini whitout need to change DB connection in CCS project).
Of course your problem might be a different one. Even in the environment I work on things were not always this way: in older versions (RH7.x) processes get reused and idle processes were killed after a while. Things changed with RH8, perhaps some issue on new releases of PHP.
PS: klw, I don't use persistent connections and every fields is ok after submmit, that is not an issue from persistent connections.
|
|
|
|
|
