June 2016 - jboss-jira - Jboss List Archives

[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, 3 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, 3 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, 3 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, 3 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, 3 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, 3 months

1
0
0 / 0

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

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6781: ------------------------------------ You description is still missing some crucial details. Are your nodes running on the same host? If you disable networking on the host, and your nodes are both running on that host, how could failover possibly work? For scenario #2, it is certainly possible that windows does not disconnect the socket used by FD_SOCK (if so, this would be a shortcoming of your VM implementation) - consequently, failures are not detected immediately. However, it should be detected by FD_ALL after it fails to receive a heartbeat response after the given timeout. Third - I have no idea how exactly you've determined that "failover isn't working". Can you be more specific? > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1625) Operation description is not complete in :read-resource-description

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-1625: ----------------------------------- Summary: Operation description is not complete in :read-resource-description Key: WFCORE-1625 URL: https://issues.jboss.org/browse/WFCORE-1625 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha2 Reporter: Jeff Mesnil Assignee: Brian Stansberry The ouput of :read-resource-description is missing some metadata for operations compared to :read-operation-description: {noformat} [domain@localhost:9990 /] /profile=default:read-resource-description(operations=true) { "outcome" => "success", "result" => { "description" => "A named set of subsystem configurations.", ... "operations" => { ... "read-attribute-group-names" => { "operation-name" => "read-attribute-group-names", "description" => "Gets the names of all the attribute groups under the selected resource", "request-properties" => {}, "reply-properties" => { "type" => LIST, "value-type" => STRING } }, ... } [domain@localhost:9990 /] /profile=default:read-operation-description(name=read-attribute-group-names) { "outcome" => "success", "result" => { "operation-name" => "read-attribute-group-names", "description" => "Gets the names of all the attribute groups under the selected resource", "request-properties" => {}, "reply-properties" => { "type" => LIST, "value-type" => STRING }, "read-only" => true, "runtime-only" => true } } {noformat} At least read-only and runtime-only metadata are missing (when they are set on the operation). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6780: --------------------------------- Assignee: Darran Lofthouse (was: Jason Greene) > could not spécify version 3 for ldap connection > ----------------------------------------------- > > Key: WFLY-6780 > URL: https://issues.jboss.org/browse/WFLY-6780 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: cyril leclerc > Assignee: Darran Lofthouse > > HI, > in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error : > Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad' > i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ? > it is a big issue for me -) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-6780: ----------------------------------- What version of WildFly / JDK? > could not spécify version 3 for ldap connection > ----------------------------------------------- > > Key: WFLY-6780 > URL: https://issues.jboss.org/browse/WFLY-6780 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: cyril leclerc > Assignee: Darran Lofthouse > > HI, > in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error : > Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad' > i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ? > it is a big issue for me -) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2016