[JBoss JIRA] Created: (JBCACHE-1082) Optimise nodes for single elements
by Manik Surtani (JIRA)
Optimise nodes for single elements
----------------------------------
Key: JBCACHE-1082
URL: http://jira.jboss.com/jira/browse/JBCACHE-1082
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.0.0.CR3, 2.0.0.GA
Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should:
1) Create a reference to 2 Objects for key and value, as well as a Map.
2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair
3) Otherwise just hold the key/value pair as direct object refs.
Would affect UnversionedNode and WorkspaceNodeImpl.
--
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
18 years, 1 month
[JBoss JIRA] Commented: (JBAS-3051) change jmx console title to display the name of the jboss server configuration with the machine name
by Jim Moran (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3051?page=comments#action_12416105 ]
Jim Moran commented on JBAS-3051:
---------------------------------
Dimitris, is right.
I think I remember this came from a customer that was running multiple instances on their machine and was frustrated keeping track when he had multiple jmx-console windows open to different instances. Anything that can uniquely identify the instance would work. I was thinking ServerName because you can be running multiple instances on the same bind address but using different ports for the various services.
> change jmx console title to display the name of the jboss server configuration with the machine name
> ----------------------------------------------------------------------------------------------------
>
> Key: JBAS-3051
> URL: http://jira.jboss.com/jira/browse/JBAS-3051
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX/Web Console
> Reporter: Jim Moran
> Assigned To: Clive Saldanha
> Priority: Trivial
> Attachments: config_in_header.patch
>
>
> When running multiple instances of JBoss on one machine the jmx console's title does not distinguish which instance it is for.
> It would be easier to distinguish which instance a jmx console was for if the title contained the server config name as well as the machine name.
--
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
18 years, 1 month
[JBoss JIRA] Commented: (JBAS-3051) change jmx console title to display the name of the jboss server configuration with the machine name
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3051?page=comments#action_12416092 ]
Dimitris Andreadis commented on JBAS-3051:
------------------------------------------
I think Jim talks about the <title> really, e.g. something like:
<title>JBoss JMX Management Console - poseidon (127.0.0.1) </title>
I wouldn't bother adding the config name on the title.
Maybe that could be added in the text:
JMX Agent View
poseidon (127.0.0.1) - default
In any case, it's preferable to read the config from the 'jboss.server.name' system property rather than doing this stuff:
2c2
< import="java.net.*,java.util.*,org.jboss.jmx.adaptor.model.*,javax.management.*,java.io.*"
---
> import="java.net.*,java.util.*,org.jboss.jmx.adaptor.model.*,java.io.*"
20,21c20
< ObjectName obname = new ObjectName("jboss.system:type=ServerConfig");
< hostname = InetAddress.getLocalHost().getHostName() + "Config: " + (String)org.jboss.jmx.adaptor.control.Server.getMBeanServer().getAttribute(obname,"ServerName");
---
> hostname = InetAddress.getLocalHost().getHostName() + "Config: " + (String)org.jboss.jmx.adaptor.control.Server.getMBeanServer().getAttribute("type=ServerConfig","ServerName");
> change jmx console title to display the name of the jboss server configuration with the machine name
> ----------------------------------------------------------------------------------------------------
>
> Key: JBAS-3051
> URL: http://jira.jboss.com/jira/browse/JBAS-3051
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX/Web Console
> Reporter: Jim Moran
> Assigned To: Clive Saldanha
> Priority: Trivial
> Attachments: config_in_header.patch
>
>
> When running multiple instances of JBoss on one machine the jmx console's title does not distinguish which instance it is for.
> It would be easier to distinguish which instance a jmx console was for if the title contained the server config name as well as the machine name.
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBAS-5594) fix org.jboss.test.bankiiop.test.BankStressTestCase
by Dimitris Andreadis (JIRA)
fix org.jboss.test.bankiiop.test.BankStressTestCase
----------------------------------------------------
Key: JBAS-5594
URL: http://jira.jboss.com/jira/browse/JBAS-5594
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Dimitris Andreadis
Assigned To: Alexey Loubyansky
run -c all
&
build one-iiop-test -Dtest=org.jboss.test.bankiiop.test.BankStressTestCase
The test fails to deploy and this looks like a metadata issue. From server.log:
2008-06-06 12:11:08,046 INFO [org.jboss.deployment.MainDeployer] (RMI TCP Connection(18)-127.0.0.1) deploy, url=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar
2008-06-06 12:11:08,046 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (RMI TCP Connection(18)-127.0.0.1) Add deployment: vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar
2008-06-06 12:11:08,046 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (RMI TCP Connection(18)-127.0.0.1) Scheduling deployment: vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar parent=null
2008-06-06 12:11:08,046 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (RMI TCP Connection(18)-127.0.0.1) Deploying vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar
2008-06-06 12:11:08,046 DEBUG [org.jboss.deployment.EjbParsingDeployer] (RMI TCP Connection(18)-127.0.0.1) Parsing file: JarEntryHandler(a)8182754[path=META-INF/ejb-jar.xml context=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar real=jar:file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar!/META-INF/ejb-jar.xml] for deploymentType: class org.jboss.metadata.ejb.spec.EjbJarMetaData
2008-06-06 12:11:08,046 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) Created parser: org.apache.xerces.jaxp.SAXParserImpl@df520e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2008-06-06 12:11:08,046 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/validation set to: true
2008-06-06 12:11:08,062 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/namespaces set to: true
2008-06-06 12:11:08,062 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://apache.org/xml/features/validation/dynamic set to: true
2008-06-06 12:11:08,062 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://apache.org/xml/features/validation/schema set to: true
2008-06-06 12:11:08,062 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/validation set to: true
2008-06-06 12:11:08,062 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) Created parser: org.apache.xerces.jaxp.SAXParserImpl@df520e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.deployment.EjbParsingDeployer] (RMI TCP Connection(18)-127.0.0.1) Parsed file: JarEntryHandler(a)8182754[path=META-INF/ejb-jar.xml context=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar real=jar:file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar!/META-INF/ejb-jar.xml] to: org.jboss.metadata.ejb.spec.EjbJar1xMetaData@1f
2008-06-06 12:11:09,312 DEBUG [org.jboss.deployment.JBossEjbParsingDeployer] (RMI TCP Connection(18)-127.0.0.1) Parsing file: JarEntryHandler(a)23126736[path=META-INF/jboss.xml context=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar real=jar:file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar!/META-INF/jboss.xml] for deploymentType: class org.jboss.metadata.ejb.jboss.JBossMetaData
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) Created parser: org.apache.xerces.jaxp.SAXParserImpl@1cad8db, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/validation set to: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/namespaces set to: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://apache.org/xml/features/validation/dynamic set to: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://apache.org/xml/features/validation/schema set to: false
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) http://xml.org/sax/features/validation set to: true
2008-06-06 12:11:09,312 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP Connection(18)-127.0.0.1) Created parser: org.apache.xerces.jaxp.SAXParserImpl@1cad8db, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2008-06-06 12:11:09,328 DEBUG [org.jboss.deployment.JBossEjbParsingDeployer] (RMI TCP Connection(18)-127.0.0.1) Parsed file: JarEntryHandler(a)23126736[path=META-INF/jboss.xml context=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar real=jar:file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar!/META-INF/jboss.xml] to: org.jboss.metadata.ejb.jboss.JBoss50DTDMetaData@1f
2008-06-06 12:11:09,328 DEBUG [org.jboss.deployers.vfs.plugins.classloader.InMemoryClassesDeployer] (RMI TCP Connection(18)-127.0.0.1) Dynamic class root for vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar is vfsmemory://5c4o0m-i7fk3s-fh4jy759-1-fh4k5dsg-31
2008-06-06 12:11:09,328 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader] (RMI TCP Connection(18)-127.0.0.1) Created BaseClassLoader@67db8a{vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar} with policy VFSClassLoaderPolicy@7e4b7d{name=vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar domain=null roots=[MemoryContextHandler@26088291[path=classes context=vfsmemory://5c4o0m-i7fk3s-fh4jy759-1-fh4k5dsg-31 real=vfsmemory://5c4o0m-i7fk3s-fh4jy759-1-fh4k5dsg-31/classes], JarHandler@10157227[path= context=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar real=file:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar]] delegates=null exported=[META-INF, org.jboss.test.util.ejb, org.jboss.test.bankiiop.interfaces, org.jboss.test.bankiiop.ejb] <IMPORT-ALL>NON_EMPTY}
2008-06-06 12:11:09,328 DEBUG [org.jboss.classloader.spi.base.BaseClassLoaderDomain] (RMI TCP Connection(18)-127.0.0.1) ClassLoaderDomain@15d252d{<DEFAULT>} registerClassLoader BaseClassLoader@67db8a{vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar}
2008-06-06 12:11:09,328 DEBUG [org.jboss.deployment.AnnotationMetaDataDeployer] (RMI TCP Connection(18)-127.0.0.1) Deployment is metadata-complete, skipping annotation processing, ejbJarMetaData=org.jboss.metadata.ejb.spec.EjbJar1xMetaData@1f, jbossWebMetaData=null, jbossClientMetaData=null, metaDataCompleteIsDefault=false
2008-06-06 12:11:09,328 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (RMI TCP Connection(18)-127.0.0.1) vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar endpoint mappings:
+ ejb/#Teller -> ContainerDependencyMetaData(deploymentPath=,componentName=Teller,containerName=bank-iiop/Teller,jndiNames=[bank-iiop/Teller],jndiAliasDepends=[],targets=[],jndiDepends=[])
+ ejb/#Account -> ContainerDependencyMetaData(deploymentPath=,componentName=Account,containerName=bank-iiop/Account,jndiNames=[bank-iiop/Account],jndiAliasDepends=[],targets=[],jndiDepends=[])
+ ejb/#Customer -> ContainerDependencyMetaData(deploymentPath=,componentName=Customer,containerName=bank-iiop/Customer,jndiNames=[bank-iiop/Customer],jndiAliasDepends=[],targets=[],jndiDepends=[])
+ ejb/#Bank -> ContainerDependencyMetaData(deploymentPath=,componentName=Bank,containerName=bank-iiop/Bank,jndiNames=[bank-iiop/Bank],jndiAliasDepends=[],targets=[],jndiDepends=[])
2008-06-06 12:11:09,328 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (RMI TCP Connection(18)-127.0.0.1) Error during deploy: vfsfile:/X:/cvs/jboss-public/jboss-head/testsuite/output/lib/bankiiop.jar
org.jboss.deployers.spi.DeploymentException: java.lang.IllegalStateException: Failed to find ContainerDependencyMetaData for: null
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.internalDeploy(MappedReferenceMetaDataResolverDeployer.java:161)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentLast(DeployersImpl.java:1112)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:913)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1394)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:786)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:914)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:836)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:674)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:456)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812)
at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:587)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
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.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:270)
at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416)
at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Failed to find ContainerDependencyMetaData for: null
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.resolveEjbInterface(MappedReferenceMetaDataResolverDeployer.java:912)
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.resolveEjbRefs(MappedReferenceMetaDataResolverDeployer.java:821)
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.resolve(MappedReferenceMetaDataResolverDeployer.java:606)
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.resolve(MappedReferenceMetaDataResolverDeployer.java:629)
at org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.internalDeploy(MappedReferenceMetaDataResolverDeployer.java:157)
... 62 more
--
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
18 years, 1 month
[JBoss JIRA] Created: (EJBTHREE-1039) Optimized replication of entities and extended persistence context in SFSBs
by Brian Stansberry (JIRA)
Optimized replication of entities and extended persistence context in SFSBs
---------------------------------------------------------------------------
Key: EJBTHREE-1039
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1039
Project: EJB 3.0
Issue Type: Feature Request
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Optimize replication of clustered SFSBs that hold refs to managed entities and extended persistence contexts, while still ensuring that object identity is maintained between refs to an entity held by the SFSB and those held by the replicated EntityManager.
Currently object identity is maintained by serializing the SFSB and the related EntityManager in one operation. The entire EM is serialized, including entities that have been flushed to the db. This is inefficient, since the replication is only done to support failover and in the case of node failover, the flushed entities can be restored from the db or the EM's 2nd level cache.
Intent is to:
1) Use JBoss serialization in order to have the ability to alter the serialized form of entities and XPCs.
1) Have Hibernate's EM impl expose getUnflushedChanges()/setUnflushedChanges() methods to support replication of only the unflushed changes held in the XPC, rather than all data.
2) When writing the fields in an SFSB, check if the object is a managed entity; if so write it's id to the stream rather than the whole object.
3) Deserialization process needs to ensure that any EntityManager is deserialized before the managed entities.
4) Deserialization of a managed entity would involve reading the id from the stream, identifying the EntityManager and doing a find().
5) SFSBs should be lazy-deserialized (i.e. only deserialize if needed to handle failover). This is the way SFSBs clustering already works. This is critical, otherwise the cost of the find() operations would likely outweigh the benefits of reducing the amount of replicated data.
Additionally, intent is to allow registration with the container of an impl, say, "ManagedPersistenceContextSerializer". If registered, implementation of many of the steps above would be delegated. JBoss Seam would intend to register an implementation.
--
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
18 years, 1 month
[JBoss JIRA] Created: (JGRP-765) @Property: setting and getting properties need to set/get the actual variables
by Bela Ban (JIRA)
@Property: setting and getting properties need to set/get the actual variables
------------------------------------------------------------------------------
Key: JGRP-765
URL: http://jira.jboss.com/jira/browse/JGRP-765
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.7
When changing a variable through a setter, e.g. UDP.setMulticastPort(), the underlying 'props' properties hashmap is not changed, only the instance var is changed. When we now call JChannel.getProperties(), we get the old properties. This leads to duplicate channels with the SAME properties when creating unique channels in TestNG (ChannelTestBase). As a result, the channels are NOT unique, and we get test failures.
SOLUTION:
- When a set a property through a setter, we need to update the underlying properties hashmap too
- When we set a property in the properties hashmap, we need to update the instance variable too
- Ditto for getting values
--
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
18 years, 1 month