June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on JGRP-2063: -------------------------------------- Not ready, this needs more thought. I closed the original PR saying: "Hm, I can't pass in any references via after_creation_hook as its just passed as string property. Needs more thought, closing for now." > JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) > ------------------------------------------------------------------------------------ > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Bela Ban > Fix For: 3.6.11, 4.0 > > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla commented on WFLY-6781: ---------------------------------------- By hampering of application functionality, I mean neither the application works as expected on Node1 nor it works as expected on Node2 after we disable the network on Node2. The same issue is seen when we test failover by powering off Node2 using the VMware client although in this case the issue is seen only on windows environment -preeta > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6782?page=com.atlassian.jira.plugin.... ] Radoslav Husar edited comment on WFLY-6782 at 6/28/16 1:50 PM: --------------------------------------------------------------- Functionality was originally introduced in: https://github.com/wildfly/wildfly/commit/72df91913de85b376d0c5d1c4d8e23c... was (Author: rhusar): https://github.com/wildfly/wildfly/commit/72df91913de85b376d0c5d1c4d8e23c... > Unable to add JGroups protocol at a given index via CLI > ------------------------------------------------------- > > Key: WFLY-6782 > URL: https://issues.jboss.org/browse/WFLY-6782 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.Final > > > Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) > 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] > {noformat} > add index is missing in the description, after the fix: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Add a protocol to a protocol stack.", > "request-properties" => { > "add-index" => { > "type" => INT, > "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true > }, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-141) StringIndexOutOfBoundsException throw while formatting log with truncation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-141?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated LOGMGR-141: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1350757 Bugzilla Update: Perform > StringIndexOutOfBoundsException throw while formatting log with truncation > -------------------------------------------------------------------------- > > Key: LOGMGR-141 > URL: https://issues.jboss.org/browse/LOGMGR-141 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > > When value in left-justified field is longer than maximum width following exception is thrown: > {code} > java.lang.StringIndexOutOfBoundsException > at java.lang.AbstractStringBuilder.delete(AbstractStringBuilder.java:733) > at java.lang.StringBuilder.delete(StringBuilder.java:244) > at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:212) > at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:83) > at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:32) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:46) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:302) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) > at org.jboss.logmanager.Logger.logRaw(Logger.java:719) > at org.jboss.logmanager.Logger.log(Logger.java:670) > at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50) > at org.jboss.logging.Logger.logf(Logger.java:2096) > {code} > Steps to Reproduce: > 1. Configure formatter with left-justified field with maximum width: > {code} > /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=formatter,value="%d{HH:mm:ss,SSS} %-5p [%c{1.}] [%-20.-20t] %s%E%n") > {code} > (in the example above thread name should be truncated to 20 characters, left-justified) > 2. Write a log from a thread which has a name containg 21 characters or more. During server startup logs are written by "MSC service thread 1-7" thread. > It seems there is an error in {{org.jboss.logmanager.formatters.Formatters()}} class, line 212. There is: > {code:java} > builder.delete(oldLen, overflow + 1); > {code} > but should be: > {code:java} > builder.delete(oldLen, oldLen + overflow); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-141) StringIndexOutOfBoundsException throw while formatting log with truncation

by James Perkins (JIRA)

