[JBoss JIRA] (WFLY-6550) Invalid use of ModuleIdentifier.create(String) for dynamic names prevents use of slots
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-6550:
--------------------------------------
Summary: Invalid use of ModuleIdentifier.create(String) for dynamic names prevents use of slots
Key: WFLY-6550
URL: https://issues.jboss.org/browse/WFLY-6550
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The ModuleIdentifier.create(String) method is a convenience method for creating an id with a slot of "main". Using this method for user-provided module names prevents the user from encoding a slot into their string. Better is to use ModuleIdentifier.fromString(String) which will parse out a slot if present.
WFCORE-1499 is due to this problem; reviewing the PR for it led me to investigate core and full for other occurrences. Found a few.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFCORE-1228) Follow up on WFCORE-1202 and make the configuration available in the management model.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1228?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1228:
-------------------------------------
Description:
WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model.
The system property should remain supported for backwards compatibility for those migrating from servers that relied on it.
was:
WFCORE-1102 makes use of a system property for configuration, this needs moving into the management model.
The system property should remain supported for backwards compatibility for those migrating from servers that relied on it.
> Follow up on WFCORE-1202 and make the configuration available in the management model.
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1228
> URL: https://issues.jboss.org/browse/WFCORE-1228
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 3.0.0.Alpha1
>
>
> WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model.
> The system property should remain supported for backwards compatibility for those migrating from servers that relied on it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFCORE-1405) Ability to configure a listener to receive management notifications
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1405?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1405:
----------------------------------------
Assignee: Kabir Khan
> Ability to configure a listener to receive management notifications
> -------------------------------------------------------------------
>
> Key: WFCORE-1405
> URL: https://issues.jboss.org/browse/WFCORE-1405
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Kabir Khan
> Priority: Blocker
> Fix For: 3.0.0.Beta1
>
>
> Provide a means to configure registration of a listener registration for management notifications.
> Users would implement a new NotificationRegistrar interface and register their impl in the configuration, with a management resource created for each configured NotificationRegistrar.
> The interface would be invoked by the kernel during add of the NotificationRegistrar resource (at boot or post-boot if it's added then.)
> The method passes in a ref to a client that subsequently can be used to invoke management ops, and a registry users can use to register listeners for future management notifications.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBEE-160) jboss-transaction-api OSGi bundle requiring optional packages
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBEE-160?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on JBEE-160:
----------------------------------
{code}
Manifest-Version: 1.0
Bundle-License: http://repository.jboss.org/licenses/cddl.txt, http://
repository.jboss.org/licenses/gpl-2.0-ce.txt
Bundle-SymbolicName: org.jboss.spec.javax.transaction.jboss-transactio
n-api_1.2_spec
Archiver-Version: Plexus Archiver
Built-By: tomaz
Bnd-LastModified: 1461356937170
Specification-Title: JSR 907: Java Transaction API (JTA)
Implementation-Vendor-Id: org.jboss.spec.javax.transaction
Bundle-DocURL: http://www.jboss.org
Import-Package: javax.enterprise.context;resolution:=optional;version=
"[1.1,2)",javax.enterprise.util;resolution:=optional;version="[1.1,2)
",javax.interceptor;version="[1.2,2)",javax.transaction.xa;version="[
1.2,2)"
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.7))"
Scm-Url: https://github.com/jboss/jboss-transaction-api_spec
Export-Package: javax.transaction;version="1.2";uses:="javax.enterpris
e.context,javax.enterprise.util,javax.interceptor,javax.transaction.x
a",javax.transaction.xa;version="1.2"
Bundle-Name: Java Transaction API
Implementation-Title: Java Transaction API
Bundle-Description: The Java Transaction 1.2 API classes
Implementation-Version: 1.0.1.Final-SNAPSHOT
Java-Version: 1.8.0_74
Scm-Connection: scm:git:git@github.com:jboss/jboss-transaction-api_spe
c.git
Specification-Vendor: Oracle, Inc.
Os-Arch: amd64
Bundle-ManifestVersion: 2
Java-Vendor: Oracle Corporation
Bundle-Vendor: JBoss by Red Hat
Os-Name: Windows 10
Tool: Bnd-3.0.0.201509101326
Implementation-Vendor: JBoss by Red Hat
Os-Version: 10.0
Scm-Revision: cb860fe516ea064074140827a02956f12a1f748e
Bundle-Version: 1.0.1.Final-SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Build-Jdk: 1.8.0_74
Specification-Version: 1.2
Implementation-URL: http://www.jboss.org/jboss-transaction-api_1.2_spec
{code}
better?
> jboss-transaction-api OSGi bundle requiring optional packages
> -------------------------------------------------------------
>
> Key: JBEE-160
> URL: https://issues.jboss.org/browse/JBEE-160
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-transaction-api
> Reporter: Brett Meyer
> Assignee: Tomaz Cerar
>
> The jboss-transaction-api_1.2_spec OSGi bundle requires the 'javax.enterprise.context'. Instead, that should be optional, right? cdi-api shouldn't be required to simply use jta. Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-5400) Failover of standalone JMS client fails with netty (blocking/non-blocking) connector
by Phil Festoso (JIRA)
[ https://issues.jboss.org/browse/WFLY-5400?page=com.atlassian.jira.plugin.... ]
Phil Festoso commented on WFLY-5400:
------------------------------------
[~anrobert] [~ahoffer] I grabbed this since I've been working in the HA section this week. Angie, assigning to you per your 5 OCT 15 comment.
> Failover of standalone JMS client fails with netty (blocking/non-blocking) connector
> ------------------------------------------------------------------------------------
>
> Key: WFLY-5400
> URL: https://issues.jboss.org/browse/WFLY-5400
> Project: WildFly
> Issue Type: Bug
> Components: Documentation, JMS
> Affects Versions: 10.0.0.CR1
> Reporter: Miroslav Novak
> Assignee: Phil Festoso
> Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml
>
>
> Failover of standalone JMS client fails if netty (blocking/non-blocking) connector is used. There are 2 EAP 7.0.0.DR10 (Artemis 1.1.0) servers configured in dedicated topology with shared store.
> If live server is killed then backup activates but client does not failover to it:
> {code}
> ent message with property count: 110867, messageId:ID:20310150-62a0-11e5-ada8-b3332c72af23
> Sent message with property count: 110868, messageId:ID:20310151-62a0-11e5-ada8-b3332c72af23
> Sep 24, 2015 11:39:27 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:39:40 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:39:55 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:40:10 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> {code}
> Attaching live/backup configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-5400) Failover of standalone JMS client fails with netty (blocking/non-blocking) connector
by Phil Festoso (JIRA)
[ https://issues.jboss.org/browse/WFLY-5400?page=com.atlassian.jira.plugin.... ]
Phil Festoso reassigned WFLY-5400:
----------------------------------
Assignee: ANGELA ROBERTSON (was: Phil Festoso)
> Failover of standalone JMS client fails with netty (blocking/non-blocking) connector
> ------------------------------------------------------------------------------------
>
> Key: WFLY-5400
> URL: https://issues.jboss.org/browse/WFLY-5400
> Project: WildFly
> Issue Type: Bug
> Components: Documentation, JMS
> Affects Versions: 10.0.0.CR1
> Reporter: Miroslav Novak
> Assignee: ANGELA ROBERTSON
> Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml
>
>
> Failover of standalone JMS client fails if netty (blocking/non-blocking) connector is used. There are 2 EAP 7.0.0.DR10 (Artemis 1.1.0) servers configured in dedicated topology with shared store.
> If live server is killed then backup activates but client does not failover to it:
> {code}
> ent message with property count: 110867, messageId:ID:20310150-62a0-11e5-ada8-b3332c72af23
> Sent message with property count: 110868, messageId:ID:20310151-62a0-11e5-ada8-b3332c72af23
> Sep 24, 2015 11:39:27 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:39:40 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:39:55 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> Sep 24, 2015 11:40:10 AM org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl acquireCredits
> WARN: AMQ212054: Destination address=jms.queue.testQueue0 is blocked. If the system is configured to block make sure you consume messages on this configuration.
> {code}
> Attaching live/backup configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years