You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt Stam (JIRA)" <ju...@ws.apache.org> on 2008/09/08 03:54:44 UTC

[jira] Updated: (JUDDI-128) Connections leak at org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)

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

Kurt Stam updated JUDDI-128:
----------------------------

    Fix Version/s: 2.0rc6
         Assignee: Tom Cunningham  (was: Kurt T Stam)

Tom can we fix this for 2.0rc6?

> 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: Tom Cunningham
>             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