Mailing-List: contact juddi-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: juddi-dev@ws.apache.org
Message-ID: <720249755.1228451084387.JavaMail.jira@brutus>
Date: Thu, 4 Dec 2008 20:24:44 -0800 (PST)
From: "Kurt Stam (JIRA)" <juddi-dev@ws.apache.org>
To: juddi-dev@ws.apache.org
Subject: [jira] Closed: (JUDDI-128) Connections leak at
 org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
In-Reply-To: <1435219966.1216894052143.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JUDDI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam closed JUDDI-128.
---------------------------

    Resolution: Fixed

Now closing the connection

> Connections leak at org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-128
>                 URL: https://issues.apache.org/jira/browse/JUDDI-128
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 2.0rc5
>         Environment: ANY
>            Reporter: Alex Murashko
>            Assignee: Kurt Stam
>             Fix For: 2.0rc6
>
>
> There is a connection leak 
>  at org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
> Connection is not closed if database scheme already initiated
> This method is normally invoked 1 time during servlet startup, but it's also  invoked in happyjuddi.jsp.
> This may lead to pool exhaustion

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org