May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9900) EJB client occasionally hangs

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-9900?page=com.atlassian.jira.plugin.... ] Flavia Rainone reassigned WFLY-9900: ------------------------------------ Assignee: Flavia Rainone (was: Cheng Fang) > EJB client occasionally hangs > ----------------------------- > > Key: WFLY-9900 > URL: https://issues.jboss.org/browse/WFLY-9900 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Beta1 > Reporter: Richard Janik > Assignee: Flavia Rainone > Priority: Major > Attachments: threaddump-client.txt, threaddump-server1.txt, threaddump-server2.txt, threaddump-server3.txt, threaddump-server4.txt > > > Seen in our clustering tests where remote EJB clients invoke beans on 4 servers in cluster, while each of those is being killed and restarted. This is done in sequence and there's plenty of time in between the kill/start/kill-another (1 minute). > In two ouf our tests, we saw a small number of clients hang at the end. The scenarios are: > [jvmkill-dist-sync|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/jo...] (36 clients) > [shutdown-dist-sync|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/j...] (1 client) > The hangs are not related to any error or warning message on the server-side. There are ClosedChannelExceptions on the client side, but these seem to be unrelated as the numbers of clients reporting the exceptions are not the same (lower) as the numbers of hanging clients. > No thread dump as I didn't manage to reproduce yet. > Might be related to JBEAP-12074 or JBEAP-13169. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12074) JAXWS Client BOM

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12074: -------------------------------------- Summary: JAXWS Client BOM Key: WFLY-12074 URL: https://issues.jboss.org/browse/WFLY-12074 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins Fix For: 15.0.0.Beta1, 15.0.0.Final The dependency management defined on WildFly, for JAXWS/CXF client, is over 1000 SLoC due to exclusions applied, which is a nightmare to manage on client apps projects, such as the jaxws-* quickstarts. To hide the dependency management complexity on apps a new client BOM should be added wrt JAXWS, which apps can just depend on it, and should includes all dependencies excluded on WildFly dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12032) Follow-up: java.rmi is not visible from EJBServerChannel

by Dennis Reed (Jira)

[ https://issues.jboss.org/browse/WFLY-12032?page=com.atlassian.jira.plugin... ] Dennis Reed commented on WFLY-12032: ------------------------------------ > It should actually already be set by the deserialization code. The TCCL is not being set. I've tracked down the version where it stopped working to EAP 7.1.0. > If you actually look at the source code of `MarshalInputStream` and follow what it's doing, it uses > `jdk.internal.misc.VM#latestUserDefinedLoader0` to determine the class loader to use. This method > searches the call stack for the class loader that it thinks the user meant to use. > Unfortunately that's never going to give the right answer. Then it might be a coincidence that RMI is using the same classloader as the incorrect TCCL? (We can open separate JIRAs if needed for the exact same error without the RMI part). > Follow-up: java.rmi is not visible from EJBServerChannel > -------------------------------------------------------- > > Key: WFLY-12032 > URL: https://issues.jboss.org/browse/WFLY-12032 > Project: WildFly > Issue Type: Bug > Affects Versions: 16.0.0.Final > Reporter: Tomas Hofman > Priority: Major > > This is follow up issue for JBEAP-16725, which was resolved with a workaround - javax.rmi was added as a dependency of wildfly.extension.io module. > The root cause is probably inside jboss-modules. > The issue is following: > * a standalone EJB client invokes remote EJB, and passes an object as an argument; > * server (trying to use the remote object) fails with "java.lang.ClassNotFoundException: java.rmi.dgc.Lease" (stacktrace bellow). > If a short delay ({{Thread.sleep(100)}}) is introduced on the server side, before manipulating the remote object, the invocation succeeds. > {code} > java.lang.ClassNotFoundException: java.rmi.dgc.Lease from [Module "org.wildfly.extension.io" version 6.0.12.Final-redhat-00001 from local module loader @6a024a67 (finder: local module finder @7921b0a2 (roots: /tmp/jboss-eap-7.2/modules,/tmp/jboss-eap-7.2/modules/system/layers/base))] (no security manager: RMI class loader disabled) > (default task-2) java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:97) > (default task-2) sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:396) > (default task-2) sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:186) > (default task-2) java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:637) > (default task-2) java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:264) > (default task-2) sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:219) > (default task-2) java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1868) > (default task-2) java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) > (default task-2) java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) > (default task-2) java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) > (default task-2) java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) > (default task-2) sun.rmi.transport.DGCImpl_Stub.dirty(DGCImpl_Stub.java:125) > (default task-2) sun.rmi.transport.DGCClient$EndpointEntry.makeDirtyCall(DGCClient.java:382) > (default task-2) sun.rmi.transport.DGCClient$EndpointEntry.registerRefs(DGCClient.java:324) > (default task-2) sun.rmi.transport.DGCClient.registerRefs(DGCClient.java:160) > (default task-2) sun.rmi.transport.LiveRef.read(LiveRef.java:312) > (default task-2) sun.rmi.server.UnicastRef.readExternal(UnicastRef.java:489) > (default task-2) java.rmi.server.RemoteObject.readObject(RemoteObject.java:455) > (default task-2) sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > (default task-2) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > (default task-2) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > (default task-2) java.lang.reflect.Method.invoke(Method.java:498) > (default task-2) org.jboss.marshalling.reflect.JDKSpecific$SerMethods.callReadObject(JDKSpecific.java:179) > (default task-2) org.jboss.marshalling.reflect.SerializableClass.callReadObject(SerializableClass.java:212) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1746) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1715) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1715) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1395) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > (default task-2) org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205) > (default task-2) org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41) > (default task-2) org.jboss.ejb.protocol.remote.EJBServerChannel$RemotingInvocationRequest.getRequestContent(EJBServerChannel.java:813) > (default task-2) org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:130) > (default task-2) org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:451) > (default task-2) org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:189) > (default task-2) org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > (default task-2) org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949) > (default task-2) org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > (default task-2) org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > (default task-2) org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > (default task-2) org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > (default task-2) java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11987) Upgrade RESTEasy to 3.7.0.Final

by Ronald Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-11987?page=com.atlassian.jira.plugin... ] Ronald Sigal updated WFLY-11987: -------------------------------- Summary: Upgrade RESTEasy to 3.7.0.Final (was: Upgrade RESTEasy to 3.6.3.SP1) > Upgrade RESTEasy to 3.7.0.Final > ------------------------------- > > Key: WFLY-11987 > URL: https://issues.jboss.org/browse/WFLY-11987 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Affects Versions: 16.0.0.Final > Reporter: Ronald Sigal > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > Fix For: 17.0.0.Beta1 > > > Upgrade from 3.6.3.Final to 3.6.3.SP1 in which all references to repository are made with https. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12073) Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) should output should reflect all changes

