July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5261) tests altering jboss.dist directory

by Aleksandar Kostadinov (JIRA)

Aleksandar Kostadinov created AS7-5261: ------------------------------------------ Summary: tests altering jboss.dist directory Key: AS7-5261 URL: https://issues.jboss.org/browse/AS7-5261 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.2.Final (EAP) Reporter: Aleksandar Kostadinov Assignee: Ondrej Zizka when running test suite with jboss.dost changed to a directory without write access two tests: org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase.testAddRemoveCapabilities org.jboss.as.test.integration.extension.remove.ExtensionRemoveTestCase.testAddAndRemoveExtension With errors: File could not be created: /usr/share/jbossas/bundles/org/jboss/test/testcap1343334290201/main/testcapabilitybundle.jar Could not create /usr/share/jbossas/modules/extensionremovemodule/main That means they are trying to alter the jboss distribution under testing which seems inconsistent with what the other tests do. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3585) Drools Planner should support JSR-331 too (for those that prefer math equations as constraints over object-orientated constraints)

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3585: ----------------------------------------- Summary: Drools Planner should support JSR-331 too (for those that prefer math equations as constraints over object-orientated constraints) Key: JBRULES-3585 URL: https://issues.jboss.org/browse/JBRULES-3585 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Priority: Minor JSR-331 is a constraint programming standardization effort and we could create a drools-planner-jsr331 to bridge that API. - Such a module shouldn't pose to many technical difficulties (it's basically translating the math equations in primitive based rules) - Such a module is a lot of effort none-the less. There need to be enough users actually wanting to use JSR 331. Personally, I doubt many users would prefer math equations to write their constraints (vote on this issue to prove me wrong). Here's an example why: In Drools scoreDRL you say something like this: {code} // Dependency constraints: each process of a service must have at least one process of it's depended services running in it's neighborhood rule "serviceDependency" when $serviceDependency : MrServiceDependency($fromService : fromService, $toService : toService) $processAssignment : MrProcessAssignment(service == $fromService, $neighborhood : neighborhood) not MrProcessAssignment(service == $toService, neighborhood == $neighborhood) then // Constraint broken end {code} In a Java ScoreDirector, you say something like this: {code} // Dependency constraints: each process of a service must have at least one process of it's depended services running in it's neighborhood for (MrServiceDependency serviceDependency : serviceDependencyList) { // TODO use Maps for (MrProcessAssignment processAssignment : serviceToProcessAssignmentMap.get(serviceDependency.getFromService()) { if (!neighborhoodToServiceListMap.get(processAssignment.getNeighborhood()).contains(serviceDependency.toService()) { // Constraint broken } } } In JSR-331, which doesn't support Object-Orientation in it's constraints, this wouldn't look good. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] (AS7-5257) Constructor injection on EJB interceptors not working

by Patrick Ruckstuhl (JIRA)

Patrick Ruckstuhl created AS7-5257: -------------------------------------- Summary: Constructor injection on EJB interceptors not working Key: AS7-5257 URL: https://issues.jboss.org/browse/AS7-5257 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.1.2.Final (EAP) Reporter: Patrick Ruckstuhl Assignee: Stuart Douglas Using JBoss 7.1 I use an EJB intercepter and would like to use constructor inject. This does not seem to work, but normal injection works fine. This one fails with Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011056: No default constructor for interceptor class public class CacheInterceptor { private final DummyCache myCache; @Inject public CacheInterceptor(final DummyCache myCache) { this.myCache = myCache; } @AroundInvoke public Object intercept(final InvocationContext ctx) throws Exception { .... } } but this works fine and DummyCache gets injected public class CacheInterceptor { @Inject private DummyCache myCache; public CacheInterceptor() { } @AroundInvoke public Object intercept(final InvocationContext ctx) throws Exception { .... } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-5256) CDI request scoped beans not destroyed after the EJB asynchronous or timeout method invocation completes

by Martin Kouba (JIRA)

Martin Kouba created AS7-5256: --------------------------------- Summary: CDI request scoped beans not destroyed after the EJB asynchronous or timeout method invocation completes Key: AS7-5256 URL: https://issues.jboss.org/browse/AS7-5256 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.1.1.Final Reporter: Martin Kouba Assignee: Stuart Douglas It seems that CDI request scoped beans are not destroyed after the EJB asynchronous or timeout method invocation completes (request context should be destroyed). See CDI TCK test: https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3584) String comparison fails when using the "==" comparator

by Lisa Horton (JIRA)

Lisa Horton created JBRULES-3584: ------------------------------------ Summary: String comparison fails when using the "==" comparator Key: JBRULES-3584 URL: https://issues.jboss.org/browse/JBRULES-3584 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.Final Environment: Win 7 / Red Hat Linux, Java 6, Netbeans Reporter: Lisa Horton Assignee: Mark Proctor Attachments: RulesTester.zip String comparison using the == operator fails in some cases. "Fails" means the comparison should match but does not. Changing the condition to use equals() operator causes a successful match. I have observed this in both decision tables and in drl rules. I will attach a test case that reproduces the bug. There are workarounds to avoid the bug - the test case demonstrates 3 of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-3491) Hornetq address settings reference non-existing DLQ

