You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/09 21:05:43 UTC

[jira] Created: (MAVENPROXY-14) Crash at startup with missing proxy.list

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVENPROXY-14

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVENPROXY-14
    Summary: Crash at startup with missing proxy.list
       Type: Bug

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-component-proxy

   Assignee: Ben Walding
   Reporter: Joerg Schaible

    Created: Thu, 9 Sep 2004 6:48 AM
    Updated: Thu, 9 Sep 2004 6:48 AM

Description:
maven-proxy fails with an exception at startup, if the properties file does not contain at least an empty entry for proxy.list.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MAVENPROXY-14) Crash at startup with missing proxy.list

Posted by ji...@codehaus.org.
The following comment has been added to this issue:

     Author: Ben Walding
    Created: Fri, 17 Sep 2004 8:53 PM
       Body:
Yeah I noticed this yesterday.  Jetty does not like running out of an uberjar anymore. (Basically it does a getPackage() on a class and this returns null under classworlds).

The bug is open in classworlds (CLASSWORLDS-1) and I'll be taking a look at it soon.

I've started committing some scripts to run the proxy not under in an uberjar (a .sh and .bat file in src/bin).  This will work around the problem.

The other upside from not using uberjar is that it starts a lot quicker - uberjar introduces a 15 second startup time.




---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVENPROXY-14?page=comments#action_24206

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVENPROXY-14

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVENPROXY-14
    Summary: Crash at startup with missing proxy.list
       Type: Bug

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-component-proxy

   Assignee: Ben Walding
   Reporter: Joerg Schaible

    Created: Thu, 9 Sep 2004 6:48 AM
    Updated: Fri, 17 Sep 2004 8:53 PM

Description:
maven-proxy fails with an exception at startup, if the properties file does not contain at least an empty entry for proxy.list.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MAVENPROXY-14) Crash at startup with missing proxy.list

Posted by ji...@codehaus.org.
The following comment has been added to this issue:

     Author: Marcus Crafter
    Created: Fri, 17 Sep 2004 12:29 PM
       Body:
Hi There,

Looks like the current snapshot fails to start up, even if there is a
proxy.list set:

fs01a[/home/marcadm]:40>java -jar /usr/local/maven-proxy/maven-proxy-standalone-20040917-uber.jar /usr/local/maven-proxy/mavenproxy.properties
maven-proxy Unversioned
Saving repository at /var/tmp/proxy-repo
Scanning repository: http://www.ibiblio.org/maven
Scanning repository: http://dist.codehaus.org
Starting...
Internal error:
java.lang.NullPointerException
        at org.mortbay.util.ThreadPool.<init>(ThreadPool.java:57)
        at org.mortbay.util.ThreadedServer.<init>(ThreadedServer.java:103)
        at org.mortbay.http.SocketListener.<init>(SocketListener.java:73)
        at org.apache.maven.proxy.standalone.Standalone.doMain(Standalone.java:141)
        at org.apache.maven.proxy.standalone.Standalone.main(Standalone.java:79)        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.codehaus.classworlds.Launcher.launchStandard(Launcher.java:410)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:344)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:474)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.codehaus.classworlds.boot.Bootstrapper.bootstrap(Bootstrapper.java:209)
        at org.codehaus.classworlds.boot.Bootstrapper.main(Bootstrapper.java:116)


proxy.list is set to 'one' which is our local proxy here.

Any ideas what might be causing the error? Any further information I can provide?

Cheers,

Marcus
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVENPROXY-14?page=comments#action_24189

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVENPROXY-14

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVENPROXY-14
    Summary: Crash at startup with missing proxy.list
       Type: Bug

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-component-proxy

   Assignee: Ben Walding
   Reporter: Joerg Schaible

    Created: Thu, 9 Sep 2004 6:48 AM
    Updated: Fri, 17 Sep 2004 12:29 PM

Description:
maven-proxy fails with an exception at startup, if the properties file does not contain at least an empty entry for proxy.list.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Closed: (MAVENPROXY-14) Crash at startup with missing proxy.list

Posted by ji...@codehaus.org.
Message:

   The following issue has been closed.

   Resolver: Ben Walding
       Date: Sat, 18 Sep 2004 10:39 PM

Rolled back to jetty 5.0.RC2. Works now.

The beginnings of a non uberjar setup are still in there, but it's not created during the distribution creation, so uberjar is still preferrred
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVENPROXY-14

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVENPROXY-14
    Summary: Crash at startup with missing proxy.list
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-component-proxy

   Assignee: Ben Walding
   Reporter: Joerg Schaible

    Created: Thu, 9 Sep 2004 6:48 AM
    Updated: Sat, 18 Sep 2004 10:39 PM

Description:
maven-proxy fails with an exception at startup, if the properties file does not contain at least an empty entry for proxy.list.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org