April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3301) JPA subsystem should check explicitely for java:comp/DefaultDataSource

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3301?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3301: ------------------------------- Attachment: msc.txt hang.txt msc.txt contains the services after waiting a few minutes for the " mvn clean install -Dtest=org.jboss.as.test.integration.jpa.datasourcedefinition.DataSourceDefinitionJPATestCase" test to complete deployment. hang.txt contains a thread dump of the app server > JPA subsystem should check explicitely for java:comp/DefaultDataSource > ---------------------------------------------------------------------- > > Key: WFLY-3301 > URL: https://issues.jboss.org/browse/WFLY-3301 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.1.0.Final > > Attachments: hang.txt, msc.txt > > > Improve checking for default datasource. Workaround for this issue to set the persistence unit "wildfly.jpa.twophasebootstrap" hint to false. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3301) JPA subsystem should check explicitely for java:comp/DefaultDataSource

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3301?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-3301: ------------------------------------ I'm intermittently seeing the "mvn clean install -Dtest=org.jboss.as.test.integration.jpa.datasourcedefinition.DataSourceDefinitionJPATestCase" test succeed or stall. > JPA subsystem should check explicitely for java:comp/DefaultDataSource > ---------------------------------------------------------------------- > > Key: WFLY-3301 > URL: https://issues.jboss.org/browse/WFLY-3301 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.1.0.Final > > Attachments: hang.txt, msc.txt > > > Improve checking for default datasource. Workaround for this issue to set the persistence unit "wildfly.jpa.twophasebootstrap" hint to false. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3274) Expose connector metric values such as requestCount , maxTime, bytesReceived, etc

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3274?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3274: --------------------------------- Summary: Expose connector metric values such as requestCount , maxTime, bytesReceived, etc (was: connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final ) Issue Type: Feature Request (was: Enhancement) > Expose connector metric values such as requestCount , maxTime, bytesReceived, etc > --------------------------------------------------------------------------------- > > Key: WFLY-3274 > URL: https://issues.jboss.org/browse/WFLY-3274 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Tomaz Cerar > > while using jboss 7.2.0 we were able to fetch above values from the cli command as > {noformat} > [domain@test.com:9999 subsystem=web] ls > configuration valve default-virtual-server=default-host native=false > connector virtual-server instance-id=${jboss.node.name} > [domain@test.com:9999 connector] ls > ajp http > [domain@test.com:9999 connector] cd http > [domain@test.com:9999 connector] pwd > /profile=ha/subsystem=web/connector=http > [domain@test.com:9999 connector=http] ls > configuration max-connections=undefined proxy-port=undefined > ssl max-post-size=2097152 redirect-port=443 > bytesReceived= max-save-post-size=4096 requestCount= > bytesSent= maxTime= scheme=http > enable-lookups=false name=http secure=false > enabled=true processingTime= socket-binding=http > errorCount= protocol=HTTP/1.1 virtual-server=undefined > executor=undefined proxy-name=undefined > {noformat} > > Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8) > as below > {noformat} > [domain@test2.com:9990 subsystem=undertow] ls > buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 ) > configuration servlet-container default-virtual-host=default-host > error-page default-server=default-server instance-id=${jboss.node.name} > {noformat} > > but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as > {noformat} > [domain@test2.com:9990 server=default-server] ls > ajp-listener host http-listener https-listener default-host=default-host servlet-container=default > {noformat} > after getting into http-listener we get the below > {noformat} > [domain@test2.com:9990 http-listener=default] ls > allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http > always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8 > buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default > buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https > {noformat} > > Can someone please look into it ..? -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2652) Add/remove load metric operations should not require service restart

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2652?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-2652: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Add/remove load metric operations should not require service restart > -------------------------------------------------------------------- > > Key: WFLY-2652 > URL: https://issues.jboss.org/browse/WFLY-2652 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1487) AUTH: X509Token Authentication is vulnerable to replay attacks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1487?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1487: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1021952|https://bugzilla.redhat.com/show_bug.cgi?id=1021952] from NEW to CLOSED > AUTH: X509Token Authentication is vulnerable to replay attacks > -------------------------------------------------------------- > > Key: JGRP-1487 > URL: https://issues.jboss.org/browse/JGRP-1487 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.0.9 > Reporter: sreenivas chinimilli > Assignee: Tristan Tarrant > Fix For: 3.5 > > > In the implementation of X509Token Authentication > The auth_value is enrypted with the certificate within the keystore and > during verification encrypted auth value is decrypted with the private key > compared against the orignial auth value. > This implementation is prone to replay attacks, that is > any user with out having any knowledge of the auth value can join the group > by replaying the enrypted auth value captured in earlier sessions. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3031) Management audit logging logs parallel boot ops in separate records

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3031?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3031: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092220|https://bugzilla.redhat.com/show_bug.cgi?id=1092220] from ASSIGNED to POST > Management audit logging logs parallel boot ops in separate records > ------------------------------------------------------------------- > > Key: WFLY-3031 > URL: https://issues.jboss.org/browse/WFLY-3031 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The parallel boot ops (i.e. the subsystem stuff) are logged in separate log records from the other stuff. > This is questionable because they are actually all part of the same execution. The main execution blocks for the parallel ops. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2997) AccessAuditContext domainUUID is not set when the domain-uuid header is set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2997?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2997: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092213|https://bugzilla.redhat.com/show_bug.cgi?id=1092213] from ASSIGNED to POST > AccessAuditContext domainUUID is not set when the domain-uuid header is set > --------------------------------------------------------------------------- > > Key: WFLY-2997 > URL: https://issues.jboss.org/browse/WFLY-2997 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler creates a UUID and sets "operations-headers" => "domain-uuid" on the op, but it does not pass the same UUID to AccessAuditContext. The result is the log record has null in the domainUUID field but the operation headers part of the "ops" field shows the uuid. Confusing. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3017: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092206|https://bugzilla.redhat.com/show_bug.cgi?id=1092206] from ASSIGNED to POST > OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config > -------------------------------------------------------------------------------------------- > > Key: WFLY-3017 > URL: https://issues.jboss.org/browse/WFLY-3017 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true): > 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this. > 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this. > Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2891) Not authorised write operation does not get audit logged if log-read-only="false"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2891?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2891: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092203|https://bugzilla.redhat.com/show_bug.cgi?id=1092203] from ASSIGNED to POST > Not authorised write operation does not get audit logged if log-read-only="false" > --------------------------------------------------------------------------------- > > Key: WFLY-2891 > URL: https://issues.jboss.org/browse/WFLY-2891 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > This is because audit logging uses the controller lock to find out if the model was a write operation. If rbac is enabled and an operation is not authorised, the error happens before the controller lock is taken. So if audit log log-read-only="false" the failed operation does not get logged. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3020) LogStoreProbeHandler overwrites the LogStoreResource root model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3020?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3020: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092198|https://bugzilla.redhat.com/show_bug.cgi?id=1092198] from ASSIGNED to POST > LogStoreProbeHandler overwrites the LogStoreResource root model > --------------------------------------------------------------- > > Key: WFLY-3020 > URL: https://issues.jboss.org/browse/WFLY-3020 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > LogStoreProbeHandler replaces the 'delegate' held by LogStoreResource. Doing this removes any data from the existing delegate's 'model' field, i.e. the "type" attribute. -- 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

12 years

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 April 2014