October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-5441?page=com.atlassian.jira.plugin.... ] Richard Janík updated WFLY-5441: -------------------------------- Priority: Minor (was: Major) > Received unsolicited state from node X for segment Y of cache Z > --------------------------------------------------------------- > > Key: WFLY-5441 > URL: https://issues.jboss.org/browse/WFLY-5441 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Minor > > Hi, > we're occasionally seeing these warnings in the server logs: > {code} > [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar > ... > [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node. > {code} > The warnings seem to be harmless. > This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-303) Verify compatibility with RFC7617 "The 'Basic' HTTP Authentication Scheme"

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-303: ------------------------------------ Summary: Verify compatibility with RFC7617 "The 'Basic' HTTP Authentication Scheme" Key: ELY-303 URL: https://issues.jboss.org/browse/ELY-303 Project: WildFly Elytron Issue Type: Task Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Alpha1 This RFC has now reached the stage of being a proposed standard. https://www.rfc-editor.org/info/rfc7617 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z

by Richard Janík (JIRA)

Richard Janík created WFLY-5441: ----------------------------------- Summary: Received unsolicited state from node X for segment Y of cache Z Key: WFLY-5441 URL: https://issues.jboss.org/browse/WFLY-5441 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Richard Janík Assignee: Paul Ferraro Hi, we're occasionally seeing these warnings in the server logs: {code} [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar ... [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node. {code} The warnings seem to be harmless. This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5432) Wildfly SOAP webservice causes JVM crash

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-5432?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-5432: --------------------------------------- To be honest, I've been thinking hardware was to be blamed too, just wanted to be sure I'm running the same test you are. If you can try running on a different host, please let us know the findings. > Wildfly SOAP webservice causes JVM crash > ---------------------------------------- > > Key: WFLY-5432 > URL: https://issues.jboss.org/browse/WFLY-5432 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.1.Final, 10.0.0.CR2 > Environment: Tested on Mac OSX 10.10.2, jdk 1.8.60, wildfly 9.0.1. Final / 10.cr2 > Also tested on Centos 6.5, jdk 1.7.51, wildfly 9.0.1. Final > Reporter: Davide Marchetti > Assignee: Alessio Soldano > Priority: Blocker > Labels: crash, jvm, soap, webservice > Attachments: SOAPTest.war > > > The JVM crashes with either a sigsegv or sigbus error when performing a SOAP load test. > The error printed is: > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f5da922afb8, pid=75645, tid=140039627204352 > # > # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_15_01_39-b00) > # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # J org.apache.cxf.message.ExchangeImpl.get(Ljava/lang/Class;)Ljava/lang/Object; > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > > # > # If you would like to submit a bug report, please include > # instructions on how to reproduce the bug and visit: > # 15:56:03,314 INFO [stdout] (default task-17) Submitted order request received with transId: <XXXXX>, opId: <SCO>, ... > http://icedtea.classpath.org/bugzilla > # > The webservice does nothing, just a System.out.print("xxxxx"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-934) Persistence unit tests - DB2 default schema not specified

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-934: ------------------------------------ Summary: Persistence unit tests - DB2 default schema not specified Key: DROOLS-934 URL: https://issues.jboss.org/browse/DROOLS-934 Project: Drools Issue Type: Bug Reporter: Tibor Zimányi Assignee: Mark Proctor Priority: Minor Unit tests in drools-persistence-jpa don't work on DB2 database system because there isn't specified DB schema in tests. Things needed to be done: - hibernate.default_schema property set in persistence.xml - schema should be set in PersistenceUtil, when creating data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-301) SetKeyStoreCredentialAuthenticationConfiguration does not translate passwords before using them

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-301?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-301. ----------------------------- Resolution: Done > SetKeyStoreCredentialAuthenticationConfiguration does not translate passwords before using them > ----------------------------------------------------------------------------------------------- > > Key: ELY-301 > URL: https://issues.jboss.org/browse/ELY-301 > Project: WildFly Elytron > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Alpha1 > > > See description. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5440) undertow http misconfiguration is not correctly reported

by Ochieng Marembo (JIRA)

Ochieng Marembo created WFLY-5440: ------------------------------------- Summary: undertow http misconfiguration is not correctly reported Key: WFLY-5440 URL: https://issues.jboss.org/browse/WFLY-5440 Project: WildFly Issue Type: Feature Request Components: EJB, JMS, JMX, Remoting, Web (Undertow) Affects Versions: 9.0.1.Final Environment: - wildfly 9.0.1.Final - oracle jdk8_u45 Reporter: Ochieng Marembo Assignee: Jeff Mesnil Priority: Minor With a misconfigured http-listener, wildfly boot-up reports unrelated problem: {noformat} <http-listener name="non-default-listener" socket-binding="http" redirect-socket="https"/> {noformat} The following boot-up process does not reveal the underlying undertow issue of no 'default' http-listener: {code:java} 11:06:43,307 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.jsr77.ejb"], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] }} 11:06:43,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default") ]) - failure description: { "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.http-upgrade-registry.default]"], "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.messaging.default.jms.manager"], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] } } 11:06:43,317 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => [ "jboss.ejb.default-local-ejb-receiver-service", "jboss.ejb3.ejbClientContext.default", "jboss.ejb3.localEjbReceiver.value" ], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] }} 11:06:43,318 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "ejb3"), ("service" => "remote") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]} {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5439) Data Race accessing org/jboss/dmr/ModelNode.value

