Eclipse, GWT plugin. Debugger does't work - eclipse

Ubuntu 10.10
SpringSource Tool Suite Version: 2.5.0.M3 Build Id: 201008251000
When I try to debug, Debug As-> web Application, the tab with Source not found opens. With stack trace in debug mode:
Thread [main] (Suspended (exception ClassNotFoundException))
URLClassLoader$1.run() line: 202 [local variables unavailable]
AccessController.doPrivileged(PrivilegedExceptionAction<T>, AccessControlContext) line: not available [native method]
Launcher$ExtClassLoader(URLClassLoader).findClass(String) line: 190
Launcher$ExtClassLoader.findClass(String) line: 229
Launcher$ExtClassLoader(ClassLoader).loadClass(String, boolean) line: 307
Launcher$AppClassLoader(ClassLoader).loadClass(String, boolean) line: 296
Launcher$AppClassLoader.loadClass(String, boolean) line: 301
Launcher$AppClassLoader(ClassLoader).loadClass(String) line: 248
InstrumentationImpl.loadClassAndStartAgent(String, String, String) line: 280
InstrumentationImpl.loadClassAndCallPremain(String, String) line: 338
In the Development Mode tab is text with Development mode is loading, where should be web app URL provided... So what is going on?

This was eclipse bug. ClassNotFoundException: caught and uncaught breakpoint was set by unknown reason.. So it should be deleted from 'Breakpoints' window/tab.
More details here: http://www.popcornfarmer.com/gamedev/2009/01/eclipse-debug-error/

Related

C0000005 ACCESS_VIOLATION Exception with Progress Openedge when calling a Web Service

I am trying to hit an external web service using Progress OE 11.5. When I execute the code from GUI Procedure Editor or the CHUI Procedure Editor, it crashes when calling the API
RUN ProcessTrack IN hTrackPortType(INPUT lcRequest, OUTPUT lcResponse) no-error.
I don't get any errors. The progress GUI window just crashes.
When I traced the logs it has "C0000005 ACCESS_VIOLATION" exception. Any idea why this is caused? But when I access the same web services from SoapUI or from a Python program it works fine. I am not sure if Progress OpenEdge has any access restrictions to contact the apis.
I have the full stack trace here.
=====================================================
PROGRESS stack trace as of Fri Aug 07 12:26:40 2020
=====================================================
Progress OpenEdge Release 11.5 build 1114 on WINNT
Startup parameters:
-pf C:\Progressx86\OpenEdge\startup.pf,-cpinternal ISO8859-1,-cpstream ISO8859-1,-cpcoll Basic,-cpcase Basic,-d mdy,-numsep 44,-numdec 46,(end .pf),-param C:\.....\api_request.p
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 025C21CC 1C3:0034002D
Registers:
EAX:086496B8
EBX:00000002
ECX:03100000
EDX:03100000
ESI:59DF2175
EDI:085AA1E0
CS:EIP:0023:025C21CC
SS:ESP:002B:00F4BFA0 EBP:00F4BFD0
DS:002B ES:002B FS:0053 GS:002B
Flags:00210206
Debugging dll: C:\Progressx86\OpenEdge\bin\DBGHELP.DLL
Symbol Path:
C:\Progressx86\OpenEdge\bin;C:\Progressx86\OpenEdge\pdbfiles
Call Stack:
Address Frame
025C21CC 00F4BF9C 0000:00000000
085AA1E0 00F4BFD0 0000:00000000
59DF27DB 00F4BFDC WSDLAttribute::getHandle+3F52B
59DA415C 00F4F130 WSDLArray_Empty+23ABC
59DCD9A0 00F4F144 WSDLAttribute::getHandle+1A6F0
59E502A8 00F4F198 WSDLAttribute::getHandle+9CFF8
59E5032C 00F4F1CC WSDLAttribute::getHandle+9D07C
59DCF04E 00F4F204 WSDLAttribute::getHandle+1BD9E
59D9B724 00F4F240 WSDLArray_Empty+1B084
59E50403 00F4F260 WSDLAttribute::getHandle+9D153
59D55D6F 00F4F2A0 csp_tweakFileURL+312F
** ABL Stack Trace **
--> C:\....\p56215_api_request.ped at line 54 (C:\.....\p56215_api_request.ped)
adecomm/_runcode.p at line 665 (adecomm/_runcode.r)
ExecuteRun adeedit/_proedit.p at line 3613 (adeedit/_proedit.r)
RunFile adeedit/_proedit.p at line 10625 (adeedit/_proedit.r)
USER-INTERFACE-TRIGGER adeedit/_proedit.p at line 1985 (adeedit/_proedit.r)
adeedit/_proedit.p at line 12280 (adeedit/_proedit.r)
_edit.p at line 408 (C:\Progressx86\OpenEdge\gui\_edit.r)
** Persistent procedures/Classes **
** PROPATH **
.,C:\Progressx86\OpenEdge\gui,C:\Progressx86\OpenEdge\gui\ablunit.pl,C:\Progressx86\OpenEdge\gui\adecomm.pl,C:\Progressx86\OpenEdge\gui\adecomp.pl,C:\Progressx86\OpenEdge\gui\adedesk.pl,C:\Progressx86\OpenEdge\gui\adedict.pl,C:\Progressx86\OpenEdge\gui\adeedit.pl,C:\Progressx86\OpenEdge\gui\adeicon.pl,C:\Progressx86\OpenEdge\gui\aderes.pl,C:\Progressx86\OpenEdge\gui\adeshar.pl,C:\Progressx86\OpenEdge\gui\adeuib.pl,C:\Progressx86\OpenEdge\gui\adeweb.pl,C:\Progressx86\OpenEdge\gui\adexml.pl,C:\Progressx86\OpenEdge\gui\dataadmin.pl,C:\Progressx86\OpenEdge\gui\OpenEdge.BusinessLogic.pl,C:\Progressx86\OpenEdge\gui\OpenEdge.Core.pl,C:\Progressx86\OpenEdge\gui\OpenEdge.ServerAdmin.pl,C:\Progressx86\OpenEdge\gui\prodict.pl,C:\Progressx86\OpenEdge\gui\protools.pl,C:\Progressx86\OpenEdge,C:\Progressx86\OpenEdge\bin
** Databases (logical/type/physical) **
** End of Protrace **
This KnowledgeBase post indicates that this is a known error. If you run a version below 11.7.1 you should consider upgrading to the latest version of 11.7 (currently 11.7.6). If you run a version later than 11.7.1 that's mentioned in the article you should consider contacting Progress support.
EDIT: since running 11.5 upgrading should be a priority!

