July 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJPA-26) Implement the clarified rules for resource discovery

by Hardy Ferentschik (JIRA)

Implement the clarified rules for resource discovery ---------------------------------------------------- Key: JBJPA-26 URL: https://jira.jboss.org/jira/browse/JBJPA-26 Project: JBoss JPA Issue Type: Task Reporter: Hardy Ferentschik Assignee: Carlo de Wolf The JPA 2 specs clarifies the usage of the <jar-file> element of persistence.xml. See section 8.2.1.6 of the spec. Section 8.2.1.6.3 gives a hole range of examples for different ear file configurations. I am opening this issue as a replacement for http://opensource.atlassian.com/projects/hibernate/browse/HHH-4666, since it is really the responsibility of the container to parse the ear file and create the right PersistenceUnitInfo instance to be passed to Hibernate. Hibernate's Ejb3Configuration already makes use of the information passed via PersistenceUnitInfo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2385) A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution

by Geoffrey De Smet (JIRA)

A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution ----------------------------------------------------------------------------------------------------------- Key: JBRULES-2385 URL: https://jira.jboss.org/jira/browse/JBRULES-2385 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet try examination example with exam set 2: after initialization the score in the dialog is stale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-541) Thread pools in transport protocols not using daemon threads

by Paul Ferraro (JIRA)

Thread pools in transport protocols not using daemon threads ------------------------------------------------------------ Key: JGRP-541 URL: http://jira.jboss.com/jira/browse/JGRP-541 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Paul Ferraro Assigned To: Bela Ban Priority: Minor The ThreadFactory used by the ThreadPoolExecutors (for both regular and OOB messages) in org.jgroups.protocols.TP does not create daemon threads. During runtime the JVM will resist exiting unless the channel is explicitly shutdown. -- 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

14 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1744) Create an ivy resolver for maven uniquely versioned snapshots

by Carlo de Wolf (JIRA)

Create an ivy resolver for maven uniquely versioned snapshots ------------------------------------------------------------- Key: EJBTHREE-1744 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1744 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2464) Unexpected test failures on IBM JDK 6

by Lukáš Petrovický (JIRA)

Unexpected test failures on IBM JDK 6 ------------------------------------- Key: JBRULES-2464 URL: https://jira.jboss.org/jira/browse/JBRULES-2464 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-testing Reporter: Lukáš Petrovický Assignee: Mark Proctor See BRMS-287. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (JBRULES-2372) Task - User ReceivedTime whenever Claim operation happens

by vijpan (JIRA)

Task - User ReceivedTime whenever Claim operation happens --------------------------------------------------------- Key: JBRULES-2372 URL: https://jira.jboss.org/jira/browse/JBRULES-2372 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-process-task Affects Versions: 5.1.0.M1 Reporter: vijpan Assignee: Mark Proctor Hi, Is there a way possible where "Received Time" can be stored at Task level. This datetime value should get updated with the current timestamp whenever "Claim" operation happens on the Task. The use case is that most of the time if its a 1 potential owner of the task - the task goes through "created/ready/reserved" status whenever a new Task gets created, in this case creation time would be same as received time --- but whenever the task is assigned to group or multiple potential owner or even when it is in reserved status it can be forwarded/delegated to other user/group - then in that case whenever user receives as task or in WSHT tem claim operation happens can we store the timestamp at the task level. Currently at task level we have creation time/activation time/expiration time ---- may be activation time can be used but i guess its use is very specific as detailed in WSHT/BPEL4People spec. In real world scenario it becomes quite important that when the user actually claimed the task or was assigned the task. Vijay -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (JBASPECT-29) Aspects Security Unit Tests

by Anil Saldhana (JIRA)

Aspects Security Unit Tests --------------------------- Key: JBASPECT-29 URL: https://jira.jboss.org/jira/browse/JBASPECT-29 Project: JBoss Aspects Issue Type: Task Components: security Reporter: Anil Saldhana Assignee: Anil Saldhana Since aspects security has been given to me based on merit, I am jittery ever since we moved it out as an external project. The unit tests are in the AS test suite. There is a need to have some unit tests for aspects security such that a change happens in aspects security, other projects (ejb3, profile services etc) do not get affected, due to regression. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1500) Discrepancies between removing a bean in cache vs bean passivated

