June 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-199) Default namespace for jboss-ra

by Jesper Pedersen (JIRA)

Default namespace for jboss-ra ------------------------------ Key: JBMETA-199 URL: https://jira.jboss.org/jira/browse/JBMETA-199 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Jeff Zhang If the user doesn't specify a namespace in the jboss-ra.xml - like <jboss-ra> and there isn't a DTD definition either we should map that namespace to JBossRAMetaData. That would allow the RA deployer to continue to parse the file and log a WARN to the user. -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBMETA-198) Default namespace for connector

by Jesper Pedersen (JIRA)

Default namespace for connector ------------------------------- Key: JBMETA-198 URL: https://jira.jboss.org/jira/browse/JBMETA-198 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Jeff Zhang If the user doesn't specify a namespace in the ra.xml - like <connector> and there isn't a DTD definition either we should map that namespace to JCA15MetaData. That would allow the RA deployer to continue to parse the file and log a WARN to the user. -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (GPD-335) add proper licence text

by Tom Baeyens (JIRA)

add proper licence text ----------------------- Key: GPD-335 URL: https://jira.jboss.org/jira/browse/GPD-335 Project: JBoss jBPM GPD Issue Type: Task Reporter: Tom Baeyens Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.0.0.CR1 -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2105) For literal constraints on BitDecimal and BigIntegers, avoid coercing the literal every constraint check

by Edson Tirelli (JIRA)

For literal constraints on BitDecimal and BigIntegers, avoid coercing the literal every constraint check -------------------------------------------------------------------------------------------------------- Key: JBRULES-2105 URL: https://jira.jboss.org/jira/browse/JBRULES-2105 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.0.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 Cache it instead. -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2103) Knowledge*/ChangeSet APIs to be extended to support BRL, DSLR and DroolsCompilerAntTask compiled rules

by Graham Gear (JIRA)

Knowledge*/ChangeSet APIs to be extended to support BRL, DSLR and DroolsCompilerAntTask compiled rules ------------------------------------------------------------------------------------------------------ Key: JBRULES-2103 URL: https://jira.jboss.org/jira/browse/JBRULES-2103 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-compiler, drools-core Affects Versions: 5.0.1.FINAL Reporter: Graham Gear Assignee: Mark Proctor I would like to see the new Knowledge*/ChangeSet API's to be extended to support all rule types, including BRL, DSLR and DroolsCompilerAntTask compiled rules Although the primary compilation mechanism for BRL and DSLR types of rules will likely be Guvnor, for completeness and an aid for developer driven rules, debug and automation I would like to see the API filled out. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1374) DLQ override depends on the queues definition order.

by Tim Fox (JIRA)

DLQ override depends on the queues definition order. ---------------------------------------------------- Key: JBMESSAGING-1374 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1374 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP3_CP03 -- 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

17 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBSER-115) Exception while deserialization of java.math.BigInteger in Sun JRE 1.6.0_14 if serialized using a previous version e.g. JRE 1.6.0_13.

by Mattias Neuling (JIRA)

Exception while deserialization of java.math.BigInteger in Sun JRE 1.6.0_14 if serialized using a previous version e.g. JRE 1.6.0_13. -------------------------------------------------------------------------------------------------------------------------------------- Key: JBSER-115 URL: https://jira.jboss.org/jira/browse/JBSER-115 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Environment: Deserializing client: - OS: Windows XP SP3 (32Bit) - JRE 1.6.0_14 Serializing Server: - OS: Linux Suse Enterprise (64 Bit) - JDK 1.6.0_13 (64 Bit) Reporter: Mattias Neuling Assignee: Clebert Suconic Failure while deserilizing java.math.BigInteger in java.math.BigDecimal on client side: Stacktrace: java.io.IOException: Current classpath has lesser fields on java.math.BigInteger than its original version at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:98) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643) at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353) at org.jboss.serial.persister.ObjectInputStreamProxy.defaultReadObject(ObjectInputStreamProxy.java:78) at java.math.BigDecimal.readObject(Unknown Source) ... 42 more In JDK 1.6.0_14 java.math.BigInteger has one field more than in previous versions. Serialization without JBoss Serialization is no problem since it implements the methods #readObject() and #writeObject(). -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1843) All SFSB Cache implementations return -1 for getAvailableCount

by Andrew Lee Rubinger (JIRA)

All SFSB Cache implementations return -1 for getAvailableCount -------------------------------------------------------------- Key: EJBTHREE-1843 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1843 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.1.7, EAP 5 SFSB Metrics getAvailableCount, powered by inquiring upon the caches, always return -1. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1558) @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) ignored on MDB onMessage

by Justin Bertram (JIRA)

@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) ignored on MDB onMessage -------------------------------------------------------------------------------------- Key: EJBTHREE-1558 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1558 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Justin Bertram Even when putting: @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) on the onMessage method of an MDB a transaction is still started. This can be verified by using a simple MDB that sleeps for longer than the transaction timeout (300 seconds by default). For example: import javax.ejb.ActivationConfigProperty; import javax.ejb.MessageDriven; import javax.ejb.TransactionAttribute; import javax.ejb.TransactionAttributeType; import javax.jms.Message; import javax.jms.MessageListener; import org.apache.log4j.Logger; @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/A"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "3") }) public class ExampleEJB3MDB implements MessageListener { private static final Logger logger = Logger.getLogger(ExampleEJB3MDB.class); @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) public void onMessage(Message m) { logger.info("message received, waiting for 10 mins..."); try { Thread.sleep(600000); // 10 mins } catch (InterruptedException e) { } logger.info("finished waiting"); } } When a message is sent to "queue/A" and the MDB picks it up it prints "message received, waiting for 10 mins..." in the log. After 5 minutes (300 seconds) the message appears in the log again because the transaction has timed-out and the message has been redelivered. I believe the problem lies in org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory in the isDeliveryTransacted method. Here is that method [1]: public boolean isDeliveryTransacted(Method method) throws NoSuchMethodException { TransactionManagementType mtype = TxUtil.getTransactionManagementType(container); if (mtype == javax.ejb.TransactionManagementType.BEAN) return false; TransactionAttribute attr = (TransactionAttribute)container.resolveAnnotation(method, TransactionAttribute.class); if (attr == null) { attr =(TransactionAttribute)container.resolveAnnotation(TransactionAttribute.class); } TransactionAttributeType type = TransactionAttributeType.REQUIRED; if (attr != null) type = attr.value(); return type == javax.ejb.TransactionAttributeType.REQUIRED; } It seems there should be an explicit check for TransactionAttributeType.NOT_SUPPORTED. If the MDB uses @TransactionManagement(TransactionManagementType.BEAN) then the redelivery doesn't occur (since the code explicitly checks this attribute and returns false if it is present). -- 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

17 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2102) Expert evaluate() does *not* throw NPE

by Travis Scheponik (JIRA)

Expert evaluate() does *not* throw NPE -------------------------------------- Key: JBRULES-2102 URL: https://jira.jboss.org/jira/browse/JBRULES-2102 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.FINAL Environment: java 1.6.0_11, Ubuntu Reporter: Travis Scheponik Assignee: Mark Proctor http://pastebin.com/m1dffefc4 <-- offending method within Expert example ObjectA( a:member1, b:member2, a > b) <-- this crashes if b is null example: ObjectA(a:member1, b:member2, eval(a > b )) <-- afaik, this *should* crash if a or b is null This was requested to be posted by: etirelli and bjornelo -- 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

17 years, 1 month

3
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 June 2009