September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2743) Some static references are stored to the ServiceRegistry that do not have permission checks

by Arun Neelicattu (JIRA)

[ https://issues.jboss.org/browse/WFLY-2743?page=com.atlassian.jira.plugin.... ] Arun Neelicattu updated WFLY-2743: ---------------------------------- Security: (was: Red Hat Internal) > Some static references are stored to the ServiceRegistry that do not have permission checks > ------------------------------------------------------------------------------------------- > > Key: WFLY-2743 > URL: https://issues.jboss.org/browse/WFLY-2743 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Labels: CVE-2014-0018, Security, SecurityTracking > Fix For: 8.0.0.Final > > > This enables a deployment to get access to the MSC ServiceRegistry, and from there change internal server state without any security manager checks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3909) Upgrade PicketBox

by David Lloyd (JIRA)

David Lloyd created WFLY-3909: --------------------------------- Summary: Upgrade PicketBox Key: WFLY-3909 URL: https://issues.jboss.org/browse/WFLY-3909 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: David Lloyd Assignee: Darran Lofthouse Fix For: 9.0.0.CR1 Upgrade PicketBox to a version which resolves SECURITY-861. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2210) fix message endpoint isDeliveryTransacted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2210?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2210: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147284 > fix message endpoint isDeliveryTransacted > ----------------------------------------- > > Key: WFLY-2210 > URL: https://issues.jboss.org/browse/WFLY-2210 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The org.jboss.as.ejb3.inflow.MessageEndpointService#isDeliveryTransacted method is checking the transaction attribute of the method using the MethodIntf.BEAN while it should use the MethodIntf.MESSAGE_ENDPOINT type. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1840) Provide docker image for JGroups

by Arne Osthues (JIRA)

[ https://issues.jboss.org/browse/JGRP-1840?page=com.atlassian.jira.plugin.... ] Arne Osthues commented on JGRP-1840: ------------------------------------ My experience with docker and jgroups so far. Running multiple containers on one host works well since all containers can connect to each other through their default interface. For discovery using a gossip router is one solution that works. If the containers run on different hosts it gets more complicated. By default each container can only be reached by its host and other containers. The general ideas to get it working are: * Add an extra software network layer to put the containers into the same network. There are several tools that try to support this approach. i.E. [weave|https://github.com/zettio/weave] , [pipework|https://github.com/jpetazzo/pipework] and [libswarm|https://github.com/docker/libswarm]. * Trying to put the load on jgroups. The different hosts can be treated like different networks separated by a firewall. Using a TUNNEL can be a solution. I haven't found the perfect way yet. I am still trying to avoid the need for the extra software network since this it makes it more complicated to automate starting containers with tools like vagrant or fig. > Provide docker image for JGroups > -------------------------------- > > Key: JGRP-1840 > URL: https://issues.jboss.org/browse/JGRP-1840 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 3.6 > > > Provide a docker image for one or more JGroups demos. People could run multiple instances and see a cluster. Candidates for demos: > * Draw (can we set DISPLAY to be the user's desktop?) > * Topology > * Some replicated map (ReplCache) > * Chat > [1] https://gist.github.com/goldmann/d38589ad919343ba30dd -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3908) Upgrade Weld

by David Lloyd (JIRA)

David Lloyd created WFLY-3908: --------------------------------- Summary: Upgrade Weld Key: WFLY-3908 URL: https://issues.jboss.org/browse/WFLY-3908 Project: WildFly Issue Type: Component Upgrade Components: CDI / Weld Reporter: David Lloyd Assignee: Stuart Douglas Priority: Critical Fix For: 9.0.0.CR1 Upgrade to a version of Weld which includes WELD-1751. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3907) Upgrade Arquillian core

by David Lloyd (JIRA)

David Lloyd created WFLY-3907: --------------------------------- Summary: Upgrade Arquillian core Key: WFLY-3907 URL: https://issues.jboss.org/browse/WFLY-3907 Project: WildFly Issue Type: Component Upgrade Components: Test Suite Reporter: David Lloyd Fix For: 9.0.0.CR1 Upgrade to a version which includes ARQ-1859. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3906) Upgrade jboss-rmi-api_1.0_spec

by David Lloyd (JIRA)

David Lloyd created WFLY-3906: --------------------------------- Summary: Upgrade jboss-rmi-api_1.0_spec Key: WFLY-3906 URL: https://issues.jboss.org/browse/WFLY-3906 Project: WildFly Issue Type: Component Upgrade Components: IIOP Reporter: David Lloyd Assignee: Tomasz Adamski Fix For: 9.0.0.CR1 Upgrade to a version which includes JBEE-156. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-950) RESTEasy: Empty cfg. param javax.ws.rs.Application produces exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-950?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-950: ---------------------------------------------- Weinan Li <weli(a)redhat.com> changed the Status of [bug 899666|https://bugzilla.redhat.com/show_bug.cgi?id=899666] from ASSIGNED to MODIFIED > RESTEasy: Empty cfg. param javax.ws.rs.Application produces exception > --------------------------------------------------------------------- > > Key: WFLY-950 > URL: https://issues.jboss.org/browse/WFLY-950 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Pavel Janousek > Assignee: Weinan Li > > RESTEasy can be configured through several configuration options in WAR application deployment file WEB-INF/web.xml. The major one (also portable defined by JAX-RS standard) is _javax.ws.rs.Application_. When I set this parameter to empty content present behavior is raising exception "java.lang.StringIndexOutOfBoundsException: String index out of range: 0", it is not so good. > I think, this is hard miss-configuration error and deployment description as this one should be rejected and a such application should not be deployed at all with appropriate error message, but not only by messed exception. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-615) Composite Package Descriptors ignore declared Enums

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-615: ------------------------------------- Summary: Composite Package Descriptors ignore declared Enums Key: DROOLS-615 URL: https://issues.jboss.org/browse/DROOLS-615 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Critical Fix For: 6.2.0.Beta2 The Composite Package Descriptor ignores declared enum types -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-234) Support for Javaflow bytecode pattern

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-234?page=com.atlassian.jira.plugi... ] Shigeru Chiba resolved JASSIST-234. ----------------------------------- Fix Version/s: 3.19.0-GA Resolution: Done The patch has been merged. > Support for Javaflow bytecode pattern > ------------------------------------- > > Key: JASSIST-234 > URL: https://issues.jboss.org/browse/JASSIST-234 > Project: Javassist > Issue Type: Patch > Affects Versions: 3.18.2-GA > Reporter: Shigeru Chiba > Assignee: Shigeru Chiba > Fix For: 3.19.0-GA > > > The Apache Javaflow project instruments class files to provide its Continuation capability. One of the bytecode patterns it generates to handle Category 2 parameters is: > NEW > DUP > DUP2_X2 > POP2 > Unfortunately, when Javassist sees this pattern when moving instructions, it recognizes the NEW DUP and removes it in order to do the move. However, this leaves the DUP2_X2 POP2 abandoned which leads to stack corruption and javassist throwing an exception due to a negative stack height. > Given this involves Category 2 operands, there is not much short of a complete rearchitecting that can be done in Javaflow to accommodate the existing Javassist patterns for NEW. Therefore, I ask the the above bytecode pattern be added to the javassist.expr.NewExpr.canReplace() method. I will submit a patch with the proposed change. > Originally reported by Baron Roberts at: > https://github.com/jboss-javassist/javassist/pull/21 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 September 2014