Moodle 3.5 self registration mail failed: auth_emailnoemail error

I am running moodle 3.5.3 LTS and I activate self registration.
When an user tries to create a an account, the following error happened:
Debug info:
Error code: auth_emailnoemail
Stack trace:
line 482 of /lib/setuplib.php: moodle_exception thrown
line 142 of /auth/email/auth.php: call to print_error()
line 99 of /auth/email/auth.php: call to auth_plugin_email->user_signup_with_confirmation()
line 89 of /login/signup.php: call to auth_plugin_email->user_signup()
When I execute the following php script, the mail is sent without error:
<?php
mail("me#mydomain.com","My subject","this is a test from php mail function");
I can send successfully mail from the command line using the mail command:
mail -s "Hello World" me#mydomain.com
What's wrong?
Setting noreplyaddress configuration field fixes the issue.
NB: enabling debugsmtp setting can be helpful to debug emails issues.

Cloudera Manager add services failed with ArithmeticException

I've installed Cloudera Manager in a three-machine cluster. While I added CDH5 services (including Hive,Spark,Yarn...) to cluster, it then failed with "ArithmeticException: / by zero".
version: Cloudera Enterprise Data Hub Edition trail 5.4.5 (#5 built by jenkins on 20150728-0320 git: ...)
org.drools.runtime.rule.ConsequenceException:Exception executing consequence for rule "Compute hiveserver2_spark_executor_cores" in com.cloudera.cmf.rules: org.drools.RuntimeDroolsException: java.lang.ArithmeticException: / by zero
at DefaultConsequenceExceptionHandler.java line 39
in org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler handleException()
Last caused-by is:
Caused by: java.lang.ArithmeticException:/ by zero
at ComputationFunctions.java line 278
in com.cloudera.cmf.rules.ComputationFunctions calculateHiveSparkExecutorMemoryTotal()
1. ComputationFunctions.java line 278
in com.cloudera.cmf.rules.ComputationFunctions calculateHiveSparkExecutorMemoryTotal()
2. Rule_Compute_HiveServer2_executor_and_driver_memory_and_overehead_25364fb53f7d4bf08ec8a11bca01bcf8.java line 16
in com.cloudera.cmf.rules.Rule_Compute_HiveServer2_executor_and_driver_memory_and_overehead_25364fb53f7d4bf08ec8a11bca01bcf8 accumulateExpression1()
3. Rule_Compute_HiveServer2_executor_and_driver_memory_and_overehead_25364fb53f7d4bf08ec8a11bca01bcf8AccumulateExpression1Invoker.java line 31
in com.cloudera.cmf.rules.Rule_Compute_HiveServer2_executor_and_driver_memory_and_overehead_25364fb53f7d4bf08ec8a11bca01bcf8AccumulateExpression1Invoker evaluate()
4. JavaAccumulatorFunctionExecutor.java line 107
in org.drools.base.accumulators.JavaAccumulatorFunctionExecutor accumulate()
5. Accumulate.java line 173
in org.drools.rule.Accumulate accumulate()
......
Anybody help? Or tells me where these compiled class such as "Rule_Compute_HiveServer2_executor_and_driver_memory_and_overehead_25364fb53f7d4bf08ec8a11bca01bcf8.java" is placed. I attempt to replace this class with more debug message.
Many thanks,

remote debug from windows to unix ClassNotFoundException

I'm trying to configure eclipse running on windows to remote debug a java application i have running on a unix box. The remote debugger connects but the Launcher fails with the following stack trace:
Thread [main] (Suspended (exception ClassNotFoundException))
URLClassLoader$1.run() line: 200 [local variables unavailable]
AccessController.doPrivileged(PrivilegedExceptionAction<T>, AccessControlContext) line: not available [native method]
Launcher$AppClassLoader(URLClassLoader).findClass(String) line: 188
Launcher$AppClassLoader(ClassLoader).loadClass(String, boolean) line: 306
Launcher$AppClassLoader.loadClass(String, boolean) line: 268
Launcher$AppClassLoader(ClassLoader).loadClass(String) line: 251
Launcher$AppClassLoader(ClassLoader).loadClassInternal(String) line: 319
I have the project src referenced in the Source tab of the debug config, the default dir contains the jars a I need and I checked 'Search for duplicate source files on the path' incase that made any difference... it didn't.
when stepping through I noticed the AppClassLoader has a URLClasspath member called ucp which has the a path ArrayList containing items from the unix classpath (ie unix paths like: /home/example.jar ) - I'm wondering if these are trying to be resolved on windows (the debug session I'm running in eclipse) which is causing the error ??
I've been searching the web for answers all day without luck - has anyone dealt with this before or got and suggestion how to resolve ?
thanks in advance...

