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

[Design the new POJO MicroContainer] - Out of order message problem (discussion thread for JBREM-96

by david.lloyd＠jboss.com

When dealing with a protocol using multiple channels (HTTP for example, and possibly a future multi-channel JRPP variant), sending two messages on two different channels can cause ordering issues if the second message sent arrives first. For example, sending a context open on channel A, and a request on channel B, may cause the request to be received before the context open message, resulting in the request being rejected with a "no such context" error. Another example is that stream messages must be handled sequentially. There are several possible solutions, including but not limited to: * for any message B that must come after A, always send A and B on the same channel (problem: HTTP channels are transient, so this won't work for HTTP) (problem: this could load up one channel while leaving other channels empty, even if load-balancing is used) * don't send B until after A is acknowledged (problem: acknowledging A might not be possible within the underlying protocol, like if A is sent in an HTTP reply, requiring a separate ACK message, which can lead to performance problems) * if a message comes in seemingly unsolicited (like a request on a nonexistant context) or out of sequence (like in a stream), queue the message for some fixed amount of time to see if the context open message arrives (problem: could be a source of DoS on the server; also this is a duplication of what protocols like TCP already do, which means that all the same problems must be in effect re-solved) Please share any ideas you have or comments on the above. The JIRA issue is at http://jira.jboss.com/jira/browse/JBREM-963 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143989#4143989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143989

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - EJBTHREE-1278, fixing jbossas5/mc integration code

by scott.stark＠jboss.org

The current direct installation of the ejb container into the mc kernel bypasses the depedency failure error reporting mechanism. We need to update the integration to: 1. Have jbossas integration provide an implementation of org.jboss.ejb3.KernelAbstraction 2. Update the org.jboss.ejb3.DeploymentUnit The KernelAbstraction would simply add the AbstractBeanMetaData to the unit as an attachment so it would be properly integrated into the jbossas deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143981#4143981 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143981

16 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: jee module's alt-dd

by alex.loubyansky＠jboss.com

I've committed the change (with a testcase) to the SchemaResolverDeployer's parse(..) method VirtualFile altDD = (VirtualFile) unit.getAttachment(getOutput().getName() + ".altDD"); | if(altDD != null) | file = altDD; I am going to create a separate issue in JBAS project for ejb, client and also war(?) deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143952#4143952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143952

16 years, 7 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by anil.saldhana＠jboss.com

Stefan, I want to try out what Adrian is saying but do not have cycles this week. I am wondering if you can make an attempt at what he has suggested. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143948#4143948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143948

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Plug-able default JNDI binding policy

by scott.stark＠jboss.org

Related to this is how the ProxyDeployer determines the remote interface binding jndi name. If I need to determine the target jndi name at reference resolution time, this needs to be set earlier. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143946#4143946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143946

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by anil.saldhana＠jboss.com

All that the ejb3 security interceptors were doing were to extend the aspects security interceptors with bulk of the processing done in the aspects layer. Carlo wanted the ejb3 sec interceptors to implement aspects interceptor and do all the processing there. I think he is right. Moving the aspects security code into the ejb3 security code enabled me to extract common code (with ejb2). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143942#4143942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143942

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1316 - Add support for a configurable time tolerance va

by darran.lofthouse＠jboss.com

I am ready to commit changes for the following Jira issue to trunk, before I do I just quickly wanted to raise the configuration approach here before I add it to the user guide. http://jira.jboss.com/jira/browse/JBWS-1316 The changes are in the following branch in SVN: - https://svn.jboss.org/repos/jbossws/stack/native/branches/dlofthouse/JBWS... The relevant commits are: - http://fisheye.jboss.com/changelog/JBossWS/?cs=6366 http://fisheye.jboss.com/changelog/JBossWS/?cs=6416 This change adds the following element to the global configuration area of the jboss-wsse configuration: - | <timestamp-verification createdTolerance="5" | warnCreated="false" | expiresTolerance="10" | warnExpires="false" /> | This allows for a tolerance to be set individually for the comparison of the created and expires value, the tolerance is in seconds in line with other time values in the configuration. The warn attributes allow for a warning to be logged if a message is accepted that would not normally be accepted without the tolerance. If this configuration is not provided then the default is the old behaviour of only using the time the message is received in the comparisons. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143938#4143938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143938

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by kabir.khan＠jboss.com

"anil.saldhana(a)jboss.com" wrote : | Aspects security is not being used (apart from the SecurityClientInterceptor which will be moved to ejb3 core). I am not sure about what classes the embedded version uses. | | I extracted the common code base between ejb2 and ejb3 into helper classes in the AS/security module, sometime ago. We do have tests in the AS testsuite to test these aspects, and there are some users using them as well View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143928#4143928 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143928

16 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Pulling security out as a separate module

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : I think the issue is just duplicate code. Between aspects, security and ejb2 there seems to be a lot of duplication. | Aspects security is not being used (apart from the SecurityClientInterceptor which will be moved to ejb3 core). I am not sure about what classes the embedded version uses. I extracted the common code base between ejb2 and ejb3 into helper classes in the AS/security module, sometime ago. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143925#4143925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143925

16 years, 7 months

1
0
0 / 0

[Design of JBoss IIOP on JBoss] - Re: Is JacORB.JAR in the bootclasspath?

by adrian＠jboss.org

"lzap" wrote : | The file jacorb.jar includes org.omg packages and I thought having it in the bootclasspath overrides Sun ones. | Those are omg classes that are not available in all JDKs. e.g. CosTransactions is not part of the JDK or some classes are not available in older JDK versions. anonymous wrote : | I will try to move the thread. | By "move the thread" I meant start a new thread in either the naming, deployment or ejb forums stating what your problem really is. Your initial question related to a method on the ORB classs which just gets delegated to the ORB singleton. Inside JBoss (in the all configuration) that is JacORB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143914#4143914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143914

16 years, 7 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 April 2008