April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-232) Deployment fails when Dependencies is empty in a jars manifest

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-232?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-232: ---------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1539985|https://bugzilla.redhat.com/show_bug.cgi?id=1539985] from POST to MODIFIED > Deployment fails when Dependencies is empty in a jars manifest > -------------------------------------------------------------- > > Key: WFLY-232 > URL: https://issues.jboss.org/browse/WFLY-232 > Project: WildFly > Issue Type: Enhancement > Reporter: Gábor Farkas > Assignee: Stuart Douglas > Priority: Major > Fix For: 8.0.0.Alpha1 > > Attachments: empty-manifest.ear > > > I have a WAR, which produces the following error on deployment: > Caused by: java.lang.IllegalArgumentException: Empty module specification > at org.jboss.modules.ModuleIdentifier.fromString(ModuleIdentifier.java:169) [jboss-modules.jar:1.1.1.GA] > at org.jboss.as.server.deployment.module.ManifestDependencyProcessor.deploy(ManifestDependencyProcessor.java:83) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > I found that my WAR contains a jar in WEB-INF/lib that has empty dependencies defined in its manifest. More exactly it's "Dependencies: ", so the colon is followed by a space character before the new line characters. The ManifestDependencyProcessor parses this as one dependency, the name of which is the empty string. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2562) NullPointerException when removing configuration history

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-2562?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2562: ------------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1434141|https://bugzilla.redhat.com/show_bug.cgi?id=1434141] from POST to MODIFIED > NullPointerException when removing configuration history > -------------------------------------------------------- > > Key: WFCORE-2562 > URL: https://issues.jboss.org/browse/WFCORE-2562 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 2.1.0.Final > Reporter: Dennis Reed > Assignee: Ken Wills > Priority: Major > Fix For: 3.0.0.Beta12 > > > org.jboss.as.controller.persistence.ConfigurationFile#deleteRecursively is missing error checking. > If an I/O error occurs while listing the directory contents (file permission error/etc) it still tries to use the listing and gets a NullPointerException. > This method is used while removing old configuration history directories during boot, and the NullPointerException causes the EAP boot to abort. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2340) SocketFactory missing createSocketChannel(String service_name) and close(SocketChannel)

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2340?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2340: --------------------------- Issue Type: Patch (was: Bug) Fix Version/s: 4.1.0 > SocketFactory missing createSocketChannel(String service_name) and close(SocketChannel) > --------------------------------------------------------------------------------------- > > Key: JGRP-2340 > URL: https://issues.jboss.org/browse/JGRP-2340 > Project: JGroups > Issue Type: Patch > Affects Versions: 4.0.19 > Reporter: Paul Ferraro > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > NioConnection should defer to the SocketFactory to create (with a service_name) and close its SocketChannel. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2339) SocketFactory missing close(ServerSocketChannel)

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2339?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2339: --------------------------- Fix Version/s: 4.1.0 > SocketFactory missing close(ServerSocketChannel) > ------------------------------------------------ > > Key: JGRP-2339 > URL: https://issues.jboss.org/browse/JGRP-2339 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Paul Ferraro > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > JGroups SocketFactory contains methods for creating named ServerSocketChannels, however, there is no corresponding close(ServerSocketChannel) method. > WF relies on the SocketFactory to register JGroups sockets with its SocketBindingManager, so that the management layer can report which sockets are connected, to which address/port are they are bound, etc. The close(...) methods are necessary to unregister from the SocketBindingManager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11007) Using OpenShift generated certificates and client auth cause TLS errors

by Sebastian Laskawiec (Jira)

