[JBoss JIRA] Created: (JBAOP-730) Rewrite CFlow Algorithm
by Flavia Rainone (JIRA)
Rewrite CFlow Algorithm
-----------------------
Key: JBAOP-730
URL: https://jira.jboss.org/jira/browse/JBAOP-730
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.1.0.GA
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 2.1.1.GA
Vide TODO at line 193 of PrecedenceSorter:
public static ArrayList<PrecedenceDefEntry> mergePrecedenceDef(ArrayList<PrecedenceDefEntry> overall, PrecedenceDef precedenceDef)
{
//TODO This can be improved. If you have the precedences
// 1) A, D
// 2) C, E
// 3) C, D
//After adding 2) to 1) since there is no relationship defined you get:
// i) A, D, C, E
//After adding 3) to i) you end up with an overall precedence of
// ii) A, C, D, C, E,
//In practice this should be fine, since the applyPrecedence() looks for the
//first matching entry, so the second (duplicate) occurrence of C is ignored.
This algorithm should be replaced by an algorithm that does not generates duplicates entries for the same advice and that recognizes when the dependencies are circular.
--
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
17 years, 2 months
[JBoss JIRA] Updated: (JBAS-6793) IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR
by Ondrej Žižka (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6793?page=com.atlassian.jira.plug... ]
Ondrej Žižka updated JBAS-6793:
-------------------------------
Environment: testStopAndStartEar (was: testStopAndStartEar
testRestartEar)
> IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR
> ---------------------------------------------------------------------------------
>
> Key: JBAS-6793
> URL: https://jira.jboss.org/jira/browse/JBAS-6793
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.Beta1
> Environment: testStopAndStartEar
> Reporter: Ondrej Žižka
> Assignee: Ales Justin
> Fix For: JBossAS-5.1.0.CR1
>
> Attachments: EarWithWar-Counter.ear
>
>
> When an EAR with WAR is stopped in the Control tab of Embedded Jopr (i.e. calling the Stop Managed Operation), starting it (i.e. calling the Start Managed Operation) again fails - error info from EmbJopr is below.
> Retrying later doesn't help.
> EAR archive to test with attached.
> ----------------------------------------------------------------------------------------------------------------
> java.lang.Exception
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:101)
> at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.invokeOperation(ManagedDeploymentComponent.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97)
> ... 11 more
> Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:869)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:255)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
> at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> at org.jboss.remoting.Client.invoke(Client.java:1708)
> at org.jboss.remoting.Client.invoke(Client.java:612)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> ... 15 more
--
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
17 years, 2 months
[JBoss JIRA] Updated: (JBAS-6793) IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR
by Ondrej Žižka (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6793?page=com.atlassian.jira.plug... ]
Ondrej Žižka updated JBAS-6793:
-------------------------------
Summary: IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR (was: NPE upon Stop'n'Start or Restart of EAR with nested WAR)
> IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR
> ---------------------------------------------------------------------------------
>
> Key: JBAS-6793
> URL: https://jira.jboss.org/jira/browse/JBAS-6793
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.Beta1
> Environment: testStopAndStartEar
> testRestartEar
> Reporter: Ondrej Žižka
> Assignee: Ales Justin
> Fix For: JBossAS-5.1.0.CR1
>
> Attachments: EarWithWar-Counter.ear
>
>
> When an EAR with WAR is stopped in the Control tab of Embedded Jopr (i.e. calling the Stop Managed Operation), starting it (i.e. calling the Start Managed Operation) again fails - error info from EmbJopr is below.
> Retrying later doesn't help.
> EAR archive to test with attached.
> ----------------------------------------------------------------------------------------------------------------
> java.lang.Exception
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:101)
> at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.invokeOperation(ManagedDeploymentComponent.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97)
> ... 11 more
> Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:869)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:255)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
> at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> at org.jboss.remoting.Client.invoke(Client.java:1708)
> at org.jboss.remoting.Client.invoke(Client.java:612)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> ... 15 more
--
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
17 years, 2 months
[JBoss JIRA] Updated: (JBAS-6793) NPE upon Stop'n'Start or Restart of EAR with nested WAR
by Ondrej Žižka (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6793?page=com.atlassian.jira.plug... ]
Ondrej Žižka updated JBAS-6793:
-------------------------------
Summary: NPE upon Stop'n'Start or Restart of EAR with nested WAR (was: IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR)
Environment:
testStopAndStartEar
testRestartEar
was:testStopAndStartEar
> NPE upon Stop'n'Start or Restart of EAR with nested WAR
> -------------------------------------------------------
>
> Key: JBAS-6793
> URL: https://jira.jboss.org/jira/browse/JBAS-6793
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.Beta1
> Environment: testStopAndStartEar
> testRestartEar
> Reporter: Ondrej Žižka
> Assignee: Ales Justin
> Fix For: JBossAS-5.1.0.CR1
>
> Attachments: EarWithWar-Counter.ear
>
>
> When an EAR with WAR is stopped in the Control tab of Embedded Jopr (i.e. calling the Stop Managed Operation), starting it (i.e. calling the Start Managed Operation) again fails - error info from EmbJopr is below.
> Retrying later doesn't help.
> EAR archive to test with attached.
> ----------------------------------------------------------------------------------------------------------------
> java.lang.Exception
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:101)
> at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.invokeOperation(ManagedDeploymentComponent.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
> at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
> at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97)
> ... 11 more
> Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/ -> org.jboss.deployers.spi.DeploymentException: Failed to create web module
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/EarWithWar-Counter.ear/" is in error due to the following reason(s): java.io.FileNotFoundException: /home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/vfs-nested.tmp/0b5ebb3b_EarWithWar-Counter-war.war (No such file or directory)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:869)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:255)
> at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
> at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> at org.jboss.remoting.Client.invoke(Client.java:1708)
> at org.jboss.remoting.Client.invoke(Client.java:612)
> at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> ... 15 more
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-1620) Be able to intercept the onclose of a client.
by Jay Howell (JIRA)
Be able to intercept the onclose of a client.
---------------------------------------------
Key: JBMESSAGING-1620
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1620
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3.CP07
Reporter: Jay Howell
Assignee: Tim Fox
Fix For: 1.4.0.SP3.CP08
There is a need to be able to have the close aspect called when connections are closed. This is done through the connection advised set forth in the aop-messaging-server.xml file. The example would look like...
<bind pointcut="execution(* org.jboss.jms.server.endpoint.advised.ConnectionAdvised->close(..))">
<interceptor-ref name="com.acme.close.interceptor"/>
</bind>
<bind pointcut="execution(* org.jboss.jms.server.endpoint.advised.ConnectionAdvised->closing(..))">
<interceptor-ref name="com.acme.close.interceptor"/>
</bind>
Currently this is not posible because the connections that are closed aren't wrapped in a ConnectionAdvised.
This was never promised as a feature of JBM, but it is useful for some to know when a client connection is closed.
--
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
17 years, 2 months
[JBoss JIRA] Commented: (JBAS-6819) The value of "Connections In Use Count" that gets displayed in the embedded console as the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
by Farah Juma (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6819?page=com.atlassian.jira.plug... ]
Farah Juma commented on JBAS-6819:
----------------------------------
Jesper's fix from rev88298 solved the problem. The value of "Connections In Use Count" now gets updated appropriately after connections are closed and the EMBJOPR tests for the "listFormattedSubPoolStatistics" operation are now passing.
The EMBJOPR metrics tests for datasources are now passing as well. We needed to modify the expected value for "Connection Count" in testMetricsAfterClosingConnections().
> The value of "Connections In Use Count" that gets displayed in the embedded console as the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6819
> URL: https://jira.jboss.org/jira/browse/JBAS-6819
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ProfileService
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Critical
> Fix For: JBossAS-5.1.0.GA
>
>
> Steps to reproduce:
> Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections.
> For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections:
> Sub Pool Statistics:
> Sub Pool Count: 1
> ------------------------------------------------------
> Track By Transaction: true
> Available Connections Count: 12
> Max Connections In Use Count:10
> Connections Destroyed Count:0
> **Connections In Use Count:10**
> Total Block Time:0
> Average Block Time For Sub Pool:0
> Maximum Wait Time For Sub Pool:0
> Total Timed Out:0
> The value of "Connections In Use Count" should be 8 in this case.
--
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
17 years, 2 months