Description of problem: There is regression in generic resource adapter version 1.0.4.Final in EAP 6.3.0.ER2 which is blocker for Tibco certification. This is regression against EAP 6.3.0.DR4. Using "rar" connection factory is not possible to send and receive messages to/from Tibco EMS 6.3 server. There are no exceptions in log. Only clue is in trace log of generic RA: 08:42:45,464 DEBUG [org.jboss.resource.adapter.jms.JmsManagedConnection] (http-/127.0.0.1:8080-1) xaSession=null, Session=Session[transacted=true, tx_started=false, ackMode=NO_ACKNOWLEDGE, listener=null, xa=false] where "ackMode=NO_ACKNOWLEDGE" could suggest that send and receive of message is not acked. Steps to Reproduce: 1. Download prepared EAP 6.3.0.ER2 - see private comment below 2. Start it by - sh standalone.sh -c standalone-full.xml -b 127.0.0.1 3. Call deployed servlet which sends and receive message to Q1: http://127.0.0.1:8080/MessageServlet/MessageServlet?in=jms/queue/Q1&out=jms/queue/Q1&count=1&sleep=5000 Source of Servlet (MessageServlet.java) is in git repo: git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-wsmq.git
Generic RA is not working at the moment, it's regression comparing to EAP 6.2.0. Proposing it as EAP 630 Beta blocker. This affects integration with other messaging systems, internal usage of HQ is not affected.
Fixed by component upgrade
Thanks Jeff! Verified with EAP 6.3.0.ER3.
Marking for exclusion from 6.3.0 Beta release notes as both 'affects' and 'fix' versions are listed as 6.3.0, suggesting this was not a customer-facing issue.