Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[gregor herrmann]

Control: clone 890905 -1
Control: retitle -1 jabref: doesn't start with liblog4j2-java 2.10.0-1
Control: tag -1 - patch pending

On Sun, 18 Mar 2018 13:48:56 +0100, c.buhtz at posteo.jp wrote:

> Dear Gregor,
> thank you very much for your fast reply.

You're welcome.
 
> > True, this is already reported as #890905/#893138.
> > I ('m trying to) merge those two bugs.
> Sorry, for reporting again. I noticed that bugs. But as a
> Java-foreigner it wasn't clear for me if they address the same issue.

No worries.
 
> > You can run
> > JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> Something is wrong here. Did openjdk-8 changed a bit?

Hm ...
 
> $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
> org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
> at
> org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
> at
> org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
> at
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
> at
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
> at
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
> net.sf.jabref.JabRefMain.<clinit>(JabRefMain.java:37)

Ouch, I have to confirm that I get the same errors.

Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 2.10.0-1

Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.

Not sure if this is a jabref problem or a liblog4j2-java issue; let's
hope the java experts can shed some light on this bug.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Cat Stevens: On The Road To Find Out
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20180318/5586c392/attachment.sig>