Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/JP2PP-test-report-V2-1-2.txt Дата изменения: Fri Feb 2 16:25:33 2001 Дата индексирования: Sun Apr 13 22:54:13 2008 Кодировка:

TEST REPORT FOR P2PP V2-1-2
===========================

Tests performed from 18/01/2001 to 26/01/2001.
The main goal here was to check whether new bug fixes and change requests
were correctly implemented (See corresponding Release Note). The most important
bug fix is about the ALIAS mechanism.

This release is to be distributed to external users for P67 Phase II.

Tests performed on :
- SunOS dfs1 5.6 Generic_105181-14 sun4u sparc SUNW,Ultra-Enterprise.
- HP-UX wu0oh B.10.20 A 9000/782 2011818983 two-user license, C200

Visitor account, user 52005, accessing SEGSRV12.
Engineering account , user 1797 and 1901, accessing SEGSRV12.


Main performed tests
--------------------
* Run P2PP and check main window content using several accounts (visitor,
and engineering).

* Manipulation of folders (create, open, rename, move).

* Manipulation of OBs (create, duplicate, move, delete, verify),
for science and calibration OBs using FORS2 and ISAAC templates.

* Import/export OBs.

* Save as OBD format.

* Synchronize OB's components (where the copy is done from the P2PP main
window).

* View phase 1 targets, download targets.

* Check in / check out, directly accessing DB.

* View obrep2 tables via the DBB.

* Interface to BOB: fetch ISAAC OBs, load OBD file generated by P2PP.


Conclusion
----------
4 releases tested in 5 days, which was too much: a tester should be able to spend
at least 2 days to properly check any P2PP new release.
Some bugs seem to be plat-form dependant, which was not the case before: transition to JVM 1.1.8
or later should be planned soon.
Anyway, no critical bug remains on the official P2PP V2-1-2.


Detailed tests results from KH
------------------------------

First results of my tests on wu0oh, HP10.20, FEB2000.

1) question to AMC (Which IPs to use ?):
==> use the latest P67 IPs.


2) HIGH: a new bug never noticed because really tricky (due to a very
specific sequence), but unfortunately it may happen. I occurs only when
creating or updating an OB, and entering values for templates containing
2 consecutive (or more) numerical parameters (float or integer format).
For instance with template ISAACSW_img_obs_AutoJitter.
If the first numerical value is entered out of the range (e.g. > 100000)
and the user directly CLICKS on the NEXT numerical parameter (and NOT
type RETURN), the first one is set to red (normal). Imagine then that
the user sees that the first cell is wrong; so, he clicks on it to
modify it, modify it entering a correct value here, and click again on
the second cell: the second cell is set to blank and it's then
IMPOSSIBLE TO ENTER ANY VALUE IN IT.
Furthermore following Java exception is generated when typing on the second cell:
In editor factory : 2In edtior factory 3
Exception occurred during event dispatching:
java.lang.NullPointerException at
org.eso.ohs.p2pp.views.EditorFactory$P2PPTextField.(EditorFactory.java:942) at
org.eso.ohs.p2pp.views.EditorFactory.getTableCellEditorComponent(EditorFactory.java:458)
at javax.swing.JTable.prepareEditor(JTable.java:2936)
at javax.swing.JTable.editCellAt(JTable.java:2016) at
org.eso.ohs.p2pp.views.ODTemplateTable.editCellAt(ODTemplateTable.java:258) at
javax.swing.plaf.basic.BasicTableUI$MouseInputHandler.mousePressed(BasicTableUI.java:312)
at
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:218)
at java.awt.Component.processMouseEvent(Component.java:2352)
at java.awt.Component.processEvent(Component.java:2200)
at java.awt.Container.processEvent(Container.java:904)
at java.awt.Component.dispatchEventImpl(Component.java:1809)
at java.awt.Container.dispatchEventImpl(Container.java:949)
at java.awt.Component.dispatchEvent(Component.java:1741) at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:1739) at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:1533) at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:1453)
at java.awt.Container.dispatchEventImpl(Container.java:936)
at java.awt.Window.dispatchEventImpl(Window.java:503)
at java.awt.Component.dispatchEvent(Component.java:1741)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:79)
This bug does NOT occur if typing RETURN to enter the first cell value.
It is somehow similar to the known problem reported in the corresponding
list, but not exactly ... It seems better to recommend to type RETURN to
leave a cell than click somewhere else.
==> Item 1226 : find in V2-1-2beta1 and solved in V2-1-2beta2.


