[JBoss JIRA] Created: (JASSIST-68) Remove limitation on public constructors
by Erik Putrycz (JIRA)
Remove limitation on public constructors
----------------------------------------
Key: JASSIST-68
URL: https://jira.jboss.org/jira/browse/JASSIST-68
Project: Javassist
Issue Type: Feature Request
Affects Versions: 3.8.1.GA
Reporter: Erik Putrycz
Assignee: Shigeru Chiba
Currently when extending a class with javassist, it is required that the superclass has a public constructor. However, in some cases, this is not a necessary constraint.
For instance when extending a class and generating a factory with Javassist, it is better to hide the constructor to prevent users to bypass the factory, and this is not possible currently.
This would involve a minor change in inheritAllConstructors() in class CtNewClass
--
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, 3 months
[JBoss JIRA] Created: (JBAS-6738) secure-wsdl-access is mssing in jboss_5_0.dtd
by Haohua xie (JIRA)
secure-wsdl-access is mssing in jboss_5_0.dtd
---------------------------------------------
Key: JBAS-6738
URL: https://jira.jboss.org/jira/browse/JBAS-6738
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.1.GA
Environment: openSUSU 11.1 x86_64, Sun JDK 1.6.0_12 x86_64
Reporter: Haohua xie
Here is my jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC
"-//JBoss//DTD JBOSS 5.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd">
<jboss>
<webservices>
<context-root>/hxie/framework/security/admin/logic</context-root>
</webservices>
<enterprise-beans>
<session>
<ejb-name>LdapAuthInfoLogicBean</ejb-name>
<port-component>
<port-component-name>LdapAuthInfoLogic</port-component-name>
<port-component-uri>/LdapAuthInfoLogic</port-component-uri>
<!-- -->
<auth-method>BASIC</auth-method>
<transport-guarantee>NONE</transport-guarantee>
<secure-wsdl-access>false</secure-wsdl-access>
</port-component>
</session>
</enterprise-beans>
</jboss>
When I deployed the ear to JBoss 5.0.1 GA, I got the following exception and deployment failed.
2009-04-04 11:52:29,348 DEBUG [org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper] (main) Parsing file: ZipEntryHandler(a)594588547[path=hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml context=file:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/ real=file:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml] for type: class org.jboss.metadata.ejb.jboss.JBossMetaData
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) Created parser: org.apache.xerces.jaxp.SAXParserImpl@3c196fa2, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/validation set to: true
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/namespaces set to: true
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/xinclude/fixup-base-uris set to: false
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/xinclude/fixup-language set to: false
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/validation/dynamic set to: true
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/validation/schema set to: false
2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/validation set to: true
2009-04-04 11:52:29,350 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) Created parser: org.apache.xerces.jaxp.SAXParserImpl@3c196fa2, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2009-04-04 11:52:29,557 DEBUG [org.jboss.deployment.JBossEjbParsingDeployer] (main) Error during deploy: vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323)
... 24 more
Caused by: org.xml.sax.SAXException: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 32 more
2009-04-04 11:52:29,560 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323)
... 24 more
Caused by: org.xml.sax.SAXException: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 32 more
in jboss_5_0.dtd:
<!-- The port-component element specifies a mapping from a webservice
port-component whose service-impl-bean/ejb-link value maps to an ejb.
Used in: session
-->
<!ELEMENT port-component (port-component-name, port-component-uri?, auth-method?,
transport-guarantee?) >
secure-wsdl-access is not included in the definition of port-component
remove the DOCTYPE of jboss.xml and the ear can be deployed successfully.
--
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, 3 months
[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:
----------------------------------
I tried modifying the test as follows:
tx.begin();
Request 10 connections
Close 2 connections
tx.commit();
Perform "List Formatted Sub Pool Statistics" operation
However, the "List Formatted Sub Pool Statistics" operation produced some strange values:
Sub Pool Statistics:
Sub Pool Count: 1
------------------------------------------------------
Track By Transaction: true
Available Connections Count: 19
Max Connections In Use Count:1
Connections Destroyed Count:0
Connections In Use Count:1
> 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)
> Components: ProfileService
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Critical
> 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
17 years, 3 months
[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:
----------------------------------
Jesper suggested that we modify our test so that requesting and closing connections gets done in a transaction that gets committed before we try to view the metrics. He said this was necessary because the value of "Connections In Use" count does not get updated in the correct locations in the JCA code. I am going to make this modification to the test and see if the metrics get displayed 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)
> Components: ProfileService
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Critical
> 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
17 years, 3 months
[JBoss JIRA] Created: (JBAOP-695) Hot un/deployment of .aop file works with war only when UseJBossWebLoader is enabled
by Flavia Rainone (JIRA)
Hot un/deployment of .aop file works with war only when UseJBossWebLoader is enabled
------------------------------------------------------------------------------------
Key: JBAOP-695
URL: https://jira.jboss.org/jira/browse/JBAOP-695
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.SP1
Reporter: Flavia Rainone
Assignee: Flavia Rainone
To reproduce the bug, follow in the steps:
-Package your web application in a WAR just like normal.
-Package your jboss-aop.xml and interceptor(s) in an AOP archive (e.g. myInterceptors.aop).
-Start JBoss with both the WAR and the AOP archive in the "deploy" directory and load-time weaving enabled. When JBoss starts it will examine the point-cuts in the jboss-aop.xml of your AOP archive and weave the classes in your WAR accordingly.
-To enable your interceptor(s), leave your AOP archive in the "deploy" directory.
-To disable your interceptor(s), remove your AOP archive from the "deploy" directory.
You will notice that the hot deploy is not working. It will work only if you change "UseJBossWebLoader" to "true" in <JBOSS_HOME>/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml.
--
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, 3 months
[JBoss JIRA] Updated: (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 Ian Springer (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ]
Ian Springer updated JBAS-6717:
-------------------------------
Comment: was deleted
> 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)
> Components: ProfileService
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Critical
> 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
17 years, 3 months