V8 version in node and ChromeDevTools?

My main questions are:
What version of V8 am I running from node 0.4.10?
How can I tell if this version is compatible with ChromeDevTools 0.2.2 in Eclipse?
Background: I've almost got Eclipse working for debugging node.js remotely. In fact it works perfectly (after adding a server proxy) for a simple "Hello World" app, but it won't hook up properly when I add "express" to the mix. The Eclipse error is:
An internal error occurred during: "Debug session initialization:
Remote NodeJS". Exception occured in callback
...which I tracked down to line 61 of the this source code (Thanks to the misspelling of "occured".)
I'd like to eliminate version skew possibilities before going further.
EDIT: Dug the stack trace out of the error log. Hmmm, maybe I have an encoding problem in my server proxy?
java.lang.RuntimeException: Exception occured in callback
at org.chromium.sdk.CallbackSemaphore.tryAcquire(CallbackSemaphore.java:61)
at org.chromium.sdk.CallbackSemaphore.tryAcquireDefault(CallbackSemaphore.java:29)
at org.chromium.sdk.internal.JavascriptVmImpl.getScripts(JavascriptVmImpl.java:33)
at org.chromium.debug.core.model.VProjectWorkspaceBridge.reloadScriptsAtStart(VProjectWorkspaceBridge.java:121)
at org.chromium.debug.core.model.LaunchInitializationProcedure.execute(LaunchInitializationProcedure.java:80)
at org.chromium.debug.core.model.LaunchInitializationProcedure.access$0(LaunchInitializationProcedure.java:64)
at org.chromium.debug.core.model.LaunchInitializationProcedure$1.run(LaunchInitializationProcedure.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.Exception: Exception saved from callback
at org.chromium.sdk.CallbackSemaphore.callbackDone(CallbackSemaphore.java:72)
at org.chromium.sdk.internal.DebugSession$ScriptLoader$2.callbackDone(DebugSession.java:276)
at org.chromium.sdk.internal.tools.v8.BaseCommandProcessor.callThemBack(BaseCommandProcessor.java:136)
at org.chromium.sdk.internal.tools.v8.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:103)
at org.chromium.sdk.internal.tools.v8.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:109)
at org.chromium.sdk.internal.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:108)
at org.chromium.sdk.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:120)
at org.chromium.sdk.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:206)
Caused by: java.lang.RuntimeException: org.eclipse.core.internal.resources.ResourceException: < is an invalid character in resource name '<eval #83>.chromium'.
at org.chromium.debug.core.util.ChromiumDebugPluginUtil$4.tryCreate(ChromiumDebugPluginUtil.java:247)
at org.chromium.debug.core.util.ChromiumDebugPluginUtil$4.tryCreate(ChromiumDebugPluginUtil.java:1)
at org.chromium.debug.core.util.UniqueKeyGenerator.createUniqueKey(UniqueKeyGenerator.java:22)
at org.chromium.debug.core.util.ChromiumDebugPluginUtil.createFile(ChromiumDebugPluginUtil.java:254)
at org.chromium.debug.core.model.ResourceManager.createAndRegisterResourceFile(ResourceManager.java:106)
at org.chromium.debug.core.model.ResourceManager.addScript(ResourceManager.java:72)
at org.chromium.debug.core.model.VProjectWorkspaceBridge$2.success(VProjectWorkspaceBridge.java:131)
at org.chromium.sdk.internal.DebugSession$ScriptLoader$1$1.call(DebugSession.java:236)
at org.chromium.sdk.internal.DebugSession$ScriptLoader$1.processCall(DebugSession.java:258)
at org.chromium.sdk.internal.DebugSession$ScriptLoader$1.success(DebugSession.java:233)
at org.chromium.sdk.internal.tools.v8.V8Helper$2.success(V8Helper.java:120)
at org.chromium.sdk.internal.tools.v8.V8CommandCallbackBase.messageReceived(V8CommandCallbackBase.java:25)
at org.chromium.sdk.internal.tools.v8.V8CommandCallbackBase.messageReceived(V8CommandCallbackBase.java:1)
at org.chromium.sdk.internal.tools.v8.BaseCommandProcessor$2.call(BaseCommandProcessor.java:99)
at org.chromium.sdk.internal.tools.v8.BaseCommandProcessor$2.call(BaseCommandProcessor.java:1)
at org.chromium.sdk.internal.tools.v8.BaseCommandProcessor.callThemBack(BaseCommandProcessor.java:129)
... 5 more
Caused by: org.eclipse.core.internal.resources.ResourceException: < is an invalid character in resource name '<eval #83>.chromium'.
at org.eclipse.core.internal.resources.Resource.checkValidPath(Resource.java:432)
at org.eclipse.core.internal.resources.File.create(File.java:116)
at org.eclipse.core.internal.resources.File.create(File.java:196)
at org.chromium.debug.core.util.ChromiumDebugPluginUtil$4.tryCreate(ChromiumDebugPluginUtil.java:245)
... 20 more
process.versions in the repl reveals this information:
> process.versions
{ node: '0.4.10', v8: '3.1.8.26', ares: '1.7.4', ev: '4.4', openssl: '1.0.0d' }
There shouldn't be any version-related problem here, at least at initialization stage.
V8 debug protocol is evolving quite slowly.
Unfortunately the message you cite is too general. Do you think you can find a stacktrace somewhere? The message may have 'details' button (but you would probably spot it), also the exception is usually logged. You can try to open a view "General->Error Log" (available in most Eclipse configurations), or you can take a look inside a file in your Eclipse workspace: /.metadata/.log.
The code indicates that there is a cause exception, which is missing from the error message.
Thank you for the spelling error report. :)