1. Sebastian Sebastian
  2. scm-manager
  3. Issues

Issues

Issue #229 resolved

SCM 1.19 does not start under Glassfish 3.1.2

Anonymous created an issue

I had trouble to run SCM 1.19 under GlassFish (3.1.2.2). Glassfish was not able to load one of the classes

[#|2012-08-18T17:19:23.336+0200|SEVERE|glassfish3.1.2|com.sun.jersey.core.spi.component.ProviderFactory|_ThreadID=28;_ThreadName=Thread-2;|The provider class, class com.sun.jersey.multipart.impl.MultiPartReaderClientSide, could not be instantiated. Processing will continue but the class will not be utilized java.lang.IllegalArgumentException: The MultiPartConfig instance we expected is not present. Have you registered the MultiPartConfigProvider class? ....

Seems SCM tries to override the Glassfish built-in Jersey with it's own version, which does not work. The workaround is to enable the class loader delegation in glassfish-web.xml

<class-loader delegate="true"/>

More about overriding Jersey here

http://jersey.java.net/nonav/documentation/latest/glassfish.html#d4e1903

Glassfish bug report here

http://java.net/jira/browse/GLASSFISH-18482

Maybe the older .war files should be available for download for cases when we hit any blocking problem after update. My first idea was to go back to 1.17 but I did not found the war file anymore.

Comments (4)

  1. Sebastian Sebastian repo owner

    It is possible that you create an bitbucket account? because the notification system of bitbucket does not notify on anonymous comments.

    I could not reproduce your error. Have you applied the jvm options of the following wiki page?

    https://bitbucket.org/sdorra/scm-manager/wiki/applicationserver

    You could find older versions of scm-manager in the download archive:

    https://bitbucket.org/sdorra/scm-manager/wiki/download-archive

  2. Robert Carnecky

    Ooops, I reinstalled my Glasfish sever and forget to update the jvm options. Looks like the setting

    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext

    makes the trick. Sorry, you can close the issue.

  3. Log in to comment