April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2263) GRAVE: JGRP000225: failed unmarshalling buffer into return value

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2263?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2263. -------------------------- Resolution: Rejected > GRAVE: JGRP000225: failed unmarshalling buffer into return value > ---------------------------------------------------------------- > > Key: JGRP-2263 > URL: https://issues.jboss.org/browse/JGRP-2263 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.11 > Environment: jdk1.8.0_66.jdk > osx 10.10 & ubuntu 17.10 > Reporter: rama rama > Assignee: Bela Ban > Attachments: SimpleChat.java > > > trying to send a class that previous work with 3.x return > "failed unmarshalling buffer into return value" > jgroups instance it's configured with the default settings > i create a test case to reproduce it, executing this class on my 2 boxes return > ---- > GRAVE: JGRP000225: failed unmarshalling buffer into return value > java.lang.InstantiationException: com.eg.util.comm.SimpleChat$EError > at java.lang.Class.newInstance(Class.java:427) > at org.jgroups.util.Util.readException(Util.java:899) > at org.jgroups.util.Util.exceptionFromStream(Util.java:843) > at org.jgroups.util.Util.exceptionFromStream(Util.java:831) > at org.jgroups.util.Util.objectFromStream(Util.java:782) > at org.jgroups.util.Util.objectFromStream(Util.java:742) > at org.jgroups.blocks.RequestCorrelator.replyFromBuffer(RequestCorrelator.java:463) > at org.jgroups.blocks.RequestCorrelator.handleResponse(RequestCorrelator.java:408) > at org.jgroups.blocks.RequestCorrelator.dispatch(RequestCorrelator.java:363) > at org.jgroups.blocks.RequestCorrelator.receiveMessageBatch(RequestCorrelator.java:326) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:589) > at org.jgroups.JChannel.up(JChannel.java:837) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:896) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.RSVP.up(RSVP.java:233) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:196) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:293) > at org.jgroups.protocols.UNICAST3.deliverBatch(UNICAST3.java:1024) > at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:833) > at org.jgroups.protocols.UNICAST3.handleBatchFromSelf(UNICAST3.java:520) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:435) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:697) > at org.jgroups.protocols.BARRIER.up(BARRIER.java:195) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:212) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.TP.passBatchUp(TP.java:1274) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.passBatchUp(MaxOneThreadPerSender.java:284) > at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.run(MaxOneThreadPerSender.java:273) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoSuchMethodException: com.eg.util.comm.SimpleChat$EError.<init>() > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.newInstance(Class.java:412) > ... 37 more > ----- -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10288) Remove ee8.preview.mode support

by James Perkins (JIRA)

