[#VISIB-45] Plug-in eats up lot of connections. doesn't release it

Confluence Extension: Visibility Plugin

Plug-in eats up lot of connections. doesn't release it

Created: 27/Mar/08 02:18 PM Updated: 18/Aug/08 07:27 AM

Component/s:

{hide-from}, {hide-if}, {show-if}, {show-to}

Affects Version/s:

1.5

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

We are using Confluence 2.5.8 Build:#814 with 2 node cluster, integrated with JIRA

Description

« Hide

We have observed that the connections are not released. After getting more details from Atlassian support, we came to know that one of the candidate might be visibility plugin which is not releasing the connections.

We would like to know from you if you have ever experienced such issues with the 1.5 version and if there is any fix?

Wiki-Support (VV)

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

David Peterson added a comment - 27/Mar/08 02:24 PM

I'm not sure what connections you're referring to (HTTP connections? Database connections?), but none of the visibility macros do anything other than either render or not render the body of the macro, depending if the current context or user matches the requirements in the parameters. These checks are all done using the standard manager objects from Confluence.

As such, I'm not sure how they could be consuming any resources.

Do you have any more details on what the issue is?

[ Permalink | « Hide ]

Wiki Support Team added a comment - 27/Mar/08 02:43 PM

The DB connections. We increased the connection pool size up to 300. but eventually all the connections are blocked and it errors out. casuing confluence to go dow

Wiki Support (VV)

[ Permalink | « Hide ]

David Peterson added a comment - 27/Mar/08 02:55 PM

The macros don't create any direct database connections. They only call standard Confluence objects such as UserAccessor. In fact, other than user data, I don't think they do any database access at all.

If there is a database-related problem due to any calls from visibility macros, the problem is almost certainly in Atlassian's code, not the visibility macros.

Can you get a thread snapshot to determine which classes are invoking the connections which are not being released?