January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3552) Error: "write size larger than buffer can fit" when opening object in workbench

by Petr Farmakovsky (Jira)

[ https://issues.jboss.org/browse/DROOLS-3552?page=com.atlassian.jira.plugi... ] Petr Farmakovsky commented on DROOLS-3552: ------------------------------------------ Hi [~manstis] I registered a [defect|https://issues.jboss.org/browse/ERRAI-1122] in the ERRAI project, please close this. > Error: "write size larger than buffer can fit" when opening object in workbench > ------------------------------------------------------------------------------- > > Key: DROOLS-3552 > URL: https://issues.jboss.org/browse/DROOLS-3552 > Project: Drools > Issue Type: Bug > Components: DSLs Editor > Affects Versions: 6.5.0.Final > Environment: KIE Drools Workbench - Distribution Wars-Version: 6.5.0.Final > Server version: Apache Tomcat/7.0.76 > Server number: 7.0.76.0 > OS Name: Linux > OS Version: 3.10.0-957.1.3.el7.x86_64 > Architecture: amd64 > JVM Version: 1.7.0_161-b13 > JVM Vendor: Oracle Corporation > H2 database > Reporter: Petr Farmakovsky > Assignee: Michael Anstis > Priority: Major > Attachments: Error.jpg, Error2.json > > > To reproduce the error, I created a new repository, created a 300 Data Object in it. In each Data Object created 1000 fields of type Integer. > After restarting the server when opening any object, Drools Workbeanch writes an error: *write size larger than buffer can fit* > {noformat} > java.lang.RuntimeException: failed to enqueue message for delivery > at org.jboss.errai.bus.server.ServerMessageBusImpl.enqueueForDelivery(ServerMessageBusImpl.java:443) > at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:391) > at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:337) > at org.jboss.errai.bus.server.service.MessageBusProxy.send(MessageBusProxy.java:87) > at org.jboss.errai.bus.client.api.base.ConversationMessageWrapper.sendNowWith(ConversationMessageWrapper.java:238) > at org.jboss.errai.bus.client.api.base.DefaultMessageBuilder$1.sendNowWith(DefaultMessageBuilder.java:84) > at org.jboss.errai.bus.server.io.ValueReplyRPCEndpointCallback.callback(ValueReplyRPCEndpointCallback.java:22) > at org.jboss.errai.bus.server.io.RemoteServiceCallback.callback(RemoteServiceCallback.java:54) > at org.jboss.errai.cdi.server.CDIExtensionPoints$2.callback(CDIExtensionPoints.java:396) > .. > {noformat} > The full text of the error is attached in the file. > I know about the description https://developer.jboss.org/thread/220428 but I did not find the parameters under which you can open objects. > I found an error in the TransmissionBuffer.java class, but I don’t know how to fix the problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11653) Kabir Demo

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11653?page=com.atlassian.jira.plugin... ] Kabir Khan moved EAP7-1182 to WFLY-11653: ----------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-11653 (was: EAP7-1182) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Management (was: Management) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Kabir Demo > ---------- > > Key: WFLY-11653 > URL: https://issues.jboss.org/browse/WFLY-11653 > Project: WildFly > Issue Type: Feature Request > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > > Don't touch!!! I need this for a demo at the F2F -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshit API calls

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on SWSQE-554: ---------------------------------------- FYI please add the missing 'f' to the title of this issue. > Add missing Openshit API calls > ------------------------------ > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7612) Replacement for org.kuali.maven.plugins:properties-maven-plugin

by Tomaz Cerar (Jira)

