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

[Design of JCA on JBoss] - Re: Pottential race condition in PoolFiller

by adrian＠jboss.org

http://jira.jboss.com/jira/browse/JBAS-4121 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019370#4019370 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019370

19 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: [long read] Info/help needed on extending EJB3 container

by bill.burke＠jboss.com

Young grasshopper, you seem to be on the right path...Dig further. Enlightenment must come from within. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019327#4019327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019327

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Seam on JBossESB

by burrsutter

We (Gavin and I) didn't discuss the distinction between having a conversational context id vs a session id. I'm guessing that it is more a session id and he manages the "conversation" on his side of things. I've sent him a link to this thread to see if he'll comment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019307#4019307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019307

19 years, 1 month

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: minor mod to testsuite server start/stop management

by akostadinov

btw I'm going to do for branch 4.0, 4.2 and trunc View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019297#4019297 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019297

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Pottential race condition in PoolFiller

by darran.lofthouse＠jboss.com

I was looking at some of the optimisations in the JCA code and it looks like there is a potential race condition in the PoolFiller implementation, just wanted to check if you wanted a Jira task raising so it can be addressed? http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/connector/src/... The class PoolFiller.java uses two seperate synchronized blocks in the run method | while (true) | { | try | { | InternalManagedConnectionPool mcp = null; | //keep iterating through pools till empty, exception escapes. | while (true) | { | | synchronized (pools) | { | mcp = (InternalManagedConnectionPool)pools.removeFirst(); | } | if (mcp == null) | break; | | mcp.fillToMin(); | } | } | catch (Exception e) | { | } | | try | { | synchronized (pools) | { | pools.wait(); | } | } | catch (InterruptedException ie) | { | return; | } | } It is possible that after the first synchronized block has finished a new connection pool is added to the list of pools before the second block is reached, the second block unconditionally waits and does not check that the list of pools is empty. The wait could be wrapped with a call to isEmpty: - | if (pools.isEmpty()) | { | pools.wait(); | } Or both synchronized blocks could be merged into one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019289#4019289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019289

19 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: [long read] Info/help needed on extending EJB3 container

by Sintel

I've been thinking a bit more on the subject and I think I'm almost there. To add metadata at client side I would also need a new client-side aspect right? It isn't mentioned in the original response, only that ThreadMetaData can be used, but I don't see any way to use it other than with a new client-side aspect, in addition to the mergemetadata interceptor. Looking at the code of InvokeRemoteInterceptor it seems there isn't really a problem in sending over references of objects from client to server and vice versa, through the use of metadata (I think if I use the AS_IS type only the unaltered reference gets sent which is sufficient, as the client's only job is to safeguard, not use it). So my new service could create a dispatcher on the server on the first invocation, which holds which target we need for the invocation. The server-side aspect can pass its reference to the client through the invocationresponse. The client can then include that reference with every invocation, the serveraspect asks that reference for the target and changes it in the invocation.. If this is all correct (confirmation?), it leaves me with this: 1) Where do i deploy my new developed aspects? 2) Is there an eclipse configuration that recognises @service etc? 3) Is there an alternative to deploying each beanimplementation in a seperate container? Thanks for listening View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019286#4019286 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019286

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Seam on JBossESB

by mark.little＠jboss.com

Context is the best place for this information. Not sure at the moment whether that is a 4.2 or a 5.0 item though. If not 4.2 then we can fudge it in WS-A, but that leads to backward compatibility problems when we eventually do it right. Anyway, I'll wait to hear from Burr. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019274#4019274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019274

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Seam on JBossESB

by tfennelly

"mark.little(a)jboss.com" wrote : Do you mean a session identifier? I'd suspect that it could be more than a session-id. Seam supports the notion of at "conversation context", which exists within the context of a session. You can have multiple conversations running in parallel within a single session. It tracks this using a conversation-id. So, I'd suspect they need something that they can map to something like "session-id:conversation-id". Not sure what Gavin/Burr has in mind - perhaps they've no intention of supporting anything beyond an equivalent of a session-id. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019273#4019273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019273

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Seam on JBossESB

by mark.little＠jboss.com

Do you mean a session identifier? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019265#4019265 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019265

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB security features

by mark.little＠jboss.com

We could certainly look at JBR as a basis for an implementation. However, we need an abstract notion of authorisation and security in order to allow other implementations to be tied in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019264#4019264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019264

19 years, 1 month

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