January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2741) Unify the Marshalling Strategies for Process Variables and Session's Snapshots

by Mauricio Salatino (JIRA)

Unify the Marshalling Strategies for Process Variables and Session's Snapshots ------------------------------------------------------------------------------ Key: JBRULES-2741 URL: https://jira.jboss.org/browse/JBRULES-2741 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino The main goal of this feature is to provide an unified mechanism to marshall objects that are used to persist the status of the knowledge session. Two different strategies were used by the sessionInfo and ProcessInstanceInfo marshallers with the Variable Persistence Strategies. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7166) org.jboss.Shutdown to use org.jboss.naming.NamingProviderURLWriter persist file

by Juergen none (JIRA)

org.jboss.Shutdown to use org.jboss.naming.NamingProviderURLWriter persist file ------------------------------------------------------------------------------- Key: JBAS-7166 URL: https://jira.jboss.org/jira/browse/JBAS-7166 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-5.1.0.GA Environment: 15:59:02,389 INFO [ServerInfo] Java version: 1.6.0_14,Sun Microsystems Inc. 15:59:02,390 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_14-b08) 15:59:02,390 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 14.0-b16,Sun Microsystems Inc. 15:59:02,390 INFO [ServerInfo] OS-System: Linux 2.6.9-22.0.1.ELsmp,amd64 Reporter: Juergen none Assignee: Scott M Stark i would like to see org.jboss.Shutdown in bin/shutdown.jar make use of persist file created by org.jboss.naming.NamingProviderURLWriter containing jnp service url i probably can do something like "java -jar shutdown.jar -s `cat jnp-service.url` -S" but it depends on OS -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2750) Drools Grid Impl2 GridServiceDescription format parsers

by Mauricio Salatino (JIRA)

Drools Grid Impl2 GridServiceDescription format parsers -------------------------------------------------------- Key: JBRULES-2750 URL: https://jira.jboss.org/browse/JBRULES-2750 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mauricio Salatino Define the structure of the GridServiceDescription id. Based on the id we should build the parsers to populate the GridServiceDescription fields. A possible structure could be: scheduler@localhost:8000/socket, whitepages@192.168.0.1:8001/http, executionode@salaboy.laptop:8002/rest -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2446) Drools Services API

by Mauricio Salatino (JIRA)

Drools Services API ------------------- Key: JBRULES-2446 URL: https://jira.jboss.org/jira/browse/JBRULES-2446 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: FUTURE Reporter: Mauricio Salatino Assignee: Mauricio Salatino Refactoring of the VSM APIs to the new Semantic for Local/Remote/Grid Environments. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2615) Drools Grid Services remove unnessary dependencies

by Mauricio Salatino (JIRA)

Drools Grid Services remove unnessary dependencies -------------------------------------------------- Key: JBRULES-2615 URL: https://jira.jboss.org/browse/JBRULES-2615 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mark Proctor remove not needed dependencies, clean up the code, refactor the tests and add comments. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2605) Obsolete and unused POI version in classpath

by Vincent Legendre (JIRA)

Obsolete and unused POI version in classpath -------------------------------------------- Key: JBRULES-2605 URL: https://jira.jboss.org/browse/JBRULES-2605 Project: Drools Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.0.1.FINAL Reporter: Vincent Legendre Assignee: Mark Proctor Hi all, drools-api project declare an obsolete version of POI (3.0.2) as a classpath entry, which is not used. I suggest removing it (from maven configuration I guess). I found this problem when trying to add an excel export in Guvnor, using the lastest POI version. Thanks -- 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

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2762) ArrayIndexOutOfBoundsException in org.drools.core.util.AbstractHashTable

by Lubos Pechac (JIRA)

ArrayIndexOutOfBoundsException in org.drools.core.util.AbstractHashTable ------------------------------------------------------------------------ Key: JBRULES-2762 URL: https://jira.jboss.org/browse/JBRULES-2762 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.1.1.FINAL Environment: JBoss 5.1 on JDK6, 64bit Windows Server Reporter: Lubos Pechac Assignee: Mark Proctor Exception occures at: org.drools.core.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:317) in Drools 5.1.1 when calling insert() on just created StatefulKnowledgeSession. I found similar issues reported for LeftTupleIndexHashTable, it had to do with initializing row to -1 instead of 0 or something similar. I see that fixed in Left/RightTupleIndexHashTable but it seems to me like it is still present in AbstractHashTable. The bug occures randomly (inserting the same data), usualy under load. The index is either -1 or too high. I create multiple sessions in threads from one KnowledgeBase, sessions are not shared. The sessions are relatively short living, about 100ms max. Stack trace I got is: java.lang.ArrayIndexOutOfBoundsException: 16 at org.drools.core.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:317) at org.drools.reteoo.EntryPointNode.updateSink(EntryPointNode.java:323) at org.drools.reteoo.ObjectTypeNode.attach(ObjectTypeNode.java:303) at org.drools.reteoo.builder.PatternBuilder.attachObjectTypeNode(PatternBuilder.java:257) at org.drools.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:92) at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:68) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:981) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:917) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:251) -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8587) Error during shutdown

