|
If you are having unreproducible crashes of the product with only a JVM terminated message, please make sure that you have applied the JVM Update. It will hopefully help the situation. You can get it from the product website. Web page: http://www-1.ibm.com/support/docview.wss?rs=715&context=SSZND2&context=SSKJJP&context=SSBRLP&context=SS2MD7&dc=D400&uid=swg24008100&loc=en_US&cs=utf-8&lang=en Here is a direct link to the download: ftp://ftp.software.ibm.com/as400/products/ad/wdt400/v512/fixes/wdsc_jvm_update.exe Now, if you have applied the JVM Update and are still experiencing problems, the next step is to turn of the J9 optimization (this seems to usually be the cause). To do this, you need to modify the wdsc.ini file. The wdsc.ini file is found in the base product install directory (it is something like C:\Program Files\IBM\WebSphere Studio\Site Developer\v5.1.2\ ). Edit the file and remove '-Xj9' from the VMArgs line. Save the file and restart the product. Hope this helps, Eric Eric Simpson WebSphere Development Studio Client for iSeries, IBM Toronto Lab, D1/140/8200/MKM Phone: (905) 413-3226, T/L: 969-3226, Fax: (905) 413-4850 Email: esimpson@xxxxxxxxxx "Kelly Cookson" <KCookson@DOTFOOD S.com> To Sent by: "Websphere Development Studio wdsci-l-bounces@m Client for iSeries" idrange.com <wdsci-l@xxxxxxxxxxxx> cc 06/30/2005 10:55 Subject AM RE: [WDSCI-L] JVM terminated. Exit code=-1073741819 Please respond to Websphere Development Studio Client for iSeries I have a developer who keeps getting a similar crash and message, except the Exit code = 255. Is the problem my developer is having related? Thanks, Kelly -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx Sent: Thursday, June 30, 2005 9:37 AM To: wdsci-l@xxxxxxxxxxxx Subject: [WDSCI-L] JVM terminated. Exit code=-1073741819 What's the latest on the following: JVM terminated. Exit code=-1073741819 C:\Program Files\IBM\WebSphere Studio\Site Developer\v5.1.2\exlipse\jre\bin\javaw.exe -Xj9 -cp C:\Program Files\IBM\WebSphere Studio\Site Developer\v5.1.2\eclipse\startup.jar org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash C:\Program Files\IBM\WebSphere Stdia\Site Developer\v5.1.2\eclipse\eclipse\.exe -showsplash 600 Files\IBM\WebSphere Studia\Site Developer\v5.1.2\.\eclipse\eclipse.exe -data C:\Documents and Settings\rob\My Documents\IBM\wdsc\workspace -feature com.ibm.wdsclient I had pmr 18070,500 open on this but I kind of let it slide. And now it fell off the 28 day cycle. We have our own internal Notes database for tracking these issues. And wouldn't you know, the very day after I close the ticket in our internal database it bites me in the (end). Version: 5.1.2.4 Build id: 20050104_2139 Sad, but I think one of our 'young pups' went to SEU and another 'young pup' is using CODE/400 because of this particular LPEX editor problem. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.