August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2599) Timers Do Not Get Triggered when using JPA Knowledge Session

by Anatoly Polinsky (JIRA)

Timers Do Not Get Triggered when using JPA Knowledge Session ------------------------------------------------------------ Key: JBRULES-2599 URL: https://jira.jboss.org/browse/JBRULES-2599 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.CR1 Environment: Windows / Ubuntu; Oracle / H2 / MySQL, it does not seem environment specific Reporter: Anatoly Polinsky Assignee: Mark Proctor When using persistence ( obtaining a session from JPAKnowledgeFactoryService ), Timers do not get triggered. The instances are still there, but when the process suspends and / or executing [ e.g. workitemhandler has a while(true) loop: just a test scenario to have a process up ], but the timer will NOT trigger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
8
0 / 0

[JBoss JIRA] Updated: (JBAS-8290) Implement solid SessionObjectReference

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8290?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated JBAS-8290: ---------------------------- Summary: Implement solid SessionObjectReference (was: Implement solid isRemoved() method for SessionObjectReference) Assignee: Marius Bogoevici Priority: Critical (was: Major) Description: JBossSessionObjectReference is a bit hacky right now: 1) Needs a proper implementation of isRemoved which interrogates the EJB container to determine the state of the reference 2) Needs a Remove implementation that can cope with no-interface-view beans 3) Needs to lookup the actual reference for getBusinessObject() not just cast the local proxy. Note that we may request remote EJBs through this mechanism! was:Currently we don't actually detect if the user or EJB container removes the EJB, not WB > Implement solid SessionObjectReference > -------------------------------------- > > Key: JBAS-8290 > URL: https://jira.jboss.org/browse/JBAS-8290 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Priority: Critical > Fix For: 6.0.0.CR1 > > > JBossSessionObjectReference is a bit hacky right now: > 1) Needs a proper implementation of isRemoved which interrogates the EJB container to determine the state of the reference > 2) Needs a Remove implementation that can cope with no-interface-view beans > 3) Needs to lookup the actual reference for getBusinessObject() not just cast the local proxy. Note that we may request remote EJBs through this mechanism! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-8342) EJB descriptor implementation must include support for remote business interfaces

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8342?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8342: ----------------------------------- Summary: EJB descriptor implementation must include support for remote business interfaces (was: The bean types of a session bean must not include remote business interfaces) Component/s: Weld/CDI > EJB descriptor implementation must include support for remote business interfaces > --------------------------------------------------------------------------------- > > Key: JBAS-8342 > URL: https://jira.jboss.org/browse/JBAS-8342 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M4 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8342) The bean types of a session bean must not include remote business interfaces

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8342?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici moved WELD-613 to JBAS-8342: --------------------------------------------- Project: JBoss Application Server (was: Weld) Key: JBAS-8342 (was: WELD-613) Issue Type: Feature Request (was: Bug) Affects Version/s: 6.0.0.M4 (was: 1.0.1.Final) Security: Public Fix Version/s: 6.0.0.CR1 (was: 1.1.0.BETA1) > The bean types of a session bean must not include remote business interfaces > ---------------------------------------------------------------------------- > > Key: JBAS-8342 > URL: https://jira.jboss.org/browse/JBAS-8342 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.M4 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2666) Use KnowledgeStoreService inside Drools Grid

by Mauricio Salatino (JIRA)

Use KnowledgeStoreService inside Drools Grid -------------------------------------------- Key: JBRULES-2666 URL: https://jira.jboss.org/browse/JBRULES-2666 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Mauricio Salatino Assignee: Mauricio Salatino Replace the old implmentation with the new interface KnowledgeStoreService -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2149) More informative error messages

by Ondrej Žižka (JIRA)

More informative error messages ------------------------------- Key: EJBTHREE-2149 URL: https://jira.jboss.org/browse/EJBTHREE-2149 Project: EJB 3.0 Issue Type: Feature Request Environment: EAP 5.1.0 Reporter: Ondrej Žižka Attachments: EJB3-errormsg.txt Let's say I am a maintainer of an EJB app. I deploy an EJB to JBoss EAP, and get hunderds of lines of stacktrace, from which I only need a single line: No container configured with name 'Custom Message Driven Bean'' and the second most important information, WHERE that dependency comes from, is completely missing. So i get 50 % of information I need packaged in useless repeatedly printed stacktraces (but that's other story). Could the Ejb3AnnotationHandler put an information to the Exception's message about where did it dig the MDB reference from? And, generally - could this be applied to all error messages? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2665) Update to latest BPMN2 XSD

by Kris Verlaenen (JIRA)

Update to latest BPMN2 XSD -------------------------- Key: JBRULES-2665 URL: https://jira.jboss.org/browse/JBRULES-2665 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (flow), drools-core (flow) Affects Versions: 5.1.0.FINAL Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.1.FINAL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (LOGMGR-23) Logger.finalize clears level; this action belongs on LoggerNode

by David Lloyd (JIRA)

Logger.finalize clears level; this action belongs on LoggerNode --------------------------------------------------------------- Key: LOGMGR-23 URL: https://jira.jboss.org/browse/LOGMGR-23 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR5 Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.CR6 When a logger disappears, it clears out its level and that of its children, even though the logger node may still be present. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2147) blocked threads in org.jboss.ejb3.pool.ThreadlocalPool

by Carlo de Wolf (JIRA)

blocked threads in org.jboss.ejb3.pool.ThreadlocalPool ------------------------------------------------------ Key: EJBTHREE-2147 URL: https://jira.jboss.org/browse/EJBTHREE-2147 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-0.1.3 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: bom-eap5-0.1.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2146) Performance bottleneck in org.jboss.ejb3.statistics.InvocationStatistics

by Carlo de Wolf (JIRA)

Performance bottleneck in org.jboss.ejb3.statistics.InvocationStatistics ------------------------------------------------------------------------ Key: EJBTHREE-2146 URL: https://jira.jboss.org/browse/EJBTHREE-2146 Project: EJB 3.0 Issue Type: Bug Affects Versions: bom-eap5-0.1.3 Reporter: Carlo de Wolf Priority: Critical Fix For: bom-eap5-0.1.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
5
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 August 2010