February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1722: -------------------------------- Parallelization doesn't help with message batches: all messages of a batch are decrypted sequentially (using the same cipher though), replaced with the decrypted message, and then the batch is passed up. Parallel decryption of the messages in a batch would probably help here, e.g. using the fork-join framework. > Improve performance of ENCRYPT protocol > --------------------------------------- > > Key: JGRP-1722 > URL: https://issues.jboss.org/browse/JGRP-1722 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Fix For: 3.5 > > > A stress tests with the following setup showed that performance (reads and writes/sec) is halved when ENCRYPT protocol is enabled: > Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on keys, 20 % writes, 80 % reads. > It would be great if we could improve the performance of ENCRYPT protocol. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2205) Undeployment prints null

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2205?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2205: ----------------------------------- Assignee: David Salter (was: Tomaz Cerar) > Undeployment prints null > ------------------------ > > Key: WFLY-2205 > URL: https://issues.jboss.org/browse/WFLY-2205 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Beta1 > Reporter: Jesper Pedersen > Assignee: David Salter > Fix For: 8.0.1.Final > > > The following is printed during a shutdown of an .ear > {noformat} > 11:21:52,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: msginflow1_mdb_msginflow_ejb.jar) in 16ms > 11:21:52,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment null (runtime-name: msginflow_mdb_msginflow_ejb.jar) in 16ms > 11:21:52,262 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment msginflow_mdb.ear (runtime-name: msginflow_mdb.ear) in 18ms > 11:21:52,387 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "msginflow_mdb.ear" (runtime-name: "msginflow_mdb.ear") > {noformat} > The 'null' part of the .jar undeployment doesn't look nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-148) Unbounded ELEvaluator cache can cause OOMEs

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/JBEE-148?page=com.atlassian.jira.plugin.s... ] Aaron Ogburn updated JBEE-148: ------------------------------ Attachment: diff.out Attached a diff reference of the related changes > Unbounded ELEvaluator cache can cause OOMEs > ------------------------------------------- > > Key: JBEE-148 > URL: https://issues.jboss.org/browse/JBEE-148 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jstl-api > Affects Versions: jboss-jstl-api_1.2_spec-1.0.5.Final, jboss-jstl-api_1.2_spec-1.1.0.Final > Reporter: Aaron Ogburn > Assignee: Shelly McGowan > Attachments: diff.out > > > Unbounded jstl ELEvaluator cache can cause OOMEs. > Related community issue: > https://issues.apache.org/bugzilla/show_bug.cgi?id=31789 > This was fixed in 1.0 and 1.1 but never got added to 1.2 so we missed this here too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-148) Unbounded ELEvaluator cache can cause OOMEs

by Aaron Ogburn (JIRA)

Aaron Ogburn created JBEE-148: --------------------------------- Summary: Unbounded ELEvaluator cache can cause OOMEs Key: JBEE-148 URL: https://issues.jboss.org/browse/JBEE-148 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-jstl-api Affects Versions: jboss-jstl-api_1.2_spec-1.1.0.Final, jboss-jstl-api_1.2_spec-1.0.5.Final Reporter: Aaron Ogburn Assignee: Shelly McGowan Unbounded jstl ELEvaluator cache can cause OOMEs. Related community issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=31789 This was fixed in 1.0 and 1.1 but never got added to 1.2 so we missed this here too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3045) Expose JAXRS deployments via the management API

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3045?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-3045: --------------------------------- Assignee: Bill Burke (was: Stuart Douglas) > Expose JAXRS deployments via the management API > ----------------------------------------------- > > Key: WFLY-3045 > URL: https://issues.jboss.org/browse/WFLY-3045 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Bill Burke > > Currently WildFly expose webapps and ejbs deployments through the management API. I think we should also expose in a similar manner the other deployments such as REST resources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3045) Expose JAXRS deployments via the management API

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3045?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3045: ------------------------------ Component/s: Domain Management > Expose JAXRS deployments via the management API > ----------------------------------------------- > > Key: WFLY-3045 > URL: https://issues.jboss.org/browse/WFLY-3045 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, REST > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Bill Burke > > Currently WildFly expose webapps and ejbs deployments through the management API. I think we should also expose in a similar manner the other deployments such as REST resources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3045) Expose JAXRS deployments via the management API

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-3045: --------------------------------------- Summary: Expose JAXRS deployments via the management API Key: WFLY-3045 URL: https://issues.jboss.org/browse/WFLY-3045 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: REST Affects Versions: 8.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Stuart Douglas Currently WildFly expose webapps and ejbs deployments through the management API. I think we should also expose in a similar manner the other deployments such as REST resources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2851) Can't validate jboss-deployment-structure.xml due to incorrect schema

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2851?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2851: ----------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1060719|https://bugzilla.redhat.com/show_bug.cgi?id=1060719] from ON_QA to VERIFIED > Can't validate jboss-deployment-structure.xml due to incorrect schema > --------------------------------------------------------------------- > > Key: WFLY-2851 > URL: https://issues.jboss.org/browse/WFLY-2851 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.CR1 > Reporter: Harald Wellmann > Assignee: Stuart Douglas > Fix For: 8.0.0.Final > > > The following deployment structure cannot be validated against the XML schema: > {code:xml} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <dependencies> > <module name="foo"/> > </dependencies> > </deployment> > </jboss-deployment-structure> > {code} > This looks like a glitch in the schema where the {{module-alias}} element in {{deploymentType}} is missing a {{minOccurs="0"}}. > The same holds for the {{filter}} element of {{resource-root}}, which should be optional according to the schema documentation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-445) Drools Workbench throw Unable to expand in guided rule with DSL

by Claudio D'Angelo (JIRA)

Claudio D'Angelo created DROOLS-445: --------------------------------------- Summary: Drools Workbench throw Unable to expand in guided rule with DSL Key: DROOLS-445 URL: https://issues.jboss.org/browse/DROOLS-445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.1.Final Environment: Linux Debian 64 Tomcat 7.0.42 java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: Claudio D'Angelo Assignee: Mark Proctor Hi, In a project workbench I've defined a data model, a drl, a dsl and an guided rule with dsl. In the guided rule with dsl the wizard (edit tab) work correctly but when I click "Validate" [6] Unable to expand: Richiesta( tipo == "RIMBORSO") [7] Unable to expand: Richiesta( condizione == "LOG") [9] Unable to expand: System.out.println("OK"); My DSL is: [when] La richiesta e' di tipo "{tipo}"=Richiesta( tipo == "{tipo}") [when] la condizione e' "{condizione}"=Richiesta( condizione == "{condizione}") [when] e=and [then] stampa = System.out.println("OK"); I've seen with the source tab of guided rule the converted rule: 1. | import it.test.modulistica.Richiesta; 2. | 3. | rule "bbb" 4. | dialect "mvel" 5. | when 6. | Richiesta( tipo == "RIMBORSO") 7. | Richiesta( condizione == "LOG") 8. | then 9. | System.out.println("OK"); 10. | end but I think that this is the converted rule. I think that the source must be: import it.test.modulistica.Richiesta; rule "bbb" dialect "mvel" when La richiesta e' di tipo "RIMBORSO" la condizione e' "LOG" then stampa end -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1438) Add support for listing WebSocket ServerEndpoints in the CLI

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-1438?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky updated WFLY-1438: ------------------------------------ Component/s: Domain Management Web Services > Add support for listing WebSocket ServerEndpoints in the CLI > ------------------------------------------------------------ > > Key: WFLY-1438 > URL: https://issues.jboss.org/browse/WFLY-1438 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: CLI, Domain Management, Web Services > Affects Versions: 8.0.0.Alpha1 > Reporter: Rich Midwinter > Priority: Minor > > It would be useful to be able to list ServerEndpoints in the cli. This was available in AS7. > https://community.jboss.org/thread/228658 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2014