[
https://issues.apache.org/jira/browse/JUDDI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Murashko updated JUDDI-128:
--------------------------------
Description:
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
was:
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 also
invoked in happyjuddi.jsp.
This may lead to pool exhaustion
> 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 T Stam
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
