August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-315) No control over the process definition when using components "taskInstanceListForType" & "pooledTaskInstanceList"

by Aravind Kumar (JIRA)

No control over the process definition when using components "taskInstanceListForType" & "pooledTaskInstanceList" ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-315 URL: http://jira.jboss.com/jira/browse/JBSEAM-315 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.0.1 Reporter: Aravind Kumar There may be multiple Business Processes running in the same application. with CreateProcess annotation we can instantiate process instance for a particular process definition. "taskInstanceListForType" & "pooledTaskInstanceList" components relies on TaskMgmtSession.java of JBPM to pull out the taskinstances that the current user is authorized to see. But theres no control over the precess definition. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-339) Event scope container (WebRequestContext) doesn't clean the beans after destroy

by German de la Cruz (JIRA)

Event scope container (WebRequestContext) doesn't clean the beans after destroy ------------------------------------------------------------------------------- Key: JBSEAM-339 URL: http://jira.jboss.com/jira/browse/JBSEAM-339 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.0.1, 1.1 Environment: Jboss Seam nightly build 20060821, myfaces 1.1.4-SNAPSHOT from cvs. Tomahawk and tomahawk-snapshot 1.1.5-SNAPSHOT from cvs facelets 1.1.11 Reporter: German de la Cruz Priority: Critical Please, after the flushAndDestroyContext call, clean the destroyed bean from the event scope session (and therefore from the http request object. It produces a bug with tomahawk-sandbox and event scoped session bean. The destroyed beans are anyway invalid references and must be destroyed. I've made a very simple patch, but anyway, it can't solve the problem since some modifications in tomahawk sandbox is 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

19 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-337) @Startup component with @Create is broken

by Shane Bryzak (JIRA)

@Startup component with @Create is broken ----------------------------------------- Key: JBSEAM-337 URL: http://jira.jboss.com/jira/browse/JBSEAM-337 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.0.1 Reporter: Shane Bryzak Assigned To: Gavin King Fix For: 1.1 Attachments: testcase.zip A component annotated with @Startup having a method annotated with @Create throws the following exception during deployment: 09:01:45,140 INFO [Lifecycle] starting up: applicationContext 09:01:45,140 INFO [Lifecycle] starting up: startupBean 09:01:45,156 ERROR [STDERR] java.lang.IllegalStateException: No active event context 09:01:45,156 ERROR [STDERR] at org.jboss.seam.core.Manager.instance(Manager.java:320) 09:01:45,156 ERROR [STDERR] at org.jboss.seam.interceptors.ConversationInterceptor.isMissingJoin(ConversationInterceptor.java:100) 09:01:45,156 ERROR [STDERR] at org.jboss.seam.interceptors.ConversationInterceptor.endOrBeginLongRunningConversation(ConversationInterceptor.java:43) 09:01:45,156 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-529) Install TCK5 locally and fix all errors that prevent Messaging from passing

by Ovidiu Feodorov (JIRA)

Install TCK5 locally and fix all errors that prevent Messaging from passing --------------------------------------------------------------------------- Key: JBMESSAGING-529 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-529 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3592) Add system property jboss.mcast.ip.ttl

by Brian Stansberry (JIRA)

Add system property jboss.mcast.ip.ttl -------------------------------------- Key: JBAS-3592 URL: http://jira.jboss.com/jira/browse/JBAS-3592 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.GA Add a system property to all JGroups multicast configs in the AS to control ip_ttl. Update testsuite build.xml to set this to 1 so running the testsuite doesn't send traffic off the box. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3587) Add a startup switch to configure TCPPING.initial_hosts

by Brian Stansberry (JIRA)

Add a startup switch to configure TCPPING.initial_hosts ------------------------------------------------------- Key: JBAS-3587 URL: http://jira.jboss.com/jira/browse/JBAS-3587 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1 As discussed on conf call, we want to make it easy to switch from a UDP-based JGroups config to a TCP-based one. With the multiplexer this can be as simple as switching the multiplexer stack name in the various config files. One thing that makes the switch a pain is the need to configure initial_hosts in TCPPING. We should make a startup switch and system property to allow this to be externalized from the xml file, e.g: <TCPPING initial_hosts={${jboss.tcp.initial.hosts:localhost[7800]} ... Should discuss on the forum whether we want a startup switch or just a property set via -D. My preference is a switch. -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-3507) Add ability to toggle the MultiplexerStack between UDP- and TCP-based versions

