September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-129: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1147352|https://bugzilla.redhat.com/show_bug.cgi?id=1147352] from NEW to ASSIGNED > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha9 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-129: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147352 > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha9 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFCORE-129: ----------------------------------------- Summary: Overlay does not work for subunits in exploded deployments. Key: WFCORE-129 URL: https://issues.jboss.org/browse/WFCORE-129 Project: WildFly Core Issue Type: Bug Components: Server Affects Versions: 1.0.0.Alpha8 Reporter: Bartosz Baranowski Assignee: Bartosz Baranowski Fix For: 1.0.0.Alpha9 If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3567) Unchecked access to MSC Service Registry under JSM

by Arun Neelicattu (JIRA)

[ https://issues.jboss.org/browse/WFLY-3567?page=com.atlassian.jira.plugin.... ] Arun Neelicattu resolved WFLY-3567. ----------------------------------- Fix Version/s: 8.0.0.Final Resolution: Duplicate Issue This was resolved via WFLY-2743. > Unchecked access to MSC Service Registry under JSM > -------------------------------------------------- > > Key: WFLY-3567 > URL: https://issues.jboss.org/browse/WFLY-3567 > Project: WildFly > Issue Type: Bug > Components: MSC > Reporter: Dipak Kesarkar > Assignee: David Lloyd > Fix For: 8.0.0.Final > > > When is the fix for this security issue https://access.redhat.com/security/cve/CVE-2014-0018 planned in Wildfly? > In which version? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[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)

9 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)

9 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)

9 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)

9 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)

9 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)

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