Source Search failing to complete

The iSphere Project for and RDi 9.5.1.3+

Brought to you by: f_hildebrandt, tools400

This project can now be found here.

#115 Source Search failing to complete

Milestone: 3.0

Status: informational

Owner: nobody

Labels: None

Updated: 2022-04-01

Created: 2021-09-16

Creator: Paul Bailey

Private: No

iSphere version 4.1.0.r, RDi version 9.6.0.11

Since upgrading RDi to 9.6.0.11 I have been unable to use the iSphere Source File Search option. Every time I try it asks for my criteria, pops up a progress bar saying "Resolving filters" and then the progress bar ~might~ finish but the popup disappears and nothing else happens. There is nothing added to the iSphere Source File Search view.

I checked the workspace's .metadata/.log file after I tried a search (after starting RDi fresh with the -clean option) and I found this:

!SESSION 2021-09-16 09:40:55.251 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=8.0.6.15 - pwa6480sr6fp15-20200724_01(SR6 FP15)
JRE 1.8.0 Windows 10 amd64-64-Bit Compressed References 20200724_452227 (JIT enabled, AOT enabled)
OpenJ9 - 4ce4b9d
OMR - 08b0594
IBM - 70917a2
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ibm.rational.developer.ibmi.product.ide -clean

!ENTRY org.eclipse.equinox.registry 2 0 2021-09-16 09:41:02.148
!MESSAGE The extensions and extension-points from the bundle "org.eclipse.emf.commonj.sdo" are ignored. The bundle is not marked as singleton.

!ENTRY com.ibm.etools.stacktool 0 0 2021-09-16 09:42:24.141
!MESSAGE plugin is early starting...

!ENTRY com.ibm.etools.stacktool 0 0 2021-09-16 09:42:24.188
!MESSAGE Save the stack tool properties file.

!ENTRY org.eclipse.ui 2 2 2021-09-16 09:42:25.485
!MESSAGE Invalid preference category path: modeling.diagram.appearance.misc (bundle: com.ibm.xtools.rmp.ui.diagram, page: com.ibm.xtools.rmp.ui.preferences.SelectionFeedbackPreferencePage)

!ENTRY biz.isphere.core 4 4 2021-09-16 09:42:42.530
!MESSAGE *** Call to FNDSTR_getHandle failed. See messages above ***
!STACK 0
com.ibm.as400.data.PcmlException: Internal Error: Unknown data type, 0. Processing <data> element 'FNDSTR_getHandle.handle'.
at com.ibm.as400.data.PcmlDataValues.byteLength(PcmlDataValues.java:430)
at com.ibm.as400.data.PcmlDataValues.parseBytes(PcmlDataValues.java:708)
at com.ibm.as400.data.PcmlData.parseBytes(PcmlData.java:1181)
at com.ibm.as400.data.PcmlProgram.callProgram(PcmlProgram.java:799)
at com.ibm.as400.data.PcmlDocument.callProgram(PcmlDocument.java:460)
at com.ibm.as400.data.ProgramCallDocument.callProgram(ProgramCallDocument.java:450)
at biz.isphere.core.sourcefilesearch.FNDSTR_getHandle.run(FNDSTR_getHandle.java:29)
at biz.isphere.core.sourcefilesearch.SearchExec$Search.run(SearchExec.java:107)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)</data>

I hope this helps you to help me. I need that source search option.

Discussion

Frank Hildebrandt - 2021-09-16

Hi Paul,

thank you for this information. We have similar problems with other of our commercial plugins when calling programs on IBM i via PCML since RDi Fix Pack 11. The main problem is, that it is not reproducable. On most of the boxes with RDi Fix Pack 11 our plugins are working properly. But on some boxes we get exactly the same pcml exception you got. At the moment we dont know why, but we are working together with IBM to find a solution. We have a workaround, where we replace the JTOpen jars in RDi Fix Pack 11, which has version 10.5 with version 9.7. For me it seems that the core problem is the JDK and not the JTOpen, but I have to wait what IBM says. I you are interested in this workaround I can post you the steps, but if you do the workaround you do it on your own risk.

Regards

Frank

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul Bailey - 2021-09-16

Thanks Frank. It seems like a risky workaround at the moment, so I'll wait, but if you need a test subject then let me know.

Now I need to remember how to do a source search in the old way... :)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Frank Hildebrandt - 2021-09-16

Just an update for you. IBM provided an interims solution which make it work now. I am waiting for IBM for further instructions. You say that you would be willing to work as test subject. Maybe, if neccessary, I'll take you up on your offer.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Frank Hildebrandt - 2021-09-17

Hi Paul,

it seems, that the solution IBM provided to me is not an interims solution, but a permanent solution. Here is what the IBM technical support wrote to me.

Edit the eclipse.ini in the RDI install directory and locate the line:
-Xshareclasses:name=IBMSDP_%u
then modify the line to be:
-Xshareclasses:none
and save the eclipse.ini then restart RDI.

For us this worked. Please give this a try and let me know if this helped for you.

Frank

😄
1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Íñigo Redín - 2021-09-21
  
  This answer worked perfectly for me.
  But the last one, not. because the parameter (and value) "Xshareclasses:destroyAll" doesn't exist.
  
  Thanks a lot! I cannot live without iSphere search!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul Bailey - 2021-09-17

Hi Frank,

I can confirm that eclipse.ini change does enable the source search option to work now.

Do you have any clue what other effect it is going to have, just in case I come across a "difference" later?

Paul.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Frank Hildebrandt - 2021-09-17

Good question. I ask IBM.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Frank Hildebrandt - 2021-09-20

Hi Paul,

I found a further solution for the problem and I think this solution is better. The core problem is the cache of the JVM delivered with RDi. For what reason ever, somtimes the cache contains trash after installation of fix pack 11. The solution IBM provided to me was to disable the caching feature completly. In the meantime I found out, how to clear the cache. On one machine with this problem, I enabled the caching feature again, cleared the cache and it worked. Please do the following.

Close RDi

Enable the caching feature again by changing -Xshareclasses:none to -Xshareclasses:name=IBMSDP_%u in eclipse.ini.

Start RDi and check, if the problem occurs again. If yes, continue at #4.

Close RDi

Execute CMD.EXE
This opens the DOS box.

Enter cd "C:\Program Files\IBM\SDP\jdk\jre\bin"
"C:\Program Files\IBM\SDP" is the default installation path of RDi. It has to be changed, if a different path has choosen during installation of RDi.

Enter java -Xshareclasses:listAllCaches
Only caches with the name "IBMSDP..." should be listed.

Enter java -Xshareclasses:destroyAll
This deletes all caches.

Enter java -Xshareclasses:listAllCaches again
No caches should be listed.

Start RDi and check, if the problem has fixed now.

Frank

Last edit: Thomas Raddatz 2023-09-28

destroy-java-cache.png

list-java-cache.png
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul Bailey - 2021-09-20

Hi Frank,

Those 10 steps also worked. The ini file is back to what it was and the problems with the iSphere plugin I was having have disappeared.

Thanks very much. This seems like a better solution.

Paul.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Raddatz - 2021-09-26

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Raddatz - 2022-01-04

status: closed --> informational
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.