by Scott Marlow (Jira)

Scott Marlow created WFLY-12073: ----------------------------------- Summary: Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) should output should reflect all changes Key: WFLY-12073 URL: https://issues.jboss.org/browse/WFLY-12073 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate Affects Versions: 14.0.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Currently Hibernate51CompatibilityTransformer.showTransformedClassFolder output doesn't show all changes that have been made to Hibernate applications, this jira is for addressing that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12073) Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) output should reflect all changes

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12073?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-12073: -------------------------------- Summary: Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) output should reflect all changes (was: Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) should output should reflect all changes) > Hibernate bytecode transformer (Hibernate51CompatibilityTransformer.showTransformedClassFolder) output should reflect all changes > --------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12073 > URL: https://issues.jboss.org/browse/WFLY-12073 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > > Currently Hibernate51CompatibilityTransformer.showTransformedClassFolder output doesn't show all changes that have been made to Hibernate applications, this jira is for addressing that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12072) Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12072?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12072: ----------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables > ---------------------------------------------------------------------- > > Key: WFLY-12072 > URL: https://issues.jboss.org/browse/WFLY-12072 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Galder Zamarreño > Assignee: Paul Ferraro > Priority: Major > > A port of ISPN-5267. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12072) Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12072?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12072: -------------------------------- Forum Reference: https://stackoverflow.com/questions/55881179/infinispan-cache-table-not-a... > Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables > ---------------------------------------------------------------------- > > Key: WFLY-12072 > URL: https://issues.jboss.org/browse/WFLY-12072 > Project: WildFly > Issue Type: Bug > Affects Versions: 16.0.0.Final > Reporter: Galder Zamarreño > Assignee: Brian Stansberry > Priority: Major > > A port of ISPN-5267. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12072) Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12072?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12072: -------------------------------- Component/s: Clustering > Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables > ---------------------------------------------------------------------- > > Key: WFLY-12072 > URL: https://issues.jboss.org/browse/WFLY-12072 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Galder Zamarreño > Assignee: Brian Stansberry > Priority: Major > > A port of ISPN-5267. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12072) Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12072?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12072: -------------------------------- Affects Version/s: 16.0.0.Final > Allow setting create-on-start / drop-on-exit on Infinispan JDBC tables > ---------------------------------------------------------------------- > > Key: WFLY-12072 > URL: https://issues.jboss.org/browse/WFLY-12072 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Galder Zamarreño > Assignee: Brian Stansberry > Priority: Major > > A port of ISPN-5267. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019