November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-435) Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed

by Volker Augustin (JIRA)

Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed ---------------------------------------------------------------------------------------------------------- Key: JBRULES-435 URL: http://jira.jboss.com/jira/browse/JBRULES-435 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables, Drl Parser/Builder Reporter: Volker Augustin Assigned To: Mark Proctor When a condition column in a decision table contains values like 25000000, this is compiled using the SpreadsheetCompiler into 2.5E7 in the DRL. However, the DRL parser/compiler cannot cope with this notation and exists with a unexpected token "E7" error message. -- 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

19 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-434) Cannot enter more than one parameter in one column on German computers

by Volker Augustin (JIRA)

Cannot enter more than one parameter in one column on German computers ---------------------------------------------------------------------- Key: JBRULES-434 URL: http://jira.jboss.com/jira/browse/JBRULES-434 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Environment: Windows XP, standard GERMAN settings Reporter: Volker Augustin Assigned To: Mark Proctor Section 4.1.4.1 of the JBoss Rules documentation states: The "$para" place holder is used in templates to indicate where data form the cell will be interpolated. You can also use "$1" to the same effect. If the cell contains a comma seperated list of values, $1 and $2 etc. may be used to indicate which positional parameter from the list of values in the cell will be used. As the German decimal separator is ',' and not '.' as in the English locale, no list of this form can be entered on a German computer system if there are e.g. only two values and they happen to be integers. E.g. if you try to create the list containing the two values 10 and 20, according to the documentation you must enter '10,20'. This will be interpreted as 10.20 by a German computer and result in a single decimal value instead of a list of two integers. The separator ',' is hardcoded somewhere (in SnippedBuilder (?) I think). Maybe this can be made configurable. E.g. a "Configuration" section in the Excel spreadsheet would do. -- 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

19 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-520) Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary.

by Joel Lindheimer (JIRA)

Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary. ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-520 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-520 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows XP, JBossServer4.0.4GA, Oracle10G Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Create a simple receiver, but do not place it within a Transaction boundary; shut down the server; look up the tables and you will see all the messages are still in the Messages and MessageRef tables. ========================================= Observations using a debbuger reveal the following: ========================================= Looking over the org.jboss.resource.adapter.jms.JmsManagedConnection the setup method will always call createXAQueueSession() and create an XAQueconnection as transacted and Session.SESSION_TRANSACTED. That being the case, non-XA Queues have no message-deletion problems with the current version (RC4) because the API removes all messages that are "not transacted and (!ack==1). I am guessing that using XA is problematic because the persistence layer is expecting manipulation of the transacted XASession--which for some reason is not working in this version of Messaging. More specifically, I suspect that when MDBs are tested you are not seeing this problem because the container is doing needed magic to manage the XASession transacted state, and therefore everything works fine therein. And consequently, when operating as a non-MDB client, AKA a simple Receiver, there is something missing in the equation ergo the problems that I have been reporting regarding the ClickCommerce applications which use Receivers and not MDBs. Work-around: None; the strategy for my team is to NOT use an XAQueueConnection while waiting for a fix. -- 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

19 years, 2 months

5
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-584) Eliminate jgroups.jar "processing"

by Ovidiu Feodorov (JIRA)

Eliminate jgroups.jar "processing" ---------------------------------- Key: JBMESSAGING-584 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-584 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.CR1 During the release procedure, the current release script expands jgroups.jar and removes service deployment descriptos (gossip-service.xml multiplexer-service.xml). It has just been confirmed by the JGroups team that the presence of those deployment descriptors is not intentional, it's just an unwanted artifact of their release process. Get rid of "jgroups jar processing" as soon as we upgrade our dependency to a "clean" jgroups jar. -- 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

19 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-438) Allow ports used by JBossMessaging to be mapped using ServiceBindingManager

by Tim Fox (JIRA)

Allow ports used by JBossMessaging to be mapped using ServiceBindingManager --------------------------------------------------------------------------- Key: JBMESSAGING-438 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-438 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.GA -- 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

19 years, 3 months

4
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-620) Remove unneeded org/jboss/mx classes from jboss-messaging-client.jar

by Ovidiu Feodorov (JIRA)

Remove unneeded org/jboss/mx classes from jboss-messaging-client.jar -------------------------------------------------------------------- Key: JBMESSAGING-620 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-620 Project: JBoss Messaging Issue Type: Task Components: Build System Affects Versions: 1.0.1.GA, 1.2.0.Alpha1 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 -- 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

19 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-558) Possible performance degradation relative to JBossMQ when using contested queues and selectors

by Ovidiu Feodorov (JIRA)

Possible performance degradation relative to JBossMQ when using contested queues and selectors ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-558 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-558 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.0.1.CR5, 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Problem described on the forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91326 -- 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

19 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-548) Remote tests occasionaly fail with "Cannot find generator for serverid:server.0"

by Ovidiu Feodorov (JIRA)

Remote tests occasionaly fail with "Cannot find generator for serverid:server.0" -------------------------------------------------------------------------------- Key: JBMESSAGING-548 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-548 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.0.1.CR5 Apparently MessageIdGeneratorFactory gets inadvertently cleaned, or there are more check ins than check outs for a specific MessageIdGenerator instance. -- 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

19 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-605) Open connections should not prevent jvm from exiting

by Tim Fox (JIRA)

Open connections should not prevent jvm from exiting ---------------------------------------------------- Key: JBMESSAGING-605 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-605 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 If the client process attempts to exit without explicitly closing connections then it can cause the process to hang. We should explicity close any open connections on jvm exit (install a shutdown hook to handle this) and log warnings (to system.err) so the programming error can be corrected. -- 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

19 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-619) Update Messaging jboss.com landing page

by Ovidiu Feodorov (JIRA)

Update Messaging jboss.com landing page --------------------------------------- Key: JBMESSAGING-619 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-619 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA http://www.jboss.com/products/messaging -- 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

19 years, 3 months

3
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 November 2006