June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-6620: --------------------------------------- This is the Narayana commit https://github.com/jbosstm/narayana/pull/1005/commits/740ddea899f01d0ce02... > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2072) UFC and MFC headers get mixed up

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2072?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2072: --------------------------- Fix Version/s: 3.6.10 4.0 > UFC and MFC headers get mixed up > -------------------------------- > > Key: JGRP-2072 > URL: https://issues.jboss.org/browse/JGRP-2072 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.9 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 3.6.10, 4.0 > > > {noformat} > 11:24:19,178 TRACE (OOB-10,NodeD-30623:[]) [MFC] NodeA-6644 used 4969 credits, 396763 remaining > 11:24:19,238 TRACE (OOB-10,NodeD-30623:[]) [MFC] sending 603237 credits to NodeA-6644 > 11:24:19,238 TRACE (OOB-10,NodeD-30623:[]) [UDP] NodeD-30623: sending msg to NodeA-6644, src=NodeD-30623, headers are MFC: REPLENISH, UNICAST3: DATA, seqno=8825, TP: [cluster_name=default] > 11:24:19,246 TRACE (INT-1,NodeA-6644:[]) [UDP] NodeA-6644: received [dst: NodeA-6644, src: NodeD-30623 (3 headers), size=8 bytes, flags=OOB|DONT_BUNDLE|INTERNAL], headers are UFC: REPLENISH, UNICAST3: DATA, seqno=8825, TP: [cluster_name=default] > 11:24:19,246 TRACE (INT-1,NodeA-6644:[]) [UFC] received 603237 credits from NodeD-30623, old credits: 938772, new credits: 1000000 > {noformat} > {noformat} > 15:20:14,596 TRACE (OOB-44,NodeC-64981:[]) [UFC] NodeA-12977 used 2305 credits, 798175 remaining > 15:20:14,614 TRACE (OOB-44,NodeC-64981:[]) [UFC] sending 1201825 credits to NodeA-12977 > 15:20:14,614 TRACE (OOB-44,NodeC-64981:[]) [UDP] NodeC-64981: sending msg to NodeA-12977, src=NodeC-64981, headers are UFC: REPLENISH, UNICAST3: DATA, seqno=34854, TP: [cluster_name=default] > 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [UDP] NodeA-12977: received [dst: NodeA-12977, src: NodeC-64981 (3 headers), size=8 bytes, flags=OOB|DONT_BUNDLE|INTERNAL], headers are MFC: REPLENISH, UNICAST3: DATA, seqno=34854, TP: [cluster_name=default] > 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [UFC] NodeC-64981 used 8 credits, 1859662 remaining > 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [MFC] received 1201825 credits from NodeC-64981, new credits for NodeC-64981: 2000000, min_credits=793978 > {noformat} > UFC/MFC expect their messages to be reliable, so they don't repeat {{REPLENISH}} messages, and the only way to replenish the credits is to send a {{CREDIT_REQUEST}} message. But UFC/MFC only send a credit request after all the threads trying to send a request or response to the affected destination block for {{max_block_time}}. > I was able to reproduce the problem with an Infinispan [micro-benchmark|https://github.com/danberindei/infinispan-microbenchmarks]: a cluster of 4 nodes, a replicated cache, 400 threads writing to the cache. It happens both with JGroups 3.6.9.Final and the latest master. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2072) UFC and MFC headers get mixed up

by Dan Berindei (JIRA)