[ https://issues.jboss.org/browse/WFLY-7612?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-7612: ----------------------------------- (y) > Replacement for org.kuali.maven.plugins:properties-maven-plugin > --------------------------------------------------------------- > > Key: WFLY-7612 > URL: https://issues.jboss.org/browse/WFLY-7612 > Project: WildFly > Issue Type: Task > Reporter: gil cattaneo > Assignee: Tomaz Cerar > Priority: Major > Fix For: 12.0.0.Final > > > Hi, > org.kuali.maven.plugins:properties-maven-plugin is used for wildfly 11.0.0.Alpha1-SNAPSHOT (master branch) > but seem the plugin source code (and also for it dependencies) is not more available @ > http://svn.kuali.org/repos/foundation/ > Please, can you use some other alternative, e.g. http://www.mojohaus.org/properties-maven-plugin/ ? > This is necessary for all Linux distributions that do not include the use of pre-compiled libraries (including maven plugins), available on various maven repository. e.g http://central.maven.org/maven2/ > https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-b... > Thanks in advance > Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5321) Deploying a war to wildfly should mention the localhost url including context root of that war in the log

by Tomaz Cerar (Jira)

[ https://issues.jboss.org/browse/WFLY-5321?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-5321: ----------------------------------- Ideal enhancement for this log message would be if it could display full URLs under which app is available for example http://localhost:8080/helloworld http://127.0.0.1:8080/helloworld http://:::1:8080/helloworld https://127.0.0.1:8443/helloworld (if ssl is enabled) ... for simple cases like default config, this is easy. but it gets tricky when you have multiple virtual hosts and multiple servers configured all with different interface configuration. as well as knowing the host name of the machine (which can be an expensive blocking operation, which is not a good thing to do on boot) > Deploying a war to wildfly should mention the localhost url including context root of that war in the log > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-5321 > URL: https://issues.jboss.org/browse/WFLY-5321 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Reporter: Geoffrey De Smet > Priority: Minor > > Here what I see now in the log: > {code} > [2015-09-10 04:56:44,211] Artifact optaconf-webapp:war exploded: Artifact is being deployed, please wait... > 16:56:44,235 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016009: Stopping weld service for deployment optaconf-webapp-0.1.0-SNAPSHOT > 16:56:44,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment optaconf-webapp-0.1.0-SNAPSHOT (runtime-name: optaconf-webapp-0.1.0-SNAPSHOT) in 15ms > 16:56:44,255 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name: "optaconf-webapp-0.1.0-SNAPSHOT") > 16:56:44,322 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name: "optaconf-webapp-0.1.0-SNAPSHOT") > ... > 16:56:44,508 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name : "optaconf-webapp-0.1.0-SNAPSHOT") > [2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Artifact is deployed successfully > [2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Deploy took 308 milliseconds > {code} > But as a developer, it's very hard to figure out the url to test the app, especially if someone changed it recently. Note that in my case it could be any of these, depending on the state of the jboss-web.xml, war file name (potentially exploded), IDE configuration, etc: > - http://localhost:8080/optaconf-webapp-0.1.0-SNAPSHOT/ > - http://localhost:8080/optaconf-webapp/ > - http://localhost:8080/optaconf/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4308) Proxies created via ContextService.createContextualProxy(...) are not Serializable

by Stephen Coy (Jira)

[ https://issues.jboss.org/browse/WFLY-4308?page=com.atlassian.jira.plugin.... ] Stephen Coy commented on WFLY-4308: ----------------------------------- I hate to "necro" this old issue, but it is currently still broken in the same way in WildFly 15. The transient {{SecurityIdentity}} in the {{org.jboss.as.ee.concurrent.IdentityAwareProxyInvocationHandler}} obviously does not survive serialisation, which happens in JMS use cases. > Proxies created via ContextService.createContextualProxy(...) are not Serializable > ---------------------------------------------------------------------------------- > > Key: WFLY-4308 > URL: https://issues.jboss.org/browse/WFLY-4308 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 10.0.0.CR1 > > > Setting priority to critical since, I believe, this is a matter of compliance with the concurrency utilities specification. > Section 3.3.4 of the specification states that: > "All invocation handlers for the contextual proxy implementation must implement java.io.Serializable." > While the invocation handler of the generated proxy does indeed implement Serializable, it contains a reference to org.jboss.as.server.moduleservice.ServiceModuleLoader (among others), which is not serializable, thus attempts to serialize the proxies generated via ContextService.createContextualProxy(...) via JBoss Marshalling throw a org.infinispan.commons.marshall.NotSerializableException: org.jboss.as.server.moduleservice.ServiceModuleLoader -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4298) Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

by jaikiran pai (Jira)

[ https://issues.jboss.org/browse/WFCORE-4298?page=com.atlassian.jira.plugi... ] jaikiran pai updated WFCORE-4298: --------------------------------- Affects Version/s: 8.0.0.Beta3 > Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4298 > URL: https://issues.jboss.org/browse/WFCORE-4298 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 8.0.0.Beta3 > Reporter: jaikiran pai > Assignee: jaikiran pai > Priority: Minor > > Pull request https://github.com/wildfly/wildfly-core/pull/3636 introduced support for loading resources from multi-release jar files, through VFSResourceLoader. However, right now, it just looks for the presence of the `Multi-Release` manifest attribute but doesn't check the value of that attribute before deciding whether or not to process the jar as a multi-release jar. As per the spec[1], the expectation is to consider the jar as multi-release enabled only if the value of `Multi-Release` attribute is `true` > [1] https://mail.openjdk.java.net/pipermail/core-libs-dev/2019-January/058131... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4298) Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

by jaikiran pai (Jira)

jaikiran pai created WFCORE-4298: ------------------------------------ Summary: Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value Key: WFCORE-4298 URL: https://issues.jboss.org/browse/WFCORE-4298 Project: WildFly Core Issue Type: Bug Reporter: jaikiran pai Assignee: jaikiran pai Pull request https://github.com/wildfly/wildfly-core/pull/3636 introduced support for loading resources from multi-release jar files, through VFSResourceLoader. However, right now, it just looks for the presence of the `Multi-Release` manifest attribute but doesn't check the value of that attribute before deciding whether or not to process the jar as a multi-release jar. As per the spec[1], the expectation is to consider the jar as multi-release enabled only if the value of `Multi-Release` attribute is `true` [1] https://mail.openjdk.java.net/pipermail/core-libs-dev/2019-January/058131... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3554) KieContainer#updateToVersion removing rules with accumulate

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3554?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3554: -------------------------------- Sprint: 2019 Week 02-04 > KieContainer#updateToVersion removing rules with accumulate > ----------------------------------------------------------- > > Key: DROOLS-3554 > URL: https://issues.jboss.org/browse/DROOLS-3554 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.16.0.Final > Reporter: Olga Rodionova > Assignee: Mario Fusco > Priority: Major > Attachments: RuleRemovalTest.java, SimpleRuleWithAccumulate.drl > > > Consider a rule with accumulate pattern in the LHS which logically inserts an object in the RHS. Build the KieModule from the KieFileSystem including this rule, create the KieContainer and the KieSession. Insert the facts. Everything works fine. > Create a new KieModule excluding this rule from the KieFileSystem, update the KieContainer. Expect the logically inserted fact to be retracted, as the rule which trigged its creation is no longer present. Turns out that the fact is still present in the working memory -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-556) Jenkins messaging configuration is broken

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-556?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-556: ------------------------------------ This issue appears to have been resolved, by disabling mb-consumer-maistra-trigger. > Jenkins messaging configuration is broken > ----------------------------------------- > > Key: SWSQE-556 > URL: https://issues.jboss.org/browse/SWSQE-556 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Matt Mahoney > Priority: Major > > Following error is thrown periodically to jenkins log: > Jan 10, 2019 5:12:04 AM com.redhat.jenkins.plugins.ci.messaging.ActiveMqMessagingWorker connect > SEVERE: Unable to connect to ssl://messaging-devops-broker02.web.qa.ext.phx1.redhat.com:61616 Could not connect to broker URL: ssl://messaging-devops-broker02.web.qa.ext.phx1.redhat.com:61616. Reason: java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019