November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1893) Restarting server with a disabled DS enables the DS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1893?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1893: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 952277|https://bugzilla.redhat.com/show_bug.cgi?id=952277] from MODIFIED to ON_QA > Restarting server with a disabled DS enables the DS > --------------------------------------------------- > > Key: WFLY-1893 > URL: https://issues.jboss.org/browse/WFLY-1893 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Reporter: Kabir Khan > Assignee: Stefano Maestri > > See https://issues.jboss.org/browse/WFLY-1874 > If you add a datasource with > subsystem=datasources/data-source=Test:add(jndi-name=java:/Test,jta=false,use-ccm=false,connection-url=url,driver-class=org.h2.Driver,driver-name=h2,user-name=user,password=pass,validate-on-match=false,background-validation=false,share-prepared-statements=false) > it shows up as not enabled/undefined: > {code} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=Test:read-resource{ "outcome" => "success", > "result" => { > ... > "enabled" => false, > {code} > {code} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=Test:read-resource(include-defaults=false) > { > "outcome" => "success", > "result" => { > ... "enabled" => undefined, > {code} > This is persisted as > {code} > <datasource jta="false" jndi-name="java:/Test" pool-name="Test" enabled="false" use-ccm="false"> > <connection-url>url</connection-url> > <driver-class>org.h2.Driver</driver-class> > <driver>h2</driver> > <security> > <user-name>user</user-name> > <password>pass</password> > </security> > <validation> > <validate-on-match>false</validate-on-match> > <background-validation>false</background-validation> > </validation> > <statement> > <share-prepared-statements>false</share-prepared-statements> > </statement> > </datasource> > {code} > Now if you stop and start the server again you end up with enabled=true. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2394) AccessControlContext and management users Subject leaking into thread pool of host controller executor.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2394?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2394: ----------------------------------------------- Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 1024072|https://bugzilla.redhat.com/show_bug.cgi?id=1024072] Verified with EAP 6.2.0.ER7. > AccessControlContext and management users Subject leaking into thread pool of host controller executor. > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-2394 > URL: https://issues.jboss.org/browse/WFLY-2394 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The JBossThreadFactory in use for the executor service is allowing for the AccessControlContext of the thread submitting the Runnable task to the executor to be associated with the Thread created. > Additional precautions should be taken within the HostController to prevent this association. > Where a Subject does need to be associated this should be handled manually. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2394) AccessControlContext and management users Subject leaking into thread pool of host controller executor.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2394?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2394: ----------------------------------------------- Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 1024072|https://bugzilla.redhat.com/show_bug.cgi?id=1024072] from ON_QA to VERIFIED > AccessControlContext and management users Subject leaking into thread pool of host controller executor. > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-2394 > URL: https://issues.jboss.org/browse/WFLY-2394 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The JBossThreadFactory in use for the executor service is allowing for the AccessControlContext of the thread submitting the Runnable task to the executor to be associated with the Thread created. > Additional precautions should be taken within the HostController to prevent this association. > Where a Subject does need to be associated this should be handled manually. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2394) AccessControlContext and management users Subject leaking into thread pool of host controller executor.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2394?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2394: ----------------------------------------------- Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 1024072|https://bugzilla.redhat.com/show_bug.cgi?id=1024072] > AccessControlContext and management users Subject leaking into thread pool of host controller executor. > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-2394 > URL: https://issues.jboss.org/browse/WFLY-2394 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The JBossThreadFactory in use for the executor service is allowing for the AccessControlContext of the thread submitting the Runnable task to the executor to be associated with the Thread created. > Additional precautions should be taken within the HostController to prevent this association. > Where a Subject does need to be associated this should be handled manually. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-317) Multiple issues with named consequences

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-317: ---------------------------------- Summary: Multiple issues with named consequences Key: DROOLS-317 URL: https://issues.jboss.org/browse/DROOLS-317 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Named consequences have the following issues: - consequence name not set for MVEL (java ok) - branch update using wrong leftTuple in phreak - missing consequence names not detected at compile time - LogicTransformer doesn't process branches with or correctly -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-212) FieldAccess.replace causes java.lang.VerifyError

by Jungkook Kim (JIRA)

Jungkook Kim created JASSIST-212: ------------------------------------ Summary: FieldAccess.replace causes java.lang.VerifyError Key: JASSIST-212 URL: https://issues.jboss.org/browse/JASSIST-212 Project: Javassist Issue Type: Bug Affects Versions: 3.18.1-GA, 3.18.0-GA, 3.17.1-GA, 3.17.0-GA Environment: JAVA7 Reporter: Jungkook Kim Assignee: Shigeru Chiba FieldAccess.replace causes java.lang.VerifyError with a specific code structure. javassist version 3.17.0~3.18.1 3.16.1 works fine. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2430) App with custom ContainerResponseFilter (JAX-RS) fails deploy

by Rudy De Busscher (JIRA)

[ https://issues.jboss.org/browse/WFLY-2430?page=com.atlassian.jira.plugin.... ] Rudy De Busscher updated WFLY-2430: ----------------------------------- Attachment: exampleRest.zip Minimal app to reproduce problem > App with custom ContainerResponseFilter (JAX-RS) fails deploy > ------------------------------------------------------------- > > Key: WFLY-2430 > URL: https://issues.jboss.org/browse/WFLY-2430 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7 > Reporter: Rudy De Busscher > Assignee: Stuart Douglas > Attachments: exampleRest.zip > > > Created a simple rest application with a ContainerResponseFilter. The deploy fails with a ClassNotFoundException of javax.ws.rs.container.ContainerResponseFilter. > See also https://community.jboss.org/message/844105 -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2433) please tag 7.3 in community repository

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/WFLY-2433?page=com.atlassian.jira.plugin.... ] Tom Eicher commented on WFLY-2433: ---------------------------------- note: filed as wilfly issue, as the as7 project is closed. please move to as7 if possible. > please tag 7.3 in community repository > -------------------------------------- > > Key: WFLY-2433 > URL: https://issues.jboss.org/browse/WFLY-2433 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Eicher > > According to JBoss dowload page, at EAP 6.2.0, there is a JBoss AS 7.3.0 release; however no such release can be found in as7 or wildfly repository. > Please tag the 7.3.0 in either repository, so as not to have the community completely out of the loop. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2433) please tag 7.3 in community repository

by Tom Eicher (JIRA)

Tom Eicher created WFLY-2433: -------------------------------- Summary: please tag 7.3 in community repository Key: WFLY-2433 URL: https://issues.jboss.org/browse/WFLY-2433 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Eicher According to JBoss dowload page, at EAP 6.2.0, there is a JBoss AS 7.3.0 release; however no such release can be found in as7 or wildfly repository. Please tag the 7.3.0 in either repository, so as not to have the community completely out of the loop. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBREM-1318) Zero is a valid value so SoLinger

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1318?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1318: ---------------------------------- Oh, I see. Linking this issue to JBREM-1307. > Zero is a valid value so SoLinger > --------------------------------- > > Key: JBREM-1318 > URL: https://issues.jboss.org/browse/JBREM-1318 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.5.4.SP3 > Reporter: Doug Grove > Priority: Minor > > MicroSocketClientInvoker checks to see that SoLinger is greater than zero: > if (soLingerSet && > soLingerDuration > 0) s.setSoLinger(soLinger, soLingerDuration); > Zero is a valid value for SoLinger. > The code should be changed to greater than or equal to zero. -- 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

11 years, 1 month

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 November 2013