September 2007 - jboss-dev-forums

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Transaction Sticky LB policy for 4.2/trunk

by galder.zamarreno＠jboss.com

Brian, Coding is in progress at the moment. While starting to code the tests for each new LB policy (ok/failure + different invokers), I have realised that it'd be very easy to use the mock infrastructure created to test standard LBs. Looking around, haven't seen tests for standard LBs, do you think it's worth adding them? I don't think it'd take much longer to add them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086846#4086846 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086846

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by clebert.suconic＠jboss.com

"clebert.suconic(a)jboss.com" wrote : "alesj" wrote : | | MC has annotations per instance via XML. | | So no luck included here. ;-) | | That would be a good option for us, so we wouldn't need to add any JBoss5 specific annotations on our code, as our code is also intended to run on JBoss4. | | but i can't find any documentation on how to do it. I just confirmed that this doesn't exist yet... I will just add the annotations to org.jboss.mq.server.jmx.Queue and Topic... So the annotation will sit in an integration layer: http://anonsvn.jboss.org/repos/jbossas/trunk/messaging/src/main/org/jboss... http://anonsvn.jboss.org/repos/jbossas/trunk/messaging/src/main/org/jboss... Clebert View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086845#4086845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086845

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by clebert.suconic＠jboss.com

"alesj" wrote : | MC has annotations per instance via XML. | So no luck included here. ;-) That would be a good option for us, so we wouldn't need to add any JBoss5 specific annotations on our code, as our code is also intended to run on JBoss4. but i can't find any documentation on how to do it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086813#4086813 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086813

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by wolfc

App client 1.4/5 and JBoss client 5 are done. Will do JBoss client 1.4 tomorrow. More issues: the model assumes that meta data from an override xml is mappable on top of the overriden xml. But these might be overrides for annotations. So either we removed that requirement (which may lead to EJB 2 issues) or we process annotations before allowing jboss override files. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086799#4086799 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086799

18 years, 6 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: TxServerInterceptor hardwiring

by reverbel

The hardcoded references to TxServerInterceptor have been removed from the CORBA servants in svn trunk. Now all three servants (the EJB3 one included) use the InboundTransactionCurrent SPI, which has been added to the integration project. TxServerInterceptor still has dependencies on DTM classes, though. I will remove those dependencies soon. After the removal of the DTM/OTS code from JBossAS, TxServerInterceptor will remain as the default OTS interceptor, used by the default implementation of InboundTransactionCurrent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086794#4086794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086794

18 years, 6 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: How to capture the data from the JVMTI

by clebert.suconic＠jboss.com

The JVMTI version for capturing performance data is not ready.. As for "JVMPI is not supported", or you are using parallel GC or a JVM 6. On that case you could use JVMPI if you use a JVM 5- or if you used regular GC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086742#4086742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086742

18 years, 6 months

1
0
0 / 0

[Design of JBossXB] - jbossxb mvn test failures

by scott.stark＠jboss.org

There are many test errors when doing a mvn install that do not show up in the eclipse project run of the testsuite. One example shows the wrong handler being used it appears. What is the surefile plugin status with jbossxb? | 374 DEBUG [RepeatableTermsUnitTestCase] ==== Starting testUnmarshal2 ==== | 379 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@2b12e7f7, isNamespaceAware: true, isValidating: true, isXIncludeAware: true | 379 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true | 379 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true | 379 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true | 379 DEBUG [SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl@2b12e7f7, isNamespaceAware: true, isValidating: true, isXIncludeAware: true | 381 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@663b1f38, isNamespaceAware: true, isValidating: true, isXIncludeAware: true | 381 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true | 381 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true | 381 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true | 381 DEBUG [RepeatableTermsUnitTestCase] Initialized parsing in 1ms | 381 DEBUG [SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl@663b1f38, isNamespaceAware: true, isValidating: true, isXIncludeAware: true | 382 DEBUG [RepeatableTermsUnitTestCase] Error during parsing: file:/home/svn/Common/trunks/jbossxb/target/test-classes/org/jboss/test/xml/RepeatableTermsUnitTestCase_testUnmarshal2.xml | org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/Common/trunks/jbossxb/target/test-classes/org/jboss/test/xml/RepeatableTermsUnitTestCase_testUnmarshal2.xml@3,60 | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:118) | at org.jboss.test.xml.JBossXBTestDelegate.unmarshal(JBossXBTestDelegate.java:146) | at org.jboss.test.xml.AbstractJBossXBTest.unmarshal(AbstractJBossXBTest.java:227) | at org.jboss.test.xml.AbstractJBossXBTest.unmarshal(AbstractJBossXBTest.java:193) | at org.jboss.test.xml.RepeatableTermsUnitTestCase.testUnmarshal2(RepeatableTermsUnitTestCase.java:93) | 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 junit.framework.TestCase.runTest(TestCase.java:154) | at junit.framework.TestCase.runBare(TestCase.java:127) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:118) | at junit.framework.TestSuite.runTest(TestSuite.java:208) | at junit.framework.TestSuite.run(TestSuite.java:203) | 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) | at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) | at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:163) | at org.apache.maven.surefire.Surefire.run(Surefire.java:84) | 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:244) | at org.apache.maven.surefire.booter. | SurefireBooter.main(SurefireBooter.java:814) | Caused by: java.lang.UnsupportedOperationException: Using Default Handler! startParticle: {http://www.jboss.org/test/xml/repeatableterms}top [org.jboss.xb.binding.sunday.unmarshalling.ElementBinding@337ec9f7({http://www.jboss.org/test/xml/repeatableterms}top, type=null), minOccurs=1, maxOccurs=0] | at org.jboss.test.xb.builder.DebugElementHandler.startParticle(DebugElementHandler.java:41) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:606) | 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.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:180) | ... 31 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086740#4086740 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086740

18 years, 6 months

1
0
0 / 0

[Design of JBoss Profiler] - How to capture the data from the JVMTI

by singhsachin13

Hi, I'm using JBoss -4.0.5. But when I start the "run.bat" file from the JBoss\bin, it gives me the error that JVMPI is not supported. Please help me out what changes I've to made or what settings to be done to capture the data from the JVMTI. Regards Sachin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086737#4086737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086737

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by alesj

Scott, is there a way to distinguish between ManagedOperation being a getter or plain method? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086711#4086711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086711

18 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

by richard_opalka

"palin" wrote : It can be obtained with less pain if the whole rm subsystem it designed keeping it in mind. I fully agree with you! We have to keep it in mind. "palin" wrote : | Are cookies really needed for rm? In any case the user loadbalancer choice is not our business ;-) If you have statefull services deployed to the cluster then cookies aware cluster nodes is a must. As I know almost all hardware/software loadbalancers are cookies aware. "palin" wrote : | I'll think about the handler issue you wrote in the meantime. | I'm looking forward for your ideas ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086701#4086701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086701

18 years, 6 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 September 2007