April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-1793) Fix the LocalTxDataSource

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1793?page=all ] Jesper Pedersen updated JBAS-1793: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Fix the LocalTxDataSource > ------------------------- > > Key: JBAS-1793 > URL: http://jira.jboss.com/jira/browse/JBAS-1793 > Project: JBoss Application Server > Issue Type: Sub-task > Components: JCA service > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > > This needs moving somewhere else (varia?). > But since it is basically a hack, it needs doing properly, > see the linked task on how todo this properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1820) JCA 1.5 compliance bug

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1820?page=all ] Jesper Pedersen updated JBAS-1820: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > JCA 1.5 compliance bug > ---------------------- > > Key: JBAS-1820 > URL: http://jira.jboss.com/jira/browse/JBAS-1820 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.2 Final > Environment: Windows 2000 > Reporter: guillaume holler > Assigned To: Jesper Pedersen > Priority: Minor > Attachments: jcasample.zip > > > This is a deployment bug that affects inflow messages. > JCA 1.5 specification states states that "Before a rsource adapter is undeployed, the application server must deactivate all active enpoints consuming messages from that specific resource adapter". This doesn't seem to be the case: > 1 - start the server with a RAR and an MDB endpoint setup (the test connector accept messages from network and the mdb merely print them on the console after wainting 10s to easealy test enpoint concurrency issues). > OK: I see the start() and endpointActivation(...) callback called > 2 - run the client test several times (in a way that enables concurrent message consumption): OK (client OK, console prints all messages) > 3 - undeploy RAR: I can see the stop callback, but no MDB undeploy or endpointDeactivation(...) callback on resource adapter. > 4 - deploy RAR again: deployment OK, I can see the start() callback but no endpointActivation(...) callback called > 5 - run the client test again: client OK, demonstrating the network endpoint is working, but no message printed on the console (no endpoint consumption). > 6 - undeploy/deploy MDB: everything works again as in 2 (plus, messages pending from step 5 are obviously consumed) > I think we should have, according to spec, an undeployment of MDBs that depend on the RAR service when the service is undeployed, and a furter restart should trigger a new endpointActivation callback. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1437) RAR MetaData Repository

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1437?page=all ] Jesper Pedersen updated JBAS-1437: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > RAR MetaData Repository > ----------------------- > > Key: JBAS-1437 > URL: http://jira.jboss.com/jira/browse/JBAS-1437 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48681 > Implement a RAR MetaData repository. > There are two use cases of this object: > * A tool wants to retrieve information about how to configure a RAR deployment > either inbound/outbound or admin object > * Avoiding the need to specify the rar-name in jboss.xml, -ds.xml or admin object deployments when > only one rar implements the connection definition or message listener. > Design: > 1) When a RAR is deployed/undeployed update the repository with information about the RAR including > cross references by > * ConnectionDefinition > * MessageListener > * AdminObject > 2) When an MDB is deployed without identifying the rar, use the repository to try to guess the RAR > 3) When a ConnectionFactory is deployed without identifying the rar, use the repository to try to guess the RAR > 4) When an AdminObject is deployed without identifying the rar, use the repository to try to guess the RAR > The algorithm to guess the RAR is > a) Is there only one RAR implementing the object > b) If there is more than one RAR, is there a specific RAR in the same top level deployment (EAR) > as the referencing deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1728) Statement.getConnection not working for remote client

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1728?page=all ] Jesper Pedersen updated JBAS-1728: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Statement.getConnection not working for remote client > ----------------------------------------------------- > > Key: JBAS-1728 > URL: http://jira.jboss.com/jira/browse/JBAS-1728 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Jesper Pedersen > > the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService is not handling Statement.getConnection. It returns the real thing instead of a proxy --> Serialization exception!!. > This is related to JBAS-1678. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2923) Making JCA security more pluggable

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2923?page=all ] Jesper Pedersen updated JBAS-2923: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Making JCA security more pluggable > ---------------------------------- > > Key: JBAS-2923 > URL: http://jira.jboss.com/jira/browse/JBAS-2923 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > > We need a mechanism to make JCA security more pluggable. > This is to cater for use cases where some extra context needs to be used. > The connection manager only understands a subject. > The connection factory (e.g. DataSource) only understands the CRI (method parameters). > The pooling uses both without needing to understand what they are in detail. > This change would provide a "wrapper" connection manager that can do things > more associated to context, e.g. it could be connection factory specific, > i.e. it understands the CRI and can do things that the connection factory doesn't do > or it can do things based on information. > An example of other information would allowing a per deployment > security domain such that you have different pre-configured user/password per ejb. > With something like the following in META-INF/jboss-[web].xml > <jboss> > <enterprise-beans> > <session> > <ejb-name>Whatever</ejb-name> > ... > <resource-ref> > <res-ref-name>jdbc/DataSource</res-ref-name> > <jndi-name>java:/MySQLDS</jndi-name> > <security-domain>FooBar</security-domain> > </resource-ref> > </session> > </enterprise-beans> > </jboss> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-274) Standalone version fails to work

by Ryszard Kozmik (JIRA)

Standalone version fails to work -------------------------------- Key: JBFORUMS-274 URL: http://jira.jboss.com/jira/browse/JBFORUMS-274 Project: JBoss Forums Issue Type: Bug Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC When trying to run it with newest Portal deployed in AS there are problems with transactions, identity and security. Probably only configuration and small fixes are needed to make it work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-885) Detect "in-the-same-VM" condition

by David Lloyd (JIRA)

Detect "in-the-same-VM" condition --------------------------------- Key: JBREM-885 URL: http://jira.jboss.com/jira/browse/JBREM-885 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Part of the session creation process should include asking the protocol if the proposed URI is in the same or a different VM. If same, use "local" protocol instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-893) Add notification callbacks for when contexts, services, and sessions are closed

by David Lloyd (JIRA)

Add notification callbacks for when contexts, services, and sessions are closed ------------------------------------------------------------------------------- Key: JBREM-893 URL: http://jira.jboss.com/jira/browse/JBREM-893 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Fix For: Remoting 3 M2 There should be callbacks so that user code can detect when the various associations are broken. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-921) Create a notification mechanism for session creation

by David Lloyd (JIRA)

Create a notification mechanism for session creation ---------------------------------------------------- Key: JBREM-921 URL: http://jira.jboss.com/jira/browse/JBREM-921 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Add a method on Endpoint that registers a notifier that is called when a Session is established. Can be used for automatic service discovery for example. A means to unregister the notifier is also needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-916) Add context/service notification to request listeners

by David Lloyd (JIRA)

Add context/service notification to request listeners ----------------------------------------------------- Key: JBREM-916 URL: http://jira.jboss.com/jira/browse/JBREM-916 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0-M2 Request listeners should be notified when they are created, and when contexts and services are connected to/disconnected from them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008