March 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by Kevin.Conner＠jboss.com

"timfox" wrote : It's up to you. Handling transactional JMS messages is a requirement of ours, this naturally comes out of it. "timfox" wrote : You'll find the bridge has other nice features It has lots of cool features and it is a different beast from the ESB. The ESB also has other cool features not available in bridging :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139388#4139388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139388

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by timfox

So I guess users have a choice - they can use the esb router if it suits their needs, or just use the bridge if they want more flexible QoS settings, batching and reconnection. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139387#4139387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139387

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by timfox

Another common situation is that users find using XA too slow to bridge each message from one provider to another, so instead opt for "DUPS_OK" quality of service mode, and then just detect duplicates in their own code at the end. This can often be much faster than using XA and gives the same overall reliability guarantee, but in order to do that you need to know that the bridge always sends the message on before acking it to the source (i.e. dups_ok) so in case of failure you know you will never lose any messages but may get duplicates. So fine grained qos control is useful there. Then you might have other uses who never want duplicate messages, but don't mind losing a few - this is "at most once" delivery in messaging terminology. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139386#4139386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139386

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by Kevin.Conner＠jboss.com

"beve" wrote : Ah, cool. Is this in the main trunk or in one of the branches? It's in both CP and trunk at the moment. There is one more task to be completed by tomorrow though, the SQL integration has to be reverified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139385#4139385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139385

16 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: PropertyReplaceTC failing in maven

by alesj

"adrian(a)jboss.org" wrote : | Do the classloading-vfs tests fail for you as well? | Yeah, but it's old-reflection-creeping-in or too-new-kernel issue. Haven't seen your problem (yet). | ------------------------------------------------------------------------------- | Test set: org.jboss.test.classloading.vfs.metadata.test.ModuleDependencyUnitTestCase | ------------------------------------------------------------------------------- | Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.594 sec <<< FAILURE! | org.jboss.test.classloading.vfs.metadata.test.ModuleDependencyUnitTestCase Time elapsed: 0 sec <<< ERROR! | java.lang.RuntimeException: Unable to properly initialize the Kernel | at org.jboss.kernel.KernelFactory.initializeKernel(KernelFactory.java:203) | at org.jboss.kernel.KernelFactory.assembleNewKernel(KernelFactory.java:107) | at org.jboss.kernel.KernelFactory.newInstance(KernelFactory.java:67) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.bootstrap(AbstractBootstrap.java:114) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:83) | at org.jboss.test.kernel.junit.MicrocontainerTestDelegate.setUp(MicrocontainerTestDelegate.java:76) | at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:63) | at junit.extensions.TestSetup$1.protect(TestSetup.java:18) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.extensions.TestSetup.run(TestSetup.java:23) | 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:140) | at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) | at org.apache.maven.surefire.Surefire.run(Surefire.java:177) | 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:338) | at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) | Caused by: java.lang.NoClassDefFoundError: org/jboss/beans/info/spi/BeanAccessMode | at java.lang.Class.getDeclaredMethods0(Native Method) | at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) | at java.lang.Class.getDeclaredMethods(Class.java:1763) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getDeclaredMethods(IntrospectionTypeInfoFactoryImpl.java:479) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getMethods(IntrospectionTypeInfoFactoryImpl.java:188) | at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredMethods(ClassInfoImpl.java:394) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getMethods(AbstractBeanInfoFactory.java:203) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:136) | at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:68) | at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:65) | at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.getImplementation(PropertyKernelConfig.java:175) | at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.createKernelConfigurator(PropertyKernelConfig.java:96) | at org.jboss.kernel.plugins.bootstrap.basic.BasicKernelInitializer.createKernelConfigurator(BasicKernelInitializer.java:124) | at org.jboss.kernel.plugins.bootstrap.basic.BasicKernelInitializer.initKernel(BasicKernelInitializer.java:73) | at org.jboss.kernel.KernelFactory.initializeKernel(KernelFactory.java:198) | ... 23 more | Caused by: java.lang.NoClassDefFoundError: org/jboss/beans/info/spi/BeanAccessMode | at java.lang.Class.getDeclaredMethods0(Native Method) | at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) | at java.lang.Class.getDeclaredMethods(Class.java:1763) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getDeclaredMethods(IntrospectionTypeInfoFactoryImpl.java:479) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getMethods(IntrospectionTypeInfoFactoryImpl.java:188) | at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredMethods(ClassInfoImpl.java:394) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getMethods(AbstractBeanInfoFactory.java:203) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:136) | at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:68) | at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:65) | at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.getImplementation(PropertyKernelConfig.java:175) | at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.createKernelConfigurator(PropertyKernelConfig.java:96) | at org.jboss.kernel.plugins.bootstrap.basic.BasicKernelInitializer.createKernelConfigurator(BasicKernelInitializer.java:124) | at org.jboss.kernel.plugins.bootstrap.basic.BasicKernelInitializer.initKernel(BasicKernelInitializer.java:73) | at org.jboss.kernel.KernelFactory.initializeKernel(KernelFactory.java:198) | ... 23 more | | But it runs OK on my Linux box. :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139383#4139383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139383

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by timfox

It's up to you. You'll find the bridge has other nice features like message batching - being able to specify a batch size and a max batch time. I.e. send a batch every 10 seconds and/or every 1000 messages. It also has reconnect functionality which makes it very useful over an unreliable WAN. We have lots of users/customers currently using it. Also bear in mind that some JMS providers don't provide an XA resource implementation that can be used outside their app server, so you won't be able use a JTA transaction, in which case having fine grained control over your qos becomes important so users can do stuff like duplicate detection at the end in order to get an effective "once and only once" guarantee. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139380#4139380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139380

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E

by beve

Ah, cool. Is this in the main trunk or in one of the branches? Thanks, Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139377#4139377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139377

16 years, 3 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: Tomcat Deployer is wrong in JBoss Head

by jhalliday

Remy What's the status on JBAS-4511? jca-hack-for-tomcat-service.xml is causing me problems with moving the TransactionManager. I could really do with is cleaning up please. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139375#4139375 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139375

16 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: org.jboss:jboss-common-core pom

by dimitris＠jboss.org

A related question is, when a dependency C in project B has 'test' scope, doesn't this imply that this is an 'optional' dependency for a consumer A of the B project? A --> B --> C View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139374#4139374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139374

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: migrating TransactionManager and Invokers to POJO

by jhalliday

Took another look at this and it seems the current stumbling block is deployers/jca-hack-for-tomcat-service.xml which can't find the TransactionManager if I move it into deploy. Who is responsible for that hack and when is it going to be cleaned up? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139372#4139372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139372

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2008