3) HIGH ? create an ISAAC OB using the ISAACLW_All_cal_Darks template
which contains an ALIAS (and 4 values entered in the corresponding
parameter "Detector Readout Mode"). Check-in (OK), but when I run the
check out I get the following exception.
Java.lang.IllegalArgumentException: true at
org.eso.ohs.dbb.client.Coordinate.toDatabaseData(Coordinate.java:133) at
org.eso.ohs.dbb.sql.DbbSqlChunk.toDatabaseFormat(DbbSqlChunk.java:370) at
org.eso.ohs.dbb.sql.DbbSqlChunk.setValue(DbbSqlChunk.java:460)
at org.eso.ohs.dbb.client.DbbWidget.setChunk(DbbWidget.java:187) at
org.eso.ohs.dbb.client.DbbWidget.getSqlChunk(DbbWidget.java:133) at
org.eso.ohs.dbb.client.DbbPanel.getActiveChunks(DbbPanel.java:280) at
org.eso.ohs.dbb.client.DbbView.getColumnChunkClasses(DbbView.java:263)
at org.eso.ohs.dbb.client.DbbView.addRows(DbbView.java:591)
at org.eso.ohs.dbb.client.DbbView$1.run(DbbView.java:978) at
javax.swing.SystemEventQueueUtilities.processRunnableEvent(SystemEventQueueUtilities.java:337) at
javax.swing.SystemEventQueueUtilities.access$0(SystemEventQueueUtilities.java:328) at
javax.swing.SystemEventQueueUtilities$RunnableTarget.processEvent(SystemEventQueueUtilities.java:369)
at java.awt.Component.dispatchEventImpl(Component.java:1809)
at java.awt.Component.dispatchEvent(Component.java:1741)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:79)

More about this bug:
I'm really able to reproduce the bug 1227, but I was not enough precise:

Create an ISAAC OB using the ISAACLW_All_cal_Darks template
which contains an ALIAS (and 4 values entered in the corresponding
parameter "Detector Readout Mode").
Check it in : OK
Open the DBB, select all ISAAC OBs for corresponding period: all OBs are
displayed in the DBB grid, the -debug log display all usual information but in the
middle there is this "IllegalArgument" exception.
I don't think I did something particular on the DBB, expect selecting
ALL possible columns to be displayed, select one period (64 here), one
instrument (ISAAC). USer ID 1797, SEGSRV12. I didn't click
on break to stop the query.

==> Item 1227. Solved by P2PP V2-1-2beta2.


4) LOW ? in fact when exporting the checked-out OB (see previous 3)
above), I also get the following exception:
OB-bug-1146.obx
Exception occurred during event dispatching:
java.lang.ClassCastException: java.awt.AWTEventMulticaster at
java.awt.EventQueue$EventQueueMulticaster.remove(EventQueue.java:251) at
java.awt.EventQueue.removeEventQueueListener(EventQueue.java:181) at
java.awt.LightweightDispatcher.stopListeningForOtherDrags(Container.java:1627) at
java.awt.LightweightDispatcher.trackMouseEnterExit(Container.java:1591) at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:1512) at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:1453)
at java.awt.Container.dispatchEventImpl(Container.java:936)
at java.awt.Window.dispatchEventImpl(Window.java:503)
at java.awt.Component.dispatchEvent(Component.java:1741)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:79)
This exception occured because I tried to export a check-out OB, where
the original (not yet checked in) OBX file already existed. If I rename
the original OBX and export the checked-out one, no exception.
==> Item 1228 set to SUSPEND because not reproducable since then.


5) no difference between the original ISAAC "ALIASED" OB and the
corresponding checked-out one, except the "Object Class" value (set to
Unknown for the checked-out OB, instead of blank, but this is a known
problem) ==> it means that exceptions 3) and 4) don't seem to be real
problem, but anyway, please check on your side.
==> I will