by Brian Stansberry (JIRA)

Add ability to toggle the MultiplexerStack between UDP- and TCP-based versions ------------------------------------------------------------------------------ Key: JBAS-3507 URL: http://jira.jboss.com/jira/browse/JBAS-3507 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta Need Branch_4_0-style "tests-clustering-all-stacks" tests, but simpler to implement due to ability to change the MultiplexerStack attribute. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-695) PojoCache transaction rollback has limitation under certain transaction context

by Ben Wang (JIRA)

PojoCache transaction rollback has limitation under certain transaction context ------------------------------------------------------------------------------- Key: JBCACHE-695 URL: http://jira.jboss.com/jira/browse/JBCACHE-695 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: POJOCache Currently PojoCache supports transaction rollback. For instance, cache.attach(id, pojo); is transactional even if there is no user transaction. However, with user transaction, tx.begin(); cache.attach(id, pojo); pojo.setAge(20); tx.rollback(); the replication is rollbacked but the in-memory copy is not, e.g., pojo.getAge() == 20. There is a workaround if you are using transaction by yourself: // Just make sure this one succeeds first. tx.begin(); cache.attach(id, pojo); tx.commit(); // All subsquent field update will be transactional then. tx.begin(); pojo.setAge(20); tx.rollback(); -- 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, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-757) Problem updating cyclic reference

by J?rn Eyrich (JIRA)

Problem updating cyclic reference --------------------------------- Key: JBCACHE-757 URL: http://jira.jboss.com/jira/browse/JBCACHE-757 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0.SP1 Reporter: J?rn Eyrich Assigned To: Manik Surtani import org.jboss.cache.aop.PojoCache; import org.jboss.cache.aop.annotation.PojoCacheable; @PojoCacheable public class Main { public Main reference; public static void main(String[] args) throws Exception { PojoCache cache = new PojoCache(); cache.startService(); Main main = new Main(); Main main2 = new Main(); main.reference = main2; main2.reference = main; cache.putObject("/main",main); main2.reference = main; // <-- System.out.println("Done..."); } } results in: Exception in thread "main" java.lang.RuntimeException: PojoCache.putObject(): fqn: /main/reference/reference at org.jboss.cache.aop.PojoCache.putObject(PojoCache.java:478) at org.jboss.cache.aop.CacheInterceptor.invoke(CacheInterceptor.java:115) at org.jboss.aop.joinpoint.FieldWriteInvocation.invokeNext(FieldWriteInvocation.java:51) at Main.reference_w_$aop(Main.java) at Main.main(Main.java:21) Caused by: java.lang.IllegalStateException: AOPInstance.incrementRefCount(): source fqn: /main/reference/reference is already present. at org.jboss.cache.aop.AOPInstance.incrementRefCount(AOPInstance.java:92) at org.jboss.cache.aop.InternalDelegate.incrementRefCount(InternalDelegate.java:98) at org.jboss.cache.aop.ObjectGraphHandler.incrementRefCount(ObjectGraphHandler.java:212) at org.jboss.cache.aop.ObjectGraphHandler.setupRefCounting(ObjectGraphHandler.java:192) at org.jboss.cache.aop.ObjectGraphHandler.objectGraphPut(ObjectGraphHandler.java:88) at org.jboss.cache.aop.TreeCacheAopDelegate._putObject(TreeCacheAopDelegate.java:201) at org.jboss.cache.aop.PojoCache._putObject(PojoCache.java:731) at org.jboss.cache.aop.PojoCache.putObject(PojoCache.java:462) ... 4 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-354) 16x16 and 32x32 icon for JBossIDE

by Marshall Culpepper (JIRA)

16x16 and 32x32 icon for JBossIDE --------------------------------- Key: JBIDE-354 URL: http://jira.jboss.com/jira/browse/JBIDE-354 Project: JBoss IDE Issue Type: Feature Request Reporter: Marshall Culpepper Assigned To: James Cobb We need a smaller 16x16 and 32x32 icon representation of our beautiful new logo =) -- 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, 10 months

3
6
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 2006