by Thomas Krieger (JIRA)

Thomas Krieger created WFLY-5439: ------------------------------------ Summary: Data Race accessing org/jboss/dmr/ModelNode.value Key: WFLY-5439 URL: https://issues.jboss.org/browse/WFLY-5439 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 10.0.0.Beta1 Environment: jdk 1.8 64 bit windows Reporter: Thomas Krieger Assignee: Jason Greene Priority: Minor Data Race while accessing org/jboss/dmr/ModelNode.value during startup of jboss: Two Threads are accessing this field without synchronization: Stacktrace for Thread writing field: org/jboss/threads/JBossThread.run java/util/concurrent/ThreadPoolExecutor$Worker.run java/util/concurrent/ThreadPoolExecutor.runWorker org/jboss/as/controller/ParallelBootOperationStepHandler$ParallelBootTask.run org/jboss/as/controller/AbstractOperationContext.executeOperation org/jboss/as/controller/AbstractOperationContext.processStages org/jboss/as/controller/AbstractOperationContext.executeStep org/jboss/as/controller/AbstractAddStepHandler.execute org/jboss/as/controller/AbstractAddStepHandler.populateModel org/jboss/as/controller/AbstractAddStepHandler.populateModel org/jboss/as/jsf/subsystem/JSFSubsystemAdd.populateModel org/jboss/as/controller/AttributeDefinition.validateAndSet org/jboss/dmr/ModelNode.get Stacktrace for reading Field: org/jboss/as/controller/AbstractControllerService$1.run org/jboss/as/server/ServerService.boot org/jboss/as/server/ServerService.boot org/jboss/as/controller/AbstractControllerService.boot org/jboss/as/controller/AbstractControllerService.boot org/jboss/as/controller/ModelControllerImpl.boot org/jboss/as/controller/OperationContextImpl.executeOperation org/jboss/as/controller/AbstractOperationContext.executeOperation org/jboss/as/controller/AbstractOperationContext.processStages org/jboss/as/controller/AbstractOperationContext.executeDoneStage org/jboss/as/controller/OperationContextImpl.createPersistenceResource org/jboss/as/controller/ModelControllerImpl.writeModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/as/controller/registry/Resource$Tools.readModel org/jboss/dmr/ModelNode.clone Found by [link vmlens|http://vmlens.com] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5432) Wildfly SOAP webservice causes JVM crash

by Davide Marchetti (JIRA)

[ https://issues.jboss.org/browse/WFLY-5432?page=com.atlassian.jira.plugin.... ] Davide Marchetti commented on WFLY-5432: ---------------------------------------- Hi Alessio, I believe you. I still do not understand why I have this problem, but I'm starting to think it must be some subtle HARDWARE-related issue. In my tests, the only "constant" is that the tested jdk versions, the wildflys, the other Centos machine... everything was running on my developer machine. Therefore, if everything is different but the hardware is the same, it must be that... figuring out what is causing this problem is however very difficult. >From my point of view you can therefore close the issue as cannot reproduce. Thank you anyway. > Wildfly SOAP webservice causes JVM crash > ---------------------------------------- > > Key: WFLY-5432 > URL: https://issues.jboss.org/browse/WFLY-5432 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.1.Final, 10.0.0.CR2 > Environment: Tested on Mac OSX 10.10.2, jdk 1.8.60, wildfly 9.0.1. Final / 10.cr2 > Also tested on Centos 6.5, jdk 1.7.51, wildfly 9.0.1. Final > Reporter: Davide Marchetti > Assignee: Alessio Soldano > Priority: Blocker > Labels: crash, jvm, soap, webservice > Attachments: SOAPTest.war > > > The JVM crashes with either a sigsegv or sigbus error when performing a SOAP load test. > The error printed is: > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f5da922afb8, pid=75645, tid=140039627204352 > # > # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_15_01_39-b00) > # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # J org.apache.cxf.message.ExchangeImpl.get(Ljava/lang/Class;)Ljava/lang/Object; > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > > # > # If you would like to submit a bug report, please include > # instructions on how to reproduce the bug and visit: > # 15:56:03,314 INFO [stdout] (default task-17) Submitted order request received with transId: <XXXXX>, opId: <SCO>, ... > http://icedtea.classpath.org/bugzilla > # > The webservice does nothing, just a System.out.print("xxxxx"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-302) Add SHA-512-256 to list of algorithms for digest passwords and SASL digest

by David Lloyd (JIRA)

David Lloyd created ELY-302: ------------------------------- Summary: Add SHA-512-256 to list of algorithms for digest passwords and SASL digest Key: ELY-302 URL: https://issues.jboss.org/browse/ELY-302 Project: WildFly Elytron Issue Type: Enhancement Components: Passwords, SASL Reporter: David Lloyd [RFC 7616|http://www.rfc-editor.org/rfc/rfc7616.txt] was released, indicating that SHA-512-256 is a supported algorithm for digest HTTP mechanisms. We need support for that algorithm as a password. We also then should add a corresponding SASL variant to the DIGEST suite. There is no MessageDigest for SHA-512-256. This can be accomplished by truncating the output of SHA-512 to 256 bits (32 bytes). A wrapper MessageDigest could be created, or the ability to arbitrarily truncate the digest could be added to the DIGEST mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2015