Bug 572478

Summary:	What is "setApplicationProperty: called with invalid property"
Product:	[Eclipse Project] JDT	Reporter:	J.F.Lanting <J.F.Lanting>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	sarika.sinha
Version:	4.19
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description J.F.Lanting

2021-03-31 05:10:07 EDT

Several times over the last years (in several ECLIPSE editions), 
while debugging, spurious messages appeared in the console log.
I fail to relate them to anything I do or to any characteristics of the
application that I was debugging then (as far as I know).
The only event I noticed is that they appeared after a dialog.
However they did not seem to touch the functioning of the application.
Still it makes me wonder if something will bother in the future.

Message examples:
2021-03-31 10:49:27.533 java[35570:3232914] ERROR: setApplicationProperty: called with invalid property
2021-03-31 10:50:14.323 java[35570:3232914] ERROR: setApplicationProperty: called with invalid property

More info:
- Java 14.0.2 with
- ECLIPSE Version: 2021-03 (4.19), Build id: I20210303-1800 on
- MacOS 10.15.7 on
- iMac 27" late 2014.
Application: desktop type, without networking.
;JOOP! (that's my name)

Comment 1 Sarika Sinha

2021-03-31 06:24:45 EDT

setApplicationProperty is not part of Debug code which I could see. Have you installed other plugins? 
Is it Eclipse platform SDK or web one?

Comment 2 J.F.Lanting

2021-03-31 06:55:29 EDT

Hi,
pure ECLIPSE SDK, no plug-in's or such.
ECLIPSE installed from "eclipse-SDK-4.19-macosx-cocoa-x86_64.dmg".
Java: installed from "jdk-14.0.2_osx-x64_bin.dmg" (ORACLE).

I am afraid that the messages come from the JAVA SDK itself, but how:
".setApplicationProperty" is, according to the JAVADOC, not a method inside Java.

Then again, I googled to find this:

https://www.jaxfront.org/javadoc/com/jaxfront/core/jep/SetApplicationProperty.html

;JOOP!

Comment 3 Sarika Sinha

2021-03-31 07:13:25 EDT

Any particular action in Eclipse, you can corner out which causes this message?

Comment 4 J.F.Lanting

2021-03-31 07:42:41 EDT

Not that I am aware of; I'm a very simple user.
Even the jar-build I have done by the jar command of the Java SDK set.
;JOOP!

Comment 5 Eclipse Genie

2023-03-25 12:31:37 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 J.F.Lanting

2023-03-25 15:23:17 EDT

I have not seen the message(s) again for some time.
Let's say: dropped (or such).
I was just curious.
;JOOP!