I have observed this on a couple of occassions before and was finally able to get all the information I could possibly get. Attached to this bug is a thread dump of a tomcat 4.1.30 container running confluence. For some pages (I have not yet figured which one's), adding and trying to subsequently modify the content of the page results in locked threads.

The attached log file has 2 thread dumps; the first dump shows TP-Processor6 waiting on some locks.. the second dump taken after a while when porforming the same update operation on the same page shows TP-processor3 locked with similar stack trace and locks.

Please let me know if I can provide any other information to help resolve this issue. Thanks.

The content of the page is below:

----------------------------------------------------------------------------------------------------------------------------------------------------------

Initial Design Discussion

Motivation

Currently we receive project definition files from the Outbound Phone (OBP) methodology, which provides needed data that uniquely defines the project, provides labelling for the project, and specifies the definition of all the questions in the corresponding OBP survey. The way OBP references and labels its questions is unique to the methodology. OBP is also, for all intents and purposes, a closed system. It can't hit external databases, and other systems have difficulty hitting the internal of OBP.

There is an emerging need to have some more standard way across data collection methodologies to reference questions, and for many applications to be able to access a central place for question information. QBank is the answer.

As such, Eldorado needs to be able to receive question information for QBank and create views based on that information. IVR and OBP (and SCAN later perhaps) will enter project/defintion information in the form of questionnaires into QBank. Question IDs will be allocated and managed by QBank. QBank will also send information on the practice, product, and client id that pertain to the project.

Use Cases

Qbank Sends Def File First, Then Phone Sends Its Version
We parse the QBank file and create a project in the PROJECTS table and create the question_id view, populating the PROJECT_VIEWS table with the appropriate info. When Phone subsequently sends its version, the project is updated with any information not included in the QBank file, and then the DEFINITIONS table is updated with the new defs. The q_tag view is created as usual.

Phone Sends Def File First, Then QBank
Proceeed with normal processing of Phone def file. When QBank send its file the defs are matched up and the additional q_id info is added to the defs in the DEFINITIONS table. The q_id view is created as in the first use case.

Updated Def File Sent From Phone
The update will replace all past information, as it does currently. QBank data will need to be mapped over to the new set of project/defintion information, much like VCT-centric information is now.

Updated Def File Sent From QBank
Added information will be added, and updates to QBank-specific info will be updated. Not sure about removal of defs from QBank view.

{info:title=Note}Any conflicts between Phone and QBank at any point will be resolved by favoring Phone information over QBank information, as Phone ultimately is in control of the data. If conflicts arise, all QBank information will be deleted, and email will be sent to the proper people.{info}

----------------------------------------------------------------------------------------------------------------------------------------------------------