by Stefano Maestri (JIRA)

Error during shutdown --------------------- Key: JBAS-8587 URL: https://jira.jboss.org/browse/JBAS-8587 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Stefano Maestri Assignee: Brian Stansberry I'm getting this stack trace time to time during server shutdown (both domain and standalone) [Server:server-two] 21:30:17,768 WARN [org.jboss.messaging] (pool-1-thread-4) failed to destroy jms topic: testTopic: javax.naming.NameNotFoundException: Name 'topic' not found in context '' [Server:server-two] at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:66) [Server:server-two] at org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355) [Server:server-two] at org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:311) [Server:server-two] at org.jboss.as.naming.InMemoryNamingStore.unbind(InMemoryNamingStore.java:138) [Server:server-two] at org.jboss.as.naming.NamingContext.unbind(NamingContext.java:257) [Server:server-two] at org.jboss.as.naming.NamingContext.unbind(NamingContext.java:266) [Server:server-two] at javax.naming.InitialContext.unbind(InitialContext.java:433) [:1.6.0_18] [Server:server-two] at org.hornetq.jms.server.impl.JMSServerManagerImpl.removeFromJNDI(JMSServerManagerImpl.java:1630) [Server:server-two] at org.hornetq.jms.server.impl.JMSServerManagerImpl.destroyTopic(JMSServerManagerImpl.java:644) [Server:server-two] at org.jboss.as.messaging.jms.JMSTopicService.stop(JMSTopicService.java:64) [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:983) [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_18] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_18] [Server:server-two] at java.lang.Thread.run(Thread.java:636) [:1.6.0_18] [Server:server-two] [Server:server-three] 21:30:17,774 INFO [org.jboss.as.deployment] (pool-1-thread-4) Undeployed jdbc-local.rar [Server:server-three] 21:30:17,774 INFO [org.jboss.as.deployment] (pool-1-thread-4) Undeployed jdbc-xa.rar [Server:server-one] 21:30:17,766 WARN [org.jboss.messaging] (pool-1-thread-4) failed to destroy jms topic: testTopic: javax.naming.NameNotFoundException: Name 'topic' not found in context '' [Server:server-one] at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:66) [Server:server-one] at org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355) [Server:server-one] at org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:311) [Server:server-one] at org.jboss.as.naming.InMemoryNamingStore.unbind(InMemoryNamingStore.java:138) [Server:server-one] at org.jboss.as.naming.NamingContext.unbind(NamingContext.java:257) [Server:server-one] at org.jboss.as.naming.NamingContext.unbind(NamingContext.java:266) [Server:server-one] at javax.naming.InitialContext.unbind(InitialContext.java:433) [:1.6.0_18] [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.removeFromJNDI(JMSServerManagerImpl.java:1630) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.destroyTopic(JMSServerManagerImpl.java:644) [Server:server-one] at org.jboss.as.messaging.jms.JMSTopicService.stop(JMSTopicService.java:64) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:983) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_18] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_18] [Server:server-one] at java.lang.Thread.run(Thread.java:636) [:1.6.0_18] [Server:server-one] -- 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

15 years, 2 months

6
8
0 / 0

[JBoss JIRA] Created: (JGRP-814) Probe dump to show deadlocks and use JDK6 APIs is available

by Galder Zamarreno (JIRA)

Probe dump to show deadlocks and use JDK6 APIs is available ----------------------------------------------------------- Key: JGRP-814 URL: https://jira.jboss.org/jira/browse/JGRP-814 Project: JGroups Issue Type: Feature Request Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 2.7 Probe dump does not currently show locked monitors or synchronisers that can be retrieved using JDK6 API and does not show detected deadlocks 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2771) NPE in update call from wrong WM Entry Point

by Wolfgang Laun (JIRA)

NPE in update call from wrong WM Entry Point -------------------------------------------- Key: JBRULES-2771 URL: https://jira.jboss.org/browse/JBRULES-2771 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M1 This sequence of statements disagrees with the documentation: WorkingMemoryEntryPoint entryPoint = kSession.getWorkingMemoryEntryPoint( "epn" ); FactHandle fh = entryPoint.insert( fact ); kSession.update( fh, fact ); // should be done using entryPoint.update But this causes (in 5.1.1) a NPE Exception in thread "main" java.lang.NullPointerException at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1379) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1338) at org.drools.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:266) at event.Main.execute(Main.java:153) at event.Main.main(Main.java:164) This is the line: if ( this.maintainTms ) { status = ((InternalFactHandle) factHandle).getEqualityKey().getStatus(); } and similar code can be found in trunk, so I suppose this is still possible. -- 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

15 years, 2 months

2
2
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 January 2011