[JBoss JIRA] Commented: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in 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-6717?page=com.atlassian.jira.plug... ]
Farah Juma commented on JBAS-6717:
----------------------------------
Similarly, if you click on the "Metrics" tab for a datasource after closing connections, the "Connection Count" metric is not updated to reflect the closed connections.
> AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6717
> URL: https://jira.jboss.org/jira/browse/JBAS-6717
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Scott M Stark
> Fix For: JBossAS-5.1.0.CR1
>
>
> 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
15 years
[JBoss JIRA] Created: (JBAS-6711) if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
by Ian Springer (JIRA)
if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6711
URL: https://jira.jboss.org/jira/browse/JBAS-6711
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
For example, I pass the following template, which has a non-null but valid value set for the "DLQ" prop:
Properties for DeploymentTemplateInfo [QueueTemplate]:
name=DLQ, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items=[name=
domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging.destination,keyP
ropertyList={service=Queue, name=DLQ }]
name=JNDIName, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:java.lang.String:rrr
name=clustered, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:boolean:true
name=downCacheSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=expiryQueue, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
name=fullSize, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:int:75000
name=maxDeliveryAttempts, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=maxSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=messageCounterHistoryDayLimit, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=pageSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=redeliveryDelay, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=securityConfig, viewUse=CONFIGURATION, mandatory=false, type=MutableCompositeMetaType, value= <<<null>>>
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
And here's the stack trace of the IAE that applyTemplate() throws:
11:04:25,156 ERROR [ApplicationServerComponent] Unable to apply template [QueueTemplate] to create ManagedComponent of type ComponentType{type=JMSDestination, s
ubtype=Queue}.
java.lang.IllegalArgumentException: Not handled value: CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items=[name=domai
n type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging.destination,keyProper
tyList={service=Queue, name=DLQ }]
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.writeTemplate(JmsDestinationTemplate.java:158)
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.applyTemplate(JmsDestinationTemplate.java:96)
at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:90)
at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1017)
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:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
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.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
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
15 years
[JBoss JIRA] Commented: (JBAS-6715) java.lang.RuntimeException thrown adding resource that was previously Deleted
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6715?page=com.atlassian.jira.plug... ]
Charles Crouch commented on JBAS-6715:
--------------------------------------
Moving to JBAS since this appears to be an app server/jfs related issue
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: JBAS-6715
> URL: https://jira.jboss.org/jira/browse/JBAS-6715
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Shelly McGowan
> Assignee: Emanuel Muckenhuber
> Fix For: JBossAS-5.1.0.CR1
>
> Attachments: servlets-examples.war
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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
15 years
[JBoss JIRA] Moved: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ]
Charles Crouch moved EMBJOPR-93 to JBAS-6717:
---------------------------------------------
Project: JBoss Application Server (was: Embedded Jopr)
Key: JBAS-6717 (was: EMBJOPR-93)
Component/s: (was: Web App/Integration)
Fix Version/s: JBossAS-5.1.0.CR1
(was: 1.2)
Security: Public
> AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6717
> URL: https://jira.jboss.org/jira/browse/JBAS-6717
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Fix For: JBossAS-5.1.0.CR1
>
>
> 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
15 years
[JBoss JIRA] Commented: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ]
Charles Crouch commented on JBAS-6717:
--------------------------------------
Moving to JBAS to investigate why this part of the operation result isnt getting updated correctly.
> AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6717
> URL: https://jira.jboss.org/jira/browse/JBAS-6717
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Fix For: JBossAS-5.1.0.CR1
>
>
> 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
15 years