July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3075) window:length windows retaining events when they shouldnt

by Radai Rosenblatt (JIRA)

window:length windows retaining events when they shouldnt --------------------------------------------------------- Key: JBRULES-3075 URL: https://issues.jboss.org/browse/JBRULES-3075 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.2.0.CR1 Environment: win64, jdk 6u24 Reporter: Radai Rosenblatt Assignee: Mark Proctor Attachments: drools length window bug.zip using the following DRL: package contrived.example import contrived.example.EventWithTimestamp declare EventWithTimestamp @role(event) @duration( duration ) @timestamp( timestamp ) end rule "no event in window" when not EventWithTimestamp (someProp=="whatever") over window:length(3) from entry-point "Event Stream" then System.err.println("retract"); end if we start with an initial matching (someProp=="whatever") event and a fire a long sequence of non-matching events: {"something else", "something else" ... "something else"} the rule should fire sometime into the long chain of "something else" events (it should fire after the 3rd such event). in practice the rule never fires. worse, it also retains all the events in memory ehrn it should only keep the last 3. to reproduce the issue, simply build the attached maven project (mvn clean install) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (AS7-1293) JNDI Binding service

by Quanlin Chen (JIRA)

JNDI Binding service -------------------- Key: AS7-1293 URL: https://issues.jboss.org/browse/AS7-1293 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Final Reporter: Quanlin Chen Priority: Critical I was just been told that so far it's impossible to bind arbitrary objects into JNDI in JBOSS 7, so would you be able to create a common binding service so that it could be working the same way as using JMX in previous AS versions? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

7
7
0 / 0

[JBoss JIRA] Created: (JGRP-1325) TopologyUUID.isSameSite() returns false if both siteIds are null

by Dan Berindei (JIRA)

TopologyUUID.isSameSite() returns false if both siteIds are null ---------------------------------------------------------------- Key: JGRP-1325 URL: https://issues.jboss.org/browse/JGRP-1325 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Dan Berindei Assignee: Bela Ban Priority: Minor When the siteId of both TopologyUUIDs is null, isSameSite() should return true but it returns false. Same with rackId/isSameRack() and machineId/isSameMachine(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9106) In domain mode, prevent end-user access to and visibility of most configuration write operations

by Brian Stansberry (JIRA)

In domain mode, prevent end-user access to and visibility of most configuration write operations ------------------------------------------------------------------------------------------------ Key: JBAS-9106 URL: https://issues.jboss.org/browse/JBAS-9106 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 In domain mode most (almost certainly all) server level operations that update the persistent configuration should not be directly accessible by the end user and should not appear in the results of the read-resource-description, read-operation-names or read-operation-description operations if executed against a server-level resource. They can only be invoked by the host controller that is responsible for the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JBEE-83) Refactor POM to extend directly from jboss-parent

by Paul Gier (JIRA)

Refactor POM to extend directly from jboss-parent ------------------------------------------------- Key: JBEE-83 URL: https://issues.jboss.org/browse/JBEE-83 Project: JBoss JavaEE APIs Issue Type: Enhancement Components: jboss-ejb-api Reporter: Paul Gier Assignee: Shelly McGowan Fix For: 3.1.0.CR1-ejb-api I think the jboss-specs parent is no longer necessary. The main jboss-parent can take care of the common information used by each of the specs jars. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (AS7-1026) add-jms-queue --help does not work inside a batch

by Brian Stansberry (JIRA)

add-jms-queue --help does not work inside a batch ------------------------------------------------- Key: AS7-1026 URL: https://issues.jboss.org/browse/AS7-1026 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.0.Beta3 Reporter: Brian Stansberry [standalone@localhost:9999 subsystem=messaging] batch [standalone@localhost:9999 subsystem=messaging #] add- add-data-source add-jms-cf add-jms-queue add-jms-topic add-xa-data-source [standalone@localhost:9999 subsystem=messaging #] add-jms- add-jms-cf add-jms-queue add-jms-topic [standalone@localhost:9999 subsystem=messaging #] add-jms-queue --help Failed to add to batch: Required argument '--name' is missing. Discard the batch (or don't start one at all) and it works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1291) UserTransaction not exposed in JDNI

by Juergen Zimmermann (JIRA)

UserTransaction not exposed in JDNI ----------------------------------- Key: AS7-1291 URL: https://issues.jboss.org/browse/AS7-1291 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey In JBoss 6 UserTransaction was exposed in JNDI named as java:comp/UserTransaction. Thus an Arquillian test method could be encapsulated in one single transaction: * lookup() the UserTransaction * begin() inside @Before * commit() inside @After Unfortunately, JBoss 7 doesn't have a JNDI entry for UserTransaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

8
11
0 / 0

[JBoss JIRA] Created: (JBAS-9072) High level commands for common standalone mode tasks

by Brian Stansberry (JIRA)

High level commands for common standalone mode tasks ---------------------------------------------------- Key: JBAS-9072 URL: https://issues.jboss.org/browse/JBAS-9072 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 Identify and implement the high level commands we want to support for a standalone mode server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-1034) ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL

by Scott Marlow (JIRA)

ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL --------------------------------------------------------------------------------------------- Key: AS7-1034 URL: https://issues.jboss.org/browse/AS7-1034 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Beta3 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
3
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 2011