Re: Bug#859660: Bug#859660: artemis running issue
- To: firstname.lastname@example.org, Debian Java List <email@example.com>
- Subject: Re: Bug#859660: Bug#859660: artemis running issue
- From: Andreas Tille <firstname.lastname@example.org>
- Date: Mon, 24 Apr 2017 08:36:53 +0200
- Message-id: <[🔎] 20170424063653.GA6320@an3as.eu>
- In-reply-to: <20170407104342.GD10611@an3as.eu>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <20170407104342.GD10611@an3as.eu>
Hi Java developers,
is there any known issue with running JARs via symlink to /usr/bin?
I suspect this is the problem with this bug but I wonder what might be
the recommended way from Java team about this way to start Java programs
that used to work but is not always relieable.
On Fri, Apr 07, 2017 at 12:43:42PM +0200, Andreas Tille wrote:
> On Fri, Apr 07, 2017 at 12:17:08PM +0200, Sascha Steinbiss wrote:
> > Hi,
> > > على الأربعاء 5 نيسـان 2017 12:32، كتب Jerome:
> > >> When running artemis package, get this issue :
> > >>
> > >> $ art
> > >> bash: /usr/bin/art: cannot execute binary file: Exec format error
> > Probably something to do with jarwrapper? I remember running into
> > something similar quite some time ago.
> I'd assume the same. I can confirm that I can not reproduce here as
> well but the problem sounds like jarwrapper connected. I do not
> remember what package I had in the past with a similar issue but
> providing a shell wrapper calling java with some options and the jar
> file solved the issue.
> It seems that jarwrapper is not really reliable - as far as I know
> specifically if users are using a self compiled kernel where this
> feature can be switched of.
> Hope this helps