[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4847?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4847.
----------------------------
> STOMP logging does not work
> ---------------------------
>
> Key: WFLY-4847
> URL: https://issues.jboss.org/browse/WFLY-4847
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 9.0.0.CR2
> Reporter: Ville Skyttä
> Assignee: Jason Greene
> Fix For: 9.0.2.Final, 10.0.0.Beta1
>
>
> STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
> Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-4771) The WildFly Arquillian ManagementClient should not assume undertow is enabled
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4771?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4771.
----------------------------
> The WildFly Arquillian ManagementClient should not assume undertow is enabled
> -----------------------------------------------------------------------------
>
> Key: WFLY-4771
> URL: https://issues.jboss.org/browse/WFLY-4771
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 10.0.0.Alpha4
>
>
> When using wildfly-arquillian with infinispan-server, the connection to the managed server breaks with the following exception:
> java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0030: No resource definition is registered for address [(\"subsystem\" => \"undertow\")]"
> at org.jboss.as.arquillian.container.ManagementClient.getWebUri(ManagementClient.java:143)
> at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:160)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> This is because the client relies on the availability of the undertow subsystem, which might not necessarily be available (as is the case with infinispan-server).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5151) Add support to mdb delivery-groups
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5151?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5151.
----------------------------
> Add support to mdb delivery-groups
> ----------------------------------
>
> Key: WFLY-5151
> URL: https://issues.jboss.org/browse/WFLY-5151
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Flavia Rainone
> Assignee: Flavia Rainone
> Priority: Minor
> Fix For: 10.0.0.Beta2
>
>
> Add support to mdb delivery-groups. A delivery-group is a resource inside ejb3 subsystem. This resource can be active:
> <delivery-groups>
> <delivery-group name="group" active="true"/>
> </delivery-groups>
> Whenever the delivery-group is active, all mdbs belonging to that group will have a delivery active state. If the delivery-group is not active, all mdbs belonging to that group will have a delivery disabled.
> The state of delivery-groups can be controlled by cli, using the commands:
> ./subsystem=ejb3/mdb-delivery-group=group:add
> ./subsystem=ejb3/mdb-delivery-group=group:remove
> ./subsystem=ejb3/mdb-delivery-group=group:write-attribute(name=active,value=true)
> An MDB can be associated with a delivery-group at jboss-ejb3.xml or with an annotation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5065) Build fails with the IBM J9 java compiler
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5065?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5065.
----------------------------
> Build fails with the IBM J9 java compiler
> -----------------------------------------
>
> Key: WFLY-5065
> URL: https://issues.jboss.org/browse/WFLY-5065
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Alpha6
> Reporter: Michael Musgrove
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Beta1
>
>
> I am getting an error from the maven enforcer plugin when building with the IBM J9 java compiler (J9VM - R28_Java8_SR1_20150410_1531_B243669):
>
> [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-feature-pack:pom:10.0.0.Beta1-SNAPSHOT
> org.apache.cxf:cxf-rt-security-saml:jar:3.1.2:compile has transitive dependencies:
> xalan:xalan:jar:2.7.1.jbossorg-1:compile
> xalan:serializer:jar:2.7.1.jbossorg-1:compile
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month