Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-2604

Http API : jndi-view and dump-services operations showing errors, browser waiting indefinitely - need to return a proper error message

    XMLWordPrintable

    Details

      Description

      Yes please report this as a bug that we do not return a proper error message.

      As to custom operations, for security reasons we have to make sure that GET can never mutate production state, since browsers operate on that assumption. For this reason we have limited GET to our universal read operations, and do not have support for custom operations. We could support an arbitrary runtime operation, but only IF we had a special flag that reported it as being read-only.

      On 11/11/11 3:01 AM, Vimal Kansal wrote:
      > So you mean to say, if I try executing a subsystem specific
      > operation(i.e a get) on any other subsystem, I should get a similar
      > error? Moreover, even with this jndi-view operation, browser just seems
      > to be waiting for response to come back, it does not show any error
      > message. I think we need a clear indication of what is supported and
      > what is not supported. In our doc also we should try to clarify it that
      > Http API is not an exact replica of what we can achieve through CLI.
      > Ideally I would have loved to be able to do whatever I can do with CLI.
      >
      > On 11/11/2011 7:20 PM, Darran Lofthouse wrote:
      >> Yes I don't think this is invalid, although I do see some problems
      >> regarding how we could implement this. At the moment it is literally
      >> just the global operations that we allow to be called but operations
      >> like this are subsystem specific.
      >>
      >> Maybe get a feature request raised for this to be further considered.
      >>
      >> Regards,
      >> Darran Lofthouse.
      >>
      >>
      >> On 11/11/2011 08:15 AM, Vimal Kansal wrote:
      >>> Thanks Darran. Semantically, don't you think dump-services is really a
      >>> get(i.e read) operation?
      >>>
      >>> On 11/11/2011 7:13 PM, Darran Lofthouse wrote:
      >>>> Hi Vimal,
      >>>>
      >>>> Using GET requests only a small subset of the read only operations are
      >>>> available, this operation would need to be invoked as a POST request
      >>>> from an external client.
      >>>>
      >>>> Regards,
      >>>> Darran Lofthouse.
      >>>>
      >>>>
      >>>> On 11/11/2011 04:20 AM, Vimal Kansal wrote:
      >>>>> Hi,
      >>>>>
      >>>>> I am trying to use Http API to display the JNDI view (which I am ble to
      >>>>> get via CLI alright) by pointing my browser as
      >>>>> http://localhost:9990/management/subsystem/naming?operation=jndi-view
      >>>>> and I get the following error :
      >>>>>
      >>>>> 15:16:53,086 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> Exception in thread "HttpManagementService-threads - 1"
      >>>>> java.lang.ExceptionInInitializerError
      >>>>> 15:16:53,087 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> org.jboss.as.domain.http.server.DomainApiHandler.convertGetRequest(DomainApiHandler.java:422)
      >>>>> 15:16:53,088 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:263)
      >>>>> 15:16:53,089 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:191)
      >>>>> 15:16:53,091 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
      >>>>> 15:16:53,093 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
      >>>>> 15:16:53,095 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
      >>>>> 15:16:53,096 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:689)
      >>>>> 15:16:53,097 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
      >>>>> 15:16:53,098 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:661)
      >>>>> 15:16:53,099 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      >>>>> 15:16:53,100 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      >>>>> 15:16:53,101 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at java.lang.Thread.run(Thread.java:662)
      >>>>> 15:16:53,102 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
      >>>>> 15:16:53,103 ERROR [stderr] (HttpManagementService-threads - 1) Caused
      >>>>> by: java.lang.IllegalArgumentException: Invalid bundle interface
      >>>>> org.jboss.as.domain.http.server.HttpServerMessages (implementati
      >>>>> on not found)
      >>>>> 15:16:53,103 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.logging.Messages.getBundle(Messages.java:81)
      >>>>> 15:16:53,104 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at org.jboss.logging.Messages.getBundle(Messages.java:46)
      >>>>> 15:16:53,105 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> at
      >>>>> org.jboss.as.domain.http.server.HttpServerMessages.<clinit>(HttpServerMessages.java:39)
      >>>>> 15:16:53,106 ERROR [stderr] (HttpManagementService-threads - 1)
      >>>>> ... 13 more
      >>>>>
      >>>>> Thx
      >>>>>
      >>>>> Vimal
      >>>>>
      >>>>>
      >>>>>
      >>>>>
      >>>>>
      >>>>> _______________________________________________
      >>>>> jboss-as7-dev mailing list
      >>>>> jboss-as7-dev@lists.jboss.org
      >>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
      >>>> _______________________________________________
      >>>> jboss-as7-dev mailing list
      >>>> jboss-as7-dev@lists.jboss.org
      >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
      >>> _______________________________________________
      >>> jboss-as7-dev mailing list
      >>> jboss-as7-dev@lists.jboss.org
      >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
      >
      > _______________________________________________
      > jboss-as7-dev mailing list
      > jboss-as7-dev@lists.jboss.org
      > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


      Jason T. Greene
      JBoss AS Lead / EAP Platform Architect
      JBoss, a division of Red Hat

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ctomc Tomaz Cerar
                Reporter:
                vimalkansal Vimal Kansal
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: