ThinkingRock Forum

Thought I would try to break TR using your method.

Created an action with F3, converted it to active using the combobox, reprocessed it to inactive, and found that it still showed the "red man" in the projects screen. I could change the action from inactive and to active. This put the action into and out of the top screen. But the bottom (tree view) of the actions screen kept the "red man" for an active task. I selected the task in the top screen, thereafter changing the status also changed the icon.

I re-performed the above actions but on clicking re-reprocess, the system froze. Had to kill the TR process which was using no cpu cycles.

Another issue is that if I press F3 and start typing test into a new action to system is slow to reflect that text. After a couple of words the cursor is re-set at the beginning of the text box and my typing continues from the front of the text I was writing.

This is re-producible. Reprocess any task twice and it locks up java.

Thanks, I can reproduce it now and we will fix it.

_________________
Claire
ThinkingRock Analyst and Tester

Could you tell me which Java version you have? I could reproduce it on my machine at (external) work but not here (in home office).

_________________
Claire
ThinkingRock Analyst and Tester

It doesn't occur with Java 6 Update 5.

I had Java 6 Update 3 and could reproduce the problem, then updated to Java 6 Update 5 and can still reproduce the problem. Am running Win2000 here. I will try at work where I have XP and see if there is any difference.

java -version gives
JRE 1.6.0_5-b13
Win XP Pro SP2

Correction

%AppData%\.thinkingrock\dev\var\log\message.log gives

>Log Session: Wednesday, April 2, 2008 3:54:08 PM BST
>System Info:
Product Version = ThinkingRock 2.0.0.rc.1
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor; Home = 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06; Sun Microsystems Inc.; C:\Java\jdk1.6.0_02\jre
System Locale; Encoding = en_GB (thinkingrock); Cp1252

I think I found the pattern, let me know if you disagree.

The problem is only when you reprocess an action and create a project for it at the same time. It does not get rid of the initial action, then if you try to reprocess the original action again, TR crashes. This creates a data corruption and display problems on the Review Actions list.

Until version 2.0 is out, please use the Convert to Project transaction instead (if you want to carry on using RC1).

_________________
Claire
ThinkingRock Analyst and Tester

I did the following.
1.) If I create a new project it creates a new project with a new action in it.
2.) If I do not create another project it creates a new single action.

The original task remains in both cases and is functional except that the proct tree icon is new longer connected to changes in status e.g. active/inactive. In summary I now have three actions with the same name.

Then I deleted both projects. Could not delete the single action. So marked it as done.

Started again. F4, F3, changed status to Active, Reprocess, make no changes i.e create project is unchecked, click cog, go to Actions screen and original action (there is also one in single actions), click Reprocess, java freezes. Re-start and there are two single actions and one project action.

So if you take a single action and reprocess it without creating a project, do you end up with 2 single actions?

_________________
Claire
ThinkingRock Analyst and Tester

No.

But after testing, I changed the status to active, and processed a second time which caused java to freeze. Killed process and got an exception the following is from the log file

tr.extract.clean [1.0 080402]
tr.extract.reports.projectoutline [1.0 080402]
*********** Exception occurred ************ at 3:08 AM on Apr 4, 2008
org.openide.filesystems.FileAlreadyLockedException: Services/org-netbeans-modules-autoupdate-Settings.settings
at org.openide.filesystems.MultiFileObject.lock(MultiFileObject.java:562)
[catch] at org.netbeans.modules.settings.ScheduledRequest.schedule(ScheduledRequest.java:83)
at org.netbeans.modules.settings.ScheduledRequest.schedule(ScheduledRequest.java:74)


Restarted again. This time without an Exception. There was only one occurence of the task.

I have to go now - Hope you can produce same result.

I think Jeremy has enough information. Thank you for your help.

_________________
Claire
ThinkingRock Analyst and Tester

This has been fixed in Release Candidate 2. See http://www.thinkingrock.com.au/forum/viewtopic.php?t=1931.

_________________
Claire
ThinkingRock Analyst and Tester