February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-325) Args Annotation

by Flavia Rainone (JIRA)

Args Annotation --------------- Key: JBAOP-325 URL: http://jira.jboss.com/jira/browse/JBAOP-325 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone -- 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

19 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAOP-356) Ability to attach a .aop deployment to a particular scoped classloader

by Kabir Khan (JIRA)

Ability to attach a .aop deployment to a particular scoped classloader ---------------------------------------------------------------------- Key: JBAOP-356 URL: http://jira.jboss.com/jira/browse/JBAOP-356 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.4.GA, 2.0.0.alpha3 e.g. if an .ear file has been scoped with: <jboss-app> <loader-repository> dot.com:loader=ear1test </loader-repository> </jboss-app> It should be possible to deploy at a later time a .aop file like: <aop> <attach-scoped-loader>dot.com:loader=ear1test</attach-scoped-loader>  </aop> The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear. -- 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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-746) Ensure MDB integration tests exist

by Tim Fox (JIRA)

Ensure MDB integration tests exist ---------------------------------- Key: JBMESSAGING-746 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-746 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Critical Fix For: 1.2.0.CR1 We need to make sure that a full set of AS MDB integration tests exist both using the old JMSContainerInvoker invoker-proxy-binding and then new JCA1.5 message inflow invoker-proxy-binding. Right now, MDB integration test coverage seems extremely poor. We need to be testing all the different ack modes, queues, topic, durable subs, selectors, all the different tx modes (Required, NotSupported etc), throwing exceptions, RuntimeExceptions etc etc -- 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

19 years, 2 months

5
7
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-141) Stateful session PostConstruct missing transaction, security contexts

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-141?page=all ] Carlo de Wolf resolved EJBTHREE-141. ------------------------------------ Resolution: Rejected EJB3 13.6.5. > Stateful session PostConstruct missing transaction, security contexts > --------------------------------------------------------------------- > > Key: EJBTHREE-141 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-141 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Environment: jboss-head > Reporter: Jeff Schnitzer > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > While PostConstruct for stateless beans does not run in a transaction or security context, stateful beans are different. From section 5.1.4.1 "Semantics of the Life Cycle Callback Methods for Stateful Session Beans" of the ejb3-edr2 spec: > "The PostConstruct method is invoked in the transaction context and security contexts of the first business method on the bean." -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-203) Interrupt reaper thread

by Mark Little (JIRA)

Interrupt reaper thread ----------------------- Key: JBTM-203 URL: http://jira.jboss.com/jira/browse/JBTM-203 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 It is possible for the reaper thread to become blocked when telling a transaction to rollback. We should have another thread that interrupts the reaper thread if it has been blocked for more than a configurable amount of time on the same transaction. In this case, the reaper could either put the transaction back on the list and try again later, or just mark it as rollback_only. My preference would actually be to have a separate list of blocked transactions that are marked as rollback_only and have the reaper try to roll them back again later. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1433) Message Inflow targetting MBeans/POJOs

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1433?page=all ] Weston Price reassigned JBAS-1433: ---------------------------------- Assignee: Weston Price > Message Inflow targetting MBeans/POJOs > -------------------------------------- > > Key: JBAS-1433 > URL: http://jira.jboss.com/jira/browse/JBAS-1433 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48674 > The JCA message inflow could target MBeans or POJOs rather than EJBs. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-785) Create long running invocation test

by Tim Fox (JIRA)

Create long running invocation test ----------------------------------- Key: JBMESSAGING-785 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-785 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Fix For: 1.2.0.CR1 Add a test that makes a JMS invocation (e.g. sendTransaction) and artifically takes a very long time to execute (this can be done by sleeping in PoisonInterceptor), maybe 2 minutes or more. (Must be much higher than any ping or lease settings). Verify that the invocation completes successfully without any timeout of connection or connection cleanup kicking in. -- 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

19 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-888) Fix DefaultRouter

by Tim Fox (JIRA)

Fix DefaultRouter ----------------- Key: JBMESSAGING-888 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-888 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.GA DefaultRouter is currently broken due to changes made to favour the failed over queue. Need to make sure the other queues get messages routed to them too. -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-735) Consider disabling pinging while failover is happening

by Tim Fox (JIRA)

Consider disabling pinging while failover is happening ------------------------------------------------------ Key: JBMESSAGING-735 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-735 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.CR1 When the call to createConnectionDelagate is in progress and it is waiting for server side failover to complete, then this can block lease pings for the duration of the failover. If failover takes longer than the lease period, then the server will close the connection. Need to add tests for this and consider diabling leasing for the duration of the failover call. -- 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

19 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-892) IIOP transaction service doesn't work with Arjuna

by Carlo de Wolf (JIRA)

IIOP transaction service doesn't work with Arjuna ------------------------------------------------- Key: EJBTHREE-892 URL: http://jira.jboss.com/jira/browse/EJBTHREE-892 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC10 - FD Environment: AS 4.2 default Reporter: Carlo de Wolf You'll get nasy IllegalStateExceptions is you do try. java.lang.IllegalStateException at org.jboss.tm.iiop.client.IIOPClientUserTransaction.rollback(IIOPClientUserTransaction.java:369) at org.jboss.ejb3.test.iiop.unit.IiopRemoteUnitTestCase.testTxPropegation(IiopRemoteUnitTestCase.java:260) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: org.omg.CosTransactions.NoTransaction: IDL:omg.org/CosTransactions/NoTransaction:1.0 at org.jboss.tm.iiop.client.IIOPClientUserTransaction.getThreadLocalTerminator(IIOPClientUserTransaction.java:164) at org.jboss.tm.iiop.client.IIOPClientUserTransaction.rollback(IIOPClientUserTransaction.java:364) ... 22 more -- 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

19 years, 2 months

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-jira February 2007