Major Description
I have a fresh install of Nexus 3 from
It starts up fine to
*SYSTEM org.eclipse.jetty.server.AbstractConnector - Started InstrumentedSelectChannelConnector@0.0.0.0:8081
2014-12-30 15:13:22,714-0800 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Started
However when I then go the UI in a browser it hangs at initializing and in the log I see
2014-12-30 15:13:42,038-0800 INFO [qtp291080617-260] *SYSTEM org.apache.shiro.nexus.NexusDefaultWebSessionManager - Global session timeout: 1800000 ms
2014-12-30 15:13:42,054-0800 INFO [qtp291080617-260] *SYSTEM org.apache.shiro.session.mgt.AbstractValidatingSessionManager - Enabling session validation scheduler...
2014-12-30 15:13:42,065-0800 INFO [qtp291080617-260] *UNKNOWN org.sonatype.nexus.internal.velocity.VelocityEngineProvider - Creating Nexus VelocityEngine
2014-12-30 15:13:43,294-0800 INFO [qtp291080617-260] *UNKNOWN com.sonatype.nexus.analytics.internal.EventSubmitterImpl - Service URL: https://analytics.sonatype.com
When trying to ping analytics I get only timeouts
ping analytics.sonatype.com
PING analytics-elb-165212944.us-east-1.elb.amazonaws.com (54.210.23.53): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Imho this should not stop Nexus UI from returning even if analytics is unavailable.
