You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex Murashko (JIRA)" <ju...@ws.apache.org> on 2008/07/24 12:07:32 UTC
[jira] Created: (JUDDI-128) Connections leak in at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Connections leak in 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 connection leak at
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
--
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
[jira] Closed: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
[ 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
[jira] Assigned: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam reassigned JUDDI-128:
-------------------------------
Assignee: Kurt Stam (was: Tom Cunningham)
> 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
[jira] Updated: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Alex Murashko (JIRA)" <ju...@ws.apache.org>.
[ 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 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
was:
There is connection leak at
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 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
--
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
[jira] Updated: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Alex Murashko (JIRA)" <ju...@ws.apache.org>.
[ 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: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org
[jira] Updated: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
[ 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
[jira] Updated: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Alex Murashko (JIRA)" <ju...@ws.apache.org>.
[ 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 also invoked in happyjuddi.jsp.
This may lead to pool exhaustion
was:
There is 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 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
[jira] Updated: (JUDDI-128) Connections leak at
org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249)
Posted by "Alex Murashko (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Murashko updated JUDDI-128:
--------------------------------
Summary: Connections leak at org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249) (was: Connections leak in at org.apache.juddi.registry.RegistryEngine.initializeDatabase(RegistryEngine.java:249))
> 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 connection leak at
> 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
--
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