Error on CS 10.5 IDE startup

FAMELIARISA

Greetings people,

I am using Eclipse Luna with JDK 1.7.0_65 (both 64bit) on a Windows 2012 Server to develop OScript code for our projects / clients.

Everytime I start up the IDE, I get the following message:

"Script crash on startup. Cannot debug.

An exception stack trace is not available.

eclipse.buildId=4.4.1.M20140925-0400
java.version=1.7.0_65
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.standard.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product"

all that about com.opentext.livelink plugin.

This happens for com.opentext.cside_10.5.1.2 AND com.opentext.cside_10.5.3.139 jars and for the Kepler Eclipse too.

Is there something I should change in the installation?
Because eventually, this, "cannot debug" problem is real, every time I debug, (breakpoint or Scheduler.DebugBreak())  the memory core is dumped, eclipse dies and so is the server too.

Thank you very much in advance.

 

Appu_Nair1

We have been using CSIDE from about since April 2014 a pool of about 6 developers who were mostly  familiar with Oscript & Builder. All of us did not feel the same warmth the builder env did ,but after a few months we eased ourselves into its idiosyncrasies and such like. The startup area of Eclipse/CSIDE  has a  file that OT support(Usually Darcy Casselman, Mark Sherry,& David Templeton ) wants for them to improve the product. I have not seen it crash completely on the env but occasional crashes are there. In one circumstance we put back the old jar and it appeared a little more stable. The more you use it for a living the less complaining you would getJ because builder ain’t coming back……The huge mdmp files are definitely there and Livelink and CSIDE misbehaves after that which a re-start fixes it.

Why did you resort to Scheduler.debugbreak() because it is easy to put an actual break point? The only thing different is we use W2k8 64 bit

 

I am very hopeful that the next release is even more better ,it can only happen as continuous improvement that is my thinking since just as us OT developers are also using it in their day today routines.

 

 

Thanks

Appu

 

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, February 05, 2015 4:10 AM
To: eLink Recipient
Subject: [EXTERNAL]Error on CS 10.5 IDE startup

 

Error on CS 10.5 IDE startup

Posted byfameliarisa@unisystems.gr (FAMELIARIS, ATHANASSIOS) On 02/05/2015 05:04 AM

 

Greetings people, I am using Eclipse Luna with JDK 1.7.0_65 (both 64bit) on a Windows 2012 Server to develop OScript code for our projects / clients. Everytime I start up the IDE, I get the following message: "Script crash on startup. Cannot debug. An exception stack trace is not available. eclipse.buildId=4.4.1.M20140925-0400 java.version=1.7.0_65 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments:  -product org.eclipse.epp.package.standard.product Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product" all that about com.opentext.livelink plugin. This happens for com.opentext.cside_10.5.1.2 AND com.opentext.cside_10.5.3.139 jars and for the Kepler Eclipse too. Is there something I should change in the installation? Because eventually, this, "cannot debug" problem is real, every time I debug, (breakpoint or Scheduler.DebugBreak())  the memory core is dumped, eclipse dies and so is the server too. Thank you very much in advance.

---

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

 

image002.jpg