November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10864) MP Health reports UP when there is port collision for port 8080

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-10864?page=com.atlassian.jira.plugin... ] Lin Gao commented on WFLY-10864: -------------------------------- Are we going to check the HTTP port only or should we consider others as well defined in the socket-bindings like HTTPS, AJP, etc? > MP Health reports UP when there is port collision for port 8080 > --------------------------------------------------------------- > > Key: WFLY-10864 > URL: https://issues.jboss.org/browse/WFLY-10864 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > MP Health reports UP when there is port collision for port 8080. > I have simple python app to acquire port 8080 and once it runs I start WF server > {code} > import SimpleHTTPServer > import SocketServer > PORT = 8080 > Handler = SimpleHTTPServer.SimpleHTTPRequestHandler > httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler) > print "serving at port", PORT > httpd.serve_forever() > {code} > WF reports Address already in use /127.0.0.1:8080, deployments are not deployed. > Accessing http://localhost:9990/health/ reports "outcome":"UP" > I think this is wrong and DOWN should be reported. > Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly. > I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3354?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3354: ------------------------------------- [~manstis] I remember commit you referenced above, however if I remember correctly, there was problem to click any cell, here I reported just empty cells, is it really the same problem? > [GDST] Not able to edit empty cell > ---------------------------------- > > Key: DROOLS-3354 > URL: https://issues.jboss.org/browse/DROOLS-3354 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.15.0.Final > > Attachments: Screenshot from 2018-11-26 09-52-42.png > > > User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: > {code} > Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null > {code} > Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11415) It should use Artemis' SQLProvider implementation

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFLY-11415?page=com.atlassian.jira.plugin... ] Chao Wang reassigned WFLY-11415: -------------------------------- Assignee: Chao Wang (was: Jeff Mesnil) > It should use Artemis' SQLProvider implementation > ------------------------------------------------- > > Key: WFLY-11415 > URL: https://issues.jboss.org/browse/WFLY-11415 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > Fix For: 15.0.0.Beta1 > > > During development and integration of JDBC persistence store into WildFly, the custom implementation of SQLProvider interface \[1\] was developed for WildFly use case. The reason was that WildFly used Artemis 1.x which was at that time maintenance branch and thus development of new features was focused on 2.x branch. > In the meantime, the code has been donated to Artemis and backported in Artemis 1.5.5.jbossorg-012. > We can now remove the implementation in WildFly code base and use the Artemis one instead. > \[1\] https://github.com/apache/activemq-artemis/blob/f2b5114af8dd505e3c5c3efc1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11415) It should use Artemis' SQLProvider implementation

by Chao Wang (Jira)

Chao Wang created WFLY-11415: -------------------------------- Summary: It should use Artemis' SQLProvider implementation Key: WFLY-11415 URL: https://issues.jboss.org/browse/WFLY-11415 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 13.0.0.Final Reporter: Chao Wang Assignee: Jeff Mesnil Fix For: 15.0.0.Beta1 During development and integration of JDBC persistence store into WildFly, the custom implementation of SQLProvider interface \[1\] was developed for WildFly use case. The reason was that WildFly used Artemis 1.x which was at that time maintenance branch and thus development of new features was focused on 2.x branch. In the meantime, the code has been donated to Artemis and backported in Artemis 1.5.5.jbossorg-012. We can now remove the implementation in WildFly code base and use the Artemis one instead. \[1\] https://github.com/apache/activemq-artemis/blob/f2b5114af8dd505e3c5c3efc1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11411) ModuleClassLoader fails with ClassNotFoundException when class in a jar file

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11411?page=com.atlassian.jira.plugin... ] Yeray Borges reassigned WFLY-11411: ----------------------------------- Assignee: Yeray Borges > ModuleClassLoader fails with ClassNotFoundException when class in a jar file > ---------------------------------------------------------------------------- > > Key: WFLY-11411 > URL: https://issues.jboss.org/browse/WFLY-11411 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 11.0.0.Final, 14.0.0.Final > Environment: Wildfly 11, 14, Java 1.8, Windows 10 > Reporter: Karl Nicholas > Assignee: Yeray Borges > Priority: Major > Attachments: JaxRsActivator.java, RestSever.java > > > Simple REST service with Application activator in project and Rest Server in another project with jar file fails to load. > Works okay with EAR project structure but not with simpler WAR project structure. > Caused by: java.lang.ClassNotFoundException: rest.service.server.RestSever from [Module "deployment.restserver7.war" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3354?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3354: ----------------------------------- Affects Version/s: (was: 7.15.0.Final) > [GDST] Not able to edit empty cell > ---------------------------------- > > Key: DROOLS-3354 > URL: https://issues.jboss.org/browse/DROOLS-3354 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.15.0.Final > > Attachments: Screenshot from 2018-11-26 09-52-42.png > > > User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: > {code} > Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null > {code} > Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3354?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3354: ----------------------------------- Fix Version/s: 7.15.0.Final > [GDST] Not able to edit empty cell > ---------------------------------- > > Key: DROOLS-3354 > URL: https://issues.jboss.org/browse/DROOLS-3354 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.15.0.Final > > Attachments: Screenshot from 2018-11-26 09-52-42.png > > > User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: > {code} > Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null > {code} > Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3354?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3354: ----------------------------------- Story Points: 2 Sprint: 2018 Week 45-47 > [GDST] Not able to edit empty cell > ---------------------------------- > > Key: DROOLS-3354 > URL: https://issues.jboss.org/browse/DROOLS-3354 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.15.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-26 09-52-42.png > > > User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: > {code} > Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null > {code} > Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3354: ----------------------------------- Summary: [GDST] Not able to edit empty cell Key: DROOLS-3354 URL: https://issues.jboss.org/browse/DROOLS-3354 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.15.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-11-26 09-52-42.png User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: {code} Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null {code} Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9855) [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars

by Tomaz Cerar (Jira)

[ https://issues.jboss.org/browse/WFLY-9855?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-9855: ----------------------------------- No need to remove them, just make sue that classes that are in same package are in same jar. That should not be an issue for CP. It would get two jars updated instead just one. But should work just fine as most of this jars are always added together to classpath > [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars > ----------------------------------------------------------------------------- > > Key: WFLY-9855 > URL: https://issues.jboss.org/browse/WFLY-9855 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > Assignee: Tomas Hofman > Priority: Critical > > Currently if you have > jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar > on your module path, jvm complains as both jars export package org.jboss.security.negotiation.spnego > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package org.jboss.security.negotiation.spnego to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 November 2018