[ https://issues.jboss.org/browse/WFLY-11007?page=com.atlassian.jira.plugin... ] Sebastian Laskawiec commented on WFLY-11007: -------------------------------------------- [~mchoma] I might be totally wrong, but I *think* {{oc cluster up}} copies all CAs from the host it's running on. I might be the case, that the list is particularly long on my local box. That could explain the situation where everything works on your box, but doesn't on mine. Could you please double check this with my Docker reproducer? https://github.com/slaskawi/WFLY-11007 > Using OpenShift generated certificates and client auth cause TLS errors > ----------------------------------------------------------------------- > > Key: WFLY-11007 > URL: https://issues.jboss.org/browse/WFLY-11007 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 13.0.0.Final > Reporter: Sebastian Laskawiec > Assignee: Stuart Douglas > Priority: Major > > h2. Summary > It seems that when using OpenShift generated certificates and client auth (with {{want-client-auth="true"}}) the TLS handshake fails with {{RECV TLSv1.2 ALERT: fatal, record_overflow}} message. > h2. Explanation > I'm using {{oc cluster up}} and deploying Keycloak (WF 13 based) on OpenShift local cluster using the (1) template. The service in the the template uses OpenShift generated certificates ({{"service.alpha.openshift.io/serving-cert-secret-name": "keycloak-x509-https-secret"}}). Both files are mounted in the Keycloak pod and translated into keystore and truststore (see the configuration after the transformation (2)). Once the pod is up and running, I'm issuing a {{curl}} command as shown in (3). {{curl}} fails saying that {{* error:1408F092:SSL routines:ssl3_get_record:data length too long}}. The server logs with TLS Handshake debugging turned on might be found here (4). As shown in the link, the server has written {{16384}} bytes. > I also did a test with manually created certificates (5). The result might be found here (6). As shown in the link, we've written {{16050}} bytes instead of {{16384}} and the handshake was successful. > h2. Possible solution > Perhaps we should cut the list CAs transmitted by the server when asking for client auth when it exceeds certain number of bytes. It would be helpful to write a warn message too. > Links: > - (1) Keycloak OCP Template https://gist.github.com/slaskawi/57ed810a7109a02a9d884b61ce2e7f13 > - (2) Transformed configuration https://gist.github.com/slaskawi/92aead6c519b867621129b640b4a3c88 > - (3) curl command https://gist.github.com/slaskawi/3bc32b8e96c2499cb7b48c3c5cb28616 > - (4) https://gist.github.com/slaskawi/b6477fe3cd65890c879cfe6f95359450#file-lo... > - (5) Keycloak and OpenShift integration demo https://github.com/keycloak/openshift-integration/blob/master/install-key... > - (6) https://gist.github.com/slaskawi/7fd87e1f2e6c4faf657d9e8289ed3392#file-lo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11928) Remove note about log4j warning from jaxws-* quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11928?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11928: ----------------------------------- Description: Since WFLY-11209 is fixed, we can remove this part of README from jaxws-* quickstarts: {code:java} You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. [INFO] Could not find log4j.xml configuration, logging to console. [INFO] [INFO] TODO! Cheek SOAP 1.2 extension [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). [ERROR] log4j:WARN Please initialize the log4j system properly. [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. {code} was: Since WFLY-11209v is fixed, we can remove this part of README from jaxws-* quickstarts: {code:java} You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. [INFO] Could not find log4j.xml configuration, logging to console. [INFO] [INFO] TODO! Cheek SOAP 1.2 extension [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). [ERROR] log4j:WARN Please initialize the log4j system properly. [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. {code} > Remove note about log4j warning from jaxws-* quickstarts > -------------------------------------------------------- > > Key: WFLY-11928 > URL: https://issues.jboss.org/browse/WFLY-11928 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Since WFLY-11209 is fixed, we can remove this part of README from jaxws-* quickstarts: > {code:java} > You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. > [INFO] Could not find log4j.xml configuration, logging to console. > [INFO] > [INFO] TODO! Cheek SOAP 1.2 extension > [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). > [ERROR] log4j:WARN Please initialize the log4j system properly. > [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11928) Remove note about log4j warning from jaxws-* quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11928?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11928: ----------------------------------- Description: Since WFLY-11209v is fixed, we can remove this part of README from jaxws-* quickstarts: {code:java} You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. [INFO] Could not find log4j.xml configuration, logging to console. [INFO] [INFO] TODO! Cheek SOAP 1.2 extension [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). [ERROR] log4j:WARN Please initialize the log4j system properly. [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. {code} was: Since JBEAP-15215 is fixed, we can remove this part of README from jaxws-* quickstarts: {code:java} You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. [INFO] Could not find log4j.xml configuration, logging to console. [INFO] [INFO] TODO! Cheek SOAP 1.2 extension [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). [ERROR] log4j:WARN Please initialize the log4j system properly. [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. {code} > Remove note about log4j warning from jaxws-* quickstarts > -------------------------------------------------------- > > Key: WFLY-11928 > URL: https://issues.jboss.org/browse/WFLY-11928 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Since WFLY-11209v is fixed, we can remove this part of README from jaxws-* quickstarts: > {code:java} > You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. > [INFO] Could not find log4j.xml configuration, logging to console. > [INFO] > [INFO] TODO! Cheek SOAP 1.2 extension > [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). > [ERROR] log4j:WARN Please initialize the log4j system properly. > [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11928) Remove note about log4j warning from jaxws-* quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11928?page=com.atlassian.jira.plugin... ] Eduardo Martins moved JBEAP-16648 to WFLY-11928: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11928 (was: JBEAP-16648) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: 16.0.0.Final (was: 7.2.0.GA.CR1) > Remove note about log4j warning from jaxws-* quickstarts > -------------------------------------------------------- > > Key: WFLY-11928 > URL: https://issues.jboss.org/browse/WFLY-11928 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Since JBEAP-15215 is fixed, we can remove this part of README from jaxws-* quickstarts: > {code:java} > You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin plugin that generates source files based on the WSDL. You can ignore these warnings. > [INFO] Could not find log4j.xml configuration, logging to console. > [INFO] > [INFO] TODO! Cheek SOAP 1.2 extension > [ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils). > [ERROR] log4j:WARN Please initialize the log4j system properly. > [ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 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 April 2019