After upgrading to 06-2015 update we get fatal crash while clicking on F3 on some function in oscripte code or ctrl+space.
We use 10.5.5.327 plugin, eclipse kepler and CS 10.5 SP1 06-2015
Errors:
Is there any way to turn off content assist fo oscript?
Hi Eugene,
The crash is caused when CSIDE tries to look up global variables. Unfortunately, there's no way to disable this behaviour yet.
While a fix has been checked in, it missed the cut-off for the 2015-06 update. Rather than force you to wait until 2015-09, we can release a patch for CS 10.5 2015-06.
Is there a way or a patch to fix this issue? If yes, please tell my the patch number.
I'm using 10.5.6.446 plug-in with Eclipse Mars and CS 10.5 and every attempt to use assist forces java to crash.
Hi Maxim,
This featured was fixed. Have you tried to get the latest CSIDE plugin version?
Regards
Juliano
Hi, Juliano,
i'll reply to your question. My dev environment:
Eclipse Version: Mars.2 Release (4.5.2) Build id: 20160218-0600
Content Server 10.5 Update 2015-06 (version 10.5.0.1715)
CSIDE com.opentext.cside_10.5.0.285.jar
Almost every time i press "." in OScript Editor (either for global variable or for core classes) i get java exception and crash:
Problem signature: Problem Event Name: APPCRASH Application Name: javaw.exe Application Version: 7.0.450.18 Application Timestamp: 5254005d Fault Module Name: StackHash_547a Fault Module Version: 6.3.9600.17031 Fault Module Timestamp: 530895af Exception Code: c0000374 Exception Offset: PCH_9B_FROM_ntdll+0x000000000009B13A OS Version: 6.3.9600.2.0.0.400.8 Locale ID: 1049 Additional Information 1: 547a Additional Information 2: 547ac4a3927600e293867075cae7097e Additional Information 3: 7257 Additional Information 4: 7257c1ec40458f172645c6831a09d071
This looks like the server VM was down. Are you using J2EE extension on your eclipse ?
can you please provide eclipse logs found in the metdata folder in your workspace?
Didn't understand about extension. My version of eclipse is java EE for web developers:
Eclipse Java EE IDE for Web Developers.
Version: Mars.2 Release (4.5.2)Build id: 20160218-0600
That's written on "about" page.
Here are the logs
There is an issue with EE eclipse tools that caused such crash I believe this is what you have, we solved it here but not yet in a released plugin. I would suggest some workaround and please update me how this works for you to ensure we solved this for good in the coming release.
Your logs shows:
!MESSAGE Bind DebugProcessListener_25_1462186377380 with RMI registry on 10Â 987
Not sure why the RMI port is corrupted like this, but the first workaround is you manually go change it to 10988 as in the snapshot. To get to this windows from run menu choose run configurations and select from left panel your server project. Please tell me what is written there to understand this corrupted logs.
Good day, Hany.
That didn't work.
At "run configuration" page was 10987 RMI port. After i've changed it to 10988 exception still appears.
Then i tryed eclipse for java developers. I created new OScript project in new workspace but server didn't start at all, then i tryed to change port to 10988 again and it did help, but java exception after "." still remains.
here is log from that new eclipse instance.
Good day Anton,
That is really weried, let me try to get the state here :
- have you closed all eclipse instaces and only running the new Java (only) eclipse ?
- Have you shut down all the JVM running on your system (from the Task explorer or better restart your system)
- When changing the port of the running server, you must stop the server first then change the port and restart it.
- Are these logs from the new Eclipse, if so are you sure you downloaded the right package I see still conflicts with shortcut keys not reproduicble when I tried this version.
can you please confirm these settings and give it another try and update me ?
Thanks,
Hany
Hello, Hany.
So i repeat experiment:
1. I restart my vm where all my environment is
2. start eclipse for java developers, here is info from about page:
Eclipse IDE for Java Developers
3. switch to new workspace, create new oscript project
4. restart sever just in case
5. in module explorer "right click" on server --> New script
6. type "Assoc." in new window and get exception:
Problem signature: Problem Event Name: APPCRASH Application Name: javaw.exe Application Version: 7.0.450.18 Application Timestamp: 5254005d Fault Module Name: StackHash_547a Fault Module Version: 6.3.9600.17031 Fault Module Timestamp: 530895af Exception Code: c0000374 Exception Offset: PCH_64_FROM_ntdll+0x000000000009B13A OS Version: 6.3.9600.2.0.0.400.8 Locale ID: 1049 Additional Information 1: 547a Additional Information 2: 547ac4a3927600e293867075cae7097e Additional Information 3: 7257 Additional Information 4: 7257c1ec40458f172645c6831a09d071
Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=280262
If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
7. then i check port setting, it's set to 10987
8. i stop server, change setting to 10988, then try steps 4-6 and get the same result
Log file included
Have some extra info.
I've found out that the problem for me is environment-dependant. Tried this config on vm for another customer and the error didn't appear.
Thanks Anton for the update !
Yes, it is for sure something local to your environement, bascially the problem from the logs is this exception
java.net.SocketException: Connection reset!STACK 0java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset
I keep trying to figure out what could be similatenously running that causes this exception to occur. It is hard while I do not have your environment setup to reproduce. If you can get "netstat" listing and "tasklist" of the system where this occur it may gives an idea what is going on.
Couldn't post listings to message, so added as txt to attachments
Hello, Hany!
I have another update for you.
We've been looking through eclipse log too, and i believe "Connection reset" part appears after javavm or cs-server crash. The exception about Content Assistant fail i think is:
!ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-13 14:47:52.190
!MESSAGE
!STACK 0
java.lang.NullPointerException
at com.opentext.oscript.parser.Location.<init>(Location.java:13)
at com.opentext.oscript.parser.AST.ASTBase.<init>(ASTBase.java:19)
at com.opentext.oscript.parser.AST.Expr.ExprBase.<init>(ExprBase.java:11)
at com.opentext.oscript.parser.AST.Expr.Id.<init>(Id.java:12)
at com.opentext.oscript.parser.ASTBuilder.visitScriptBody(ASTBuilder.java:737)
at com.opentext.oscript.parser.ASTBuilder.visitScriptBody(ASTBuilder.java:32)
at com.opentext.oscript.parser.OScriptParser$ScriptBodyContext.accept(OScriptParser.java:1467)
at com.opentext.oscript.parser.utils.ParserTools.parseFileThen(ParserTools.java:144)
at com.opentext.oscript.parser.utils.ParserTools.parseFileThen(ParserTools.java:89)
at com.opentext.oscript.parser.utils.ParserTools.parseFileThen(ParserTools.java:85)
at com.opentext.oclipse.ui.editor.AbstractOclipseTextEditor.runWithAST(AbstractOclipseTextEditor.java:271)
at com.opentext.oclipse.ui.editor.OccurrenceMarkerListener.selectionChanged(OccurrenceMarkerListener.java:47)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyPostSelectionListeners(SelectionService.java:173)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$4(SelectionService.java:170)
at org.eclipse.ui.internal.e4.compatibility.SelectionService$2.selectionChanged(SelectionService.java:86)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:156)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:154)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:151)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:253)
at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:251)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:334)
at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:348)
at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:34)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:128)
at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2755)
at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2703)
at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2682)
at org.eclipse.swt.widgets.Display.runTimer(Display.java:4271)
at org.eclipse.swt.widgets.Display.messageProc(Display.java:3358)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Looks like there is some problem at OScriptParser.java
Hi Anton,
Thank you for the update, sorry I ook at the listing you sent but no obvious thing was there and I got to look for other stuff here but I hope we get to the problem on this system soon !
As for the parser exception you sent, I am aware of it and on my list to process but unfortuanetly it is not the crash cause. It is noisy but harmless, I guess you would see it on the logs of the running system as well.
Just to get full view of the system of the problem, is there a firewall or something blocking or administer the network/sockets there ?
Hi Hany,
I've searched through logs on working environment and could not find 'oscript' keyword, there is no such exception.
No, standart Windows Firewall is disabled and there is no other firewall software.
We do have proxy in our network, but I use on both working and not working environment
I try to narrow it down to find where this happening, is the other machine you mentioned working good have the same CS installation " Content Server 10.5 Update 2015-06 (version 10.5.0.1715)" ?
can you send to me the CS logs for failing case and success case please ? OTHOME/logs
I am more interested in thread0.out there but if you like to zip the whole folder that will be better.
Thank you!
our "working-ok" environments are:
So, for the logs the test case on both working and non-working evironments was:
Logs included.
After investigation, We found this was an issue with the CS itslef (not the IDE) only the 10.5 June update. If you can apply patch to upgrade to later update, this should have been resolved. Can you give it a try and update how this worked for you ?
Hi, Hany.
It is impossible to update production cs-instanse right now, and we fear to update developer evnvironment, due to possible incompatibility of code written on latest update for an older one. Is there some patch we can use for now, before the update?
