April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3950) Add drl example to Summit demo app

by Mario Fusco (Jira)

Mario Fusco created DROOLS-3950: ----------------------------------- Summary: Add drl example to Summit demo app Key: DROOLS-3950 URL: https://issues.jboss.org/browse/DROOLS-3950 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10813) OutOfMemory error when trying to display resource adapters in web console

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-10813?page=com.atlassian.jira.plugin... ] Harald Pehl commented on WFLY-10813: ------------------------------------ [~obludik] Are there any updates? > OutOfMemory error when trying to display resource adapters in web console > ------------------------------------------------------------------------- > > Key: WFLY-10813 > URL: https://issues.jboss.org/browse/WFLY-10813 > Project: WildFly > Issue Type: Bug > Components: Management, Web Console > Affects Versions: 10.0.0.Final, 13.0.0.Final > Reporter: Helena Knyttlová > Assignee: Harald Pehl > Priority: Minor > Attachments: standalone-full-ha.xml > > > We have about 25 resource adapters set through CLI. When I want to display them in web administration console it kills the whole wildfly server - server is not responding and after several minutes it ends up with OutOfMemory error and server must be restarted. We've seen this issue since wildfly 10 (it was the first version we used). With only a few resource adapters it is not happening. > Memory settings: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > The error which appeared on WidlFly 13.0.0.Final: > {panel:title=Log} > ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([ > ("subsystem" => "resource-adapters"), > ("resource-adapter" => "AppAdapter"), > ("connection-definitions" => "cp-host") > ]): java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.resize(HashMap.java:704) > at java.util.HashMap.putVal(HashMap.java:629) > at java.util.HashMap.put(HashMap.java:612) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.set(ModelNode.java:693) > at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$ReadResourceDescriptionAssemblyHandler.execute(ReadResourceDescriptionHandler.java:618) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1404) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.jboss.as.controller.ModelControllerImpl$$Lambda$490/414756260.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/367363594.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$790/1228674018.run(Unknown Source) > {panel} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11846) Deployment classloader leak on EE Concurrency managed threads

by Martin Perina (Jira)

[ https://issues.jboss.org/browse/WFLY-11846?page=com.atlassian.jira.plugin... ] Martin Perina commented on WFLY-11846: -------------------------------------- [~dfediuck] > Deployment classloader leak on EE Concurrency managed threads > ------------------------------------------------------------- > > Key: WFLY-11846 > URL: https://issues.jboss.org/browse/WFLY-11846 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 16.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Critical > Fix For: 17.0.0.Beta1 > > Attachments: Screenshot 2019-03-13 at 20.21.19.png > > > A followup to WFLY-11678, managed threads have another deployment CL leak, which happens due to parent thread having a reference to it in its AccessControlContext. When a thread is created it inherits parent's AccessControlContext. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6143) Global EJB Server Side Interceptors Configuration

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-6143?page=com.atlassian.jira.plugin.... ] Tomasz Adamski edited comment on WFLY-6143 at 4/29/19 11:48 AM: ---------------------------------------------------------------- @HaraldPehl the draft is ready. I will open PR today. This would require reviews but I hope the management model will stay unchanged. was (Author: tomekadamski): @HaraldPehl the draft is ready. I will open PR today. This would require reviews but I hope the management model will stay. > Global EJB Server Side Interceptors Configuration > ------------------------------------------------- > > Key: WFLY-6143 > URL: https://issues.jboss.org/browse/WFLY-6143 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > > Ability to configure global server side interceptors (container interceptors) and specify their order via the JBoss profile xml. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6143) Global EJB Server Side Interceptors Configuration

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-6143?page=com.atlassian.jira.plugin.... ] Tomasz Adamski commented on WFLY-6143: -------------------------------------- @HaraldPehl the draft is ready. I will open PR today. This would require reviews but I hope the management model will stay. > Global EJB Server Side Interceptors Configuration > ------------------------------------------------- > > Key: WFLY-6143 > URL: https://issues.jboss.org/browse/WFLY-6143 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > > Ability to configure global server side interceptors (container interceptors) and specify their order via the JBoss profile xml. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6143) Global EJB Server Side Interceptors Configuration

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-6143?page=com.atlassian.jira.plugin.... ] Harald Pehl commented on WFLY-6143: ----------------------------------- [~tomekadamski] Any update when this will be available in WildFly master? > Global EJB Server Side Interceptors Configuration > ------------------------------------------------- > > Key: WFLY-6143 > URL: https://issues.jboss.org/browse/WFLY-6143 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > > Ability to configure global server side interceptors (container interceptors) and specify their order via the JBoss profile xml. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12026) java.rmi is not visible from wildfly.extension.io module

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-12026?page=com.atlassian.jira.plugin... ] Tomas Hofman closed WFLY-12026. ------------------------------- Resolution: Duplicate Issue Closing this as duplicate of WFCORE-4450. > java.rmi is not visible from wildfly.extension.io module > -------------------------------------------------------- > > Key: WFLY-12026 > URL: https://issues.jboss.org/browse/WFLY-12026 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 16.0.0.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > java.rmi is not visible from wildfly.extension.io module > The CNF is being thrown but not logged on the server side: > {code} > (default task-2) [BYTEMAN-1] CNF: 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-57) Update WildFly Checkstyle Config to 1.0.8.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-57: -------------------------------------- Summary: Update WildFly Checkstyle Config to 1.0.8.Final Key: ELYWEB-57 URL: https://issues.jboss.org/browse/ELYWEB-57 Project: Elytron Web Issue Type: Component Upgrade Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.5.0.CR3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3949) "Diagram properties" is empty, if you'll go to Business Central you'll get error

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3949?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3949: ----------------------------------- Component/s: Stunner > "Diagram properties" is empty, if you'll go to Business Central you'll get error > -------------------------------------------------------------------------------- > > Key: DROOLS-3949 > URL: https://issues.jboss.org/browse/DROOLS-3949 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Stunner > Affects Versions: 7.21.0.Final > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Blocker > Labels: Stunner, drools-tools > Attachments: Error.jpeg, Screenshot from 2019-04-29 15-22-18.png > > > The "Diagram properties" is empty in any step of creation diagram(see attach), also you will receive an error after attempting to click on "Business Central" after using "Diagram properties". > Please notice the issue affects also Business Processes. If user create new business process, the diagram properties panel is always empty. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-56) Upgrade JBoss Parent to version 35

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-56: -------------------------------------- Summary: Upgrade JBoss Parent to version 35 Key: ELYWEB-56 URL: https://issues.jboss.org/browse/ELYWEB-56 Project: Elytron Web Issue Type: Component Upgrade Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.5.0.CR3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 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