Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 845219

Summary: The properties of tomcat container configuration in arquillian.xml are not parsed properly
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Tomas Repel <trepel>
Component: ArquillianAssignee: Aslak Knutsen <aknutsen>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Repel <trepel>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0.GACC: kpiwko
Target Milestone: CR1   
Target Release: 2.1.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://issues.jboss.org/browse/ARQ-1044
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-30 15:34:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Repel 2012-08-02 10:25:28 UTC
It is impossible to use tabs or newlines in arquillian.xml when defining properties for tomcat configuration. Only space (" ") can be used as delimiter.

For example, this configuration is OK:

<container qualifier="tomcat" default="true">
  <configuration>
    <property name="catalinaHome">/home/tomcat6</property>
    <property name="javaVmArguments">-Xmx1024m -XX:MaxPermSize=512</property>
  </configuration>
</container>

While this one causes failure on startup:

<container qualifier="tomcat" default="true">
  <configuration>
    <property name="catalinaHome">/home/tomcat6</property>
    <property name="javaVmArguments">
-Xmx1024m
-XX:MaxPermSize=512
    </property>
  </configuration>
</container>


Version-Release number of selected component (if applicable):

arquillian-tomcat-managed-5.5, 6, 7; 1.0.0.CR3

Comment 1 JBoss JIRA Server 2012-08-02 12:22:16 UTC
Aslak Knutsen <aslak> updated the status of jira ARQ-1044 to Resolved

Comment 2 JBoss JIRA Server 2012-08-02 12:22:16 UTC
Aslak Knutsen <aslak> made a comment on jira ARQ-1044

pushed upstream, https://github.com/arquillian/arquillian-container-tomcat/commit/710b42bb548ec3f824dc599a8811b7261c571dab

Comment 3 Karel Piwko 2012-08-03 08:40:31 UTC
We need a new Arquillian Tomcat upstream release to incorporate the fix in wfk-arquillian-bom.

Comment 6 JBoss JIRA Server 2012-09-25 12:55:20 UTC
Aslak Knutsen <aslak> updated the status of jira ARQ-1044 to Closed

Comment 7 JBoss JIRA Server 2012-09-25 12:58:24 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Reopened

Comment 8 JBoss JIRA Server 2012-09-25 12:58:24 UTC
Karel Piwko <kpiwko> made a comment on jira ARQ-1044

Reopening to assign Tomas.

Comment 9 JBoss JIRA Server 2012-09-25 12:58:36 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Resolved

Comment 12 JBoss JIRA Server 2012-11-06 17:42:09 UTC
Aslak Knutsen <aslak> made a comment on jira ARQ-1044

[~kpiwko] This should be closed, no?

Comment 13 JBoss JIRA Server 2012-11-07 16:38:57 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Closed

Comment 14 JBoss JIRA Server 2012-11-07 16:38:57 UTC
Karel Piwko <kpiwko> made a comment on jira ARQ-1044

Closing, fixed in 1.0.0.CR4.

Comment 15 Tomas Repel 2012-11-12 13:14:49 UTC
Verified in WFK 2.1.0.CR1.

Comment 16 Karel Piwko 2012-11-30 15:34:30 UTC
Distributed as a part of WFK 2.1.0.GA release.