February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2011) Rsp: optimize in-memory size

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2011?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2011: --------------------------- Description: The in-memory size of {{Rsp}} can be made smaller. Currently, it looks like this: {noformat} public class Rsp { protected boolean received; protected boolean suspected; protected boolean unreachable; protected final Address sender; protected T retval; protected Throwable exception; } {noformat} Optimizations: # received, suspected and unreachable can be compacted into a byte field (flags) # retval and exception can be merged into {{Object value}} # sender can be removed: {{RspList}} already has the sender Size of {{Rsp}} is 32 bytes (used JOL to measure) before, and 24 bytes after the changes. was: The in-memory size of {{Rsp}} can be made smaller. Currently, it looks like this: {noformat} public class Rsp { protected boolean received; protected boolean suspected; protected boolean unreachable; protected final Address sender; protected T retval; protected Throwable exception; } {noformat} Optimizations: # received, suspected and unreachable can be compacted into a byte field (flags) # retval and exception can be merged into {{Object value}} # sender can be removed: {{RspList}} already has the sender Size of {{Rsp}} is 32 bytes (used JOL to measure) > Rsp: optimize in-memory size > ---------------------------- > > Key: JGRP-2011 > URL: https://issues.jboss.org/browse/JGRP-2011 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8, 4.0 > > > The in-memory size of {{Rsp}} can be made smaller. Currently, it looks like this: > {noformat} > public class Rsp { > protected boolean received; > protected boolean suspected; > protected boolean unreachable; > protected final Address sender; > protected T retval; > protected Throwable exception; > } > {noformat} > Optimizations: > # received, suspected and unreachable can be compacted into a byte field (flags) > # retval and exception can be merged into {{Object value}} > # sender can be removed: {{RspList}} already has the sender > Size of {{Rsp}} is 32 bytes (used JOL to measure) before, and 24 bytes after the changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1605) API changes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1605?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1605: --------------------------- Description: API changes to be done in 4.0, which break code: * MessageDispatcher: remove MessageListener * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH * DONE: Remove @Deprecated methods, properties or classes * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) * Make {{RspFilter}} --> {{RspFilter<T>}} * {{ProtocolStack.findProtocol(Class<?> clazz)}} should return generic type {{<T extends Protocol>>}}, so no casting is needed. Requires changes to a number of methods in the same class. * Request<T> * RpcDispatcher: only 1 Marshaller, not separate ones for reqs and rsps * RpcDispatcher: use CompletableFuture instead of NotifiyingFuture * Rsp: ** Club {{received}}, {{suspected}}, {{unreachable}} into 1 boolean field, use 1 field for result/exception ** Remove {{sender}} was: API changes to be done in 4.0, which break code: * MessageDispatcher: remove MessageListener * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH * DONE: Remove @Deprecated methods, properties or classes * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) * Make {{RspFilter}} --> {{RspFilter<T>}} * {{ProtocolStack.findProtocol(Class<?> clazz)}} should return generic type {{<T extends Protocol>>}}, so no casting is needed. Requires changes to a number of methods in the same class. * Request<T> * RpcDispatcher: only 1 Marshaller, not separate ones for reqs and rsps * RpcDispatcher: use CompletableFuture instead of NotifiyingFuture * Rsp: ** Club {{received}}, {{suspected}}, {{unreachable}} into 1 boolean field, use 1 field for result/exception ** Remove {{sender}} ** Remove {{equals()}} and {{hashCode()}} > API changes > ----------- > > Key: JGRP-1605 > URL: https://issues.jboss.org/browse/JGRP-1605 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > API changes to be done in 4.0, which break code: > * MessageDispatcher: remove MessageListener > * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH > * DONE: Remove @Deprecated methods, properties or classes > * Remove direct access to Message in JChannel.send() methods (to prevent passing in the same message more than once) > * Make {{RspFilter}} --> {{RspFilter<T>}} > * {{ProtocolStack.findProtocol(Class<?> clazz)}} should return generic type {{<T extends Protocol>>}}, so no casting is needed. Requires changes to a number of methods in the same class. > * Request<T> > * RpcDispatcher: only 1 Marshaller, not separate ones for reqs and rsps > * RpcDispatcher: use CompletableFuture instead of NotifiyingFuture > * Rsp: > ** Club {{received}}, {{suspected}}, {{unreachable}} into 1 boolean field, use 1 field for result/exception > ** Remove {{sender}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1348) Specify filesystem rights for deployment content

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1348?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-1348: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Brian Stansberry) > Specify filesystem rights for deployment content > ------------------------------------------------ > > Key: WFCORE-1348 > URL: https://issues.jboss.org/browse/WFCORE-1348 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.0.10.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Currently when we add a content to the ContentRepository we are using Files.createTempFile whitout specifying the file attributes. On GNU/Linux this may create a file with only read write rights for the user (and not the group or other). We should change that as this could lead to some strange errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1348) Specify filesystem rights for deployment content

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1348: ----------------------------------------- Summary: Specify filesystem rights for deployment content Key: WFCORE-1348 URL: https://issues.jboss.org/browse/WFCORE-1348 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 2.0.10.Final Reporter: ehsavoie Hugonnet Assignee: Brian Stansberry Currently when we add a content to the ContentRepository we are using Files.createTempFile whitout specifying the file attributes. On GNU/Linux this may create a file with only read write rights for the user (and not the group or other). We should change that as this could lead to some strange errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6113) TransactionAttributeMergingProcessor fails when using generics

