[JBoss JIRA] (WFLY-9305) ActiveMQ Resource Adapter can not lookup destination in app namespace
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9305?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil updated WFLY-9305:
------------------------------
Workaround Description: Specify an explicit destinationName in the @JMSDestinationDefinition so that ActiveMQ resource adapter can create the destination from its name (instead of looking up in JNDI)
Workaround: Workaround Exists
> ActiveMQ Resource Adapter can not lookup destination in app namespace
> ---------------------------------------------------------------------
>
> Key: WFLY-9305
> URL: https://issues.jboss.org/browse/WFLY-9305
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Naming
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> When using JMSDefinition defining a non-global JNDI name, Queue/Topic isn't created and MDB listening to those won't read incoming messages.
> Example using non global JNDI (this doesn't work (x) ):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> Example using global JNDI (this works (/)):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:/app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> When using the non-global JNDI and deploying, a message like this can be seen:
> {noformat}
> 13:20:15,542 INFO [org.apache.activemq.artemis.ra] (default-threads - 2) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@78712571 destination=java:app/jms/queue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
> {noformat}
> and creating an MDB to listen sent messages won't receive any.
> Attached a reproducer WAR Maven project. Just deploy, access index.xhtml, click on "Test" button and check logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9305) ActiveMQ Resource Adapter can not lookup destination in app namespace
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9305?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil moved JBEAP-13022 to WFLY-9305:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9305 (was: JBEAP-13022)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
Naming
(was: JMS)
(was: Naming)
Affects Version/s: (was: 7.1.0.ER2)
> ActiveMQ Resource Adapter can not lookup destination in app namespace
> ---------------------------------------------------------------------
>
> Key: WFLY-9305
> URL: https://issues.jboss.org/browse/WFLY-9305
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Naming
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> When using JMSDefinition defining a non-global JNDI name, Queue/Topic isn't created and MDB listening to those won't read incoming messages.
> Example using non global JNDI (this doesn't work (x) ):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> Example using global JNDI (this works (/)):
> {code:java}
> @JMSDestinationDefinition(
> name = "java:/app/jms/queue",
> interfaceName = "javax.jms.Queue"
> )
> {code}
> When using the non-global JNDI and deploying, a message like this can be seen:
> {noformat}
> 13:20:15,542 INFO [org.apache.activemq.artemis.ra] (default-threads - 2) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter@78712571 destination=java:app/jms/queue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
> {noformat}
> and creating an MDB to listen sent messages won't receive any.
> Attached a reproducer WAR Maven project. Just deploy, access index.xhtml, click on "Test" button and check logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9304) Remove unused DOMImplementationRegistryTestCase
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9304?page=com.atlassian.jira.plugin.... ]
Jan Blizňák reassigned WFLY-9304:
---------------------------------
Assignee: Jan Blizňák (was: Tomaz Cerar)
> Remove unused DOMImplementationRegistryTestCase
> -----------------------------------------------
>
> Key: WFLY-9304
> URL: https://issues.jboss.org/browse/WFLY-9304
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: Jan Blizňák
> Assignee: Jan Blizňák
> Priority: Minor
>
> As part of the initiative to get rid of ignored tests in our testsuite, DOMImplementationRegistryTestCase was identified as a candidate for removal.
> There is WFLY-4416 reporting a bug and that is why the testcase was introduced but it was always ignored and there is no progress in years and no plan for resolving WFLY-4416 in foreseeable future.
> For this reason we should remove this testcase. This jira will be linked to original feature request to be able to recover the test from git history in case there is a reason for it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9304) Remove unused DOMImplementationRegistryTestCase
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9304?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated WFLY-9304:
------------------------------
Description:
As part of the initiative to get rid of ignored tests in our testsuite, DOMImplementationRegistryTestCase was identified as a candidate for removal.
There is WFLY-4416 reporting a bug and that is why the testcase was introduced but it was always ignored and there is no progress in years and no plan for resolving WFLY-4416 in foreseeable future.
For this reason we should remove this testcase. This jira will be linked to original feature request to be able to recover the test from git history in case there is a reason for it.
was:
As part of the initiative to get rid of ignored tests in our testsuite, DOMImplementationRegistryTestCase was identified as a candidate for removal.
There is JBEAP-103 reporting a bug and that is why the testcase was introduced but it was always ignored and there is no progress in years and no plan for resolving JBEAP-103 in foreseeable future.
For this reason we should remove this testcase. This jira will be linked to original feature request to be able to recover the test from git history in case there is a reason for it.
> Remove unused DOMImplementationRegistryTestCase
> -----------------------------------------------
>
> Key: WFLY-9304
> URL: https://issues.jboss.org/browse/WFLY-9304
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: Jan Blizňák
> Assignee: Tomaz Cerar
> Priority: Minor
>
> As part of the initiative to get rid of ignored tests in our testsuite, DOMImplementationRegistryTestCase was identified as a candidate for removal.
> There is WFLY-4416 reporting a bug and that is why the testcase was introduced but it was always ignored and there is no progress in years and no plan for resolving WFLY-4416 in foreseeable future.
> For this reason we should remove this testcase. This jira will be linked to original feature request to be able to recover the test from git history in case there is a reason for it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9304) Remove unused DOMImplementationRegistryTestCase
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9304?page=com.atlassian.jira.plugin.... ]
Jan Blizňák moved JBEAP-13021 to WFLY-9304:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9304 (was: JBEAP-13021)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
> Remove unused DOMImplementationRegistryTestCase
> -----------------------------------------------
>
> Key: WFLY-9304
> URL: https://issues.jboss.org/browse/WFLY-9304
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: Jan Blizňák
> Assignee: Tomaz Cerar
> Priority: Minor
>
> As part of the initiative to get rid of ignored tests in our testsuite, DOMImplementationRegistryTestCase was identified as a candidate for removal.
> There is JBEAP-103 reporting a bug and that is why the testcase was introduced but it was always ignored and there is no progress in years and no plan for resolving JBEAP-103 in foreseeable future.
> For this reason we should remove this testcase. This jira will be linked to original feature request to be able to recover the test from git history in case there is a reason for it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3251) Elytron, misconfiguration of http-authentication-factory leads to 403 - should be 500
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3251?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-3251.
--------------------------------------
Fix Version/s: 3.0.1.Final
Resolution: Done
> Elytron, misconfiguration of http-authentication-factory leads to 403 - should be 500
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-3251
> URL: https://issues.jboss.org/browse/WFCORE-3251
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 3.0.1.Final
>
>
> When I misconfigured {{http-authentication-factory}}, e.g. with unreal protocol "DOES_NOT_EXIST" I get http status code 403.
> I think 500 would be more appropriate here, as server is misconfigured and can't authenticate.
> 403 means user has not appropriate roles.
> In log there is
> {code}
> 10:08:06,309 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='SPNEGO', hostName='localhost.localdomain', protocol='http'.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3251) Elytron, misconfiguration of http-authentication-factory leads to 403 - should be 500
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3251?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved WFLY-8463 to WFCORE-3251:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3251 (was: WFLY-8463)
Component/s: Security
(was: Security)
> Elytron, misconfiguration of http-authentication-factory leads to 403 - should be 500
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-3251
> URL: https://issues.jboss.org/browse/WFCORE-3251
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 3.0.1.Final
>
>
> When I misconfigured {{http-authentication-factory}}, e.g. with unreal protocol "DOES_NOT_EXIST" I get http status code 403.
> I think 500 would be more appropriate here, as server is misconfigured and can't authenticate.
> 403 means user has not appropriate roles.
> In log there is
> {code}
> 10:08:06,309 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='SPNEGO', hostName='localhost.localdomain', protocol='http'.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8874) jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-8874?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski resolved WFLY-8874.
--------------------------------------
Resolution: Cannot Reproduce
> jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> ---------------------------------------------------------------
>
> Key: WFLY-8874
> URL: https://issues.jboss.org/browse/WFLY-8874
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 10.1.0.Final
> Environment: java version "1.8.0_131"
> Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
> ubuntu 17.04
> Reporter: Gaétan QUENTIN
> Assignee: Bartosz Baranowski
>
> Launching wildfly with these options:
> JAVA_OPTS='-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xbootclasspath/p:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final.jar -Djboss.modules.system.pkgs=org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl '
> will result in this error:
> [Loaded org.jboss.as.server.Main from jar:file:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-2.2.0.Final.jar!/]
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:505)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8874) jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-8874?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski commented on WFLY-8874:
------------------------------------------
~/redhat/git/wildfly/dist/target/wildfly-11.0.0.Final-SNAPSHOT [master|⚑ 1] $ export JAVA_OPTS='-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xbootclasspath/p:/home/baranowb/redhat/git/wildfly/dist/target/wildfly-11.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.7.Final.jar -Djboss.modules.system.pkgs=org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl'
✘-1 ~/redhat/git/wildfly/dist/target/wildfly-11.0.0.Final-SNAPSHOT [master|⚑ 1] $ ./bin/standalone.sh --server-config=standalone-full.xml
[org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Final-SNAPSHOT (WildFly Core 3.0.1.Final) started in 3521ms - Started 402 of 630 services (353 services are lazy, passive or on-demand)
> jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> ---------------------------------------------------------------
>
> Key: WFLY-8874
> URL: https://issues.jboss.org/browse/WFLY-8874
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 10.1.0.Final
> Environment: java version "1.8.0_131"
> Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
> ubuntu 17.04
> Reporter: Gaétan QUENTIN
> Assignee: Bartosz Baranowski
>
> Launching wildfly with these options:
> JAVA_OPTS='-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xbootclasspath/p:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final.jar -Djboss.modules.system.pkgs=org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl '
> will result in this error:
> [Loaded org.jboss.as.server.Main from jar:file:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-2.2.0.Final.jar!/]
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:505)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9303) Remove unused ServiceRefWithoutExplicitWsdlServletTestCase
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9303?page=com.atlassian.jira.plugin.... ]
Jan Blizňák reassigned WFLY-9303:
---------------------------------
Assignee: Jan Blizňák (was: Tomaz Cerar)
> Remove unused ServiceRefWithoutExplicitWsdlServletTestCase
> ----------------------------------------------------------
>
> Key: WFLY-9303
> URL: https://issues.jboss.org/browse/WFLY-9303
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 11.0.0.CR1
> Reporter: Jan Blizňák
> Assignee: Jan Blizňák
> Priority: Minor
>
> As part of the check for ignored tests in our testsuite, ServiceRefWithoutExplicitWsdlServletTestCase was identified as an adept for removal. It was initially introduced for feature requested in WFLY-3262/WFLY-4026 but there is currently no plan for developing this feature thus it is safe remove it at this time. This jira will be linked to original feature request to be able to recover the test in case the feature is delivered.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months