The connection (using the key) is OK ?
Maybe it's related to KARAF-3819 (but it looks different).
I gonna dig.
Thanks,
Regards
JB
On 07/08/2015 04:45 PM, Gary Hodgson wrote:
Hi again
Sorry to be dragging the thread out like this, but I think I found the
"real" cause of the problem. The repo config change was a red herring,
I hadn't realised that what I was also doing after creating new instance
was updating keys.properties to uncomment the karaf key. I can't say
why this causes the error message though.
These are the steps I took to reproduce the problem:
* Started a new install of karaf and connect (on Windows 7 btw.).
* Create a new instance.
* Manually update keys.properties under etc of the instance,
uncommenting the karaf entry.
* Start and connect to the instance.
* run la causes the error.
Again, sorry for the run-around in defining this problem but I thought
it would be worthwhile adding this information.
On 8 July 2015 at 15:50, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>> wrote:
Thanks for the update Gary.
Regards
JB
On 07/08/2015 03:47 PM, Gary Hodgson wrote:
Yeah I think it was definitely something wrong with the repo,
because
after updating the indexes the problem appears to have gone away.
Unfortunately the nexus logs don't appear to show anything that
would
cause this problem. I think we'll just have to put it down to an
unreproducible environment problem.
On 8 July 2015 at 14:42, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
What's on your repo ?
It looks like something on your repo (or your repo itself)
pollutes
Karaf.
Regards
JB
On 07/08/2015 01:29 PM, Gary Hodgson wrote:
So I did some more playing around and could recreate
the issue. It
turns out that it has something to do with me updating the
"org.ops4j.pax.url.mvn.repositories" property to my
local Nexus
repository before starting the instance. If I replaced all
entries with
my repo, or had it at the top of the list, I would get the
"Context 0
does not evaluate to a bundle" error issuing the la
command after
connecting.
I therefore performed a manual update of the repository
indices
and now
the problem appears to have gone away. I can't say for
sure
what the
exact cause is (stale information in the repository
perhaps?), I
mention
this in case others have the same problem.
On 8 July 2015 at 11:28, Jean-Baptiste Onofré
<[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
<mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>> wrote:
Maybe related to region, not sure. Let me double
check.
Regards
JB
On 07/08/2015 11:25 AM, Achim Nierbeck wrote:
Hi Gary,
no problem at all, looking at the stack trace
and given
your
input, I'd
say something else did go wrong there and it's
been
unrelated to
decanter.
Never the less we should keep an eye on this,
as it
might happen for
someone else too.
regards, Achim
2015-07-08 11:21 GMT+02:00 Gary Hodgson
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>>>:
Hi again,
So, embarrassingly I can't now recreate the
problem, either
in a new
instance nor even with a fresh karaf
install. The old
install still
exhibits the problem but I suspect it was a
problem with the
creation of the instance itself. FWIW
here's the
stacktrace..
2015-07-08 10:10:38,189 | ERROR | nsole
user karaf
| ShellUtil
| 43 -
org.apache.karaf.shell.core - 4.0.0 |
Exception caught while executing command
java.lang.IllegalArgumentException:
Context 0 does not
evaluate to a
bundle
at
org.apache.karaf.bundle.core.internal.BundleServiceImpl.doGetBundleContext(BundleServiceImpl.java:162)
at
org.apache.karaf.bundle.core.internal.BundleServiceImpl.selectBundles(BundleServiceImpl.java:81)
at
org.apache.karaf.bundle.command.BundlesCommand.execute(BundlesCommand.java:53)
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.0]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:267)[43:org.apache.karaf.shell.core:4.0.0]
at
java.lang.Thread.run(Thread.java:745)[:1.8.0_25]
Sorry the the inconvenience :/
Gary
On 8 July 2015 at 10:29, Gary Hodgson
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>>> wrote:
Hi Achim, That explains it - i was only
registered for the
"Karaf - Dev" list.
Ill reproduce the problem and send any
relevant logs asap.
On 8 July 2015 at 10:24, Achim Nierbeck
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>>> wrote:
Hi,
for the message of the forum, you
have to be
registered to
the mailing-list to post to the
mailing-list via
the forum.
actually I tested Decanter quite
a lot
with Karaf
4, and
couldn't see such issues, do you
have a
stack-trace?
regards, Achim
2015-07-08 10:22 GMT+02:00
Jean-Baptiste
Onofré
<[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>
<mailto:[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>
<mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>>:
Hi Gary,
Let me try to reproduce.
Decanter 3.0.0-SNAPSHOT (that
will be
released
as 3.0.0)
has been tested on Karaf 2 &
3 (not
yet on 4).
I will test it today and fix
if required.
Thanks !
Regards
JB
On 07/08/2015 10:18 AM, Gary
Hodgson
wrote:
Hi,
(I posted this on June
27th via
the forum
but it
still has a message:
"This post has NOT been
accepted
by the
mailing list
yet.", so I will
post it here aswell...)
I was just playing around
with the
recent 4.0.0
release and found the
following issue when
installing
decanter
features.
I created a new instance,
started
it and
connected.
Then I ran the
following:
feature:repo-add decanter
feature:install elasticsearch
decanter-appender-elasticsearch
decanter-collector-log
decanter-simple-scheduler
la
The bundle:list command
throws an
error:
"Context 0
does not evaluate to
a bundle".
The decanter features
appear to
have installed
correctly.
Let me know if I can add
any further
information.
Best regards,
Gary
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>>
<mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>> <mailto:[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Apache Member
Apache Karaf
<http://karaf.apache.org/>
Committer & PMC
OPS4J Pax Web
<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook
<http://bit.ly/1ps9rkS>
Software Architect / Project
Manager /
Scrum Master
--
Apache Member
Apache Karaf <http://karaf.apache.org/>
Committer & PMC
OPS4J Pax Web
<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer
& Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook
<http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum
Master
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
<mailto:[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
