October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7871) Decouple backup/site name from the name of the corresponding resource

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7871?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7871: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Decouple backup/site name from the name of the corresponding resource > --------------------------------------------------------------------- > > Key: WFLY-7871 > URL: https://issues.jboss.org/browse/WFLY-7871 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > > Currently, the site names defined in the JGroups subsystem RELAY2 protocol, and the backup names defined in the Infinispan subsystem do not allow expressions, since these name are used for the corresponding resource paths. To simplify the use of cross-site replication (specifically, to allow each site to use an identical domain.xml/standalone.xml), we can support expressions if we decouple the site name from the resource name. > e.g. > {noformat} > <backups> > <backup name="remote" site="${...}" strategy="SYNC"/> > </backups> > <relay site="local"> > <remote-site name="local" site-name="${...}" channel=".."/> > <remote-site name="remote" site-name="${...}" channel=".."/> > </relay> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7822) The default-security-domain attribute in the Undertow subsystem should not support expressions.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7822?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7822: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > The default-security-domain attribute in the Undertow subsystem should not support expressions. > ----------------------------------------------------------------------------------------------- > > Key: WFLY-7822 > URL: https://issues.jboss.org/browse/WFLY-7822 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Stuart Douglas > Fix For: 12.0.0.Alpha1 > > > This attribute may be deprecated and removed at some point when we start to transition off PicketBox but for now it leads to a service dependency being set based on the value so should not support expressions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7795) org.jboss.sasl classes still making it into jboss-client.jar

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7795?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7795: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > org.jboss.sasl classes still making it into jboss-client.jar > ------------------------------------------------------------ > > Key: WFLY-7795 > URL: https://issues.jboss.org/browse/WFLY-7795 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 12.0.0.Alpha1 > > > The dependencies should have been removed but maybe this is still coming in as a transitive dependency from elsewhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8250) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8250?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8250: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8250 > URL: https://issues.jboss.org/browse/WFLY-8250 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9267) Upgrade Hibernate Validator to 6.0.3.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9267?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9267: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Upgrade Hibernate Validator to 6.0.3.Final > ------------------------------------------- > > Key: WFLY-9267 > URL: https://issues.jboss.org/browse/WFLY-9267 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9266) Upgrade Hibernate ORM to 5.2.12.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9266?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9266: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Upgrade Hibernate ORM to 5.2.12.Final > ------------------------------------- > > Key: WFLY-9266 > URL: https://issues.jboss.org/browse/WFLY-9266 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9261) Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9261?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9261: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9261 > URL: https://issues.jboss.org/browse/WFLY-9261 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Flavia Rainone > Assignee: Martyn Taylor > Fix For: 12.0.0.Alpha1 > > > When rebooting a cluster node that uses singleton cluster mdbs, we get this error message: > {noformat} > 2017-07-25 16:08:54,426 ERROR [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.HelloWorldMDBQueuedea3e995-713c-11e7-85f2-b8f6b112daf7 on ClusterConnectionImpl@1129705701[nodeUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7, connector=TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101) > 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} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8449: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency, ejb > Fix For: 12.0.0.Alpha1 > > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9417?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9417: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > No default-response-code during deployment sent > ----------------------------------------------- > > Key: WFLY-9417 > URL: https://issues.jboss.org/browse/WFLY-9417 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Nero M > Assignee: Stuart Douglas > Fix For: 12.0.0.Alpha1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10. > When a *.dodeploy file exists during server-start. The Default response code > e.g. > <host name="default-host" alias="localhost" default-response-code="503"> > Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout. > If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete. > (After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms > I think the server should not "hang" during the deployment-time, just like it was on WF10. > Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9415) Add test cases to cover EJB client clustered session creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9415?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9415: ------------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Add test cases to cover EJB client clustered session creation > ------------------------------------------------------------- > > Key: WFLY-9415 > URL: https://issues.jboss.org/browse/WFLY-9415 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 12.0.0.Alpha1 > > > EJB client session creation involves creating a proxy for a SFSB deployed on a remote server, which has the side effect of creating a session instance on the chosen target node. > Whether or not the operation is successful depends on three factors: > * the connections defined in the EJB client configuration > * the server environment in which the client is executing > * any strong affinity set by the client > These tests consider session creation in a clustered environment. The default server environment is a cluster called "ejb" with two nodes, "node-0" and "node-1". > The following test scenarios are covered: > 1. "normal" scenario > * client configuration: points to node-0 > * server environment: module deployed on cluster "ejb" = {node-0, node-1} > 2. "failover" scenario > * client configuration: points to node-0 > * server environment: module deployed on cluster "ejb" = {node-1} > 3. "bad connection" scenario > * client configuration: points to node-2 (non-existent) > * server environment: module deployed on cluster "ejb" = {node-0, node-1} > As mentioned earlier, these tests operate in a single two-node cluster environment. A third singleton, non-clustered node added to the available environment would permit more complex scenarios (where we could test cluster affinity specification more directly). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 October 2017