December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-692) Create extended RunAs roles for additional mapped principals

by Bill Burke (JIRA)

Create extended RunAs roles for additional mapped principals ------------------------------------------------------------ Key: EJBTHREE-692 URL: http://jira.jboss.com/jira/browse/EJBTHREE-692 Project: EJB 3.0 Issue Type: Task Reporter: Bill Burke Fix For: EJB 3.0 RC10 - FD See the TODO in RunAsSecurityInterceptorFactory -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-702) Quartz Timer Service in E-EJB3 hangs process, exception on shutdown

by Bill Burke (JIRA)

Quartz Timer Service in E-EJB3 hangs process, exception on shutdown ------------------------------------------------------------------- Key: EJBTHREE-702 URL: http://jira.jboss.com/jira/browse/EJBTHREE-702 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Bill Burke Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC10 - FD to test this out: build embedded.dist go run one of the tutorials. You will see that the applicatoin will never exit. I'm guessing this is becuase a Quartz thread is a non-daemon thread and holding up the exit of the process. Also there is a NullPointerException on shutdown. I have disabled the Quartz Timer Service in embedded-jboss-beans.xml for now. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-780) dlqmaxresent parameter is not taken from main jboss config

by Ramil Israfilov (JIRA)

dlqmaxresent parameter is not taken from main jboss config ---------------------------------------------------------- Key: EJBTHREE-780 URL: http://jira.jboss.com/jira/browse/EJBTHREE-780 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Ramil Israfilov Fix For: EJB 3.0 RC10 - FD During tests recovered JMS message goes immediatelly to DQL queue, in standardjboss.xml file dlqmaxresent parameter is set to 10, but it is not used. If I put this property in MDB as annotation it works, but I don't want to put it there as it is a parameter which can be set on jboss config. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-779) MDB doesn't rebind after JBOSS MQ recover

by Ramil Israfilov (JIRA)

MDB doesn't rebind after JBOSS MQ recover ------------------------------------------ Key: EJBTHREE-779 URL: http://jira.jboss.com/jira/browse/EJBTHREE-779 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - FD Environment: Solarisx86, JDK1.5_06 Reporter: Ramil Israfilov Priority: Critical Fix For: EJB 3.0 RC10 - FD I have an MDB which is described using annotations: @Depends("jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider") @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/certione/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "dLQMaxResent", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }, messageListenerInterface=MessageListener.class) public class EJBExecutorMDB implements MessageListener { ... } I deploy it in clustered environment with HAJNDI and clustered JBOSS MQ. So far so good. Then cluster node on which JBOSS MQ is running crashed MDB is not rebind. >From log file I see that JBOSS MQ successfully restarted on second node. And all permamnet queue destinations (defined in config files) are available, but destinations which are defined in annotations don't exist. And in log file I see that server constantly tries bind MDB, but got alway the same error: javax.naming.NameNotFoundException: queue/certione/ExecutorQueue at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy249.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.util.naming.Util.lookup(Util.java:215) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:399) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:306) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:250) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.onException(AbstractDLQHandler.java:94) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348) at java.lang.Thread.run(Thread.java:595) -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-395) drools-repository API

by Michael Neale (JIRA)

drools-repository API --------------------- Key: JBRULES-395 URL: http://jira.jboss.com/jira/browse/JBRULES-395 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the parent task for the drools-repository module and API. This covers the back end storage, using JCR, and the API over it (not the front end). All specific tasks should be sub tasks of this. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-585) syntax sugar for binding to a field on a bound fact

by Michael Neale (JIRA)

syntax sugar for binding to a field on a bound fact --------------------------------------------------- Key: JBRULES-585 URL: http://jira.jboss.com/jira/browse/JBRULES-585 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Mark Proctor Fix For: 3.1-m3 For example: c: Customer($id: id) p: Person(customerId == $id.....) could become: c: Customer() p: Person(customerId == c.id) much more OO looking. Can use an extractor (if possible). -- 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, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-456) Nested field accessor - contributions from Patrick Niemeyer

by Michael Neale (JIRA)

Nested field accessor - contributions from Patrick Niemeyer ----------------------------------------------------------- Key: JBRULES-456 URL: http://jira.jboss.com/jira/browse/JBRULES-456 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Mark Proctor Priority: Critical Fix For: 3.1-m3 Attachments: jboss-nested-asm.jar This is from Patrick Niemeyer <pat(a)pat.net>. Provides Foo(a.b.c etc). We are hoping for some more enhancements that can also do map/array access like javascript. -- 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, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1079) Add testing of error handling on the Consumer (in particular, retries after errors)

by Chris Laprun (JIRA)

Add testing of error handling on the Consumer (in particular, retries after errors) ----------------------------------------------------------------------------------- Key: JBPORTAL-1079 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1079 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBAOP-287) Tighten integration with MC 2.0 once it is released

by Kabir Khan (JIRA)

Tighten integration with MC 2.0 once it is released --------------------------------------------------- Key: JBAOP-287 URL: http://jira.jboss.com/jira/browse/JBAOP-287 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 -- 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, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (JBPM-783) isPropagated calculation for event is not correct

by Olga Ivanova (JIRA)

isPropagated calculation for event is not correct ------------------------------------------------- Key: JBPM-783 URL: http://jira.jboss.com/jira/browse/JBPM-783 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.2 alpha 1 Reporter: Olga Ivanova Assigned To: Tom Baeyens As it is stated in comment inside org.jbpm.graph.def.GraphElement.fireAndPropagateEvent method // calculate if the event was fired on this element or if it was a propagated event boolean isPropagated = (this.equals(executionContext.getEventSource())); I believe code does not correspond to the intent and should look following: boolean isPropagated = !(this.equals(executionContext.getEventSource())); i.e if event source is same element that this, event is not propagated, if they are different - event is propagated. -- 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, 1 month

2
1
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 December 2006