[arquillian-issues] [JBoss JIRA] Commented: (ARQ-606) Glassfish JUnit test fails upon successful deploy (but with warnings)

[Pedro Kowalski (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630739#comment-12630739 ] 

Pedro Kowalski commented on ARQ-606:
------------------------------------

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

Is the AS7 formatting style the default one for Arquillian?

> Glassfish JUnit test fails upon successful deploy (but with warnings)
> ---------------------------------------------------------------------
>
>                 Key: ARQ-606
>                 URL: https://issues.jboss.org/browse/ARQ-606
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: GlassFish Containers
>    Affects Versions: 1.0.0.CR1
>         Environment: GNU/Linux Ubuntu 11.04 x86
>            Reporter: Pedro Kowalski
>            Assignee: Pedro Kowalski
>              Labels: exception, failing, glassfish_v3, junit, rest, warning
>             Fix For: glassfish_1.0.0.Final
>
>
> 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).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira