[JBoss JIRA] Updated: (JBCACHE-486) Optimize activations
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ]
Manik Surtani updated JBCACHE-486:
----------------------------------
Fix Version/s: 2.1.0.CR1
> Optimize activations
> --------------------
>
> Key: JBCACHE-486
> URL: http://jira.jboss.com/jira/browse/JBCACHE-486
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.3.0.GA
> Reporter: Jerry Gauthier
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> JBCACHE-420 notes that activation processing is performed excessively. The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue.
> The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor. Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated. This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination. This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader).
> It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance. One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__
> to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when
> activated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Deleted: (JBAS-4855) jboss-web with 4.0 dtd does not deploy
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4855?page=all ]
Thomas Diesler deleted JBAS-4855:
---------------------------------
> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
> Key: JBAS-4855
> URL: http://jira.jboss.com/jira/browse/JBAS-4855
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assigned To: Alexey Loubyansky
>
> [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
> at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
> ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
> at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.xinclude.XIncludeHandler.startElement(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.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Deleted: (JBAS-4857) NPE in ContainerConfigurationMetaDataWrapper
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4857?page=all ]
Thomas Diesler deleted JBAS-4857:
---------------------------------
> NPE in ContainerConfigurationMetaDataWrapper
> --------------------------------------------
>
> Key: JBAS-4857
> URL: http://jira.jboss.com/jira/browse/JBAS-4857
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assigned To: Scott M Stark
>
> [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> getContainerConfigurations returns null
> configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
> defaults.getContainerConfigurations());
> Caused by: java.lang.NullPointerException
> at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
> at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
> at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
> at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBPM-1070) The jBPM test configuration has problem with database setup
by Jiri Pechanec (JIRA)
The jBPM test configuration has problem with database setup
-----------------------------------------------------------
Key: JBPM-1070
URL: http://jira.jboss.com/jira/browse/JBPM-1070
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM jPDL 3.2.2
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
The jBPM test process expects hiberante.properties file to be placed in defined configuration directory. jBPM config file JBPM.3/jpdl/jar/src/test/config/jbpm.cfg.xml orders to use hibernate.properties file (<string name="resource.hibernate.properties" value="hibernate.properties" />).
But the JBPM.3/jpdl/jar/src/test/java/org/jbpm/db/AbstractDbTestCase.java uses config file less JBPM.3/jpdl/jar/src/test/java/org/jbpm/jbpm.test.cfg.xml and the line mentioned above is missing. Thus the configuration is read from standard hibernate.cfg.xml.
Solution
Either add the missing line to jbpm.test.cfg.xml or change AbstractDbTestCase.java to use central config file in config directory. The second one is preferred.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBAS-4853) jbossxb-1.0.0.GA shows webservice regression
by Thomas Diesler (JIRA)
jbossxb-1.0.0.GA shows webservice regression
--------------------------------------------
Key: JBAS-4853
URL: http://jira.jboss.com/jira/browse/JBAS-4853
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossAS-4.2.2.GA
This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
junit.framework.ComparisonFailure: expected:< > but was:<>
at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months