November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5418) start-delivery/stop-delivery operations descriptions are missing from MDB deployment in domain mode

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5418?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-5418: ----------------------------------- These operations are not available in domain mode with JMX because the jmx subsystem only exposes operations that are READ_ONLY for domain servers. The operations are RUNTIME_ONLY and do not affect the management model. [~brian.stansberry] Would you agree to also expose operations that are RUNTIME_ONLY in the JMX subsystem? I don't see any issue with that... > start-delivery/stop-delivery operations descriptions are missing from MDB deployment in domain mode > --------------------------------------------------------------------------------------------------- > > Key: WFLY-5418 > URL: https://issues.jboss.org/browse/WFLY-5418 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.4.3 > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 10.0.0.CR4 > > > It is possible to start/stop delivery of messages to MDB in standalone mode using operations > start-delivery() and stop-delivery() on MDB deployment. > Those operations are available in domain mode but their descriptions are missing (preventing CLI autocompletion to work as expected). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-5449: ------------------------------------ [~enriquegonzalez] Why was this reopened? The comments in the BZ don't seem relevant to WildFly. Shared transport is deprecated (i.e. not supported) in WF10. See https://issues.jboss.org/browse/WFLY-5460 > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR4 > > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-970) Missing date coercion in constraint using an instance field or a declaration

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-970: ---------------------------------- Summary: Missing date coercion in constraint using an instance field or a declaration Key: DROOLS-970 URL: https://issues.jboss.org/browse/DROOLS-970 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Automatic String to Date coercion is not performed in case the accessed field is not a getter method but an instance field of the class as in: {code} public class Person { public java.util.Date date; } rule x when Person( date < "1-Jan-2000" ) // Error flagged here, if... then ...end {code} or when the class has proper a getter method but the constraint is expressed with a binding declaration as in: {code} rule x when Person( $date: date, $date < "1-Jan-2000" ) then ...end {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5626) EAP is unable to destroy the protocol stack with full-ha profile

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5626?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-5626. ------------------------------ Resolution: Cannot Reproduce Bug I'll leave the EAP jira open. I suspect the issue will disappear next release. > EAP is unable to destroy the protocol stack with full-ha profile > ---------------------------------------------------------------- > > Key: WFLY-5626 > URL: https://issues.jboss.org/browse/WFLY-5626 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Paul Ferraro > > *Description of problem:* > EAP is unable to destroy the protocol stack with full-ha profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./bin/standalone.sh -c standalone-full-ha.xml > # Stop EAP (Ctrl+C) > *Actual results:* > {noformat} > 14:13:21,292 ERROR [org.jgroups.JChannel] (MSC service thread 1-5) JGRP000020: failed destroying the protocol stack: java.lang.IllegalStateException > at org.jboss.as.network.SocketBindingManagerImpl$UnnamedRegistryImpl.unregisterBinding(SocketBindingManagerImpl.java:501) > at org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73) > at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:148) > at org.jgroups.protocols.UDP.closeUnicastSocket(UDP.java:577) > at org.jgroups.protocols.UDP.destroySockets(UDP.java:429) > at org.jgroups.protocols.UDP.destroy(UDP.java:294) > at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:887) > at org.jgroups.JChannel.stopStack(JChannel.java:1005) > at org.jgroups.JChannel._close(JChannel.java:990) > at org.jgroups.JChannel.close(JChannel.java:385) > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.stop(ChannelBuilder.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > *Expected results:* > No errors on output -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5629) Deploying distributable web application starts an unnecessary cache.

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5629: ---------------------------------- Summary: Deploying distributable web application starts an unnecessary cache. Key: WFLY-5629 URL: https://issues.jboss.org/browse/WFLY-5629 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Deploying a web application should only start 2 caches: * Cache for storing sessions (deployment specific) * Cache for storing routing information (shared) However, currently, the default cache is also started, even though it is never used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5628) Deploying distributable web application starts an unnecessary cache.

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5628: ---------------------------------- Summary: Deploying distributable web application starts an unnecessary cache. Key: WFLY-5628 URL: https://issues.jboss.org/browse/WFLY-5628 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Deploying a web application should only start 2 caches: * Cache for storing sessions (deployment specific) * Cache for storing routing information (shared) However, currently, the default cache is also started, even though it is never used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1300) <datasource-class> in <driver> is ignored

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1300?page=com.atlassian.jira.plugin... ] Jesper Pedersen moved WFLY-5625 to JBJCA-1300: ---------------------------------------------- Project: IronJacamar (was: WildFly) Key: JBJCA-1300 (was: WFLY-5625) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: Deployer (was: JCA) > <datasource-class> in <driver> is ignored > ----------------------------------------- > > Key: JBJCA-1300 > URL: https://issues.jboss.org/browse/JBJCA-1300 > Project: IronJacamar > Issue Type: Bug > Components: Deployer > Reporter: Martin Simka > Assignee: Stefano Maestri > Priority: Critical > > {code:xml} > <driver name="oracle-ucp" module="com.oracle.ucp"> > <xa-datasource-class>[class]</xa-datasource-class> > <datasource-class>[class]</datasource-class> > </driver> > {code} > datasource-class setting is ignored and Driver class is used instead, DataSource class should have priority over Driver if defined > <datasource-class> in <datasource> works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1300) <datasource-class> in <driver> is ignored

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1300?page=com.atlassian.jira.plugin... ] Jesper Pedersen reassigned JBJCA-1300: -------------------------------------- Assignee: Jesper Pedersen (was: Stefano Maestri) > <datasource-class> in <driver> is ignored > ----------------------------------------- > > Key: JBJCA-1300 > URL: https://issues.jboss.org/browse/JBJCA-1300 > Project: IronJacamar > Issue Type: Bug > Components: Deployer > Reporter: Martin Simka > Assignee: Jesper Pedersen > Priority: Critical > > {code:xml} > <driver name="oracle-ucp" module="com.oracle.ucp"> > <xa-datasource-class>[class]</xa-datasource-class> > <datasource-class>[class]</datasource-class> > </driver> > {code} > datasource-class setting is ignored and Driver class is used instead, DataSource class should have priority over Driver if defined > <datasource-class> in <datasource> works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5627?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-5627. ------------------------------ Resolution: Rejected The reason you aren't seeing any change in statistics is because the default cache is no longer used to store routing information, thus there never any activity on that cache. > Unable to view the infinispan statistics from CLI > ------------------------------------------------- > > Key: WFLY-5627 > URL: https://issues.jboss.org/browse/WFLY-5627 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Chao Wang > Assignee: Paul Ferraro > > When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as: > {noformat} > Steps to Reproduce: > =================== > 1) Build latest Wildfly master and consider `standalone-ha.xml` file. > 2) Enable the infinispan statistics in the standalone-ha.xml file. > Configuration looks as below: > ----- > <subsystem xmlns="urn:jboss:domain:infinispan:4.0"> > <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default"> > <transport lock-timeout="60000"/> > <replicated-cache name="default" mode="SYNC"> > <transaction mode="BATCH"/> > </replicated-cache> > </cache-container> > <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true"> > <transport lock-timeout="60000"/> > <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2"> > <locking isolation="REPEATABLE_READ"/> > <transaction mode="BATCH"/> > <file-store/> > </distributed-cache> > </cache-container> > ----- > 3) Start the server with `standalone-ha.xml` file. > 4) Deploy the cluster web application and hit the application. > 5) and check the infinispan statistics by using the below cli command: > ----- > /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true) > ----- > 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change. > Actual results: > =============== > - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed. > Expected results: > ================= > - There should be a change in the runtime parameters values. > Additional info: > ================= > - I can see the expected result from the jconsole statistics. > jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics. > {noformat} > It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI

by Chao Wang (JIRA)

Chao Wang created WFLY-5627: ------------------------------- Summary: Unable to view the infinispan statistics from CLI Key: WFLY-5627 URL: https://issues.jboss.org/browse/WFLY-5627 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Chao Wang Assignee: Paul Ferraro When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as: {noformat} Steps to Reproduce: =================== 1) Build latest Wildfly master and consider `standalone-ha.xml` file. 2) Enable the infinispan statistics in the standalone-ha.xml file. Configuration looks as below: ----- <subsystem xmlns="urn:jboss:domain:infinispan:4.0"> <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default"> <transport lock-timeout="60000"/> <replicated-cache name="default" mode="SYNC"> <transaction mode="BATCH"/> </replicated-cache> </cache-container> <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true"> <transport lock-timeout="60000"/> <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2"> <locking isolation="REPEATABLE_READ"/> <transaction mode="BATCH"/> <file-store/> </distributed-cache> </cache-container> ----- 3) Start the server with `standalone-ha.xml` file. 4) Deploy the cluster web application and hit the application. 5) and check the infinispan statistics by using the below cli command: ----- /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true) ----- 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change. Actual results: =============== - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed. Expected results: ================= - There should be a change in the runtime parameters values. Additional info: ================= - I can see the expected result from the jconsole statistics. jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics. {noformat} It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015