November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2785) Documentation fixes w.r.t. events

by Wolfgang Laun (JIRA)

Documentation fixes w.r.t. events ---------------------------------- Key: JBRULES-2785 URL: https://jira.jboss.org/browse/JBRULES-2785 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.M1 Correct the documentation: (1) Explicit expiry time by @expires() in declare has precedence over implicit, dervide from rules. (Critical, because right now is documented the other way round.) (2) Document that declare without any fields must refer to an existing, imported type. (3) Document the semantics of timer, and that timer() can only be used in a STREAM session. Also, document that "int:" (as in "timer(int: 0 1m)") is optional. (4) Make it clear that window:length( N ) is also satisfied if there are less than N events. -- 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

12 years, 8 months

6
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2681) Drools: Unable to load session snapshot

by Gustavo Tenrreiro (JIRA)

Drools: Unable to load session snapshot --------------------------------------- Key: JBRULES-2681 URL: https://jira.jboss.org/browse/JBRULES-2681 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Environment: Windows Server, SQL Server 2005, Tomcat 5.5, Hibernate, Bitronix Reporter: Gustavo Tenrreiro Assignee: Mark Proctor After an event is processed the session fails to load using JPA persistence. I ve attached a test case. It uses a Drools flow file, and a drl file. Both very simple.. The flow file has a "Start" then an action that prints a message to the console, then "End" The Drl has one rule that processes an event: import com.kgcontrols.services.company.standardsRequests.workflow.events.VoteCreatedEvent declare VoteCreatedEvent @role(event) end rule "testEvents" when VoteCreatedEvent() from entry-point "VoteCreatedStream" then System.out.println("--------------------------- YEAH the event got here"); end I can see the "YEAH the event go here" on the console so I know the rule fired. But after that, if I try to load the session from the database I get: 1. INFO 2010-09-02 08:28:56 [ERROR] com.kgcontrols.services.company.standardsRequ 2. ests.workflow.TimerRunner java.lang.reflect.InvocationTargetException 3. java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException 4. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 5. Service(KnowledgeStoreServiceImpl.java:106) 6. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.loadStatefu 7. lKnowledgeSession(KnowledgeStoreServiceImpl.java:74) 8. at org.drools.persistence.jpa.JPAKnowledgeService.loadStatefulKnowledgeS 9. ession(JPAKnowledgeService.java:118) 10. at com.kgcontrols.services.company.standardsRequests.workflow.JPAKnowle 11. dgeSessionLookup.loadSession(JPAKnowledgeSessionLookup.java:103) 12. at com.kgcontrols.services.company.standardsRequests.workflow.TimerRunn 13. er.run(TimerRunner.java:39) 14. at java.lang.Thread.run(Thread.java:619) 15. Caused by: java.lang.reflect.InvocationTargetException 16. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 17. 18. at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct 19. orAccessorImpl.java:39) 20. at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC 21. onstructorAccessorImpl.java:27) 22. at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 23. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 24. Service(KnowledgeStoreServiceImpl.java:91) 25. ... 5 more 26. Caused by: java.lang.RuntimeException: Unable to load session snapshot 27. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 28. ot(JPASessionMarshallingHelper.java:96) 29. at org.drools.persistence.session.SingleSessionCommandService.initKsessi 30. on(SingleSessionCommandService.java:196) 31. at org.drools.persistence.session.SingleSessionCommandService.<init>(Sin 32. gleSessionCommandService.java:159) 33. ... 10 more 34. Caused by: java.lang.NullPointerException 35. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:135) 36. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:121) 37. at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarsha 38. ller.java:461) 39. at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMars 40. haller.java:351) 41. at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshall 42. er.java:205) 43. at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarsh 44. aller.java:91) 45. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 46. ot(JPASessionMarshallingHelper.java:91) 47. ... 12 more -- 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

12 years, 8 months

7
18
0 / 0

[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

12 years, 8 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

12 years, 8 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

12 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-8595) Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always.

by Nishant Parikh (JIRA)

Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always. ------------------------------------------------------------------------------------------------------- Key: JBAS-8595 URL: https://jira.jboss.org/browse/JBAS-8595 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.0.1.GA Environment: Windows/Linux, JDK1.5, RAM 2GB, Processor 3GHz, Intel Core Due CPU Reporter: Nishant Parikh Assignee: Darran Lofthouse Priority: Critical When we fire concurrent request more than 200, let's say 200+x (With maxThreads specified 1000 from jmx/web console), Everything works fine but after few seconds x NUMBER OF THREADS GETS BUSY and they never get free. On server log we are getting below ArrayIndexOutOfBoundsException. Exception in thread "http-192.168.1.166-8080-4" java.lang.ArrayIndexOutOfBoundsException: 200 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-16" java.lang.ArrayIndexOutOfBoundsException: 201 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-91" java.lang.ArrayIndexOutOfBoundsException: 202 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-98" java.lang.ArrayIndexOutOfBoundsException: 203 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) 17:08:49,515 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 203 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,530 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 202 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,546 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 201 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,548 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 200 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) -- 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

12 years, 8 months

4
5
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

12 years, 8 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

12 years, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-8366) Failure to deploy a war file with JBoss 5.0

by Sasha Matison (JIRA)

Failure to deploy a war file with JBoss 5.0 ------------------------------------------- Key: JBAS-8366 URL: https://jira.jboss.org/browse/JBAS-8366 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.GA Environment: Windows 2003 R2 SP2, JBoss AS 5.0, JDK 1.6_16 Reporter: Sasha Matison Assignee: Scott M Stark Priority: Blocker While deploying our war file with JBoss AS 5.0 we are getting the following error: org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser We are shipping the product with a version of Xerces-j 2.9.1. Removing this version from the product is not an option. Note that the war file used to work with JBoss 4.x. This issue is blocking JBoss 5.0 testing. Please advise on the solution. -- 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

12 years, 8 months

4
5
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

12 years, 8 months

5
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010