May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-691) Ability to modify server-config, subresource system properties

by Heiko Braun (JIRA)

Ability to modify server-config, subresource system properties -------------------------------------------------------------- Key: AS7-691 URL: https://issues.jboss.org/browse/AS7-691 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (AS7-771) Provide extended logging management operations

by Heiko Braun (JIRA)

Provide extended logging management operations ---------------------------------------------- Key: AS7-771 URL: https://issues.jboss.org/browse/AS7-771 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry I would like to be able to do at least five things with jboss logging. First, I would like to be able to turn on and off CONSOLE logging. I would like to be able to go back and forth between ASYNC and SYNC logging. I would like to be able to change the log format. I would like to be able to change the log location, and finally, I would like to be able to change the log file attributes, like how large, and whether its a rolling log file or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
9
0 / 0

[JBoss JIRA] Created: (AS7-900) @Resource and @EJB don't currently support mappedName attribute value

by jaikiran pai (JIRA)

@Resource and @EJB don't currently support mappedName attribute value ---------------------------------------------------------------------- Key: AS7-900 URL: https://issues.jboss.org/browse/AS7-900 Project: Application Server 7 Issue Type: Bug Components: EE Reporter: jaikiran pai Assignee: jaikiran pai Before the "lookup" attribute was introduced in @EJB and @Resource, users used to specify the jndi name via the "mappedName" attribute of these annotations. We currently aren't supporting the mappedName value while processing these annotations. We'll have to fix this since there are many applications out there, relying on mappedName. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-746) Subsystem "web": Expose boolean attributes as boolean values, not as string values

by Heiko Braun (JIRA)

Subsystem "web": Expose boolean attributes as boolean values, not as string values ----------------------------------------------------------------------------------- Key: AS7-746 URL: https://issues.jboss.org/browse/AS7-746 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.0.0.CR1 take a look that the resource description. the "configuration" subresources contains plenty of boolean values that are exposed as strings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (AS7-899) Class hierarchy is not taken into account when determining transaction attributes

by Carlo de Wolf (JIRA)

Class hierarchy is not taken into account when determining transaction attributes --------------------------------------------------------------------------------- Key: AS7-899 URL: https://issues.jboss.org/browse/AS7-899 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical EJB 3.1 FR 13.3.7.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (AS7-715) web subsystem has boolean parameters listed as strings

by Heiko Rupp (JIRA)

web subsystem has boolean parameters listed as strings ------------------------------------------------------ Key: AS7-715 URL: https://issues.jboss.org/browse/AS7-715 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Heiko Rupp Assignee: Jason Greene Do a read-resource-description for the web subsystem and see the following. All attributes are marked as strings, even if in reality they are boolean or ints. "webdav" => { "type" => STRING, "description" => "Enable WebDAV functionality. The default value is \"false\".", "required" => false }, "max-depth" => { "type" => STRING, "description" => "Maximum recursion for PROPFIND. The default value is 3.", "required" => false }, "disabled" => { "type" => STRING, "description" => "Enable the JSP container. The default value is \"true\".", "required" => false }, "development" => { "type" => STRING, "description" => "Enable the development mode, which gives more information when an error occurs. The default value is \"false\".", "required" => false [...] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (AS7-897) Using an older standalone.xml a NoSuchElementException: No child 'process-id' exists during add handler execution.

by Darran Lofthouse (JIRA)

Using an older standalone.xml a NoSuchElementException: No child 'process-id' exists during add handler execution. ------------------------------------------------------------------------------------------------------------------ Key: AS7-897 URL: https://issues.jboss.org/browse/AS7-897 Project: Application Server 7 Issue Type: Bug Components: Transactions Reporter: Darran Lofthouse The following is the reported stack trace: - 10:59:51,286 ERROR [org.jboss.as.controller] operation ("add") failed - address: ([("subsystem" => "transactions")]): java.util.NoSuchElementException: No child 'process-id' exists at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) at org.jboss.dmr.ModelNode.require(ModelNode.java:703) at org.jboss.as.txn.TransactionSubsystemAdd.execute(TransactionSubsystemAdd.java:83) at org.jboss.as.controller.BasicModelController.doExecute(BasicModelController.java:403) at org.jboss.as.server.ServerControllerImpl.doExecute(ServerControllerImpl.java:189) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:275) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:231) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:80) at org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:46) at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:187) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] If there is a problem with the XML this should really be picked up before the operations are executed during the XML parsing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-3048) Error in Rule created by Guvnor

by Vikash Agrawal (JIRA)

