Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR StatusLogger Log4j2 could not find a logging implementation. #5475

Closed
bernhard-kleine opened this issue Oct 18, 2019 · 29 comments · Fixed by #8226
Closed

ERROR StatusLogger Log4j2 could not find a logging implementation. #5475

bernhard-kleine opened this issue Oct 18, 2019 · 29 comments · Fixed by #8226
Labels
bug Confirmed bugs or reports that are very likely to be bugs Logging status: depends-on-external A bug or issue that depends on an update of an external library

Comments

@bernhard-kleine
Copy link

JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 7 6.1 amd64
Java 12.0.2

Steps to reproduce the behavior:

  1. When opening jabref a console starts with this error message
    ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
  2. Then Jabref opens still. I do not know what the effect of this error will be.
  3. ...
Log File
Paste an excerpt of your log file here
@AEgit
Copy link

AEgit commented Oct 18, 2019

JabRef 5.0.0-dev--2019-10-18----bc26c3ac5
Windows 10 10.0 amd64
Java 12.0.2

I can confirm this "issue". As mentioned by @bernhard-kleine I do not know, whether the error is an actual problem, since JabRef starts flawlessly.

As explained by @tobiasdiez the console starts due to a limitation of the software that is used to created the installer: #5468 (comment)
There is already a ticket open to remove the console window:
#5474

@Siedlerchr
Copy link
Member

We also have a ticket open at the log4j guys.
It should not be a problem for n the user as JabRef works with it.

@tobiasdiez tobiasdiez added bug Confirmed bugs or reports that are very likely to be bugs freeze labels Oct 18, 2019
@tobiasdiez tobiasdiez added this to Needs triage in Bugs via automation Oct 18, 2019
@tobiasdiez tobiasdiez added this to the v5.0 milestone Oct 18, 2019
@tobiasdiez tobiasdiez moved this from Needs triage to Normal priority in Bugs Oct 18, 2019
@bernhard-kleine
Copy link
Author

bernhard-kleine commented Oct 18, 2019

the version from 2019-08-25 didnot show the console. What has changed inbetween?

@AEgit
Copy link

AEgit commented Oct 18, 2019

@bernhard-kleine : See here
#5468 (comment)

and here:

#5475 (comment)

@tobiasdiez tobiasdiez added status: depends-on-external A bug or issue that depends on an update of an external library and removed freeze labels Oct 21, 2019
@Siedlerchr Siedlerchr mentioned this issue Dec 15, 2019
5 tasks
@koppor
Copy link
Member

koppor commented Feb 2, 2020

To make is explicit (especially for me): The issue with the console is described here #5474.

@bernhard-kleine
Copy link
Author

bernhard-kleine commented Feb 2, 2020 via email

@Siedlerchr
Copy link
Member

@digdig
Copy link

digdig commented Feb 4, 2020

the version from 2019-08-25 didnot show the console. What has changed inbetween?

neither does 2019-04-19 or 2010-09-16 has the black console problem

@AEgit
Copy link

AEgit commented Feb 4, 2020

@digdig:
See the comments in this thread (and elsewhere) - the reason has already been explained.
#5475 (comment)
#5468 (comment)

@digdig
Copy link

digdig commented Feb 8, 2020

@AEgit Does the explained reason say something about why previous versions are OK and no consoles?
If it has explained, why not roll back to the previous versions?

@Siedlerchr
Copy link
Member

Siedlerchr commented Feb 8, 2020

We switched to a new installer, we now use the native Java packager to create custom versions for each OS. This enables us to directly build native packages/installer for each OS
And there is currently a bug in one of our external dependencies in combination with the new installation system.

Bugs automation moved this from Normal priority to Closed Feb 8, 2020
@Siedlerchr Siedlerchr reopened this Feb 8, 2020
Bugs automation moved this from Closed to Needs triage Feb 8, 2020
@bernhard-kleine
Copy link
Author

Which version is supposed the new version, since the snapshot is still from 2020-06-02?

@AEgit
Copy link

