February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3626) EJB's that use constructor injection and do not implement Serializable cannot be serialized

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3626: ----------------------------------- Summary: EJB's that use constructor injection and do not implement Serializable cannot be serialized Key: AS7-3626 URL: https://issues.jboss.org/browse/AS7-3626 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.CR1b Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
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] (AS7-2624) Determine Version / Build

by Rich Sharples (Created) (JIRA)

Determine Version / Build -------------------------- Key: AS7-2624 URL: https://issues.jboss.org/browse/AS7-2624 Project: Application Server 7 Issue Type: Enhancement Components: Build System Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Paul Gier We need a very simple way to determine the version number of AS (and also determine if it's EAP). This shouldn't require starting the server and scanning the log file, or opening jar files and looking for manifest files. Ideally I would be able to get the version / build info. from the command line (scripted) or from a Java program. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2749) Various rules stop firing when adding more, totally unrelated rules to a knowledge base

by Ansgar Konermann (JIRA)

Various rules stop firing when adding more, totally unrelated rules to a knowledge base --------------------------------------------------------------------------------------- Key: JBRULES-2749 URL: https://jira.jboss.org/browse/JBRULES-2749 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert), drools-core (expert) Affects Versions: 5.1.1.FINAL Environment: Environment 1: Fedora Core 12 x86_64, Sun JVM 1.6.0_20 64-bit Server VM Environment 2: Windows XP Professional, Service Pack 3, 32 bit; Sun JVM 1.6.0_20 32-bit Server VM Reporter: Ansgar Konermann Assignee: Mark Proctor A certain rule suddenly stops firing when adding more and more rules to the knowledge base, which (not only?) on first sight have *nothing* to do with the rule in question. We created a few unit tests which show the faulty behaviour. What we observed so far: * when using declared functions plus declared data types, this error occurrs. * sometimes, one can work around this problem by renaming a package. We're not sure if this is a reliable workaround, i. e. works in all situations. * one can work around this problem by not using declared functions. We're not sure if this is a reliable workaround. Find attached a ZIPed git repository containing: * a Maven 2.1+ pom.xml suitable to trigger the unit tests via mvn test * Java source files for a TestNG-based unit test * example drools source files to illustrate the problem (used by the unit tests) Please have a look at java file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages.java. This should make quite clear what we're expecting of the drools library and where it fails to fulfil these expectations. -- 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

14 years, 2 months

5
16
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, 2 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3405) Evaluate benchmark results per average ranking, not per average score

by Lukáš Petrovický (JIRA)

Lukáš Petrovický created JBRULES-3405: ----------------------------------------- Summary: Evaluate benchmark results per average ranking, not per average score Key: JBRULES-3405 URL: https://issues.jboss.org/browse/JBRULES-3405 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.4.0.Beta2 Reporter: Lukáš Petrovický Assignee: Geoffrey De Smet Currently. when deciding which solver config is the winner in a particular benchmark, the one with the best average score is picked. I believe this to be the wrong approach. When averaging two numbers, one if which is significantly smaller than the other, the average isn't the best metric you could use. (10, 10, 10, 20 and 1000 give you 210 as the average - is that really the best metric available to describe the data set?) For this reason, I would like the winner-picking algorithm to work different: 1) For each input file in the benchmark, rank the solvers per their score. (Basically 1st to Nth place.) 2) Then make a median of all these "places" and the best-placed algorithm wins. This way, you don't compare the solver results themselves. You compare how the solvers did in relation to the other solvers - which is something I consider much more important. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
11
0 / 0

[JBoss JIRA] (AS7-3887) quickstarts using wrong jboss-as-maven plugin version

by shay Matasaro (JIRA)

shay Matasaro created AS7-3887: ---------------------------------- Summary: quickstarts using wrong jboss-as-maven plugin version Key: AS7-3887 URL: https://issues.jboss.org/browse/AS7-3887 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.0.Final Reporter: shay Matasaro Assignee: Paul Gier Priority: Minor quickstarts are using version 7.0 of jboss deploy plugin , should be 7.1.final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 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, 2 months

4
7
0 / 0

[JBoss JIRA] (JBRULES-3298) NPE in ExpireJobContextTimerOutputMarshaller.write

by Drools User (Created) (JIRA)

NPE in ExpireJobContextTimerOutputMarshaller.write -------------------------------------------------- Key: JBRULES-3298 URL: https://issues.jboss.org/browse/JBRULES-3298 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.3.0.Final Reporter: Drools User Assignee: Mark Proctor Priority: Blocker {code} Caused by: java.lang.NullPointerException at org.drools.reteoo.ObjectTypeNode$ExpireJobContextTimerOutputMarshaller.write(ObjectTypeNode.java:639) at org.drools.marshalling.impl.OutputMarshaller.writeTimers(OutputMarshaller.java:1105) at org.drools.marshalling.impl.OutputMarshaller.writeSession(OutputMarshaller.java:172) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:142) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:125) at org.drools.persistence.SessionMarshallingHelper.getSnapshot(SessionMarshallingHelper.java:72) at org.drools.persistence.info.SessionInfo.update(SessionInfo.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.ejb.event.BeanCallback.invoke(BeanCallback.java:23) at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:80) at org.hibernate.ejb.event.EntityCallbackHandler.preUpdate(EntityCallbackHandler.java:65) at org.hibernate.ejb.event.EJB3FlushEntityEventListener.invokeInterceptor(EJB3FlushEntityEventListener.java:41) at org.hibernate.event.def.DefaultFlushEntityEventListener.handleInterception(DefaultFlushEntityEventListener.java:330) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:270) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:151) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:219) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:99) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:49) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1028) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:366) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:137) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) ... 34 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3307) Event does not expire when temporal operators are used.

by Scott Embler (Created) (JIRA)

Event does not expire when temporal operators are used. ------------------------------------------------------- Key: JBRULES-3307 URL: https://issues.jboss.org/browse/JBRULES-3307 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Final Environment: OS: Windows XP Java: 1.6.0_29 Reporter: Scott Embler Assignee: Mark Proctor Expectations: When rules use temporal operators to relate two events in time, it is expected that those both events will be expired when the session clock advances far enough. In the unit tests I have provided you'll see that there are two event types A and B. Each rule tries to relate these two events using a different temporal operator. After the rules match, both A and B should be expired, and a String should be inserted into working memory to signal to the test that the rule worked. Observed behavior: When A and B are inserted into their respective entry points the rules do match, and the appropriate String is inserted into working memory. B is also retracted. However A remains in working memory forever, causing heap space exceptions if there are many A's to process. It can also be seen using JMX that the computed event expiration for B is 0, and for A is the maximum long value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

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 February 2012