Error in Rule created by Guvnor ------------------------------- Key: JBRULES-3048 URL: https://issues.jboss.org/browse/JBRULES-3048 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Vikash Agrawal Assignee: Mark Proctor Hello , Below is a rule created from Guvnor and while executing it it is giving me a issue: Rule Code ------------------------------------------- package ACTIVITY_POC import com.sample.Message global com.sample.Message message rule "NewRule" dialect "mvel" when Message( status == "200" && messageText == "test" ) then Message fact0 = new Message(); fact0.setStatus( 200 ); insert(fact0 ); end Error: -------------------------------------------------------------------------- org.drools.runtime.rule.ConsequenceException: rule: NewRule at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:927) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:856) at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1071) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:785) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:751) at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218) at com.sample.ABCD.main(ABCD.java:41) Caused by: [Error: unable to access property (null parent): setStatus] [Near : {... Unknown ....}] ^ [Line: 1, Column: 0] at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:886) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:314) at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:137) at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:137) at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:104) at org.mvel2.MVEL.executeExpression(MVEL.java:1001) at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:103) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) ... 6 more -------------------------------------------------------------------------------------- Message Object: ----------------------------------------------------------------------------------- package com.sample; public class Message { private String messageText; public String getMessageText() { return messageText; } public void setMessageText(String messageText) { this.messageText = messageText; } private int status; public int getStatus() { return this.status; } public void setStatus(int status) { this.status = status; } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1314) FD_SOCK port conflicts with concurrently connected channels

by Paul Ferraro (JIRA)

FD_SOCK port conflicts with concurrently connected channels ----------------------------------------------------------- Key: JGRP-1314 URL: https://issues.jboss.org/browse/JGRP-1314 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Paul Ferraro Assignee: Bela Ban Because of the high level of concurrency in AS7, I'm seeing occasional socket exceptions in FD_SOCK when trying to start multiple channels using a shared transport. It appears that there are some thread safety issues with the port increment logic within FD_SOCK. Until JGRP-790 is complete, measures need to be taken to ensure that multiple concurrently connected channels do not select the same port on which to open a server socket. Here's a sample stack trace: 10:01:26,716 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.infinispan.cluster: org.jboss.msc.service.StartException in service jboss.infinispan.cluster: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1696) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: org.infinispan.CacheException: Unable to invoke method public abstract void org.infinispan.remoting.transport.Transport.start() on object at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:174) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:889) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:687) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:589) at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:137) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:137) at org.infinispan.CacheDelegate.start(CacheDelegate.java:323) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:516) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:439) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:77) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:66) at org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.start(EmbeddedCacheManagerService.java:171) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) ... 3 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22] at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171) ... 15 more Caused by: java.lang.IllegalArgumentException: failed to start server socket at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:295) at org.jgroups.protocols.FD.down(FD.java:310) at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:70) at org.jgroups.protocols.BARRIER.down(BARRIER.java:90) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:634) at org.jgroups.protocols.UNICAST.down(UNICAST.java:443) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:330) at org.jgroups.protocols.VIEW_SYNC.down(VIEW_SYNC.java:186) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:926) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) at org.jgroups.protocols.FRAG2.down(FRAG2.java:155) at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:324) at org.jgroups.protocols.pbcast.FLUSH.handleConnect(FLUSH.java:302) at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1081) at org.jgroups.JChannel.downcall(JChannel.java:1680) at org.jgroups.JChannel.connect(JChannel.java:425) at org.jgroups.JChannel.connect(JChannel.java:388) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:171) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:155) ... 20 more Caused by: java.net.SocketException: Address already in use at java.net.PlainSocketImpl.socketListen(Native Method) [:1.6.0_22] at java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:365) [:1.6.0_22] at java.net.ServerSocket.bind(ServerSocket.java:337) [:1.6.0_22] at java.net.ServerSocket.<init>(ServerSocket.java:202) [:1.6.0_22] at org.jgroups.util.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:49) at org.jgroups.util.Util.createServerSocket(Util.java:3046) at org.jgroups.protocols.FD_SOCK.startServerSocket(FD_SOCK.java:561) at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:292) ... 40 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-1327) Cluster name should be quoted in JMX object names

by Galder Zamarreño (JIRA)

Cluster name should be quoted in JMX object names ------------------------------------------------- Key: JGRP-1327 URL: https://issues.jboss.org/browse/JGRP-1327 Project: JGroups Issue Type: Bug Reporter: Galder Zamarreño Assignee: Bela Ban Priority: Minor Any of the parameters that form the object names in JmxConfigurator that are provided by users, such as the cluster name, need to be quoted to avoid issues with invalid characters being used in cluster name, i.e. ObjectName.quote(clusterName) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
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 May 2011