January 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Portal] - Re: Exception while loading application

by vivek_saini07

Did you get the solution. I am facing the same problem. it seems transaction is not getting started. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199875#4199875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199875

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Commented out code in org.jboss.messaging.integration.transp

by timfox

| // This block has been disabled because this method can be called from | // the Netty I/O thread. | // TODO Netty should be improved to provide a way to determine | // if the current code is running in the I/O thread. | // | // if (channel.getParent() == null) { | // // A client channel - wait until everything is cleaned up. | // // TODO Do not spin - use signal. | // MessagingChannelHandler handler = (MessagingChannelHandler) channel.getPipeline().get("handler"); | // while (handler.active) { | // Thread.yield(); | // } | // } | Does anyone (trustin?) know if the comment still applies? Does netty need to be changed? can the comment be deleted? etc View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199858#4199858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199858

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

How about a variation on the caching approach? The old caching approach that we discounted involved evaluating the routing address against all wildcards once to get the matching list, then caching the list for subsequent lookups. The problem with the approach was that if a new match was added you had to invalidate the cache, so the next lookup would re-evaluate all matches. If a lot of new queues were being added frequently (as is often the case), then this would cause a lot of re-evaluation and slowness. We could be a bit cleverer, and not invalidate the entire cache very time a new wildcard queue is added, but just evaluate the new match and add it to the cache. If a match is removed from the post office then we could just look in the cache for each routing address and remove it from there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199836#4199836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199836

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Maximum path length easly exceeded

by timfox

"clebert.suconic(a)jboss.com" wrote : anonymous wrote : The paging files could also be broken by crashes, it's no different. | | It is different... we have put a lot of effort in making the Journal transactional, validating the health of records.. and etc... | | If we start having a file per address it's better, but once a destination gets on page-mode, you will have that file on disk until someome manually delete it. | Reaper thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199824#4199824 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199824

15 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - JBJCA-35: Resource adapter deployer

by jesper.pedersen

See http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199822 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199823#4199823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199823

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBMESSAGING-1457 - Unexistent destinations on both nodes

by clebert.suconic＠jboss.com

Howard, I think you need to add a test somehow you have destinations deployed in only one node (without any messages), and failover with other destinations deployed on both nodes. You need to validate the test in two cases. - destinations only deployed in one node, but no messages on them. - destinations only deployed in one node, but with messages on them on both cases you need a second destination with messages on both nodes. The failover on that second destination shouldn't be affected. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199812#4199812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199812

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Maximum path length easly exceeded

by clebert.suconic＠jboss.com

anonymous wrote : The paging files could also be broken by crashes, it's no different. It is different... we have put a lot of effort in making the Journal transactional, validating the health of records.. and etc... If we start having a file per address it's better, but once a destination gets on page-mode, you will have that file on disk until someome manually delete it. Think about if a temporary destination gets in page mode. What will remove that file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199806#4199806 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199806

15 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: jboss_5_0.xsd: jboss version attribute

by alex.loubyansky＠jboss.com

Ok, I should have read the comments in the XSD before posting, it's actually the EJB spec. Are you sure the value should be fixed here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199800#4199800 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199800

15 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - jboss_5_0.xsd: jboss version attribute

by alex.loubyansky＠jboss.com

What is version attribute supposed to indicate? EJB spec version? At the moment, in jboss_5_0.xsd its value is fixed and is 3.0. Everything else appearing in XML is invalid. In our tests though, some jboss.xml files have it set to 5.0, some 3.0. <jboss xmlns="http://www.jboss.com/xml/ns/javaee" | xmlns:jee="http://java.sun.com/xml/ns/javaee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" | version="5.0"> | | <jboss | xmlns="http://www.jboss.com/xml/ns/javaee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee | http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" | version="3.0"> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199797#4199797 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199797

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

"ataylor" wrote : | Ok so this means either creating all the possible combinations, which is how it works now. | Or checking for matching wildcard mappings on send, which will have an overhead. I'm not convinced those are the only two possibilities. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199786#4199786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199786

15 years, 4 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 January 2009