glassfish
  1. glassfish
  2. GLASSFISH-8893

Problem when getting deployment status form JetBrains IDEA ide

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: v2.2
    • Fix Version/s: None
    • Component/s: amx
    • Labels:
      None
    • Environment:

      Operating System: Windows Vista
      Platform: Other

    • Issuezilla Id:
      8,893
    • Status Whiteboard:
      Hide

      3.1-exclude v3_exclude

      Show
      3.1-exclude v3_exclude
    • Tags:

      Description

      Trying to deploy war project form IDEA ide. When plugin tries to get deployment
      status from Glassfish following one of the following stacktraces is swhon in
      logs

      Stacktrace 1

      java.lang.reflect.UndeclaredThrowableException
      at $Proxy119.getStandaloneServerConfigMap(Unknown Source)
      at
      com.sun.enterprise.deployment.client.DeploymentFacilityImpl.listAppRefs(Deployme
      ntFacilityImpl.java:275)
      at
      com.fuhrer.idea.glassfish.server.GlassfishServer2.getDeploymentStatus(GlassfishS
      erver2.java:156)
      at
      com.fuhrer.idea.glassfish.server.GlassfishServer2.handleDeployment(GlassfishServ
      er2.java:83)
      at
      com.fuhrer.idea.javaee.server.JavaeeServerInstance$4.run(JavaeeServerInstance.ja
      va:158)
      at
      com.intellij.openapi.application.impl.ApplicationImpl$5.run(ApplicationImpl.java
      :10)
      at
      java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8
      86)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)
      at
      com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.ja
      va:10)
      Caused by: java.io.IOException
      at
      java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)
      at
      java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:
      2750)
      at
      java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
      at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
      at
      com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.receive(ServletConnec
      tion.java:136)
      at
      com.sun.enterprise.admin.jmx.remote.comm.MBeanServerMessageConductor.invoke(MBea
      nServerMessageConductor.java:84)
      at
      com.sun.enterprise.admin.jmx.remote.internal.RemoteMBeanServerConnection.getAttr
      ibute(RemoteMBeanServerConnection.java:297)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invokeTarget(AMXProxyH
      andler.java:460)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invokeProxyMapGetter(A
      MXProxyHandler.java:654)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler._invoke(AMXProxyHandle
      r.java:1101)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invoke(AMXProxyHandler
      .java:1024)
      ... 13 more

      Stacktrace 2

      java.lang.reflect.UndeclaredThrowableException
      at $Proxy119.getStandaloneServerConfigMap(Unknown Source)
      at
      com.sun.enterprise.deployment.client.DeploymentFacilityImpl.listAppRefs(Deployme
      ntFacilityImpl.java:275)
      at
      com.fuhrer.idea.glassfish.server.GlassfishServer2.getDeploymentStatus(GlassfishS
      erver2.java:156)
      at
      com.fuhrer.idea.glassfish.server.GlassfishServer2.handleDeployment(GlassfishServ
      er2.java:83)
      at
      com.fuhrer.idea.javaee.server.JavaeeServerInstance$4.run(JavaeeServerInstance.ja
      va:158)
      at
      com.intellij.openapi.application.impl.ApplicationImpl$5.run(ApplicationImpl.java
      :10)
      at
      java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8
      86)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)
      at
      com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.ja
      va:10)
      Caused by: java.io.IOException
      at
      java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)
      at
      java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:
      2750)
      at
      java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
      at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
      at
      com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.receive(ServletConnec
      tion.java:136)
      at
      com.sun.enterprise.admin.jmx.remote.comm.MBeanServerMessageConductor.invoke(MBea
      nServerMessageConductor.java:84)
      at
      com.sun.enterprise.admin.jmx.remote.internal.RemoteMBeanServerConnection.getAttr
      ibute(RemoteMBeanServerConnection.java:297)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invokeTarget(AMXProxyH
      andler.java:460)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invokeProxyMapGetter(A
      MXProxyHandler.java:654)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler._invoke(AMXProxyHandle
      r.java:1101)
      at
      com.sun.appserv.management.client.handler.AMXProxyHandler.invoke(AMXProxyHandler
      .java:1024)
      ... 13 more

        Activity

        Hide
        zlowred added a comment -

        PS
        same works fine on Linux and MacOS.
        PPS
        doesn't work on WindowsXP on different PC

        Show
        zlowred added a comment - PS same works fine on Linux and MacOS. PPS doesn't work on WindowsXP on different PC
        Hide
        llc added a comment -

        I won't be looking at this unless instructed to do so as a priority.

        Show
        llc added a comment - I won't be looking at this unless instructed to do so as a priority.
        Hide
        zlowred added a comment -

        Maybe anyone else can take care of it?
        Or, can you give any estimation when it can be done?

        We are commercial developers and IDEA is a standard for commercial development. Because of this issue
        we were forced to use JBoss as platform for our product. I don't think that this helps Glassfish to become
        No1 open source enterprise platform.

        Thanks

        Show
        zlowred added a comment - Maybe anyone else can take care of it? Or, can you give any estimation when it can be done? We are commercial developers and IDEA is a standard for commercial development. Because of this issue we were forced to use JBoss as platform for our product. I don't think that this helps Glassfish to become No1 open source enterprise platform. Thanks
        Hide
        llc added a comment -

        This is almost certainly not an AMX issue, the stack trace is deep down in DeploymentFacilityImpl.

        I've inquired as to whether we'll fix this.

        Show
        llc added a comment - This is almost certainly not an AMX issue, the stack trace is deep down in DeploymentFacilityImpl. I've inquired as to whether we'll fix this.
        Hide
        kumara added a comment -

        GlassFish does JMX operations by sending serialized java objects over http and it looks like on some
        platforms there is some data loss over the network and hence the exceptions while trying to read
        objects from ServletConnection. The root cause could be anywhere from the issues on the local network
        (where test is being run), for example firewall software to the configuration of http stack in glassfish
        (maybe it needs to wait longer for all packets to arrive) to a plain bug.

        To make further progress, it is important to get either a well defined test case to reproduce the problem
        or detailed information on which APIs are being used and how (so we can create a test case).

        As a workaround, it might be possible to use standard JMX RMI connector.

        Show
        kumara added a comment - GlassFish does JMX operations by sending serialized java objects over http and it looks like on some platforms there is some data loss over the network and hence the exceptions while trying to read objects from ServletConnection. The root cause could be anywhere from the issues on the local network (where test is being run), for example firewall software to the configuration of http stack in glassfish (maybe it needs to wait longer for all packets to arrive) to a plain bug. To make further progress, it is important to get either a well defined test case to reproduce the problem or detailed information on which APIs are being used and how (so we can create a test case). As a workaround, it might be possible to use standard JMX RMI connector.
        Hide
        zlowred added a comment -

        I don't this that it is related to local network config (doesn't work when running server on local PC) nor PC
        config (doesn't work on different PC with different configuration and OS).
        I'll try to communicate with JetBrains developer responsible for Glassfish integration.

        Show
        zlowred added a comment - I don't this that it is related to local network config (doesn't work when running server on local PC) nor PC config (doesn't work on different PC with different configuration and OS). I'll try to communicate with JetBrains developer responsible for Glassfish integration.
        Hide
        kumara added a comment -

        Excluding from v3 list because we no longer use the mechanism of "serialized java objects over http" for
        deployment. We are still interested in getting a test case that can be used to reproduce the problem so it
        can be fixed in next v2.x release.

        Show
        kumara added a comment - Excluding from v3 list because we no longer use the mechanism of "serialized java objects over http" for deployment. We are still interested in getting a test case that can be used to reproduce the problem so it can be fixed in next v2.x release.
        Hide
        Nazrul added a comment -

        Excluding from 3.1

        Show
        Nazrul added a comment - Excluding from 3.1

          People

          • Assignee:
            prasads
            Reporter:
            zlowred
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: