July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1184) Resteasy-jaxrs module is missing log4j dependency

by Stuart Douglas (JIRA)

Resteasy-jaxrs module is missing log4j dependency ------------------------------------------------- Key: AS7-1184 URL: https://issues.jboss.org/browse/AS7-1184 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3119) Timestamp and Duration no longer work with complex expressions

by Mark Proctor (JIRA)

Timestamp and Duration no longer work with complex expressions -------------------------------------------------------------- Key: JBRULES-3119 URL: https://issues.jboss.org/browse/JBRULES-3119 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor They needed to be updated to use the MVEL reader method, so they can work on things beyond direct accessors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1183) Class-Path entries in ear/lib that point outside the deployment create module dependencies

by Stuart Douglas (JIRA)

Class-Path entries in ear/lib that point outside the deployment create module dependencies ------------------------------------------------------------------------------------------ Key: AS7-1183 URL: https://issues.jboss.org/browse/AS7-1183 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.0.Final This means that a third party jar can prevent a deployment from completing, and is not consistent with other Class-Path handling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-933) Commands to create and remove datasources

by Alexey Loubyansky (JIRA)

Commands to create and remove datasources ----------------------------------------- Key: AS7-933 URL: https://issues.jboss.org/browse/AS7-933 Project: Application Server 7 Issue Type: Sub-task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 Commands to create and delete datasources. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1883) Server side failover may cause ClientConsumer.waitForOnMessageToComplete() to hang

by Yong Hao Gao (JIRA)

Server side failover may cause ClientConsumer.waitForOnMessageToComplete() to hang ---------------------------------------------------------------------------------- Key: JBMESSAGING-1883 URL: https://issues.jboss.org/browse/JBMESSAGING-1883 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.8.SP1, 1.4.0.SP3.CP13 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2 When server side failover happens, the failover node will get "node left" notification from jgroups as well as "connection broken" notification from remoting on the connections through which message suckers are created. The listeners of the two notifications are executed concurrently and both try to close related resources. The "node left" listener performs failover for the dead node, where it closes all message suckers (underneath the ClientConsumers). The "connection broken" listener will close the related connection/session/consumer. If 1. in failover the ClientConsumer.close() is called but before waitForOnMessageToComplete() is called, 2. the session is being closed by the 'connection broken' listener. 3. when the waitForOnMessageToComplete() is called, it puts a 'Closer' task to executor and wait for it. However at that time the executor has been closed already in step 2. So the 'Closer' task will never get executed and it will wait forever. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1882) Missing jbossweb.jar in JBM test suite

by Miroslav Novak (JIRA)

Missing jbossweb.jar in JBM test suite -------------------------------------- Key: JBMESSAGING-1882 URL: https://issues.jboss.org/browse/JBMESSAGING-1882 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.8.SP1 Reporter: Miroslav Novak Fix For: 1.4.8.SP2 Hi Howard, when I've started clustering tests target then all of them failed because jbossweb.jar is missing. Could you modify our ant scripts to download it and put to classpath when for "tests" target, please. Thank you, Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
11
0 / 0

[JBoss JIRA] Created: (AS7-1176) Update to Arquillian OSGi 1.0.0.CR2 or later

by Thomas Diesler (JIRA)

Update to Arquillian OSGi 1.0.0.CR2 or later -------------------------------------------- Key: AS7-1176 URL: https://issues.jboss.org/browse/AS7-1176 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1151) Error while registering Oracle JDBC Diagnosability MBean

by Nicklas Karlsson (JIRA)

Error while registering Oracle JDBC Diagnosability MBean -------------------------------------------------------- Key: AS7-1151 URL: https://issues.jboss.org/browse/AS7-1151 Project: Application Server 7 Issue Type: Bug Components: JMX Affects Versions: 7.0.0.CR1 Reporter: Nicklas Karlsson Deploying the Oracle 11.1 driver jdbc-driver-11.1.0.6.0.jar through the admin console gives a 10:42:15,938 SEVERE [oracle.jdbc] (MSC service thread 1-7) Error while registering Oracle JDBC Diagnosability MBean.: java.lang.NullPointerException at oracle.jdbc.driver.OracleDriver.registerMBeans(OracleDriver.java:301) at oracle.jdbc.driver.OracleDriver$1.run(OracleDriver.java:213) at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_23] at oracle.jdbc.driver.OracleDriver.<clinit>(OracleDriver.java:209) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_23] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_23] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_23] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_23] at org.jboss.as.connector.deployers.processors.DriverProcessor.deploy(DriverProcessor.java:66) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] the driver looks registered/enabled, though, this is just an error from the diagnose bean -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3114) regression: set test operator "in" broken

by Wolfgang Laun (JIRA)

regression: set test operator "in" broken ------------------------------------------ Key: JBRULES-3114 URL: https://issues.jboss.org/browse/JBRULES-3114 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Blocker Fix For: FUTURE This simple DRL runs into a NPE rule a when then insert( Integer.class ); end rule xxx when $t: Class( $name: name not in ( "java.lang.Integer", "Bar", "Blech" ) ) then System.out.println( "odd name: " + $t.getName() ); end Caused by: java.lang.NullPointerException at org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:104) at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:291) If the "not" is removed, another strange error is thrown, claiming that 'name' cannot be accessed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-687) Add proxy for jfrog plugin releases repo

by Paul Gier (JIRA)

Add proxy for jfrog plugin releases repo ---------------------------------------- Key: JBBUILD-687 URL: https://issues.jboss.org/browse/JBBUILD-687 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Reporter: Paul Gier Assignee: Paul Gier Fix For: Build Support 2011 Hardy and Sanne requested to add a proxy repo for the jfrog plugin releases repository. This repository contains org.jfrog.maven.annomojo:maven-plugin-tools-anno http://repo.jfrog.org/artifactory/plugins-releases-local -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011