Test PoolStatistics and operations of the Pool in rhq plugin
------------------------------------------------------------
Key: JBJCA-561
URL: https://issues.jboss.org/browse/JBJCA-561
Project: IronJacamar
Issue Type: Task
Components: Management
Reporter: Lin Gao
Assignee: Lin Gao
Fix For: 1.0.0.Beta7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
performance report include profiler data
----------------------------------------
Key: JBJCA-424
URL: https://jira.jboss.org/browse/JBJCA-424
Project: IronJacamar
Issue Type: Task
Components: Performance
Reporter: Jeff Zhang
Assignee: Jeff Zhang
Fix For: 1.0.0.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Performance report with different connection manager strategies
---------------------------------------------------------------
Key: JBJCA-423
URL: https://jira.jboss.org/browse/JBJCA-423
Project: IronJacamar
Issue Type: Task
Components: Performance
Reporter: Jeff Zhang
Assignee: Jeff Zhang
Fix For: 1.0.0.CR1
Ddoing a run with the connection tests with the
-Dironjacamar.mcp=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool
system property then one with
-Dironjacamar.mcp=org.jboss.jca.core.connectionmanager.pool.mcp.ArrayBlockingQueueManagedConnectionPool
so we can see if the numbers are different.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Change dependencies on org.jboss.javaee APIs to org.jboss.spec
---------------------------------------------------------------
Key: JBJCA-564
URL: https://issues.jboss.org/browse/JBJCA-564
Project: IronJacamar
Issue Type: Bug
Reporter: Shelly McGowan
Assignee: Jesper Pedersen
The JBoss Java EE API Specs project has revised the naming convention of the APIs to identify the version of the specification that the APIs align with. IronJacamar has dependencies on the older API project.
<dependency org="org.jboss.javaee" name="jboss-jaspi-api" rev="${version.jboss.jaspi.api}" conf="common,ironjacamar-core-impl,ironjacamar-depchain"/>
<dependency org="org.jboss.javaee" name="jboss-transaction-api" rev="${version.transaction.api}" conf="common,ironjacamar-core-api,ironjacamar-core-impl,ironjacamar-depchain,ironjacamar-deployers-fungal,ironjacamar-spec-api"/>
I'd recommend updating these dependencies to the newer versions being maintained:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Verify OSGi information in all manifests
----------------------------------------
Key: JBJCA-77
URL: https://jira.jboss.org/jira/browse/JBJCA-77
Project: JBoss JCA
Issue Type: Task
Components: Common, Core, Deployer
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Priority: Blocker
Fix For: 1.0.0.Beta1
Verify that the OSGi information in all the MANIFEST.MF files are correct.
This information needs to be kept in sync from this point on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira