March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-191) Amend NullPointerException in RegexFilter.isLoggable()

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-191?page=com.atlassian.jira.plugin... ] Yeray Borges reassigned LOGMGR-191: ----------------------------------- Assignee: Toshiya Kobayashi (was: Yeray Borges) > Amend NullPointerException in RegexFilter.isLoggable() > ------------------------------------------------------ > > Key: LOGMGR-191 > URL: https://issues.jboss.org/browse/LOGMGR-191 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 2.1.0.Alpha5 > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Labels: support > > When log message is null, RegexFilter.isLoggable() throws NullPointerException. > https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... > It often results in unexpected outcomes. For example, assuming you have a filter-spec with "not(match(xxx))" to suppress some messages in your logger configuration: > {code:xml} > <subsystem xmlns="urn:jboss:domain:logging:3.0"> > <console-handler name="CONSOLE"> > <level name="INFO"/> > <filter-spec value="not(match("SOME_MESSAGE"))"/> > <formatter> > <named-formatter name="COLOR-PATTERN"/> > </formatter> > </console-handler> > {code} > and an application has a code like this: > {code:java} > try { > ... > } catch (Exception e) { > logger.error(e.getMessage(), e); > } > {code} > "e.getMessage()" could be null. But you want to log the stacktrace 'e' anyway. > In this case, NullPointerException is thrown from RegexFilter and reaches to LoggerNode and disappears. ConsoleHandler cannot publish the log at all. > https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... > I think 'null' message should simply return 'false' in RegexFilter.isLoggable(). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2255) [DMN designer] Node labels move between savings

by Kirill Gaevskii (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2255?page=com.atlassian.jira.plugi... ] Kirill Gaevskii updated DROOLS-2255: ------------------------------------ Sprint: 2018 Week 09-10 > [DMN designer] Node labels move between savings > ----------------------------------------------- > > Key: DROOLS-2255 > URL: https://issues.jboss.org/browse/DROOLS-2255 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Wagner Scholl Lemos > Priority: Critical > Labels: Stunner > Attachments: after-save.png, before-save.png > > > The attachments shows DMN diagram before and after saving, it can be seen that node labels moved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2255) [DMN designer] Node labels move between savings

by Kirill Gaevskii (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2255?page=com.atlassian.jira.plugi... ] Kirill Gaevskii updated DROOLS-2255: ------------------------------------ Priority: Critical (was: Minor) > [DMN designer] Node labels move between savings > ----------------------------------------------- > > Key: DROOLS-2255 > URL: https://issues.jboss.org/browse/DROOLS-2255 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Roger Martínez > Priority: Critical > Labels: Stunner > Attachments: after-save.png, before-save.png > > > The attachments shows DMN diagram before and after saving, it can be seen that node labels moved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2255) [DMN designer] Node labels move between savings

by Kirill Gaevskii (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2255?page=com.atlassian.jira.plugi... ] Kirill Gaevskii reassigned DROOLS-2255: --------------------------------------- Assignee: Wagner Scholl Lemos (was: Roger Martínez) > [DMN designer] Node labels move between savings > ----------------------------------------------- > > Key: DROOLS-2255 > URL: https://issues.jboss.org/browse/DROOLS-2255 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Wagner Scholl Lemos > Priority: Critical > Labels: Stunner > Attachments: after-save.png, before-save.png > > > The attachments shows DMN diagram before and after saving, it can be seen that node labels moved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2255) [DMN designer] Node labels move between savings

by Kirill Gaevskii (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2255?page=com.atlassian.jira.plugi... ] Kirill Gaevskii commented on DROOLS-2255: ----------------------------------------- I guess this issue is related to [~josephblt] is doing about Labels in lienzo. > [DMN designer] Node labels move between savings > ----------------------------------------------- > > Key: DROOLS-2255 > URL: https://issues.jboss.org/browse/DROOLS-2255 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Roger Martínez > Priority: Minor > Labels: Stunner > Attachments: after-save.png, before-save.png > > > The attachments shows DMN diagram before and after saving, it can be seen that node labels moved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ] Jive JIRA Integration updated WFCORE-3667: ------------------------------------------ Forum Reference: https://developer.jboss.org/message/980862#980862 > Wildfly 12 : jboss-cli.sh in infinite loop > ------------------------------------------- > > Key: WFCORE-3667 > URL: https://issues.jboss.org/browse/WFCORE-3667 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: ubuntu 16.06 lxd container > java version "1.8.0_161" oracle > v12 migrated from v11 > Reporter: Gaétan QUENTIN > Assignee: Jean-Francois Denise > Priority: Critical > Labels: regression > Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt > > > i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12: > > wildfly@java2:/opt/Wildfly$ ls -la > drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration > drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays > drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts > drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final > drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final > lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final > > > my wildfly management console is on 172.20.12.192. > v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip. > > > with wildfly-current link on -> wildfly-11.0.0.Final: > > this works perfectly: > (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990) > > > with wildfly-current -> wildfly-12.0.0.Final: > this go in infinite loop until crash : > (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990) > > output: > > '[standalone@172.20.12.192:9990' is not a valid operation name. > [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name. > ''[standalone@172.20.12.192:9990'' is not a valid operation name. > [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name. > '[standalone@172.20.12.192:9990' is not a valid operation name. > [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name. > ''''[standalone@172.20.12.192:9990'''' is not a valid operation name. > [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name. > '[standalone@172.20.12.192:9990' is not a valid operation name. > [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name. > ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name. > attached is a strace capture file (one of thousands) of jboss-cli . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-51) Cuccushift PR to Openshift QE

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-51?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo updated SWSQE-51: ----------------------------------------- Issue Type: Task (was: Bug) > Cuccushift PR to Openshift QE > ----------------------------- > > Key: SWSQE-51 > URL: https://issues.jboss.org/browse/SWSQE-51 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-51) Cuccushift PR to Openshift QE

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-51?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo reassigned SWSQE-51: -------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Cuccushift PR to Openshift QE > ----------------------------- > > Key: SWSQE-51 > URL: https://issues.jboss.org/browse/SWSQE-51 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-31) QE Git Repository for SWS

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-31?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo updated SWSQE-31: ----------------------------------------- Team: Infrastructure > QE Git Repository for SWS > -------------------------- > > Key: SWSQE-31 > URL: https://issues.jboss.org/browse/SWSQE-31 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9961) [JDK9+] @WebListener and Spring WebApplicationInitializer not working (JDK8 OK!)

by cnsgithub cnsgithub (JIRA)

[ https://issues.jboss.org/browse/WFLY-9961?page=com.atlassian.jira.plugin.... ] cnsgithub cnsgithub edited comment on WFLY-9961 at 3/6/18 7:32 AM: ------------------------------------------------------------------- The jar introducing this error is jandex 2.0.4 Reverting to 2.0.3 fixes the issue! Created Issue for JANDEX: https://issues.jboss.org/browse/JANDEX-45 was (Author: pcom.progweb): The jar introducing this error is jandex 2.0.4 Reverting to 2.0.3 fixes the issue! > [JDK9+] @WebListener and Spring WebApplicationInitializer not working (JDK8 OK!) > -------------------------------------------------------------------------------- > > Key: WFLY-9961 > URL: https://issues.jboss.org/browse/WFLY-9961 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 12.0.0.Final > Reporter: cnsgithub cnsgithub > Assignee: Stuart Douglas > Priority: Blocker > > After upgrading to WFLY 12 Final, the WebApplicationInitializer class residing in the *.war classes Folder is no longer being detected when built with JDK 9. However with JDK 1.8 it works as expected. > With WFLY 11, both variants JDK9, and JDK1.8 Build were working. > {code:java} > package de.test; > import javax.servlet.ServletContext; > import javax.servlet.ServletException; > import org.springframework.web.WebApplicationInitializer; > public class MyWebApplicationInitializer implements WebApplicationInitializer { > @Override > public void onStartup(ServletContext container) throws ServletException { > System.out.println("!!!!!!!!!!!!!! ;-) !!!!!!!!!!!!"); > } > } > {code} > Maybe(!) related to this: https://issues.jboss.org/browse/WFLY-9081 > Even more serious: the @WebListener doesn't seem to be recognized with JDK9 as well: > {code:java} > package de.test; > import javax.servlet.ServletContextEvent; > import javax.servlet.ServletContextListener; > import javax.servlet.annotation.WebListener; > import javax.servlet.http.HttpSessionEvent; > import javax.servlet.http.HttpSessionIdListener; > import javax.servlet.http.HttpSessionListener; > @WebListener > public class MyWebListener implements ServletContextListener, HttpSessionIdListener, HttpSessionListener { > @Override > public void contextInitialized(ServletContextEvent event) { > System.out.println("contextInitialized !!!!!!!! I'm only working when i was built with JDK8"); > } > > @Override > public void sessionIdChanged(HttpSessionEvent arg0, String arg1) { > // TODO Auto-generated method stub > > } > } > {code} > The actual error seems to happen quite early: JBossWebMetaData -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 March 2018