James Perkins created WFLY-10288: ------------------------------------ Summary: Remove ee8.preview.mode support Key: WFLY-10288 URL: https://issues.jboss.org/browse/WFLY-10288 Project: WildFly Issue Type: Sub-task Components: EE Reporter: James Perkins Once Java EE 8 compliant we need to remove the support for the {{ee8.preview.mode}} system property. The following modules will need to be updated: * {{javax.enterprise.api}} * {{javax.validation.api}} * {{javax.json.bind.api}} * {{javax.json.api}} * {{javax.annotation.api}} * {{javax.servlet.api}} * {{org.wildfly.bridge.servlet-api-bridge}} (needs to be removed) * {{org.eclipse.yasson}} * {{org.glassfish.javax.json}} * {{javax.persistence.api}} * {{javax.ws.rs.api}} * {{javax.faces.api}} * {{javax.mail.api}} * {{javax.xml.bind.api}} * {{org.wildfly.cdi-api-bridge}} * {{org.jboss.resteasy.resteasy-json-binding-provider}} * {{org.jboss.resteasy.resteasy-jaxrs}} * {{org.hibernate.validator}} * {{org.hibernate.validator.cdi}} * {{com.sun.jsf-impl}} The following configuration needs to be removed: * {{./feature-pack/src/main/resources/configuration/standalone/template-ee8.xml}} The following source files should be updated: * {{org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.java}} * {{org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.java}} The following documentation needs to be updated: * {{./docs/src/main/asciidoc/Getting_Started_Guide.adoc}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose information on authentication in use

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3443: ---------------------------------------------- Yes, enhancement. Fixing that. > CLI ConnectionInfo should expose information on authentication in use > --------------------------------------------------------------------- > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 5.0.0.Alpha3 > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose information on authentication in use

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3443: ----------------------------------------- Issue Type: Enhancement (was: Bug) > CLI ConnectionInfo should expose information on authentication in use > --------------------------------------------------------------------- > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 5.0.0.Alpha3 > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose information on authentication in use

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3443: ------------------------------------------ This is an Enhancement, right? > CLI ConnectionInfo should expose information on authentication in use > --------------------------------------------------------------------- > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 5.0.0.Alpha3 > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-154) Session based DigestCredential support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-154?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-154: -------------------------------------- What this means is the password is never revealed in any re-usable form. Where we have username / realm / password hashes that hash can then be used both client side and server side for future messages. Session based Digest mean that the only hashes in the application server are never re-usable, if the heap of the application server was stolen and the hashes on the heap analysed they would not be useful. There does then need to be another server able to generate these session based hashes. > Session based DigestCredential support > -------------------------------------- > > Key: ELY-154 > URL: https://issues.jboss.org/browse/ELY-154 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Passwords > Reporter: Darran Lofthouse > > DigestCredential but where additional information is included such as nonce and cnonce to create a credential applicable to a session. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3742) management operation to generate provisioning feature specs for managed resources

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3742?page=com.atlassian.jira.plugi... ] Alexey Loubyansky commented on WFCORE-3742: ------------------------------------------- https://github.com/wildfly/wildfly-core/pull/3227 contains the tests > management operation to generate provisioning feature specs for managed resources > --------------------------------------------------------------------------------- > > Key: WFCORE-3742 > URL: https://issues.jboss.org/browse/WFCORE-3742 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > To be able to use Galleon as the provisioning mechanism we need to be able to represent resources in the domain management model as Galleon features, i.e. we need to be able to generate feature spec files for all the resources. The idea is to add a global operation handler which will describe a resource as a Galleon feature (using the ModelNode API) that will later be persisted (by the caller) as a feature spec file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3742) management operation to generate provisioning feature specs for managed resources

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3742?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3742: -------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3223, https://github.com/wildfly/wildfly-core/pull/3227 (was: https://github.com/wildfly/wildfly-core/pull/3223) > management operation to generate provisioning feature specs for managed resources > --------------------------------------------------------------------------------- > > Key: WFCORE-3742 > URL: https://issues.jboss.org/browse/WFCORE-3742 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > To be able to use Galleon as the provisioning mechanism we need to be able to represent resources in the domain management model as Galleon features, i.e. we need to be able to generate feature spec files for all the resources. The idea is to add a global operation handler which will describe a resource as a Galleon feature (using the ModelNode API) that will later be persisted (by the caller) as a feature spec file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-179) Repair B21 Openshift Cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-179?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-179: ------------------------------------------ Summary: Repair B21 Openshift Cluster (was: Repair B21 Node) > Repair B21 Openshift Cluster > ---------------------------- > > Key: SWSQE-179 > URL: https://issues.jboss.org/browse/SWSQE-179 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > NAME STATUS AGE VERSION > b06.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62 > b16.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62 > b18.jonqe.lab.eng.bos.redhat.com Ready 85d v1.7.6+a08f5eeb62 > b21.jonqe.lab.eng.bos.redhat.com NotReady 85d v1.7.6+a08f5eeb62 > {panel:title=b21} > oc describe node b21.jonqe.lab.eng.bos.redhat.com  1 ↵  10571  09:40:42 > Name: b21.jonqe.lab.eng.bos.redhat.com > Role: > Labels: beta.kubernetes.io/arch=amd64 > beta.kubernetes.io/os=linux > kubernetes.io/hostname=b21.jonqe.lab.eng.bos.redhat.com > openshift-infra=apiserver > region=infra > zone=default > Annotations: volumes.kubernetes.io/controller-managed-attach-detach=true > Taints: <none> > CreationTimestamp: Sun, 28 Jan 2018 09:01:00 -0200 > Conditions: > Type Status LastHeartbeatTime LastTransitionTime Reason Message > ---- ------ ----------------- ------------------ ------ ------- > OutOfDisk False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientDisk kubelet has sufficient disk space available > MemoryPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasSufficientMemory kubelet has sufficient memory available > DiskPressure False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 15 Apr 2018 20:47:45 -0300 KubeletHasNoDiskPressure kubelet has no disk pressure > Ready False Mon, 23 Apr 2018 09:42:17 -0300 Sun, 22 Apr 2018 18:28:43 -0300 KubeletNotReady PLEG is not healthy: pleg was last seen active 15h17m29.5748908s ago; threshold is 3m0s > Addresses: > InternalIP: 10.16.23.44 > Hostname: b21.jonqe.lab.eng.bos.redhat.com > Capacity: > cpu: 24 > memory: 65757652Ki > pods: 240 > Allocatable: > cpu: 24 > memory: 65655252Ki > pods: 240 > System Info: > Machine ID: b1d9d75ab38b42d095ccf0e9ebe3a2d7 > System UUID: 4C4C4544-0050-4D10-8059-C8C04F4C3032 > Boot ID: cff20a97-dbf1-4bfa-b9b2-0face47d2646 > Kernel Version: 3.10.0-693.17.1.el7.x86_64 > OS Image: Red Hat Enterprise Linux Server 7.4 (Maipo) > Operating System: linux > Architecture: amd64 > Container Runtime Version: docker://1.12.6 > Kubelet Version: v1.7.6+a08f5eeb62 > Kube-Proxy Version: v1.7.6+a08f5eeb62 > ExternalID: b21.jonqe.lab.eng.bos.redhat.com > Non-terminated Pods: (24 in total) > Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits > --------- ---- ------------ ---------- --------------- ------------- > hayk-test mongodb-1-gflrd 0 (0%) 0 (0%) 512Mi (0%) 512Mi (0%) > kiali-test-box kiali-test-service-b-qs5tv 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-box kiali-test-service-e-jw56k 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-breadth-sink kiali-test-service-a-hmh8t 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-breadth-sink kiali-test-service-c-svxgs 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-breadth-sink kiali-test-service-e-6fchg 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-breath kiali-test-service-c-czxr5 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-breath kiali-test-service-e-cr88j 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-circle-callback kiali-test-service-b-zljtr 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-circle-callback kiali-test-service-e-8f6rt 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-circle kiali-test-service-c-28d5h 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-circle kiali-traffic-generator-lglth 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-depth-sink kiali-test-service-b-xq8ff 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-depth-sink kiali-test-service-e-nnnxw 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-depth-sink kiali-traffic-generator-fd786 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-depth kiali-test-service-c-nch7m 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-depth kiali-traffic-generator-vqmg9 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-hourglass kiali-test-service-b-j89jp 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kiali-test-hourglass kiali-test-service-e-6r77d 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kube-service-catalog apiserver-566mp 0 (0%) 0 (0%) 0 (0%) 0 (0%) > kube-service-catalog controller-manager-sqmlh 0 (0%) 0 (0%) 0 (0%) 0 (0%) > openshift-infra hawkular-metrics-xp9hl 0 (0%) 0 (0%) 1500M (2%) 2500M (3%) > openshift-template-service-broker apiserver-rntz8 0 (0%) 0 (0%) 0 (0%) 0 (0%) > react-test-demo git-explorer-4-8bdzh 0 (0%) 0 (0%) 0 (0%) 0 (0%) > {panel} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose information on authentication in use

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3443?page=com.atlassian.jira.plugi... ] Martin Choma updated WFCORE-3443: --------------------------------- Affects Version/s: 5.0.0.Alpha3 > CLI ConnectionInfo should expose information on authentication in use > --------------------------------------------------------------------- > > Key: WFCORE-3443 > URL: https://issues.jboss.org/browse/WFCORE-3443 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 5.0.0.Alpha3 > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 April 2018