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

Bug 1180565

Summary: [GSS](6.4.z) method-params containing an array not correctly processed for EJB2.1 with CMT
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ricardo Martinelli de Oliveira <rmartine>
Component: EJBAssignee: Radovan Netuka <rnetuka>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact: Scott Mumford <smumford>
Priority: unspecified    
Version: 6.3.2CC: bmaxwell, cdewolf, istudens, jawilson, jbilek, msochure, ppalaga, rnetuka, smumford
Target Milestone: CR1   
Target Release: EAP 6.4.12   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: eap6412-proposed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When defining trans-attribute for an EJB2.1 method when the method has the same name and one takes a paramter and the other takes an array of the same parameter, the trans-attribute specified gets applied to both methods when it should only be applied to one method. This fix resolves the issue so that the trans-attribute is applied only to the method that it was specified upon.
 Story Points: ---
Clone Of:
: 1180571 (view as bug list) Environment:
Last Closed: 2017-01-17 13:12:35 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:
Bug Depends On:    
Bug Blocks: 1180571, 1375585    

Description Ricardo Martinelli de Oliveira 2015-01-09 13:12:53 UTC 
It seems that the method-params for container transactions are not matched correctly if the contain arrays.
I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]);
If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with 
JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6)
I define the container transaction like this:
<container-transaction>
<method>
<ejb-name>FirstWithParams</ejb-name>
<method-intf>Local</method-intf>
<method-name>test</method-name>
<method-params>
<method-param>java.lang.String[]</method-param>
</method-params>
</method>
<method>
<ejb-name>FirstWithParams</ejb-name>
<method-intf>Local</method-intf>
<method-name>test</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<method>
<ejb-name>FirstWithParams</ejb-name>
<method-intf>Local</method-intf>
<method-name>test</method-name>
<method-params>
<method-param>int</method-param>
</method-params>
</method>
<method>
<ejb-name>Second</ejb-name>
<method-intf>Local</method-intf>
<method-name>test</method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int).
Comment 11 Jiří Bílek 2016-11-04 14:10:48 UTC 
Verified with EAP 6.4.12.CP.CR1
Comment 12 Petr Penicka 2017-01-17 13:12:35 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.