Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-606

Glassfish JUnit test fails upon successful deploy (but with warnings)

      Arquillian controlled JUnit test is failing because of Glassfish WARNING:

      [#|2011-09-19T23:52:35.182+0200|WARNING|glassfish3.1.1|javax.org.glassfish.persistence.org.glassfish.persistence.common|_ThreadID=18;_ThreadName=admin-thread-pool-4848(2);|PER01000: Got SQLException executing statement "CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))": java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'.|#]

      The REST deployer returns:

      org.jboss.arquillian.container.spi.client.container.DeploymentException: "http://localhost:4848/management/domain/applications/application/test" created successfully.

      but the tests are failing.

      According to Glassfish team (http://java.net/projects/glassfish/lists/persistence/archive/2006-11/message/221) this message can be safely ignored.

      Suggestion: Apparently the deployer re-catches the exception and marks test as failed. The deployer should be aware of the return status (in this case the archive is deployed successfully) or check the thrown exception and react appropriately (i.e. ignore the above exception).

            [ARQ-606] Glassfish JUnit test fails upon successful deploy (but with warnings)

            pushed upstream

            Aslak Knutsen added a comment - pushed upstream

            Ok, with Aslak's help I've changed the formatter, so I think right now points exactly what was changed.

            Cheers!

            Piotr Nowicki (Inactive) added a comment - Ok, with Aslak's help I've changed the formatter, so I think right now points exactly what was changed. Cheers!

            Not yet, but it will be in time. This is the formatter currently in use: http://pastebin.com/xnBxYZZk

            Aslak Knutsen added a comment - Not yet, but it will be in time. This is the formatter currently in use: http://pastebin.com/xnBxYZZk

            Agree, but don't really know what to do at this point...

            Is the AS7 formatting style the default one for Arquillian?

            Piotr Nowicki (Inactive) added a comment - Agree, but don't really know what to do at this point... Is the AS7 formatting style the default one for Arquillian?

            Works fine, thanks! However, the formating change makes the pull request hard to read.

            Jozef Hartinger added a comment - Works fine, thanks! However, the formating change makes the pull request hard to read.

            1. No exit code - Exception,
            2. Warning exit code - log.warning but move along,
            3. Non-success code - Exception

            Piotr Nowicki (Inactive) added a comment - 1. No exit code - Exception, 2. Warning exit code - log.warning but move along, 3. Non-success code - Exception

              PedroKowalski Piotr Nowicki (Inactive)
              PedroKowalski Piotr Nowicki (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: