Found it.  It's this bit of code in console.js, console.profile.get():

                if (!object) {
                    var item = localStorage.getItem('composum.core.' + aspect);
                    if (item) {
                        object = JSON.parse(item);
                        console.profile.aspects[aspect] = object;
                    }
                }


I was looking at one of my components last in the console, which

resulted in the view location to be stored in local storage.  I then

nuked my repo and started fresh, and so the attempt to view

the now-missing component fails when I re-enter the console.


That's easy enough to sort out in my browser for now.  If I were

to log a JIRA issue, should it go to Sling or Felix?


jgl

________________________________
From: John Logan <john.lo...@texture.com>
Sent: Wednesday, March 15, 2017 9:11:02 AM
To: users@sling.apache.org
Subject: Felix console stopped working?

This is strange.

The Felix console on my Sling instance stopped working.  It doesn't work
even if I start with a clean repository.  Is anyone else seeing this?  I can't
find anything on the mailing list about this, nor did anything obvious
pop up in JIRA.

The HTTP error page I get instead of the console UI is:

HTTP ERROR: 404

Problem accessing /system/console/components/449. Reason:

    Not Found

I see these log messages:

15.03.2017 08:56:18.587 *WARN* [0:0:0:0:0:0:0:1 [1489593377889] GET 
/bin/packages.html HTTP/1.1] 
org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl Error while 
registering nodetypes. Package installation might not work correctly.
javax.jcr.AccessDeniedException: Failed to register namespace mapping vlt -> 
http://www.day.com/jcr/vault/1.0
        at 
org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:231)
        at 
org.apache.jackrabbit.oak.plugins.name.ReadWriteNamespaceRegistry.registerNamespace(ReadWriteNamespaceRegistry.java:97)
        at 
org.apache.jackrabbit.vault.fs.spi.impl.jcr20.JcrNodeTypeInstaller.install(JcrNodeTypeInstaller.java:100)
        at 
org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.initNodeTypes(JcrPackageManagerImpl.java:629)
        at 
org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.<init>(JcrPackageManagerImpl.java:104)
        at 
org.apache.jackrabbit.vault.packaging.PackagingService.getPackageManager(PackagingService.java:51)

I thought I'd try to download a new version of the launchpad (I was using
org.apache.sling.launchpad-9-20170117.181656-2922.jar straight
from apache.org), and the Apache repo is also giving me an error:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET 
/content/groups/snapshots/org/apache/sling/org.apache.sling.launchpad/9-SNAPSHOT/.

Reason: Error reading from remote server

Thanks in advance for any assistance you can provide!

John

Reply via email to