Dan Berindei created JGRP-2072: ---------------------------------- Summary: UFC and MFC headers get mixed up Key: JGRP-2072 URL: https://issues.jboss.org/browse/JGRP-2072 Project: JGroups Issue Type: Bug Affects Versions: 3.6.9 Reporter: Dan Berindei Assignee: Bela Ban {noformat} 11:24:19,178 TRACE (OOB-10,NodeD-30623:[]) [MFC] NodeA-6644 used 4969 credits, 396763 remaining 11:24:19,238 TRACE (OOB-10,NodeD-30623:[]) [MFC] sending 603237 credits to NodeA-6644 11:24:19,238 TRACE (OOB-10,NodeD-30623:[]) [UDP] NodeD-30623: sending msg to NodeA-6644, src=NodeD-30623, headers are MFC: REPLENISH, UNICAST3: DATA, seqno=8825, TP: [cluster_name=default] 11:24:19,246 TRACE (INT-1,NodeA-6644:[]) [UDP] NodeA-6644: received [dst: NodeA-6644, src: NodeD-30623 (3 headers), size=8 bytes, flags=OOB|DONT_BUNDLE|INTERNAL], headers are UFC: REPLENISH, UNICAST3: DATA, seqno=8825, TP: [cluster_name=default] 11:24:19,246 TRACE (INT-1,NodeA-6644:[]) [UFC] received 603237 credits from NodeD-30623, old credits: 938772, new credits: 1000000 {noformat} {noformat} 15:20:14,596 TRACE (OOB-44,NodeC-64981:[]) [UFC] NodeA-12977 used 2305 credits, 798175 remaining 15:20:14,614 TRACE (OOB-44,NodeC-64981:[]) [UFC] sending 1201825 credits to NodeA-12977 15:20:14,614 TRACE (OOB-44,NodeC-64981:[]) [UDP] NodeC-64981: sending msg to NodeA-12977, src=NodeC-64981, headers are UFC: REPLENISH, UNICAST3: DATA, seqno=34854, TP: [cluster_name=default] 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [UDP] NodeA-12977: received [dst: NodeA-12977, src: NodeC-64981 (3 headers), size=8 bytes, flags=OOB|DONT_BUNDLE|INTERNAL], headers are MFC: REPLENISH, UNICAST3: DATA, seqno=34854, TP: [cluster_name=default] 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [UFC] NodeC-64981 used 8 credits, 1859662 remaining 15:20:14,629 TRACE (INT-1,NodeA-12977:[]) [MFC] received 1201825 credits from NodeC-64981, new credits for NodeC-64981: 2000000, min_credits=793978 {noformat} UFC/MFC expect their messages to be reliable, so they don't repeat {{REPLENISH}} messages, and the only way to replenish the credits is to send a {{CREDIT_REQUEST}} message. But UFC/MFC only send a credit request after all the threads trying to send a request or response to the affected destination block for {{max_block_time}}. I was able to reproduce the problem with an Infinispan [micro-benchmark|https://github.com/danberindei/infinispan-microbenchmarks]: a cluster of 4 nodes, a replicated cache, 400 threads writing to the cache. It happens both with JGroups 3.6.9.Final and the latest master. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/519 > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Environment: JBoss EAP 7.0.0 > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won commented on JBJCA-1320: -------------------------------- Yes, it's right, however, some cases there is no need to specify <connection-property>, now it occurs migration error to EAP 7. WFLY-6198 will give a warning for this like below after merging this. :) {code} 18:46:36,350 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 18:46:36,398 WARN [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-6) WFLYJCA0098: The datasource MySqlDS is using the driver datasource class "com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource", only connection-properties are used for configuration. 18:46:36,440 INFO [stdout] (MSC service thread 1-6) dataSourceClass=com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource 18:46:36,444 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/MySqlDS] {code} > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Environment: JBoss EAP 7.0.0 > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] Lin Gao commented on JBJCA-1320: -------------------------------- Or you can specify the {{<connection-property>}} in the {{datasource}} element: {code:xml} <datasource jndi-name="java:jboss/datasources/MySqlDS" pool-name="MySqlDS"> <connection-property name="url">jdbc:mysql://localhost:3306/mydb</connection-property> <driver>com.mysql</driver> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <pool> <min-pool-size>10</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>true</prefill> </pool> <security> <user-name>root</user-name> <password></password> </security> <statement> <prepared-statement-cache-size>32</prepared-statement-cache-size> <share-prepared-statements/> </statement> </datasource> {code} to make it work > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Environment: JBoss EAP 7.0.0 > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-73) Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-73?page=com.atlassian.jira.plugin.... ] James Perkins updated JBASMP-73: -------------------------------- Fix Version/s: 7.8.Final > Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase > ------------------------------------------------------------------------------------------------ > > Key: JBASMP-73 > URL: https://issues.jboss.org/browse/JBASMP-73 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Reporter: Martin Basovnik > Assignee: James Perkins > Fix For: 7.8.Final > > Attachments: jbasmp-deploy-reproducer.zip > > > If I try to deploy a deployment just after the server reloading it sometimes fails: > {code} > 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" > {code} > https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-73) Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-73?page=com.atlassian.jira.plugin.... ] James Perkins reassigned JBASMP-73: ----------------------------------- Assignee: James Perkins > Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase > ------------------------------------------------------------------------------------------------ > > Key: JBASMP-73 > URL: https://issues.jboss.org/browse/JBASMP-73 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Reporter: Martin Basovnik > Assignee: James Perkins > Attachments: jbasmp-deploy-reproducer.zip > > > If I try to deploy a deployment just after the server reloading it sometimes fails: > {code} > 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" > {code} > https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2016