Upgrade to 8.5.0.6..Notes issue

[jeffs42885]

Has anyone experienced any issue with the OnDemand notes process after upgrading to 8.5.0.6?

Our users are able to add notes, but not view them once added.

[Justin Derrick]

Ick!  Can you provide more info?  I've got at least three customers on 8.5.0.6 -- two of them using annotations daily. 

Do the annotations show up in the arsann table when added?  Can you retrieve the doc + annotation using arsdoc (with -A 7 to extract annotations with the document)?  Are clients on the 8.5.0.6 Thick Client, or are they using CGI / Java API?

[jeffs42885]

It's weird.

I start the process and there is a whole bunch of messages returned most of which seem cryptic to me.

I just did a test using the thick client--the note successfully adds, and I am able to view it via thick client, and the yellow "note" symbol appears next to the hit in the hitlist. I checked the ARSANN table and it is showing up.

I went into the thin client (ODWEK) and went to the same folder and pulled up the hitlist. I had the option to add a note, but not view one..

I tried adding another note via thin client, it did not update the ARSANN table, and this message was returned, and of course...the process died.

Our websphere servers are running 6.1 on AIX 6.6.15 with ODWEK 8.4.1.6

Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000032
Handler1=F22C60A8 Handler2=F22C01F0
R0=00000000 R1=2FF20700 R2=F22C76BC R3=301B9100
R4=000004B8 R5=00000000 R6=301B9138 R7=7DF042A6
R8=161300EB R9=161300EB R10=319D2308 R11=00000000
R12=53424325 R13=301B9100 R14=314E22CC R15=F36714B8
R16=00000007 R17=00000000 R18=F22C7F30 R19=000000E4
R20=00000000 R21=314E2300 R22=00000000 R23=00000000
R24=F36A3DD4 R25=319D2308 R26=DDEBE8A8 R27=314E22EC
R28=DDEBE320 R29=000004B8 R30=2FF209B0 R31=301B9100
IAR=D90125EC LR=DDD1FB8C MSR=0000D032 CTR=D90125A0
CR=33425325 FPSCR=82020000 XER=C00714B8 TID=00000000
MQ=DEADBEEF
FPR0 4a39524f4d434c41 (f: 1296256128.000000, d: 3.700745e+49)
FPR1 5353434f4f4b4945 (f: 1330334080.000000, d: 2.511314e+93)
FPR2 c1e0000000000000 (f: 0.000000, d: -2.147484e+09)
FPR3 3fee666660000000 (f: 1610612736.000000, d: 9.500000e-01)
FPR4 4330000000400000 (f: 4194304.000000, d: 4.503600e+15)
FPR5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR6 41e0000000000000 (f: 0.000000, d: 2.147484e+09)
FPR7 41f0000000000000 (f: 0.000000, d: 4.294967e+09)
FPR8 002e0063006c0061 (f: 7077985.000000, d: 8.344447e-308)
FPR9 00730075006c0074 (f: 7078004.000000, d: 1.691215e-306)
FPR10 0057005700520065 (f: 5374053.000000, d: 5.117965e-307)
FPR11 0041007200730057 (f: 7536727.000000, d: 1.891506e-307)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4020800000000000 (f: 0.000000, d: 8.250000e+00)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/java5/jre/bin/libj9vm23.so
Module_base_address=D8FDB000
Target=2_30_20110623_85457_bHdSMr (AIX 6.1)
CPU=ppc (4 logical CPUs) (0x180000000 RAM)
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/notes/core.20121204.072601.19398728.0001.dmp' in response to an event
Note: "Enable full CORE dump" in smit is set to FALSE and as a result there will be limited threading information in core file.
JVMDUMP010I System dump written to /notes/core.20121204.072601.19398728.0001.dmp
JVMDUMP032I JVM requested Snap dump using '/notes/Snap.20121204.072601.19398728.0002.trc' in response to an event
JVMDUMP010I Snap dump written to /notes/Snap.20121204.072601.19398728.0002.trc
JVMDUMP032I JVM requested Java dump using '/notes/javacore.20121204.072601.19398728.0003.txt' in response to an event
JVMDUMP010I Java dump written to /notes/javacore.20121204.072601.19398728.0003.txt
JVMDUMP013I Processed dump event "gpf", detail "".

[kbsiva]

Hi - You might want to try upgrading your ODWEK to 8.5.X version. I had similar issues with WEBi when ODWEK was at a lower version and CMOD was 8.5.x version.

Thanks
Siva

[jeffs42885]

Not sure if this makes a difference, but we are currently running ODWEK 8.5.0.6 on our server, it's a mix of the library and object server. It's installed but nobody is using it

On our websphere servers, we are running WAS 6.1 and ODWEK 8.4.1.6

[kbsiva]

Hello Jeff,
 It might be worth a shot to upgrade the ODWEK on the WebSphere server, since you are not getting issues on the Fat Client . I believe the fat client will use the odwek on the cmod server. Where as thin client will be using odwek from WebSphere server. In my case I had an message in the log complaining about version.

Thanks,
siva

[Justin Derrick]

Just to clarify -- the Thick Client DOES NOT use ODWEK at all -- it connects directly to the server and communicates with the arssockd process.  ODWEK allows you to use Java APIs to make requests to arssockd.  ODWEK is optional, and not a required component for CMOD, as long as you only access the server using the thick client or command-line utilities like arsdoc.

-JD.

[jeffs42885]

Good Morning all,

We did some research, and we saw that we were using an outdated version of ODAPI.jar (from version 8.4)

We replaced this with the 8.5 jar file, and the notes process:

1) Starts and runs
2) Works with the thick client as expected
3) Notes can be added and viewed in the log file for notes, and also in the ARSANN table

The only remaining issue, is that there is no option to view the note within the OnDemand web client.

[kbsiva]

Thanks Justin for the clarification!

[jeffs42885]

update again, 

I tried a different folder, and it is working as expected. I suspect there is a permission issue with the original folder I was trying.