December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JGRP-181) Concurrent stack

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-181?page=all ] Bela Ban updated JGRP-181: -------------------------- Summary: Concurrent stack (was: Threadless stack) > Concurrent stack > ---------------- > > Key: JGRP-181 > URL: http://jira.jboss.com/jira/browse/JGRP-181 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.9.1, 2.2.8, 2.2.9 > Reporter: Bela Ban > Assigned To: Bela Ban > Priority: Critical > Fix For: 2.5 > > > Investigate setting all down_thread and up_thread properties to false by default > Performance tests have shown that in almost all cases this is always faster, so why not make it the default. This is e.g. already the case in fc-fast-minimalthreads.xml -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-361) Look at Event.START/STOP events, possibly replace them with direct start()/stop() method calls

by Bela Ban (JIRA)

Look at Event.START/STOP events, possibly replace them with direct start()/stop() method calls ---------------------------------------------------------------------------------------------- Key: JGRP-361 URL: http://jira.jboss.com/jira/browse/JGRP-361 Project: JGroups Issue Type: Sub-task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBPM-454) conditional transitions

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-454?page=all ] Tom Baeyens closed JBPM-454. ---------------------------- Fix Version/s: jBPM 3.2 alpha 3 (was: jBPM 3.2) Resolution: Done For in depth comments on backwards compatibility: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=98013 > conditional transitions > ----------------------- > > Key: JBPM-454 > URL: http://jira.jboss.com/jira/browse/JBPM-454 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 alpha 3 > > > add a mechanism to calculate the available transitions at runtime for 1) a token in a node 2) a task instance in a node -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-809) Conditional transitions

by Gavin King (JIRA)

Conditional transitions ----------------------- Key: JBPM-809 URL: http://jira.jboss.com/jira/browse/JBPM-809 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens It seems to be useful to be able to "filter" the transitions that are available: <transition name="delete" restrict="#{user.admin}"/> -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-822) StackOverFlow when enabling log level TRACE to org.jboss.ejb3.mdb.inflow

by Juha Moisio (JIRA)

StackOverFlow when enabling log level TRACE to org.jboss.ejb3.mdb.inflow ------------------------------------------------------------------------- Key: EJBTHREE-822 URL: http://jira.jboss.com/jira/browse/EJBTHREE-822 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: RHEL 3, Sun JVM 1.5.0_08-b03 Reporter: Juha Moisio Priority: Minor When you enable TRACE logging level for package org.jboss.ejb3.mdb.inflow, you get java.StackOverFlow. XAResourceWrapper CTOR 2006-12-27 10:10:24,811 TRACE [org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory] createEndpoint org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory$ 2006-12-27 10:10:24,838 ERROR [Sonic Resource Adapter for JCA] EXCEPTION: Failure in SonicActivation: java.lang.StackOverflowError java.lang.StackOverflowError at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:109) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) at $Proxy290.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-789) add finder methods for current tasks and current nodes

by Tom Baeyens (JIRA)

add finder methods for current tasks and current nodes ------------------------------------------------------ Key: JBPM-789 URL: http://jira.jboss.com/jira/browse/JBPM-789 Project: JBoss jBPM Issue Type: Feature Request Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.1.4 as per gavin's request | List<TaskInstance> currentTasks = | processInstance.getCurrentTasks(); | List<Node> currentNodes = processInstance.getCurrentNodes(); -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-816) added description to node, transition, process and task

by Tom Baeyens (JIRA)

added description to node, transition, process and task ------------------------------------------------------- Key: JBPM-816 URL: http://jira.jboss.com/jira/browse/JBPM-816 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 alpha 3 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-814) depending on the isolation level of your JDBC connection join might not reactivate parent

by Tom Baeyens (JIRA)

depending on the isolation level of your JDBC connection join might not reactivate parent ----------------------------------------------------------------------------------------- Key: JBPM-814 URL: http://jira.jboss.com/jira/browse/JBPM-814 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 alpha 3 see the join node. Requires upgrade to hibernate 3.2 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-815) upgrade to hibernate 3.2.1.GA

by Tom Baeyens (JIRA)

upgrade to hibernate 3.2.1.GA ----------------------------- Key: JBPM-815 URL: http://jira.jboss.com/jira/browse/JBPM-815 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 alpha 3 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-821) extend EJB3DeployerMBean attributes regarding JarsIgnoredForScanning

by Avishay Halperen (JIRA)

extend EJB3DeployerMBean attributes regarding JarsIgnoredForScanning -------------------------------------------------------------------- Key: EJBTHREE-821 URL: http://jira.jboss.com/jira/browse/EJBTHREE-821 Project: EJB 3.0 Issue Type: Feature Request Environment: JBoss 4.0.4 + EJB3 support Reporter: Avishay Halperen instead of just declaring an attribute: JarsIgnoredForScanning, allow extending this this metadata by setting either a regexp based jarsForScan attribute or use a better include/exclude attribute. the problem starts that instead of just declaring the one or two jars in the application that realy needs the EJB3 deployer service, We need to specify all our application jars (more then a hundred) just to improve the performance of the Jboss's load time, and to maintain this list cause it is very dynamic (jars are added and removed). -- 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, 7 months

1
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