glassfish
  1. glassfish
  2. GLASSFISH-14939

Warning about cluster profile when using keep state with standalone instance

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1_b31
    • Fix Version/s: 3.1_b32
    • Component/s: deployment
    • Labels:
      None
    • Environment:

      build: ogs-3.1-b31-12_01_2010.zip

      Description

      Steps to reproduce:

      1. In Admin Console create a standalone instance, e.g. sin1, and start it.
      2. Go to JDBC Resources, jdbc/__TimerPool, Targets tab and add sin1 as a target, save.
      3. Go to JDBC Resources, jdbc/__default, Targets tab and add sin1 as a target. save.
      4. Start database, e.g. asadmin start-database
      5. Go to Standalone Instances, click on instance name and Applications tab, click Deploy button.
      6. Select scrumtoys application and check run verifier and keep state checkboxes, click OK. The following error is displayed:

      Deployment succeeded with a warning, please look at the log file for details
      Application deployed with name scrumtoys. WARNING: The keepstate option is only supported in developer profile and not cluster profile. Ignoring the keepstate option.

      There are no developer/cluster profiles in v3.1, also deployment was done on a standalone instance.

      Another issue is that server.log contains the following warning additionally:

      [#|2010-12-01T19:08:19.916-0800|WARNING|oracle-glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=19;_ThreadName=Thread-1;|Verifier is not installed yet. Install verifier module.|#]

      If verifier is not available, why do we have the checkbox for it in Admin Console?

      Both warnings are logged to DAS server.log, even though the application is deployed to a standalone instance. The log for standalone instance contains only the following:

      [#|2010-12-01T19:08:39.011-0800|INFO|oracle-glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=19;_ThreadName=Thread-1;|scrumtoys was successfully deployed in 6,490 milliseconds.|#]

      I think this will be misleading to users.

      1. server.log
        21 kB
        lidiam
      1. scrumtoys-warning.JPG
        99 kB

        Activity

        Hide
        lidiam added a comment -

        The second time I tried the same scenario I saw also the following exception in DAS server.log:

        [#|2010-12-01T19:35:37.706-0800|SEVERE|oracle-glassfish3.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=19;_ThreadName=Thread-1;|Exception while visiting com/sun/gjc/spi/ManagedConnection.class of size 23073
        java.lang.ArrayIndexOutOfBoundsException: 58
        at java.util.ArrayList.add(ArrayList.java:352)
        at org.glassfish.hk2.classmodel.reflect.impl.TypeImpl.addMethod(TypeImpl.java:80)
        at org.glassfish.hk2.classmodel.reflect.impl.ModelClassVisitor.visitMethod(ModelClassVisitor.java:222)
        at org.objectweb.asm.ClassReader.accept(Unknown Source)
        at org.objectweb.asm.ClassReader.accept(Unknown Source)
        at org.glassfish.hk2.classmodel.reflect.Parser$5.on(Parser.java:358)
        at org.glassfish.hk2.classmodel.reflect.util.JarArchive.onSelectedEntries(JarArchive.java:122)
        at org.glassfish.hk2.classmodel.reflect.Parser.doJob(Parser.java:342)
        at org.glassfish.hk2.classmodel.reflect.Parser.access$300(Parser.java:66)
        at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:303)
        at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:290)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:139)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
        at java.lang.Thread.run(Thread.java:619)

        #]
        Show
        lidiam added a comment - The second time I tried the same scenario I saw also the following exception in DAS server.log: [#|2010-12-01T19:35:37.706-0800|SEVERE|oracle-glassfish3.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=19;_ThreadName=Thread-1;|Exception while visiting com/sun/gjc/spi/ManagedConnection.class of size 23073 java.lang.ArrayIndexOutOfBoundsException: 58 at java.util.ArrayList.add(ArrayList.java:352) at org.glassfish.hk2.classmodel.reflect.impl.TypeImpl.addMethod(TypeImpl.java:80) at org.glassfish.hk2.classmodel.reflect.impl.ModelClassVisitor.visitMethod(ModelClassVisitor.java:222) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.glassfish.hk2.classmodel.reflect.Parser$5.on(Parser.java:358) at org.glassfish.hk2.classmodel.reflect.util.JarArchive.onSelectedEntries(JarArchive.java:122) at org.glassfish.hk2.classmodel.reflect.Parser.doJob(Parser.java:342) at org.glassfish.hk2.classmodel.reflect.Parser.access$300(Parser.java:66) at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:303) at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:290) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:139) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909) at java.lang.Thread.run(Thread.java:619) #]
        Hide
        Anissa Lam added a comment -

        Its pretty clear this warning is not from admin gui.
        Transfer to deployment.
        Hong, you can reproduce this by just

        %asadmin deploy --keepstate=true --verify=true --target ST scrumtoys.war

        Show
        Anissa Lam added a comment - Its pretty clear this warning is not from admin gui. Transfer to deployment. Hong, you can reproduce this by just %asadmin deploy --keepstate=true --verify=true --target ST scrumtoys.war
        Hide
        Hong Zhang added a comment -

        Had discussions on this with Lidia/Anissa/Marina, have improved the warning message for the keepstate option used with non-DAS target.

        Show
        Hong Zhang added a comment - Had discussions on this with Lidia/Anissa/Marina, have improved the warning message for the keepstate option used with non-DAS target.
        Hide
        lidiam added a comment -

        verified on build b41

        Show
        lidiam added a comment - verified on build b41

          People

          • Assignee:
            Hong Zhang
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: