jersey
  1. jersey
  2. JERSEY-1614

the com.sun.jersey.server.spi.monitoring.glassfish.GlassfishMonitoringServiceProvider can not be found when jersey application run firstly in glassfish3.1.2

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.11
    • Fix Version/s: 1.18
    • Component/s: core
    • Labels:
      None
    • Environment:

      JDK1.6
      glassfish3.1.2

      Description

      the log level of jersey is set to CONFIG in glassfish3.1.2.
      when I ran my jersey's application firstly, the following exception happened.
      [#|2012-12-07T10:17:04.531+0800|CONFIG|glassfish3.1.2|com.sun.jersey.server.impl.monitoring.GlassFishMonitoringInitializer|_ThreadID=19;_ThreadName=Thread-2;|GlassFish Jersey monitoring could not be enabled. Processing will continue but montoring is disabled.
      com.sun.jersey.spi.service.ServiceConfigurationError: com.sun.jersey.spi.monitoring.GlassfishMonitoringProvider: The class com.sun.jersey.server.spi.monitoring.glassfish.GlassfishMonitoringServiceProvider implementing the provider interface com.sun.jersey.spi.monitoring.GlassfishMonitoringProvider is not found. The provider implementation is ignored.
      at com.sun.jersey.spi.service.ServiceFinder.fail(ServiceFinder.java:610)
      at com.sun.jersey.spi.service.ServiceFinder.access$400(ServiceFinder.java:159)
      at com.sun.jersey.spi.service.ServiceFinder$LazyObjectIterator.hasNext(ServiceFinder.java:861)
      at com.sun.jersey.server.impl.monitoring.GlassFishMonitoringInitializer.initialize(GlassFishMonitoringInitializer.java:58)
      at com.sun.jersey.spi.container.servlet.WebComponent.configure(WebComponent.java:582)
      at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.configure(ServletContainer.java:311)
      at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:608)
      at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:210)
      at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:373)
      at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:556)
      at javax.servlet.GenericServlet.init(GenericServlet.java:244)
      at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1445)
      at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1072)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:189)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
      at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
      at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
      at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
      at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
      at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
      at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
      at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
      at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
      at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
      at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
      at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
      at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
      at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
      at java.lang.Thread.run(Thread.java:662)

      #]
      but the class com.sun.jersey.server.spi.monitoring.glassfish.GlassfishMonitoringServiceProvider is in {glassfish_path}

      /glassfish/modules/jersey-gf-statsproviders.jar.so i don't know why this happened.

        Activity

        Hide
        luchao added a comment -

        who can explain this issue for me?

        Show
        luchao added a comment - who can explain this issue for me?
        Hide
        Pavel Bucek added a comment -

        looks like OSGi related issue - module headers might be incorrect for some reason. Can you retry with Jersey 1.16?

        Btw I'm not very sure whether this feature (monitoring) is supported any longer; are you interested more on getting rid of this exception or getting monitoring data from Jersey service?

        Show
        Pavel Bucek added a comment - looks like OSGi related issue - module headers might be incorrect for some reason. Can you retry with Jersey 1.16? Btw I'm not very sure whether this feature (monitoring) is supported any longer; are you interested more on getting rid of this exception or getting monitoring data from Jersey service?
        Hide
        luchao added a comment -

        thank you for your reply.
        i retried with Jersey 1.16,but the same exception has happened.
        about this feature(monitoring),there is monitoring function in glassfish server and RESTful Web Service also support,so i want to use this function to monitor my Jersey service.
        if this feature is not supported, it's OK to me.

        Show
        luchao added a comment - thank you for your reply. i retried with Jersey 1.16,but the same exception has happened. about this feature(monitoring),there is monitoring function in glassfish server and RESTful Web Service also support,so i want to use this function to monitor my Jersey service. if this feature is not supported, it's OK to me.
        Hide
        Pavel Bucek added a comment -

        no longer supported.

        Show
        Pavel Bucek added a comment - no longer supported.

          People

          • Assignee:
            Pavel Bucek
            Reporter:
            luchao
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2 weeks
              2w
              Remaining:
              0m
              Logged:
              Time Not Required
              5m