by Markus Chur (JIRA)

[ https://issues.jboss.org/browse/WFLY-6113?page=com.atlassian.jira.plugin.... ] Markus Chur updated WFLY-6113: ------------------------------ Attachment: log.txt > TransactionAttributeMergingProcessor fails when using generics > -------------------------------------------------------------- > > Key: WFLY-6113 > URL: https://issues.jboss.org/browse/WFLY-6113 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Markus Chur > Assignee: Jason Greene > Priority: Minor > Attachments: log.txt, reproducer.zip > > > Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1347) StringListAttributeDefinition.unwarp doesn't take default value into account

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-1347: ----------------------------------- Summary: StringListAttributeDefinition.unwarp doesn't take default value into account Key: WFCORE-1347 URL: https://issues.jboss.org/browse/WFCORE-1347 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar unwrap method should first call resolveMethodAttribute to get value of attribute and than do unwrapping. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6114) service.bat points user to wrong directory

by Nicklas Karlsson (JIRA)

Nicklas Karlsson created WFLY-6114: -------------------------------------- Summary: service.bat points user to wrong directory Key: WFLY-6114 URL: https://issues.jboss.org/browse/WFLY-6114 Project: WildFly Issue Type: Feature Request Components: Scripts Affects Versions: 10.0.0.Final Reporter: Nicklas Karlsson Assignee: Tomaz Cerar Priority: Trivial Running service.bat from the docs/contrib/scripts/service dir tells user to run the script under bin/service*s* but the binary paths to the services expects bin/service, resulting in service install failure with file not found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6113) TransactionAttributeMergingProcessor fails when using generics

by Markus Chur (JIRA)

Markus Chur created WFLY-6113: --------------------------------- Summary: TransactionAttributeMergingProcessor fails when using generics Key: WFLY-6113 URL: https://issues.jboss.org/browse/WFLY-6113 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Markus Chur Assignee: Jason Greene Priority: Minor Attachments: reproducer.zip Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1049) Upgrade jaxb2-maven-plugin from 1.x to 2.x

by Petr Široký (JIRA)

Petr Široký created DROOLS-1049: ----------------------------------- Summary: Upgrade jaxb2-maven-plugin from 1.x to 2.x Key: DROOLS-1049 URL: https://issues.jboss.org/browse/DROOLS-1049 Project: Drools Issue Type: Task Components: build Reporter: Petr Široký Assignee: Petr Široký We are seeing intermittent build failures related to {{jaxb2-maven-plugin}} in droolsjbpm-integration repo (kie-remote-jaxb-gen module). Upgrading to latest 2.x version should fix these issues. We should also upgrade to latest version because we are at a start of the development cycle and the risks of breaking something are more acceptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1049) Upgrade jaxb2-maven-plugin from 1.5 to 2.2

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1049?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1049: -------------------------------- Summary: Upgrade jaxb2-maven-plugin from 1.5 to 2.2 (was: Upgrade jaxb2-maven-plugin from 1.x to 2.x) > Upgrade jaxb2-maven-plugin from 1.5 to 2.2 > ------------------------------------------ > > Key: DROOLS-1049 > URL: https://issues.jboss.org/browse/DROOLS-1049 > Project: Drools > Issue Type: Task > Components: build > Reporter: Petr Široký > Assignee: Petr Široký > > We are seeing intermittent build failures related to {{jaxb2-maven-plugin}} in droolsjbpm-integration repo (kie-remote-jaxb-gen module). Upgrading to latest 2.x version should fix these issues. We should also upgrade to latest version because we are at a start of the development cycle and the risks of breaking something are more acceptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 February 2016