| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| ESQL-Editor in Integration Toolkit 10.0.0.11 very slow |
« View previous topic :: View next topic » |
| Author |
Message
|
| souciance |
 Posted: Fri Apr 13, 2018 11:08 am Post subject: |
 |
|
Disciple
Joined: 29 Jun 2010
Posts: 169
|
| Have others experienced this or is the slow esql editor something that just happens "randomly"? We are about to migrate to fix pack 11. |
|
| Back to top |
|
 |
| timber |
| Posted: Sat Apr 14, 2018 3:00 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Haven't experienced it, but I'm watching this thread very carefully because we're all going to need to upgrade at some point. At this point, put me down as 'concerned' because the 10.0.0.12 fix sounds like sticking plaster rather than a proper fix. Let's hope that IBM knows what the problem is, but could not prepare the proper fix in time for 10.0.0.12. |
|
| Back to top |
|
|
| souciance |
| Posted: Tue Apr 24, 2018 11:10 am Post subject: |
|
|
Disciple
Joined: 29 Jun 2010
Posts: 169
|
| I experienced this slow response in the editor as well. I followed the same workaround, namely point to the 10.0.0.7 jre in my eclipse.ini and it works much better. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Apr 25, 2018 6:53 pm Post subject: Re: ESQL-Editor in Integration Toolkit 10.0.0.11 very slow |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| souciance wrote: |
| Have others experienced this or is the slow esql editor something that just happens "randomly"? We are about to migrate to fix pack 11. |
I'm waiting to hear how effective IT24372 is at fixing this performance issue, before upgrading my toolkit beyond v10.0.0.10.
| Gralgrathor wrote: |
So, quick experiment running Toolkit v10.0.0.11 against the .7 jvm: the editor's response to keystrokes seems normal, and I haven't seen anything strange yet, so I'm keeping this in my eclipse.ini for now:
| Code: |
-vm
C:/IBM/IIB/10.0.0.7/common/jdk/jre/bin/javaw-IIB-10.0.0.7.exe |
|
I didn't read this closely enough, the first time around. I had thought that this workaround was to use the Java 7 JRE that I assumed comes with v10.0.0.11.
Mixing and matching the v10.0.0.11 toolkit with the v10.0.0.10 (or earlier) JRE seems like a bad idea. Doesn't that also affect the toolkit classpath? How is that better than just using the older toolkit? |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