by Robert Reimann (JIRA)

Robert Reimann created AS7-3491: ----------------------------------- Summary: Hornetq address settings reference non-existing DLQ Key: AS7-3491 URL: https://issues.jboss.org/browse/AS7-3491 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Assignee: Andy Taylor The hornetq address-settings inside standalone-full.xml and domain.xml reference a non-existing dead-letter-address "jms.queue.DLQ". See forum reference for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
11
0 / 0

[JBoss JIRA] (AS7-2142) CLI: missing :remove-attribute command

by Rostislav Svoboda (Created) (JIRA)

CLI: missing :remove-attribute command -------------------------------------- Key: AS7-2142 URL: https://issues.jboss.org/browse/AS7-2142 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Alexey Loubyansky Fix For: 7.1.0.CR1 We have _:read-attribute_ and _:write-attribute_ commands but we do not have *:remove-attribute* command. It would be invoked on attributes which have flag required set to false. For example when I define socket-binding-port-offset for server-group I can't remove it and I can't set it to 0 using CLI. {code} /server-group=main-server-group:read-resource-description() "socket-binding-port-offset" => { "description" => "The default offset to be added to the port values given by the socket binding group.", "type" => INT, "required" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

13
19
0 / 0

[JBoss JIRA] (AS7-5215) Deployments unecessarily trigger Framework create service

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5215: ----------------------------------- Summary: Deployments unecessarily trigger Framework create service Key: AS7-5215 URL: https://issues.jboss.org/browse/AS7-5215 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Fix For: 7.2.0.CR1 Non-OSGi deployments are registered with the resolver environment (XEnvironment) so that bundle can define requirements on the package capabilities of those deployments. There is plenty of processing needed in order to obtain those non-osgi capabilities and to register them with the environment. The OSGi resolver may however never be activated and there may never be any (bundle) deployment that defines requirements on those capabilities. This processing should be lazy and triggered by an actual resolve request. Remove this from FrameworkActivateProcessor {code} // Always make the system context & the environment available phaseContext.addDeploymentDependency(Services.SYSTEM_CONTEXT, OSGiConstants.SYSTEM_CONTEXT_KEY); phaseContext.addDeploymentDependency(Services.ENVIRONMENT, OSGiConstants.ENVIRONMENT_KEY); {code} and do this more intelligently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1271) Fired object messages violate classloaders

by John Ament (JIRA)

Fired object messages violate classloaders ------------------------------------------ Key: AS7-1271 URL: https://issues.jboss.org/browse/AS7-1271 Project: Application Server 7 Issue Type: Bug Reporter: John Ament JMS allows you to fire an object message. In this case, I have a object of type in my deployment. It fires fine. I bind a message consumer to a queue in AS7. the object message coming in results in a classloader violation: 22:13:35,116 ERROR [org.jboss.seam.jms.example.statuswatcher.messagedriven.DistributorMDB] (Thread-2 (group:HornetQ-client-global-threads-767046602)) org.jboss.seam.jms.example.statuswatcher.model.Status from [Module "org.hornetq:main" from local module loader @19d009b4 (roots: /apps/jboss-as-7.0.0.Final/modules)]: javax.jms.JMSException: org.jboss.seam.jms.example.statuswatcher.model.Status from [Module "org.hornetq:main" from local module loader @19d009b4 (roots: /apps/jboss-as-7.0.0.Final/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) at java.lang.Class.forName0(Native Method) [:1.6.0_22] at java.lang.Class.forName(Class.java:247) [:1.6.0_22] at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:603) [:1.6.0_22] at org.hornetq.utils.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:69) [hornetq-core-2.2.6.Final.jar:] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1574) [:1.6.0_22] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) [:1.6.0_22] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) [:1.6.0_22] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) [:1.6.0_22] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) [:1.6.0_22] at org.hornetq.jms.client.HornetQObjectMessage.getObject(HornetQObjectMessage.java:158) [hornetq-jms-2.2.6.Final.jar:] at org.jboss.seam.jms.example.statuswatcher.messagedriven.DistributorMDB.onMessage(DistributorMDB.java:46) at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [hornetq-jms-2.2.6.Final.jar:] at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866) [hornetq-core-2.2.6.Final.jar:] at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44) [hornetq-core-2.2.6.Final.jar:] at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983) [hornetq-core-2.2.6.Final.jar:] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.6.Final.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

13
29
0 / 0

[JBoss JIRA] (AS7-5252) Upgrade to JBoss Negotiation 2.2.1

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5252: ------------------------------------- Summary: Upgrade to JBoss Negotiation 2.2.1 Key: AS7-5252 URL: https://issues.jboss.org/browse/AS7-5252 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 This upgrade is required to receive the latest Negotiation fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
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 2012