April 2019 - jboss-jira - Jboss List Archives

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

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3949?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-3949: ----------------------------------- Assignee: Michael Anstis (was: Mario Fusco) > "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 > Affects Versions: 7.21.0.Final > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Blocker > Labels: 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". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3949?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3949: -------------------------------- Component/s: DMN Editor > "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 > Affects Versions: 7.21.0.Final > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Blocker > Labels: 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". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12031) Memory leak in wildfly transaction client

by Joachim Petrich (Jira)

Joachim Petrich created WFLY-12031: -------------------------------------- Summary: Memory leak in wildfly transaction client Key: WFLY-12031 URL: https://issues.jboss.org/browse/WFLY-12031 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 15.0.1.Final Environment: wildfly-transaction-client-1.1.3.Final wildfly.15.0.1.Final Window 10 Reporter: Joachim Petrich Assignee: Thomas Jenkinson After a volume run of our system we recognized millions of entries in the openFilePaths Object of class FileSystemXAResourceRegistry. When enabling traces for org.wildfly.transaction it seems that for adding an entry a xid string is used XAResourceRegistryFile(Xid xid) throws SystemException { xaRecoveryPath.toFile().mkdir(); // create dir if non existent final String xidString = SimpleXid.of(xid).toHexString('_'); this.filePath = xaRecoveryPath.resolve(xidString); openFilePaths.add(*xidString*); and for removing the entire file path protected void removeResource(XAResource resource) throws XAException { if (resources.remove(resource)) { if (resources.isEmpty()) { // delete file try { if (fileChannel != null) { fileChannel.close(); } Files.delete(filePath); // deleting using the filepath as key caused a memory leak, // if xid string have been added, therefore build the xid string for removing openFilePaths.remove(*filePath.toString()*); We didn't find any code where this xid are cleaned up. As workaround we additionally extract the xid String from the file path and remove the corresponding entry. String xidString = filePath.toString().substring(filePath.toString().indexOf( xaRecoveryPath.toString()) + xaRecoveryPath.toString().length() + 1); openFilePaths.remove(xidString); -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3832) [DMN Designer] Included Models - Users must be able to add an imported node to the canvas

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3832?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3832: ------------------------------------- [~dadossan] I got some compilation errors when I created really simple artificial project [^empty-one-project.zip] . I created *logic1.dmn* file. There I declared single decision node, that acts as a constant it always returns a *true*. Then in *logic.dmn* I imported *logic1.dmn* and wanted to return value of the constant from there. However got the error attached in [^error.log] . > [DMN Designer] Included Models - Users must be able to add an imported node to the canvas > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3832 > URL: https://issues.jboss.org/browse/DROOLS-3832 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: empty-one-project.zip, error.log > > > Users must be able to add imported node to the canvas by dragging them from the "Decision Components" component. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3832) [DMN Designer] Included Models - Users must be able to add an imported node to the canvas

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3832?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3832: -------------------------------- Attachment: empty-one-project.zip > [DMN Designer] Included Models - Users must be able to add an imported node to the canvas > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3832 > URL: https://issues.jboss.org/browse/DROOLS-3832 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: empty-one-project.zip, error.log > > > Users must be able to add imported node to the canvas by dragging them from the "Decision Components" component. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3832) [DMN Designer] Included Models - Users must be able to add an imported node to the canvas

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3832?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3832: -------------------------------- Attachment: error.log > [DMN Designer] Included Models - Users must be able to add an imported node to the canvas > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3832 > URL: https://issues.jboss.org/browse/DROOLS-3832 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: empty-one-project.zip, error.log > > > Users must be able to add imported node to the canvas by dragging them from the "Decision Components" component. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 Yevgeniy Fomin (Jira)

Yevgeniy Fomin created DROOLS-3949: -------------------------------------- Summary: "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 Affects Versions: 7.21.0.Final Reporter: Yevgeniy Fomin Assignee: Mario Fusco 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". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by Tomas Hofman (Jira)

Tomas Hofman created WFLY-12030: ----------------------------------- Summary: java.rmi is not visible from wildfly.extension.io module Key: WFLY-12030 URL: https://issues.jboss.org/browse/WFLY-12030 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 16.0.0.Final Reporter: Tomas Hofman Assignee: Tomas Hofman 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12029) Update Checkstyl Config to 1.0.8.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12029: --------------------------------------- Summary: Update Checkstyl Config to 1.0.8.Final Key: WFLY-12029 URL: https://issues.jboss.org/browse/WFLY-12029 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 17.0.0.Beta1 Also remove the checkstyle plug-in version override. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12028) Upgrade JBoss Parent to version 35

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12028: --------------------------------------- Summary: Upgrade JBoss Parent to version 35 Key: WFLY-12028 URL: https://issues.jboss.org/browse/WFLY-12028 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 17.0.0.Beta1 -- 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 April 2019