6) LOW ? double clicking on a cell attaching ALIAS still opens twice a
Select From List box. Only the hidden one is taken into consideration.
Not very important, but to be said in the list of known problems.

7) adding a new ALIAS value in the ISF, create an OB using it, check-in,
check-out, compare OBX before and after check-in : no difference.
==> OK, correct.


8) according to previous comments, BUG [1146] (removed feature to add
new keywords ..) can be considered as FIXED.
==> OK, bug solved.


9) [1122] Default maximum heap size is now 64 MB :
==> OK, bug solved.


10) [1188] Fixed bug: a range like "0..15 -1" was not recognized
properly, user could not enter "-1" as a value:
==> OK, bug solved.


11) create a very long template name (length>50 char): export, check-in,
check-out, export, compare the 2 OBX: no difference.
==> OK, correct.


2) HIGH: retrieve the installation package from the uss web page,
install it on my dfs1 khaggouc account (Solaris). Apply all the
installation procedure: I get following error message when running the
p2pp script:
"dfs1{khaggouc}523: p2pp
Please set $JAVA_HOME and $SWING_HOME
before calling /home/khaggouc/tools/P2PP/p2pp-2.1.2beta1/bin/p2pp"

but the installation instructions say:".the environment variable
$JAVA_HOME must be correctly set in order for the Unix version of P2PP
to run. When in doubt, one should best unset it and let the system
choose the default value."

In my case, both JAVA_HOME and SWING_HOME are unset.
jre -help gives me:
dfs1{khaggouc}526: jre -help
Java(tm) Runtime Loader Version 1.1.7
Usage: jre [-options] classname [arguments]
........

Something missing in the installation procedure about these 2
variables.
==> Item 1229, installation instructions to be improved: OK, done with P2PP 2-1-2beta2.


Back to the wu0oh configuration installed by Carlos:
----------------------------------------------------
13) test folder manipulation (create, move, delete, rename, ...):
==> OK, correct.


14) test P2PP / BOB communications: create an ISAAC OB, fetch it:OK.
Create another ISAAC OB, check it in, fetch it:
==> OK, correct.


Install latest IPs for period 67:
---------------------------------
15) CRITICAL:
In fact the bug reported in my previous comment 2) (=your new item 1226)
occurs several times again.
I played to try to find a workaround, but I didn't find any. So, it
means that when this bug occurs there is no way than delete the template
and enterely re-create it carefully, i.e. using the RETURN key to
validate a new value, and NOT click away from the edited cell : this
should really be precisely described in the list of Known problems. Or
even fixed before delivering this release ? to be discussed with you and
Dave ...
Then, strange, I don't understand why I never noticed this problem
before.


16) item 1188 (range including the "-1" value): I updated
an ISAAC tsf to get a range value
"0..15 -1" and I could enter "-1" as value in the corresponding
parameter:
==> OK, bug solved.


17) item 1145a, create a FOSR2 OB, export it, Check it IN it. Check it
OUT, and re-export it (with a specific name). "ObsGrade" field was
previously exported for Obs and Cal blocks: not the case anymore, this
field doesn't exist in any OBX (OBX created just after OB creation, just
after checkin, just after checkout).
==> OK, bug solved.


18) item 1145b, the "objectClass" field value was deleted by export: not
the case now and same number of blanks before and after exporting.
Anyway, the value contains several blanks before and after the real
value
(objectClass " Moon ")
==> OK, correct.


19) item 1145c, "description" field value exactly the same for OBX
created just after OB creation, for OBX created just after checkin, for
OBX created just after checkout):
==> OK, correct.