James Perkins created LOGMGR-141: ------------------------------------ Summary: StringIndexOutOfBoundsException throw while formatting log with truncation Key: LOGMGR-141 URL: https://issues.jboss.org/browse/LOGMGR-141 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins When value in left-justified field is longer than maximum width following exception is thrown: {code} java.lang.StringIndexOutOfBoundsException at java.lang.AbstractStringBuilder.delete(AbstractStringBuilder.java:733) at java.lang.StringBuilder.delete(StringBuilder.java:244) at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:212) at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:83) at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:32) at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:46) at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:302) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:310) at org.jboss.logmanager.Logger.logRaw(Logger.java:719) at org.jboss.logmanager.Logger.log(Logger.java:670) at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50) at org.jboss.logging.Logger.logf(Logger.java:2096) {code} Steps to Reproduce: 1. Configure formatter with left-justified field with maximum width: {code} /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=formatter,value="%d{HH:mm:ss,SSS} %-5p [%c{1.}] [%-20.-20t] %s%E%n") {code} (in the example above thread name should be truncated to 20 characters, left-justified) 2. Write a log from a thread which has a name containg 21 characters or more. During server startup logs are written by "MSC service thread 1-7" thread. It seems there is an error in {{org.jboss.logmanager.formatters.Formatters()}} class, line 212. There is: {code:java} builder.delete(oldLen, overflow + 1); {code} but should be: {code:java} builder.delete(oldLen, oldLen + overflow); {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6745) Support for SSL out of the box

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6745?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6745: ---------------------------------------- Perhaps, but Darran may have other things he wants to do beyond what is covered by the work Stuart did for this issue, which is the functionality discussed in http://lists.jboss.org/pipermail/wildfly-dev/2016-June/005040.html. > Support for SSL out of the box > ------------------------------ > > Key: WFLY-6745 > URL: https://issues.jboss.org/browse/WFLY-6745 > Project: WildFly > Issue Type: Feature Request > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6788) Fix typo in batch-jberet for capability registry

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-6788?page=com.atlassian.jira.plugin.... ] Cheng Fang reassigned WFLY-6788: -------------------------------- Assignee: James Perkins (was: Cheng Fang) > Fix typo in batch-jberet for capability registry > ------------------------------------------------ > > Key: WFLY-6788 > URL: https://issues.jboss.org/browse/WFLY-6788 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: Claudio Miranda > Assignee: James Perkins > Priority: Trivial > > There is a typo in org.wildfy.batch.job.repository, a missing letter l. > https://github.com/wildfly/wildfly/blob/master/batch/extension-jberet/src... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-710) Problem when loading a jar in kie workbench

by Nicolas Heron (JIRA)

[ https://issues.jboss.org/browse/DROOLS-710?page=com.atlassian.jira.plugin... ] Nicolas Heron closed DROOLS-710. -------------------------------- Resolution: Done > Problem when loading a jar in kie workbench > -------------------------------------------- > > Key: DROOLS-710 > URL: https://issues.jboss.org/browse/DROOLS-710 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4 > Environment: Tomcat 7 > Reporter: Nicolas Heron > Assignee: Mark Proctor > Attachments: loyalty-model-0.5.1-SNAPSHOT.jar, Problem.txt > > > I am uploading that jar in the artifact repository of the kid-wb. I am using version 6.2.0.CR4. > I have defined the variable that point to the maven installation and the maven repo as follows. > CATALINA_OPTS="-Xms1536m -Xmx6536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=556m -XX:+DisableExplicitGC -Dhibernate.dialect=org.hibernate.dialect.PostgreSQLDialect -Dorg.kie.example.repositories=/home/kie-samples -Dorg.kie.example=true -Dorg.uberfire.nio.git.daemon.host=0.0.0.0 -Dorg.guvnor.m2repo.dir=$M2_HOME -Dorg.uberfire.nio.git.dir=/home/niodir -Djava.security.auth.login.config=/home/tomcat7/apache-tomcat-7.0/conf/jaasConfig -Dbtm.root=/home/bittronix -Dbitronix.tm.configuration=/home/tomcat7/apache-tomcat-7.0/conf/btm-config.properties -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchroniz > I am running on tomcat7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6788) Fix typo in batch-jberet for capability registry

by Claudio Miranda (JIRA)

Claudio Miranda created WFLY-6788: ------------------------------------- Summary: Fix typo in batch-jberet for capability registry Key: WFLY-6788 URL: https://issues.jboss.org/browse/WFLY-6788 Project: WildFly Issue Type: Bug Components: Batch Reporter: Claudio Miranda Assignee: Cheng Fang Priority: Trivial There is a typo in org.wildfy.batch.job.repository, a missing letter l. https://github.com/wildfly/wildfly/blob/master/batch/extension-jberet/src... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla commented on WFLY-6781: ---------------------------------------- Sure. We have wildfly horizontal cluster with 2 topologies. A Horizontal cluster have the nodes on different VMs. Topologies:- 1. Two VM Wildfly horizontal cluster where Node1 is on one VM and Node2 is on another VM. 2. Four VM Wildfly horizontal cluster where we have 4 nodes on 4 different VMs. We work for Cisco Systems. Recently the failover was tested for only the 2 VM cluster where there are 2 Nodes on 2 seperate VMs. Our QA has tried testing the failover with the scenarios I listed in description. Where I have indicated that the failover did not work as expected, the consequence was that it hampered the application functionality, for the entire cluster setup. Thanks, Preeta > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016