June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-514) Clean up jetty dependencies in kie-parent-with-dependencies pom.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-514?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer resolved DROOLS-514. ------------------------------------------- Resolution: Done > Clean up jetty dependencies in kie-parent-with-dependencies pom.xml > ------------------------------------------------------------------- > > Key: DROOLS-514 > URL: https://issues.jboss.org/browse/DROOLS-514 > Project: Drools > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta4 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Attachments: jetty-depTree.txt > > > 1) Make an inventory (using "mvn-all dependency:tree) of all modules that use jetty dependency and clearly indicate per module: > - Jetty groupId and Jetty version > - Scope: test or production > - Build classpath: normal dependency or plugin dependency (latter makes scope n/a) > 2) In theory, we should have no normal dependency in a non-test scope to Jetty, as our stuff is deployed on JBoss EAP, Tomcat, Jetty and WildFly alike. Is this true? > GWT does use Jetty, but only during compilation (= plugin classpath, not the dependencies classpath). gwt-dev is a fat jar that includes jetty even... but gwt-dev shouldn' be in the dependencies either (but it is and it needs to be removed!). > 3) Based on this inventory, discuss with ge0ffrey and mantis plan of attack. > Goal: Get rid of the jetty mess in kie-parent-with-dependencies. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3450) Allow addition of HTTP headers to management console responses

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/WFLY-3450?page=com.atlassian.jira.plugin.... ] James Livingston commented on WFLY-3450: ---------------------------------------- Sorry, I wasn't clear - yes I meant web console to browser responses. You could for example add "X-Frame-Options: deny" to prevent the console from being places in various kinds of framing, to help prevent "clickjacking". There are plenty more environment-specific headers that may be useful in some situtations. > Allow addition of HTTP headers to management console responses > -------------------------------------------------------------- > > Key: WFLY-3450 > URL: https://issues.jboss.org/browse/WFLY-3450 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: James Livingston > Assignee: Heiko Braun > > It would be useful to be able to add additional HTTP headers to the responses from the web management console, such as X-Frame-Options. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3422) VFSResourceLoader is creating too many code sources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3422?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3422: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1103298|https://bugzilla.redhat.com/show_bug.cgi?id=1103298] from MODIFIED to ON_QA > VFSResourceLoader is creating too many code sources > --------------------------------------------------- > > Key: WFLY-3422 > URL: https://issues.jboss.org/browse/WFLY-3422 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, VFS > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 8.1.0.Final, 9.0.0.Alpha1 > > > A new code source is being created for every class. We should be mapping code signer lists to cached code sources instead. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3392) Make the test suite more robust for DomainDeployWithRuntimeNameTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3392?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3392: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1100223|https://bugzilla.redhat.com/show_bug.cgi?id=1100223] from MODIFIED to ON_QA > Make the test suite more robust for DomainDeployWithRuntimeNameTestCase > ----------------------------------------------------------------------- > > Key: WFLY-3392 > URL: https://issues.jboss.org/browse/WFLY-3392 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR2 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Trivial > Fix For: 9.0.0.Alpha1 > > > The test DomainDeployWithRuntimeNameTestCase depends on the server groups list which is backed by a Set. > Converting it to a list ands osrting it makes the test more reliable -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3375) The HornetQ address settings are not properly inherited

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3375?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3375: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1099404|https://bugzilla.redhat.com/show_bug.cgi?id=1099404] from MODIFIED to ON_QA > The HornetQ address settings are not properly inherited > -------------------------------------------------------- > > Key: WFLY-3375 > URL: https://issues.jboss.org/browse/WFLY-3375 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.2.2 > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 9.0.0.Alpha1 > > > When using multiple address settings in HornetQ configuration the address setting should be inherited from more generic setting by more specific setting. If two address setting are used like > {code:xml} > <address-settings> > <address-setting match="#"> > <dead-letter-address>jms.queue.DLQ</dead-letter-address> > <expiry-address>jms.queue.ExpiryQueue</expiry-address> > <redelivery-delay>0</redelivery-delay> > <max-delivery-attempts>5</max-delivery-attempts> > <max-size-bytes>10485760</max-size-bytes> > <page-size-bytes>2097152</page-size-bytes> > <address-full-policy>PAGE</address-full-policy> > <message-counter-history-day-limit>10</message-counter-history-day-limit> > </address-setting> > <address-setting match="jms.queue.testQueue"> > <dead-letter-address>jms.queue.DLQ</dead-letter-address> > <expiry-address>jms.queue.ExpiryQueue</expiry-address> > <redelivery-delay>0</redelivery-delay> > <max-size-bytes>10485760</max-size-bytes> > <page-size-bytes>2097152</page-size-bytes> > <address-full-policy>PAGE</address-full-policy> > <message-counter-history-day-limit>10</message-counter-history-day-limit> > </address-setting> > </address-settings> > {code} > It is expected that the setting for {{jms.queue.testQueue}} would inherit {{max-delivery-attempts}} from default address setting {{"#"}} but it does not. Instead if uses the default value for {{max-delivery-attempts}} which is *9*. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3374) Upgrade HAL to 2.2.7.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3374?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3374: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1099366|https://bugzilla.redhat.com/show_bug.cgi?id=1099366] from MODIFIED to ON_QA > Upgrade HAL to 2.2.7.Final > -------------------------- > > Key: WFLY-3374 > URL: https://issues.jboss.org/browse/WFLY-3374 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 8.1.0.Final > > > Fixes HAL-396 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2789) Remote client transaction timeout values are overwrote by hardcoded values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2789?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2789: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1093128|https://bugzilla.redhat.com/show_bug.cgi?id=1093128] from MODIFIED to ON_QA > Remote client transaction timeout values are overwrote by hardcoded values > -------------------------------------------------------------------------- > > Key: WFLY-2789 > URL: https://issues.jboss.org/browse/WFLY-2789 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Johnathon Lee > Assignee: David Lloyd > Fix For: 8.1.0.Final, 9.0.0.Alpha1 > > > The EJB3 interceptor is not using client values for timeouts, this is a problem for users trying to use EJB for transaction propagation. > Refer to the code in https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...: > private void createOrResumeXidTransaction(final XidTransactionID xidTransactionID) throws Exception { > final TransactionManager transactionManager = this.ejbRemoteTransactionsRepository.getTransactionManager(); > final Transaction alreadyCreatedTx = this.ejbRemoteTransactionsRepository.getImportedTransaction(xidTransactionID); > if (alreadyCreatedTx != null) { > // resume the already created tx > transactionManager.resume(alreadyCreatedTx); > } else { > // begin a new tx and add it to the tx repository > // TODO: Fix the tx timeout (which currently is passed as 300 seconds) > final Transaction newSubOrdinateTx = this.ejbRemoteTransactionsRepository.importTransaction(xidTransactionID, 300); > // associate this tx with the thread > transactionManager.resume(newSubOrdinateTx); > } > } -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-465) Attribute check-for-live-server must set on live server to faillback

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-465?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-465: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 908261|https://bugzilla.redhat.com/show_bug.cgi?id=908261] from MODIFIED to ON_QA > Attribute check-for-live-server must set on live server to faillback > -------------------------------------------------------------------- > > Key: WFLY-465 > URL: https://issues.jboss.org/browse/WFLY-465 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 8.2.0.CR1 > > Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml > > > When there is live/backup pair with replicated journal then it should be sufficient to set attribute "check-for-live-server" in messaging subsystem only on backup to force backup server to shutdown when live server comes alive again. Problem is this won't happen. > Only when attribute "check-for-live-server" is set on live server then failback is successful (backup shutdown itself) > It's not well documented where "check-for-live-server" should be set in HornetQ project documentation: > http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/inde... > This issue was hit with EAP 6.1.0.DR2 (HQ 2.3.0.CR1). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3418) deployed applications are not distributed to host controller(s)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3418?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3418: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1102752|https://bugzilla.redhat.com/show_bug.cgi?id=1102752] from MODIFIED to ON_QA > deployed applications are not distributed to host controller(s) > --------------------------------------------------------------- > > Key: WFLY-3418 > URL: https://issues.jboss.org/browse/WFLY-3418 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.CR2 > Environment: Wildfly 8.1.0 CR5 domain mode > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > when a new HC is brought up into an existing DC/HC environment, it does not receive a copy of all deployed applications (e.g. the "content" folder) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3358) Mixed domain testing must use vanilla distributions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3358?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3358: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1098065|https://bugzilla.redhat.com/show_bug.cgi?id=1098065] from MODIFIED to ON_QA > Mixed domain testing must use vanilla distributions > --------------------------------------------------- > > Key: WFLY-3358 > URL: https://issues.jboss.org/browse/WFLY-3358 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > Priority: Critical > > With a vanilla distribution zip mixed domain testing fails with: > java.lang.IllegalStateException: Could not find /home/jboss/hudson_workspace/jobs/eap6-testsuite/workspace/testsuite/mixed-domain/target/old-versions/jboss-eap-6.2.0 > It must be possible to use vanilla distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 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 June 2014