by Galder Zamarreno (JIRA)

Discrepancies between removing a bean in cache vs bean passivated ----------------------------------------------------------------- Key: EJBTHREE-1500 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1500 Project: EJB 3.0 Issue Type: Sub-task Affects Versions: AS 4.2.3.GA, AS 5.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno There's a discrepancy between removing a bean from the cache after a timeout when bean is in cache compared to when bean is passivated: Example, when bean is in cache and has to be removed, this is called: if (now - centry.lastUsed >= removalTimeout * 1000) { synchronized (centry) { it.remove(); } } Now, when bean is passivated, this is called: if (now - centry.lastUsed >= removalTimeout * 1000) { get(centry.getId(), false); remove(centry.getId()); } And remove() method calls: if(log.isTraceEnabled()) { log.trace("Removing context " + key); } StatefulBeanContext ctx = null; synchronized (cacheMap) { ctx = (StatefulBeanContext) cacheMap.get(key); } if(ctx == null) throw new NoSuchEJBException("Could not find Stateful bean: " + key); if (!ctx.isRemoved()) container.destroy(ctx); ++removeCount; if (ctx.getCanRemoveFromCache()) { synchronized (cacheMap) { cacheMap.remove(key); } } What this means is that when a bean in cache is removed: 1.- removeCount is not updated 2.- container.destroy(ctx); is not executed and hence the @Remove method is not executed either. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-855) java.lang.IllegalStateException: Could not flush the cluster and proceed with state retri eaval

by Clebert Suconic (JIRA)

java.lang.IllegalStateException: Could not flush the cluster and proceed with state retri eaval ------------------------------------------------------------------------------------------------ Key: JGRP-855 URL: https://jira.jboss.org/jira/browse/JGRP-855 Project: JGroups Issue Type: Bug Affects Versions: 2.6.5 Reporter: Clebert Suconic Assignee: Vladimir Blagojevic When getState is called right after the connect even with flush, eventually (intermitently) you will get this exception: SomeException: ... Caused by: java.lang.IllegalStateException: Could not flush the cluster and proceed with state retri eaval at org.jgroups.JChannel.getState(JChannel.java:1041) at org.jgroups.JChannel.getState(JChannel.java:973) at org.jgroups.JChannel.getState(JChannel.java:927) at org.jboss.messaging.core.impl.postoffice.GroupMember.start(GroupMember.java:152) ... Notice that this only started to happen only after this change: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/messaging/branches/Branch_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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (JBLOGGING-45) Support automatic log file compression in FileHandler (for compressing all files in real time) and PeriodicRotatingFileHandler (for compressing upon rotation)

by Aleksander Adamowski (JIRA)

Support automatic log file compression in FileHandler (for compressing all files in real time) and PeriodicRotatingFileHandler (for compressing upon rotation) -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBLOGGING-45 URL: https://jira.jboss.org/jira/browse/JBLOGGING-45 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Aleksander Adamowski Assignee: David Lloyd This is a follow up to JBAS-6917. It would be nice to have an automatic compression of log files similar to the one implemented in Log4j extras: http://logging.apache.org/log4j/companions/extras/apidocs/org/apache/log4... "TimeBasedRollingPolicy supports automatic file compression. This feature is enabled if the value of the FileNamePattern option ends with .gz or .zip." In JBoss Logging, I suppose this could be implemented on 2 levels: 1) In the FileHandler (http://anonsvn.jboss.org/repos/common/jboss-logmanager/trunk/src/main/jav...) so that, with proper configuration, each log file is compressed in real time, and it exists only in compressed form from the moment of its creation. 2) In the PeriodicRotatingFileHandler (http://anonsvn.jboss.org/repos/common/jboss-logmanager/trunk/src/main/jav...) so that with proper configuration, archival log files can be compressed the moment they are rotated (e.g. server.log.2010-05-06.gz is created instead of server.log.2010-05-06), but the current log file should be plain text. In PeriodicRotatingFileHandler, the implementation must take into account that compression of rotated log files may take considerable time and should be performed in the background - the handler should be able to process log records at any time, particularly during rotation, without losing any. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
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 July 2010