February 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBossCache] - Re: CacheListener events for state transfer marshalling

by manik.surtani＠jboss.com

And would the callback be for every node being marshalled for ST, or the fqn representing the region/subroot? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010831#4010831 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010831

19 years, 2 months

1
0
0 / 0

[Design of JBossCache] - Re: CacheListener events for state transfer marshalling

by manik.surtani＠jboss.com

Wow, this is a pretty specialised case. And I can't say I entirely like such a specialised call back in the listener, although I can't think of an alternative way of achieving the same. I presume you need this in 1.4.1 though, for AS 4.2? Also, as an FYI, the way the marshalling works in 2.0.0 for ST is that a List of NodeData objects is passed to the VAM. I suppose the callbacks could happen before and after generating each NodeData object in a loop. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010779#4010779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010779

19 years, 2 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: 4.0.5 org.jboss.test.compatibility.test.SerialVersionUID

by visolvejboss

Hello, "test401Compatibility" test case shows the error message. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010699#4010699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010699

19 years, 2 months

1
0
0 / 0

[Design of JBossCache] - CacheListener events for state transfer marshalling

by bstansberry＠jboss.com

There's no CacheListener event generated before a node is about to be marshalled for state transfer. Use case for this is EJB3 SFSB, where we are storing a bean context in the cache. EJB3 spec says we should invoke any prePassivate/postActivate callbacks the bean declares when we serialize/deserialize. These callbacks allow the bean to clean up it's state. There are 3 types of serialization involved: replication, serialization to disk as part of eviction/passivation, and state transfer. The first is easy for the EJB3/JBC integration layer, as it causes the replication. The second we handle during the CacheListener callbacks. But we have no hook to handle the third. This is kind of a specialized case, but then again maybe not. We have events for all the other significant stuff that happens to a node, except this one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010618#4010618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010618

19 years, 2 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: 4.0.5 org.jboss.test.compatibility.test.SerialVersionUID

by ryan.campbell＠jboss.com

Which version of JBoss is the serial UID incompatible with? IE, which test is actually failing and printing this error message? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010545#4010545 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010545

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by clebert.suconic＠jboss.com

As part of the investigation of this issue, and per what you said about producers, I have found this other one: anonymous wrote : http://jira.jboss.com/jira/browse/JBMESSAGING-809 It has to do with sending messages now. It's a rare event but it can happen if you crash the server under high load. (>30% of probability on MultiThreadFailover if you have numberOfThreadConsumers>numberOfThreadProducers). (you have two properties you can change for these number of threads on MultiThreadFailover) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010472#4010472 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010472

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Backport to 1_0_1_SP1 has broken the test suite

by ovidiu.feodorov＠jboss.com

Ummmm, should I kindly remind you this is a public forum? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010470#4010470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010470

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by clebert.suconic＠jboss.com

"Tim Fox" wrote : But when you make changes don't just comment things out, get rid of them if they are not needed. Fair enough... I will remove these comments later (if you haven't done so yet). "Tim Fox" wrote : | I'm not sure if the log.warn is really necessary either. | | log.warn would imply there is probably something wrong. Is this the case? It's not a problem. I just wanted to log ACKs not found case we get lots of them.. (if something is wrong with our code at some point for example). And I kept it as log.warn because I thought if something is wrong wit a config in a Production system. (Say... for example if someone deleted information from the database in the middle of an operation). But we could use log.debug if you think it's better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010469#4010469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010469

19 years, 2 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Reducing Java object lock contention in org.jboss.invoca

by scott.stark＠jboss.org

The full testsuite is run using the tests target in the testsuite module. There are several other sub starting points: [starksm@succubus testsuite]$ ant -projecthelp Buildfile: build.xml Main targets: all Builds everything. clean Cleans up most generated files. clobber Cleans up all generated files. compile Compile all source files. deployment-service-tests Tests targeting the deployment service docs Builds all documentation. help Displays the project help iiop-test Execute a single test. jars Builds all jar files. jboss-all-config-tests The units tests which are run against the jboss all config jboss-minimal-tests Validate the minimal config main Executes the default target (most). most Builds almost everything. netboot-tests Tests run against a custom netboot configuration one-test Execute a single test. one-test-debug Execute a single test. one-test-ssl Execute a single test. reports Generates all reports. test Execute a a group of tests test-example-binding-manager Test the example binding configuration tests Execute all non-benchmark tests. tests-aop-scoped AOP tests requiring a native classloader hook tests-apache Test that apache can be started/stopped from ant tests-apache-tomcat-clustering Execute clustering tests requiring an apache load balanced two TC nodes. tests-clustering Execute clustering tests requiring two nodes. tests-clustering-all-stacks Execute clustering tests requiring two nodes. tests-compatibility Checks compatibility on SerialUUID tests-custom-securitymgr Tests run against a jboss server with custom security manager configured tests-deployment Execute deployment Tests tests-ha Execute ha tests. tests-jacc-security Tests run against a jboss server with JACC configured tests-jacc-security-external Tests run against a jboss server with JACC configured with an external policy provider tests-jacc-securitymgr Tests run against a jboss server with JACC configured + security manager tests-jboss-cluster Test that two jboss cluster nodes can be started/stopped from ant tests-matrix Executes only the version check compatibility suite. Use -Dmatrix-versions=[version container] for this task tests-security-manager Tests run against a jboss server with a security manager tests-stress Execute all stress tests. tests-webservice Execute JBossWS Tests tests-webservice-ssl Tomcat tests requiring an SSL connector tests-wsrp-integration Execute WSRP Integration Tests tomcat-federation-tests Tomcat tests requiring Federation configured tomcat-ssl-tests Tomcat tests requiring an SSL connector tomcat-sso-clustered-tests Tomcat tests requiring clustered SSO configured tomcat-sso-tests Tomcat tests requiring SSO configured tomcat-webctx-tests Tomcat tests requiring classloader set to the web loader Default target: main Nothing uses the pooled invoker by default though, so to run the basic pooled invoker tests from the org.jboss.test.pooled package: ant -Dtest=pooled test View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010453#4010453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010453

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

That is just a bad configuration of the jmx name as it is the same as the bean name: | <bean class="org.jboss.system.BarrierController" | name="jboss.ha:service=HASingletonDeployer,type=BarrierController"> | | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.ha:service=HASingletonDeployer,type=BarrierController", exposedInterface=org.jboss.system.BarrierControllerMBean.class, registerDirectly=true)</annotation> | I checked in a change to set the jmx name to jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010444#4010444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010444

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2007