[arquillian-issues] [JBoss JIRA] Closed: (ARQ-613) GlassFish - succesful deployment with warning considered failed

Aslak Knutsen (JIRA) jira-events at lists.jboss.org
Tue Sep 27 08:28:26 EDT 2011


     [ https://issues.jboss.org/browse/ARQ-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen closed ARQ-613.
-----------------------------

      Assignee: Aslak Knutsen
    Resolution: Done


Duplicate of ARQ-606

Could you give the fix here a test? https://github.com/PedroKowalski/arquillian-container-glassfish/tree/ARQ-606

> GlassFish - succesful deployment with warning considered failed
> ---------------------------------------------------------------
>
>                 Key: ARQ-613
>                 URL: https://issues.jboss.org/browse/ARQ-613
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: GlassFish Containers
>    Affects Versions: glassfish_1.0.0.CR1
>         Environment: GF 3.1.1
> arquillian-glassfish-container (2b5c0726fdaf7a6eadac9bf5795ea13df88b4152) - remote
>            Reporter: Jozef Hartinger
>            Assignee: Aslak Knutsen
>            Priority: Critical
>             Fix For: glassfish_1.0.0.Final
>
>
> When deploying applications that use GlassFish's built-in database, the deployment often succeeds with a warning like the one mentioned below. The "SEQUENCE" already exists is a very common case.
> Unfortunately, arquillian-glassfish-container treats every response with non-success response as deployment failures - which is wrong. As a result, an application that would normally deploy with a warning and work as expected cannot be tested with Arquillian ATM.
> The proposed solution is to log the WARNING message and consider the deployment successful.
> {noformat}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><map><entry key="message" value="&quot;http://localhost:4848/management/domain/applications/application/seam-booking&quot; created successfully.&#10;&#10;PER01003: Deployment encountered SQL Exceptions:&#10;&#9;PER01000: Got SQLException executing statement &quot;CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))&quot;: java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'."/><entry key="exit_code" value="WARNING"/><entry key="command"/><entry key="subReports"><list><map><entry key="message" value="&#10;PER01003: Deployment encountered SQL Exceptions:&#10;&#9;PER01000: Got SQLException executing statement &quot;CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))&quot;: java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'."/><entry key="exit_code" value="WARNING"/><entry key="command"/></map></list></entry></map>
> {noformat}

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

       



More information about the arquillian-issues mailing list