20) more about item 1145 : the only differences remaining between OBX
(created just after OB creation) and OBX (created after checkout) are:
4c4
< userComments "fgh;afg;;asfdkjg kjfghajgfjsagj
sjg'jsgj[0q34986jhma;lk erkgt'aerirtyper8y-09;lk,gh, ;okg';kfdg'k
k'ka'k'gkla fgh;afg;;asfdkjg kjfghajgfjsagj sjg'jsgj[0q34986jhma;lk
erkgt'aerirtyper8y-09;lk,gh, ;okg';kfdg'k k'ka'k'gkla "
---
> userComments "fgh;afg;;asfdkjg kjfghajgfjsagj sjg'jsgj[0q34986jhma;lk erkgt'aerirtyper8y-09;lk,gh, ;okg';kfdg'k k'ka'k'gkla fgh;afg;;asfdkjg kjfghajgfjsagj sjg'jsgj[0q34986jhma;lk erkgt'aerirtyper8y-09;lk,gh, ;okg';kfdg'k k'ka'k'gkla"
6c6
< calibrationReq "blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj
blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c
kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb
xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj "
---
> calibrationReq "blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj blblbllb xb;kl;kb'vkx'c kjgb;lksjdfkgj"
==> Correct. The only difference is in the whitespace at the end, which cannot be preserved.


21) item 1069 (DB browser "ProgID" column didn't work): still not able
to reproduce it.
==> OK, bug solved


22) HIGH: Bug which occcured ONCE on Solaris ONLY (never on HP-UX) :
P2PP crashes when closing one of the 2 ALIAS boxes I just
opened. I was creating an ISAAC OB attaching the famous
ISAACLW_All_cal_Darks template which contains an ALIAS list; as I'm used
to do it, I DOUBLE clicked on the "Detector Readout Mode" template
field, and 2 superimposed boxes "Select from List" opened (another known
small bug). P2PP just crashed when I clicked on the Cancel button of the
first Box, giving following segmentation violation message and
Exception.
By "P2PP crashes", I mean the process is killed, and all opened p2pp
windows disappeared.
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Error 0
si_code [1]: SEGV_MAPERR [addr: 0x148]
stackbase=EE7F3D74, stackpointer=EE7F26E4
Full thread dump:
"AWT-Dispatch-Proxy" (TID:0xeb0cc130, sys_thread_t:0x78a320,
state:R, thread_t: t@29, sp:0x0 threadID:0xea3f3de0,
stack_base:0xea3f3d74, stack_size:0x22000) prio=5
javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:132)
javax.swing.JComponent.firePropertyChange(JComponent.java:2915)
javax.swing.JComponent.removeNotify(JComponent.java:3190)
java.awt.Container.removeNotify(Container.java:1194)
javax.swing.JComponent.removeNotify(JComponent.java:3186)
java.awt.Container.removeNotify(Container.java:1194)
javax.swing.JComponent.removeNotify(JComponent.java:3186)
java.awt.Container.removeNotify(Container.java:1194)
javax.swing.JComponent.removeNotify(JComponent.java:3186)
java.awt.Container.removeNotify(Container.java:1194)
javax.swing.JComponent.removeNotify(JComponent.java:3186)
javax.swing.JRootPane.removeNotify(JRootPane.java:418)
java.awt.Container.removeNotify(Container.java:1194)
java.awt.Window.dispose(Window.java:185)
org.eso.ohs.p2pp.views.EditorFactory$4.actionPerformed(EditorFactory.java:701)
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1066)
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1101)
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378)
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250)
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:217)
"AWT-Modal" (TID:0xeb098f98, sys_thread_t:0x797990, state:CW,
thread_t: t@28, sp:0xee482db8 threadID:0xee483de0,
stack_base:0xee483d74, stack_size:0x22000) prio=5
sun.awt.motif.ModalThread.run(MDialogPeer.java:148)
"AWT-Dispatch-Proxy" (TID:0xeb099670, sys_thread_t:0x790d10,
state:R, thread_t: t@27, sp:0xee7f3d80 threadID:0xee7f3de0,
stack_base:0xee7f3d74, stack_size:0x22000) prio=5 *current thread*
java.awt.EventDispatchThread.stopDispatching(EventDispatchThread.java:42)
java.awt.Dialog.show(Dialog.java:221)
org.eso.ohs.p2pp.views.EditorFactory.shouldSelectCell(EditorFactory.java:185)
javax.swing.plaf.basic.BasicTableUI$MouseInputHandler.mousePressed(BasicTableUI.java:329)
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:218)
java.awt.Component.processMouseEvent(Component.java:2355)
java.awt.Component.processEvent(Component.java:2203)
java.awt.Container.processEvent(Container.java:904)
java.awt.Component.dispatchEventImpl(Component.java:1812)
java.awt.Container.dispatchEventImpl(Container.java:949)
java.awt.Component.dispatchEvent(Component.java:1744)
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:1739)
java.awt.LightweightDispatcher.processMouseEvent(Container.java:1533)
java.awt.LightweightDispatcher.dispatchEvent(Container.java:1453)
java.awt.Container.dispatchEventImpl(Container.java:936)
java.awt.Window.dispatchEventImpl(Window.java:492)
java.awt.Component.dispatchEvent(Component.java:1744)
java.awt.EventDispatchThread.run(EventDispatchThread.java:81)
"AWT-Finalizer" (TID:0xeb0984d0, sys_thread_t:0x3a49e0, state:CW,
thread_t: t@16, sp:0xee452f38 threadID:0xee453de0,
stack_base:0xee453d74, stack_size:0x22000) prio=9
java.lang.Object.wait(Object.java)
sun.awt.AWTFinalizer.run(AWTFinalizer.java:40)
"AutoSaver Thread" (TID:0xeb064b78, sys_thread_t:0x43d560, state:CW,
thread_t: t@14, sp:0xee502e48 threadID:0xee503de0,
stack_base:0xee503d74, stack_size:0x22000) prio=3
org.eso.ohs.persistence.AutoSaver.shortPause(AutoSaver.java:274)
org.eso.ohs.persistence.AutoSaver.run(AutoSaver.java:295)
"Screen Updater" (TID:0xeb064a88, sys_thread_t:0x42c0f0, state:CW,
thread_t: t@13, sp:0xee532ed8 threadID:0xee533de0,
stack_base:0xee533d74, stack_size:0x22000) prio=4
java.lang.Object.wait(Object.java)
sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:70)
sun.awt.ScreenUpdater.run(ScreenUpdater.java:90)
"ConnectionPool - Dead Connection Reaper" (TID:0xeb06fb08,
sys_thread_t:0x37be60, state:CW, thread_t: t@12, sp:0xee7c2ea8
threadID:0xee7c3de0, stack_base:0xee7c3d74, stack_size:0x22000) prio=5

org.eso.ohs.utilities.ConnectionPool$Reaper.run(ConnectionPool.java:299)
"TimerQueue" (TID:0xeb07e338, sys_thread_t:0x2bc630, state:CW,
thread_t: t@9, sp:0xef042ed8 threadID:0xef043de0, stack_base:0xef043d74,
stack_size:0x22000) prio=5
javax.swing.TimerQueue.run(TimerQueue.java:205)
java.lang.Thread.run(Thread.java)
"AWT-Motif" (TID:0xeb004bd8, sys_thread_t:0xf5208, state:R,
thread_t: t@7, sp:0xef0730d0 threadID:0xef073de0, stack_base:0xef073d74,
stack_size:0x22000) prio=5
java.lang.Thread.run(Thread.java)
"AWT-EventQueue-0" (TID:0xeb004b00, sys_thread_t:0xe9ce8, state:CW,
thread_t: t@6, sp:0xef0a2f38 threadID:0xef0a3de0, stack_base:0xef0a3d74,
stack_size:0x22000) prio=5
java.lang.Object.wait(Object.java)
sun.awt.motif.MDialogPeer.show(MDialogPeer.java:104)
java.awt.Dialog.show(Dialog.java:219)
org.eso.ohs.p2pp.views.EditorFactory.shouldSelectCell(EditorFactory.java:185)
javax.swing.plaf.basic.BasicTableUI$MouseInputHandler.mousePressed(BasicTableUI.java:329)
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:218)
java.awt.Component.processMouseEvent(Component.java:2355)
java.awt.Component.processEvent(Component.java:2203)
java.awt.Container.processEvent(Container.java:904)
java.awt.Component.dispatchEventImpl(Component.java:1812)
java.awt.Container.dispatchEventImpl(Container.java:949)
java.awt.Component.dispatchEvent(Component.java:1744)
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:1739)
java.awt.LightweightDispatcher.processMouseEvent(Container.java:1533)
java.awt.LightweightDispatcher.dispatchEvent(Container.java:1453)
java.awt.Container.dispatchEventImpl(Container.java:936)
java.awt.Window.dispatchEventImpl(Window.java:492)
java.awt.Component.dispatchEvent(Component.java:1744)
java.awt.EventDispatchThread.run(EventDispatchThread.java:81)
"SIGQUIT handler" (TID:0xeb0002a0, sys_thread_t:0x9a998, state:R,
thread_t: t@5, sp:0xef343af0 threadID:0xef343de0, stack_base:0xef343d74,
stack_size:0x22000) prio=0
"Finalizer thread" (TID:0xeb000088, sys_thread_t:0x9b760, state:CW,
thread_t: t@4, sp:0xef373a30 threadID:0xef373de0, stack_base:0xef373d74,
stack_size:0x22000) prio=1
"main" (TID:0xeb0000b0, sys_thread_t:0x77f70, state:CW, thread_t:
t@1, sp:0xefffe128 threadID:0x236f8, stack_base:0x0,
stack_size:0x800000) prio=5
Monitor Cache Dump:
(0x37be60):
Waiting to be notified:
"ConnectionPool - Dead Connection Reaper" (0x37be60)
sun.awt.motif.MToolkit@EB004B80/EB0E7FD0:
Waiting to be notified:
"AWT-Modal" (0x797990)
java.lang.Object@EB081160/EB1605E0: owner "AWT-Dispatch-Proxy"
(0x78a320, 6 entries)
sun.awt.AWTFinalizer@EB0984D0/EB0D0740:
Waiting to be notified:
"AWT-Finalizer" (0x3a49e0)
java.lang.Class@EB004B08/EB0E8500: owner
"AWT-Dispatch-Proxy" (0x790d10, 1 entry)
javax.swing.TimerQueue@EB07E330/EB1D60C0:
Waiting to be notified:
"TimerQueue" (0x2bc630)
sun.awt.ScreenUpdater@EB064A88/EB1BBE78:
Waiting to be notified:
"Screen Updater" (0x42c0f0)
(0x43d560):
Waiting to be notified:
"AutoSaver Thread" (0x43d560)
sun.awt.motif.ModalThread@EB098F98/EB3C9FB8: owner "AWT-Modal"
(0x797990, 1 entry)
Waiting to be notified:
"AWT-EventQueue-0" (0xe9ce8)
Registered Monitor Dump:
Thread queue lock:
Waiting to be notified:
"main" (0x77f70)
Name and type hash table lock:
String intern lock:
JNI pinning lock:
JNI global reference lock:
BinClass lock:
Class loading lock: owner "AWT-Dispatch-Proxy" (0x790d10, 1 entry)
Java stack lock:
Code rewrite lock:
Heap lock:
Has finalization queue lock:
Finalize me queue lock:
Waiting to be notified:
"Finalizer thread" (0x9b760)
Monitor registry: owner "AWT-Dispatch-Proxy" (0x790d10, 1 entry)
Abort
==> Critical bug to be solved by moving to Java VM 1.1.8 ?


23) try same sequence as comment 22) on another new OB: no problem here,
it works ...On the previous OB which crashed, it works also ...


24) More about comment 22) : Maybe the following can help you ?
When I DOUBLE click on the "Detector Readout mode" field (from the
ISAACLW_all_cal_Darks template) the jre CPU goes up and up from less
than 1 or 2% to 33% EVEN IF I DO NOTHING (double click opens twice the
"Select from list" box, but then I do nothing, just watching the CPU
increase as displayed by the "top" command).
If I close the 2 boxes, CPU goes back to 2%.
If I SIMPLE click the CPU stays around 2 or 3%, as it is normally when I
define or update a template.
So, even if 1.1.7. VM may be responsible for the previous crash, is
there something bad somewhere in the P2PP code about events handling
when double clicking ... ? I mean P2PP should rather prevent to open the
"Select from list" box several times when double or triple click occurs.

25) View phase 1 targets, download targets:
==> OK, it works.


26) Testing move OB, verify, check-in, check-out, Dowload /refresh obs
runs, import, export, display in OBD format, create/ssave all types of
reports:
==> OK, it works.


27) MINOR: create an ISAAC OB whose "userComments", "calibrationReq" and
"description" field contains several Returns. Export it. Import it and
re-export it again. Then compare the 2 obx files: the returns are not
interpreted in the same way:
dfs1{khaggouc}197: diff OB-after-crash.obx OB-after-crash-again.obx
4c4,9
< userComments "hgshgh4yptooiu '
rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
dhe[yueuy073-467-076-0dhdh;ld;hlk djshjdh"
---
> userComments "hgshgh4yptooiu
> '
> rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
> dhe[yueuy073-467-076-0dhdh;ld;hlk djshjdh"
6c11,16
< calibrationReq "hgshgh4yptooiu '
rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
dhe[yueuy073-467-076-0dhdh;ld;hlk djshjdh sghhjsg;ah;h40618-90-09 9
-4-96-996 316-="
---
> calibrationReq "hgshgh4yptooiu
> '
> rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh rtr\eq3-4-861-7461386gfajgjgj98^&&^ 6 609462509876jdhljsdkjh
> dhe[yueuy073-467-076-0dhdh;ld;hlk djshjdh sghhjsg;ah;h40618-90-09 9 -4-96-996 316-="
27c37,41
< description "shlg;hgs; 984363=417 n168
61t;jtajt';jhy;jf'h;j';jh'dfjlh'jl dfhkd'h;jdlfh
8-0358761709796)%&(^$*&$Gkglkgksjhtg;laeh erjtylerjy;lerjyl"
---
> description "shlg;hgs; 984363=417 n168 61t;jtajt';jhy;jf'h;j';jh'dfjlh'jl
> dfhkd'h;jdlfh 8-0358761709796)%&(^$*&$Gkglkgksjhtg;laeh erjtylerjy;lerjyl
> dfhkd'h;jdlfh 8-0358761709796)%&(^$*&$Gkglkgksjhtg;laeh erjtylerjy;lerjyl"
dfs1{khaggouc}198:
==> Item 1236.


28) MINOR: Several NullPointer exception when entering wrong values
several times and double click, but MINOR because the value entered is
always the one which is displayed.
==> Item 1237.


29) MINOR: create an ISAAC OB (user 1797) save it as IMPEX. Check it in.
> Check it out. Save the checked-out as IMPEX, and compare the 2 OBX:
> wu0oh visitor:~/impex 57 > diff Doucle-click-bug-orig.obx
> Doucle-click-bug.obx
> 19c19
> < comments " "
> ---
> > comments ""
> 69c69
> < SEQ.NDIT.LIST "43 3454 4774 0 "
> ---
> > SEQ.NDIT.LIST "43 3454 4774 0"
==> Item 1238.


30) HIGH: in some cases, no way to select a CalBlock within the DBB grid:
"IndexOutOfBound" exception raised each time I click in the grid to
select the Cal OB I wish to check-out. This doesn't happen all the time:
only noticed on HP, never on Solaris. I have still to test to understand
exactly HOW it happens.
There is a workaround= just quit and re-start P2PP. I think we can
deliver V2-1-2 but explained this in the list of Known Problems.
Exception occurred during event dispatching:
java.lang.ArrayIndexOutOfBoundsException: 11 at
org.eso.ohs.gui.widgets.TableSorter.setValueAt(TableSorter.java:282)
at javax.swing.JTable.setValueAt(JTable.java:1422)
at javax.swing.JTable.editingStopped(JTable.java:2557) at
javax.swing.DefaultCellEditor.fireEditingStopped(DefaultCellEditor.java:281) at
javax.swing.DefaultCellEditor.stopCellEditing(DefaultCellEditor.java:239)
at javax.swing.JTable.editCellAt(JTable.java:2004) at
javax.swing.plaf.basic.BasicTableUI$MouseInputHandler.mousePressed(BasicTableUI.java:312) at
java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:218)
at java.awt.Component.processMouseEvent(Component.java:2352)
at java.awt.Component.processEvent(Component.java:2200)
at java.awt.Container.processEvent(Container.java:904)
at java.awt.Component.dispatchEventImpl(Component.java:1809)
at java.awt.Container.dispatchEventImpl(Container.java:949)
at java.awt.Component.dispatchEvent(Component.java:1741) at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:1739) at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:1533) at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:1453)
at java.awt.Container.dispatchEventImpl(Container.java:936)
at java.awt.Window.dispatchEventImpl(Window.java:503)
at java.awt.Component.dispatchEvent(Component.java:1741)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:79)
==> add warning in the list of known problems