AEgit commented Feb 8, 2020

@bernhard-kleine Which new version are you talking about? Is this relevant to this issue?

@bernhard-kleine
Copy link
Author

I would like to know whether the snapshot from 2020-06-02 has already the new installer or not. Since the statusLogger error is the only thing which is not ok as far as I see, I donot want to download every new snapshot. Maybe you can understand.

@AEgit
Copy link

AEgit commented Feb 8, 2020

You opened the issue yourself (#5475 (comment)) - the new installer has been part of the JabRef dev version since (at least) JabRef 5.0.0-dev--2019-10-18----bc26c3ac5

There is no other current dev version out there, without this "new" installer (at least I am not aware of it).

Do I misunderstand you?

@bernhard-kleine
Copy link
Author

Then I have Christoph misinterpreted. I seemed to me that as of today there was a new installer. Sorry for the noise.

@tobiasdiez
Copy link
Member

The problem is that Log4j2 is simply not compatible with Java 9. I've created a very simple Java 9 application which shows this problem: https://github.com/tobiasdiez/javatestbed.
Currently, I'm in contact with the log4j devs to solve this problem. Luckily the consequences for JabRef are not that negative - the only functionality that does not work because of this issue is the "error console" and errors are only written to the command line.

@tobiasdiez tobiasdiez modified the milestones: v5.0, v5.1 Feb 23, 2020
@jorgman1
Copy link

I do not habe the console log anymore in the latest version:

JabRef 5.0-beta.457--2020-02-22--d38f813
Windows 7 6.1 amd64
Java 13.0.2

@bernhard-kleine
Copy link
Author

bernhard-kleine commented Feb 23, 2020

JabRef 5.0-beta.458--2020-02-23--b2ab177
Windows 10 10.0 amd64
Java 13.0.2

I can confirm that there is any console any further. Thanks a lot. Could be closes! :D

Bugs automation moved this from Needs triage to Closed Feb 24, 2020
@tobiasdiez
Copy link
Member

Sadly, the bug is still there - it's only not displayed anymore because the console window is hidden. For the same reason, the Error console is currently not working (nothing is shown there).

@tobiasdiez tobiasdiez reopened this Feb 26, 2020
Bugs automation moved this from Closed to Needs triage Feb 26, 2020
@tobiasdiez tobiasdiez moved this from Needs triage to High priority in Bugs Mar 25, 2020
@tobiasdiez tobiasdiez removed this from the v5.1 milestone Apr 12, 2020
@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2020

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

@bernhard-kleine
Copy link
Author

@tobiasdiez , @Siedlerchr Is this issue with the Log4j2 resolved, then this should be closed, otherwise it should remain open, even its last activity was 6 months ago.

@AEgit
Copy link

AEgit commented Dec 10, 2020

I think the issue is still present in:

JabRef 5.2--2020-11-07--df80c13
Linux 5.4.0-53-generic amd64
Java 15.0.1

@Siedlerchr
Copy link
Member

Yep, issue is still here, apache log4j team did not fix it yet. Were thinking of switching to another log framework maybe.

@github-actions
Copy link
Contributor

github-actions bot commented Jun 8, 2021

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

@AEgit
Copy link

AEgit commented Jun 9, 2021

JabRef 5.3--2021-06-08--9d1c448
Windows 10 10.0 amd64
Java 16.0.1
JavaFX 16+8

I think the issue is still present in the current dev version.

@koppor
Copy link
Member

koppor commented Jun 9, 2021

Yep, issue is still here, apache log4j team did not fix it yet. Were thinking of switching to another log framework maybe.

In 2021, I am fan of tinylog in contrast to 2017, where I tried to convince people to use jcabi: #3015

@koppor koppor mentioned this issue Jul 13, 2021
6 tasks
@Siedlerchr Siedlerchr mentioned this issue Dec 18, 2021
5 tasks
Bugs automation moved this from High priority to Done Dec 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs Logging status: depends-on-external A bug or issue that depends on an update of an external library
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

8 participants