Bug 951188

Summary:	pooled connection factory does not define an application security policy
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jeff Mesnil <jmesnil>
Component:	JMS	Assignee:	Jeff Mesnil <jmesnil>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	brian.stansberry, mnovak, rsvoboda
Target Milestone:	ER6
Target Release:	EAP 6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:	960740

Description Jeff Mesnil 2013-04-11 15:51:32 UTC

Description of problem:

From a customer case, it appears that AS7 pooled-connection-factory does not set an application security policy for its JCA pool.

This implies a performance overhead since destroying a connection implies having to creating a new one every time (https://docspace.corp.redhat.com/docs/DOC-101004#IJ000612_Destroying_a_connection)

Comment 3 JBoss JIRA Server 2013-04-12 09:42:45 UTC

Jeff Mesnil <jmesnil> made a comment on jira AS7-6876

PR for master branch

Comment 5 JBoss JIRA Server 2013-04-16 15:21:14 UTC

Jeff Mesnil <jmesnil> made a comment on jira AS7-6876

PR merged in master branch

Comment 7 Rostislav Svoboda 2013-05-04 07:25:44 UTC

Code change from PR 101 is present in decompiled code for modules/system/layers/base/org/jboss/as/messaging/main/jboss-as-messaging-7.2.0.Final-redhat-6.jar

Functional check TBD.

Comment 8 Miroslav Novak 2013-05-04 17:03:33 UTC

@Jeff
I tried to reproduce this issue but without success. Could you help, please?

Comment 9 Miroslav Novak 2013-05-14 06:40:20 UTC

May 13 14:26:31 <mnovak>        jmesnil, ping
May 13 14:28:59 <jmesnil>       mnovak: pong
May 13 14:31:54 <mnovak>        jmesnil, hi
May 13 14:32:04 <mnovak>        jmesnil, could you help with https://bugzilla.redhat.com/show_bug.cgi?id=951188
May 13 14:32:25 <mnovak>        jmesnil, I don't know how to reproduce it
May 13 14:32:44 <jmesnil>       mnovak: sorry, I was in holidays the last 2 weeks, I'll look at it today 
May 13 14:32:55 <mnovak>        jmesnil, thanks a lot

I think you forgot we're pushed to verify all bugzillas.

Comment 10 Miroslav Novak 2013-05-15 08:10:17 UTC

I've managed to reproduce this issue with EAP 6.0.1.GA. There are warnings:

09:55:17,255 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Thread-43 (HornetQ-client-global-threads-1498674576)) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@4784afe6[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@41672f15 connection handles=0 lastUse=1368604517253 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@40c1ed25 pool internal context=SemaphoreArrayListManagedConnectionPool@206ab4f[pool=HornetQConnectionDefinition] xaResource=XAResourceWrapperImpl@5d442d3e[xaResource=org.hornetq.ra.HornetQRAXAResource@2be181a0 pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/JmsXA] txSync=null]

which is the problem described in:
https://docspace.corp.redhat.com/docs/DOC-101004#IJ000612_Destroying_a_connection

and this bz should fix. There are no such warnings in EAP 6.1.0.ER8. Setting as Verified.

Comment 13 mark yarborough 2013-07-23 18:43:41 UTC

Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html