Anyway, I think you found something.

If I compare the etc folder from a created instance with the etc folder from the root instance, a bunch of files are "missing", including the org.apache.command.acl* and the jmx.acl* files.

More over, I think the properties file from the instances is not up to date with all properties.

I'm reviewing and fixing that.

Regards
JB

On 12/21/2013 06:40 AM, Ryan Moquin wrote:
I have no doubt it works correctly except the shutdown of every test
starts doing thag now.  If you run my cellar fork, you should see the
issue happen on a lot of tests .

Thanks,
Ryan

On Dec 21, 2013 12:36 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net
<mailto:j...@nanthrax.net>> wrote:

    Hi Ryan,

    let me take a look on that. AFAIR, I tested it without problem when
    preparing Karaf 3.0.0 release.

    Regards
    JB

    On 12/20/2013 10:47 PM, Ryan Moquin wrote:

        Hi, I ran into a problem recently as I was working on some code
        where
        Karaf responds with the following error when I execute an
        "instance:stop" command:

        Caused by: java.lang.SecurityException: Insufficient credentials.
                  at
        
org.apache.karaf.service.__guard.impl.GuardProxyCatalog$__ProxyInvocationListener.__preInvoke(GuardProxyCatalog.__java:527)[27:org.apache.karaf.__ser
        vice.guard:3.0.0.SNAPSHOT]
                  at
        
org.apache.aries.proxy.impl.__ProxyHandler$1.invoke(__ProxyHandler.java:52)[12:org.__apache.aries.proxy.impl:1.0.2]
                  at
        
org.apache.aries.proxy.impl.__ProxyHandler.invoke(__ProxyHandler.java:119)[12:org.__apache.aries.proxy.impl:1.0.2]
                  at
        
org.apache.karaf.shell.__console.commands.$__BlueprintCommand1284042692.__execute(Unknown
        Source)[39:org.apache.karaf.__shell.console:3.0.0.SNAPSHO
        T]
                  at
        
org.apache.felix.gogo.runtime.__CommandProxy.execute(__CommandProxy.java:78)
        ...

        I'm using the default karaf/karaf credentials which work to
        connect to
        an instance, but for some reason this happens whenever I try to
        stop the
        instance... is there something additional to be aware of in
        regards to
        the GuardProxyCatalog?  I'm going to take a look at the source,
        but just
        in case nothing turns up, I thought I'd ask to see if anyone has ran
        into something like this?

        Regards,
        Ryan


    --
    Jean-Baptiste Onofré
    jbono...@apache.org <mailto:jbono...@apache.org>
    http://blog.nanthrax.net
    Talend - http://www.talend.com


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to