[JBoss JIRA] (WFLY-3974) Move 'Channel end notification received, closing channel' to DEBUG
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3974?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3974:
-----------------------------------------------
Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1147506|https://bugzilla.redhat.com/show_bug.cgi?id=1147506] from VERIFIED to MODIFIED
> Move 'Channel end notification received, closing channel' to DEBUG
> ------------------------------------------------------------------
>
> Key: WFLY-3974
> URL: https://issues.jboss.org/browse/WFLY-3974
> Project: WildFly
> Issue Type: Enhancement
> Components: Naming
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 9.0.0.Beta1
>
>
> When a remote jms queue is located the following is seen:
> 2014-09-25 16:48:29,327 INFO [org.jboss.as.naming] (Remoting "jeev6dev01_200" task-1) JBAS011806: Notification de fin de canal reçue, fermeture du canal Channel ID 0cb79bd5 (inbound) of Remoting connection 53a1933a to /10.23.132.245:57733
> This is due to org.jboss.as.naming.NamingLogger where the following is used:
> @LogMessage(level=Logger.Level.INFO)
> @Message(id=11806, value="Channel end notification received, closing channel %s")
> public abstract void closingChannelOnChannelEnd(Channel paramChannel);
> Changin this to
> @LogMessage(level=Logger.Level.DEBUG)
> Would ensure that an INFO log event is not seen every time a jms message is sent to the server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3548:
-----------------------------------------------
Amos Feng <zfeng(a)redhat.com> changed the Status of [bug 1098127|https://bugzilla.redhat.com/show_bug.cgi?id=1098127] from ASSIGNED to POST
> JTA synchronization for a distributed transaction called with incorrect TCCL
> ----------------------------------------------------------------------------
>
> Key: WFLY-3548
> URL: https://issues.jboss.org/browse/WFLY-3548
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.1.0.Final
> Reporter: Martin Kouba
> Assignee: Martin Kouba
> Fix For: 9.0.0.Beta1
>
>
> It seems the RequestProcessor which is processing JTA synchronizations
> does not have the right TCCL set.
> As a result, during synchronization invocation:
> * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction"
> * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment."
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3519) process-id-uuid and related attribute should consider alternatives/required attributes in :write-attribute handler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3519?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3519:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1090406|https://bugzilla.redhat.com/show_bug.cgi?id=1090406] from POST to MODIFIED
> process-id-uuid and related attribute should consider alternatives/required attributes in :write-attribute handler
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3519
> URL: https://issues.jboss.org/browse/WFLY-3519
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: Stefano Maestri
> Assignee: Stefano Maestri
> Fix For: 9.0.0.Beta1
>
>
> The transaction subsystem causes the server fails to start (is halted) when just process-id-uuid is set to false without specifying the process-id-socket-binding.
> When you run commands:
> /subsystem=transactions:write-attribute(name=process-id-uuid,value=false)
> :reload
> Server fails with exception [1]
> The transaction subsystem should block changes that causes the server would fail on reload. The user should get information that the process-id-socket-binding has to be set before reload could proceed, i.e., fail the reload operation.
> [1]
> 11:13:53,630 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.server.ServerService.boot(ServerService.java:321) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[287,17]
> Message: JBAS014723: Must include one of the following elements: SOCKET, UUID
> at org.jboss.as.controller.parsing.ParseUtils.missingOneOf(ParseUtils.java:194) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseProcessIdEnvironmentElement(TransactionSubsystem14Parser.java:390)
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseCoreEnvironmentElement(TransactionSubsystem14Parser.java:340)
> at org.jboss.as.txn.subsystem.TransactionSubsystem15Parser.readElement(TransactionSubsystem15Parser.java:59)
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:110)
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:53)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
> at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1035) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:469) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10]
> ... 3 more
> 11:13:53,635 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-450) Support using parent system properties in child properties
by Samuli Saarinen (JIRA)
Samuli Saarinen created WFCORE-450:
--------------------------------------
Summary: Support using parent system properties in child properties
Key: WFCORE-450
URL: https://issues.jboss.org/browse/WFCORE-450
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Samuli Saarinen
Assignee: Brian Stansberry
Using wildfly domain I would like to define some properties in domain.xml and then be able to use these properties when defining others in server-group or server level. Currently this leads to JBAS014802: Cannot resolve expression.
More detailed example:
{code:xml|title=domain.xml}
<domain>
<system-properties>
<property name="foo" value="bar"/>
</system-properties>
...
<server-group name="g1">
<system-properties>
<property name="g1_foo" value="${foo}"/>
</system-properties>
</server-group>
</domain>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-776) Inject POJO to MBean by using <inject bean="XXX"> in jboss-service.xml does not work in SAR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-776?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-776:
----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 901304|https://bugzilla.redhat.com/show_bug.cgi?id=901304] from NEW to ASSIGNED
> Inject POJO to MBean by using <inject bean="XXX"> in jboss-service.xml does not work in SAR
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-776
> URL: https://issues.jboss.org/browse/WFLY-776
> Project: WildFly
> Issue Type: Bug
> Components: JMX, POJO
> Reporter: Masafumi Miura
> Attachments: HelloService-AS7-inject-reproducer.tar.gz
>
>
> When injecting POJO to MBean by using {{<inject bean="myTask"/>}} in {{jboss-service.xml}} of SAR like the following:
> * META-INF/jboss-service.xml:
> {code:xml}
> <server>
> <mbean code="com.redhat.jboss.support.HelloService"
> name="example:type=HelloService,service=Hello">
> <attribute name="Message">Hello!!</attribute>
> <attribute name="Task"><inject bean="myTask"/></attribute>
> </mbean>
> </server>
> {code}
> * META-INF/jboss-beans.xml:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment ... >
> <bean name="myTask" class="com.redhat.jboss.support.SimpleTask">
> </bean>
> </deployment>
> {code}
> Then the following ERROR is happened at deployment of SAR:
> {noformat:title=7.1.4.Final}
> ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.mbean.service.example:type=HelloService,service=Hello.start Missing[jboss.mbean.service.myTask.start]","jboss.mbean.registration.example:type=HelloService,service=Hello Missing[JBAS014861: <one or more transitive dependencies>]","jboss.mbean.service.example:type=HelloService,service=Hello.create Missing[jboss.mbean.service.myTask.create]"]}}}
> {noformat}
> {noformat:title=7.2.0.Alpha1}
> ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "HelloService.sar" was rolled back with the following failure message:
> {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.mbean.service.example:type=HelloService,service=Hello.start is missing [jboss.mbean.service.myTask.start]",
> "jboss.mbean.service.example:type=HelloService,service=Hello.create is missing [jboss.mbean.service.myTask.create]"
> ]}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-2376) DataSource properties are not persisting via CLI
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2376?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2376:
-----------------------------------------------
Martin Simka <msimka(a)redhat.com> changed the Status of [bug 1023064|https://bugzilla.redhat.com/show_bug.cgi?id=1023064] from ON_QA to VERIFIED
> DataSource properties are not persisting via CLI
> ------------------------------------------------
>
> Key: WFLY-2376
> URL: https://issues.jboss.org/browse/WFLY-2376
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Jay Kumar SenSharma
> Assignee: Stefano Maestri
> Fix For: 9.0.0.Beta1
>
>
> - The CLI command show that there are some valid configuration properties available like following while configuring DataSources, However those properties never get persisted in the DataSource configuration:
> {quote}
> ./jboss-cli.sh --user=admin --password=admin@123 -c --controller=remote://localhost:9999 command="/subsystem=datasources/data-source=testpool:read-resource-description(recursive=true)"
> "stale-connection-checker-properties" => {
> "type" => OBJECT,
> "description" => "The stale connection checker properties",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "reauth-plugin-properties" => {
> "type" => OBJECT,
> "description" => "The properties for the reauthentication plugin",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "exception-sorter-properties" => {
> "type" => OBJECT,
> "description" => "The exception sorter properties",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> {quote}
> - Following command never complains about any issue and the following command executed without any issue but the above properties are not persisted in the DataSource.
> ./jboss-cli.sh --user=admin --password=admin@123 -c --controller=remote://localhost:9999 command="/subsystem=datasources/data-source=testpool:add(jndi-name=\"java:jboss/TestDS\",driver-name=\"ojdbc6.jar\",connection-url=\"jdbc:oracle:thin:@DBHostName:1521:DBName\",user-name=\"user\",password=\"pass\",new-connection-sql=\"select 1 from dual\", check-valid-connection-sql=\"select 2 from dual\",valid-connection-checker-class-name=\"org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker\",exception-sorter-properties={\"prop1\"=>\"value1\"},reauth-plugin-properties={\"reauthProp1\"=>\"reauthValue1\"},exception-sorter-properties={\"exceptionSorterProp1\"=>\"exceptionSorterValue1\"})"
> - The Generated DataSource looks like following:
> ${quote}
> <datasource jndi-name="java:jboss/TestDS" pool-name="testpool" enabled="true">
> <connection-url>jdbc:oracle:thin:@DBHostName:1521:DBName</connection-url>
> <driver>ojdbc6.jar</driver>
> <new-connection-sql>select 1 from dual</new-connection-sql>
> <security>
> <user-name>user</user-name>
> <password>pass</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker"/>
> <check-valid-connection-sql>select 2 from dual</check-valid-connection-sql>
> </validation>
> </datasource>
> ${quote}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-288) Memory leak in org.xnio.ByteBufferSlicePool
by Sergey Lisovoy (JIRA)
[ https://issues.jboss.org/browse/WFCORE-288?page=com.atlassian.jira.plugin... ]
Sergey Lisovoy edited comment on WFCORE-288 at 12/8/14 3:25 AM:
----------------------------------------------------------------
I try Wildfly 8.2.0.Final and client libs. I found no leak during tests.
Should I close It's ticket or someone else?
was (Author: s.lisovoy):
I try Woldfly 8.2.0.Final and client libs. I found no leak during tests.
Should I close It's ticket or someone else?
> Memory leak in org.xnio.ByteBufferSlicePool
> -------------------------------------------
>
> Key: WFCORE-288
> URL: https://issues.jboss.org/browse/WFCORE-288
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Sergey Lisovoy
> Assignee: David Lloyd
> Labels: memory_leak, memoryleak
>
> I have a simple thread that monitor remote wildfly process status. After some time it fail with OutOfMemory exception.
> I wrote simple exsample how to reproduce its error:
> {code:java}
> package ru.kamis.tests.xniomemoryleaks;
> import org.jboss.as.controller.client.ModelControllerClient;
> import org.jboss.as.controller.client.helpers.Operations;
> import org.jboss.dmr.ModelNode;
> public class OutOfMemoryDemo {
> public static void main(String[] args) throws Exception {
>
> for(int i=0; i<1000000; i++) {
> ModelControllerClient client = null;
> client = ModelControllerClient.Factory.create("localhost", 9990);
>
> ModelNode operation = Operations.createReadAttributeOperation(new ModelNode().setEmptyList(), "server-state");
> client.execute(operation);
>
> client.close();
>
> if(i % 1000 == 0) {
> System.out.println("Processed: " + i);
> }
> }
> }
> }
> {code}
> Program produces folowing output:
> {noformat}
> сен 09, 2014 2:33:20 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.2.2.Final
> сен 09, 2014 2:33:20 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.2.2.Final
> сен 09, 2014 2:33:20 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.3.Final
> Processed: 0
> Processed: 1000
> Processed: 2000
> Processed: 3000
> Processed: 4000
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at java.lang.String.toCharArray(String.java:2746)
> at sun.net.www.ParseUtil.encodePath(ParseUtil.java:107)
> at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:757)
> at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:842)
> at sun.misc.URLClassPath.getResource(URLClassPath.java:199)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:358)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:15)
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> сен 09, 2014 2:35:20 PM org.jboss.as.controller.client.impl.RemotingModelControllerClient finalize
> WARN: JBAS010600: Closing leaked controller client
> JBAS010649: Allocation stack trace:
> at java.lang.Thread.getStackTrace(Thread.java:1589)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:76)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:353)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:200)
> at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:12)
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> {noformat}
> Used libraries:
> {code:xml}
> <dependency>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-controller-client</artifactId>
> <version>8.1.0.Final</version>
> </dependency>
> {code}
> The same bug is reproduced on other xnio versions: 3.2.3.Final, 3.3.0.Beta2
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months