March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4460) Speed up clustering test suite using ARQ custom containers

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-4460?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4460: ------------------------------------- PS: the decision was not to merge this for AS 7.x versions. > Speed up clustering test suite using ARQ custom containers > ---------------------------------------------------------- > > Key: AS7-4460 > URL: https://issues.jboss.org/browse/AS7-4460 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering, Test Suite > Affects Versions: 7.1.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Leveraging ARQ-850. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6745) Clustering tests leave a hanging instance if they are run in opposite order

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-6745: ----------------------------------- Summary: Clustering tests leave a hanging instance if they are run in opposite order Key: AS7-6745 URL: https://issues.jboss.org/browse/AS7-6745 Project: Application Server 7 Issue Type: Enhancement Components: Clustering, Test Suite Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 8.0.0.Alpha1 Interestingly, if the tests are run in the opposite order i.e. alphabetically, one server instance remains running and doesnt switch off. I have used a workaround for now {code} +  + <runOrder>reversealphabetical</runOrder> {code} -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6745) Clustering tests leave a hanging instance if they are run in opposite order

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-6745?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-6745: ------------------------------------- Workaround: https://github.com/jbossas/jboss-as/commit/8a6aac3c8eb6bc94b7eddfa4d090c9... > Clustering tests leave a hanging instance if they are run in opposite order > --------------------------------------------------------------------------- > > Key: AS7-6745 > URL: https://issues.jboss.org/browse/AS7-6745 > Project: Application Server 7 > Issue Type: Enhancement > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Interestingly, if the tests are run in the opposite order i.e. alphabetically, one server instance remains running and doesnt switch off. > I have used a workaround for now > {code} > +  > + <runOrder>reversealphabetical</runOrder> > {code} -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6744) Upgrade Hibernate to 4.2.0 Final

by Dave Stahl (JIRA)

Dave Stahl created AS7-6744: ------------------------------- Summary: Upgrade Hibernate to 4.2.0 Final Key: AS7-6744 URL: https://issues.jboss.org/browse/AS7-6744 Project: Application Server 7 Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Dave Stahl Assignee: Scott Marlow Upgrade Hibernate from 4.2.0.CR2 to 4.2.0.Final -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6743) Move javadoc configuration into a separate module pom

by Paul Gier (JIRA)

Paul Gier created AS7-6743: ------------------------------ Summary: Move javadoc configuration into a separate module pom Key: AS7-6743 URL: https://issues.jboss.org/browse/AS7-6743 Project: Application Server 7 Issue Type: Enhancement Components: Build System Reporter: Paul Gier Assignee: Ondrej Zizka Fix For: 8.0.0.Alpha1 There is a lot of javadoc configuration information in build/pom.xml. Since this pom is already pretty large even without the javadoc config, it might be good to move the javadoc generation to a separate module and pom. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6730) switching users between ejb calls does not work when the call originates from a remote client

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/AS7-6730?page=com.atlassian.jira.plugin.s... ] Derek Horton updated AS7-6730: ------------------------------ Issue Type: Bug (was: Feature Request) > switching users between ejb calls does not work when the call originates from a remote client > --------------------------------------------------------------------------------------------- > > Key: AS7-6730 > URL: https://issues.jboss.org/browse/AS7-6730 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Description of problem: > Switching users between ejb calls does not work when the call originates > from a remote client. In this case, both ejbs are on the same JBoss instance. > The use case looks like the following: > remote standalone client ---> unsecured ejb3 (switch user here) -> secured ejb3 > I tried to use both approaches outlined in Q10/A10 of the JBoss > Security FAQ [1] in order to establish a security context in > the unsecured ejb that should be used to invoke the secured ejb. > Neither approach worked in my testing. > When the same unsecured ejb is called from a web application (secured > or unsecured), then the user switching works correctly. > The ejb security code appears to work differently based on the client > type (standalone remote ejb client vs a web application). > I believe this is happening because the > org.jboss.as.security.service.SimpleSecurityManager.push method (called > by the SecurityContextInterceptor) is checking for an existing > RemotingContext and grabbing the security context from there even > though the security context that should be used appears to be getting > propagated correctly. > The following area of the code appears to be causing the issue. This > section of code is executed which causes the newly established security > context to be ignored: > if (RemotingContext.isSet()) { > // In this case the principal and credential will not have been set to set some random values. > SecurityContextUtil util = current.getUtil(); > Steps to Reproduce: > Create a test application that looks like the following: > remote client ---> unsecured ejb3 (switch user here) -> secured ejb3 > Actual results: > If the unsecured ejb is invoked from a remote client, the user switching that takes place in the first ejb is ignored. Replace the remote standalone client with a web application and the user switching works. > Expected results: > User switching should work if the client is a standalone remote client or a web application. > Additional info: -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1010) Addition of the 4470 FATAL error for the DB2 ExceptionSorter

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1010?page=com.atlassian.jira.plugin... ] Johnathon Lee updated JBJCA-1010: --------------------------------- Attachment: JBJCA-1010.patch > Addition of the 4470 FATAL error for the DB2 ExceptionSorter > ------------------------------------------------------------ > > Key: JBJCA-1010 > URL: https://issues.jboss.org/browse/JBJCA-1010 > Project: IronJacamar > Issue Type: Feature Request > Components: JDBC > Reporter: Johnathon Lee > Assignee: Jesper Pedersen > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > Attachments: JBJCA-1010.patch > > > DB2 has a FATAL SQL error code of 4470 that needs to be handled by the DB2ExceptionSorter -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-92) Add support for Equinox ExtendedLogService

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-92?page=com.atlassian.jira.plug... ] Philippe Marschall updated JBLOGGING-92: ---------------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logging/pull/5 > Add support for Equinox ExtendedLogService > ------------------------------------------ > > Key: JBLOGGING-92 > URL: https://issues.jboss.org/browse/JBLOGGING-92 > Project: JBoss Logging > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jboss-logging-spi > Reporter: Philippe Marschall > Assignee: David Lloyd > > We are running some JBoss libraries that use jboss-logging inside Eclipse RCP. We'd like to centralise all our logging. Unfortunately OSGi LogService does not support named loggers, for now they're only available through the Equinox ExtendedLogService. > I'll attach a pull request. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-82) unbalanced braces ( ... ) error when performing equalsIgnoreCase where RHS contains !. operator

by Marcin Grzejszczak (JIRA)

[ https://issues.jboss.org/browse/DROOLS-82?page=com.atlassian.jira.plugin.... ] Marcin Grzejszczak updated DROOLS-82: ------------------------------------- Attachment: Test.zip Project needed to replicate the issue > unbalanced braces ( ... ) error when performing equalsIgnoreCase where RHS contains !. operator > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-82 > URL: https://issues.jboss.org/browse/DROOLS-82 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5 > Reporter: Marcin Grzejszczak > Assignee: Mark Proctor > Attachments: Test.zip > > > GIVEN RULE: > rule "Nested nested model rule - doesn't compile" > dialect "mvel" > when > $model : Model( $nestedModel : nestedModel, > $nestedNestedModel : nestedModel!.nestedNestedModel, > "NestedNestedModelName".equalsIgnoreCase(nestedModel!.nestedNestedModel!.nestedNestedModelName) ) > then > System.out.println( "I'm a nested nested model! My name is [" + $nestedNestedModel.nestedNestedModelName +"] " ); > end > The following error occurs: > Caused by: java.lang.RuntimeException: Unable to Analyse Expression "NestedNestedModelName".equalsIgnoreCase(nestedModel != null && "NestedNestedModelName".equalsIgnoreCase(nestedModel.nestedNestedModel != null && "NestedNestedModelName".equalsIgnoreCase(nestedModel.nestedNestedModel.nestedNestedModelName): > [Error: unbalanced braces ( ... )] > [Near : {... me".equalsIgnoreCase(nestedModel != null && "Neste ....}] > ^ > [Line: 6, Column: 4] : [Rule name='Nested nested model rule - doesn't compile'] > at org.drools.container.spring.beans.KnowledgeBaseBeanFactory.afterPropertiesSet(KnowledgeBaseBeanFactory.java:121) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477) > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417) > ... 17 more > The project needed to replicate the issue is attached to the issue -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-82) unbalanced braces ( ... ) error when performing equalsIgnoreCase where RHS contains !. operator

by Marcin Grzejszczak (JIRA)

Marcin Grzejszczak created DROOLS-82: ---------------------------------------- Summary: unbalanced braces ( ... ) error when performing equalsIgnoreCase where RHS contains !. operator Key: DROOLS-82 URL: https://issues.jboss.org/browse/DROOLS-82 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5 Reporter: Marcin Grzejszczak Assignee: Mark Proctor Attachments: Test.zip GIVEN RULE: rule "Nested nested model rule - doesn't compile" dialect "mvel" when $model : Model( $nestedModel : nestedModel, $nestedNestedModel : nestedModel!.nestedNestedModel, "NestedNestedModelName".equalsIgnoreCase(nestedModel!.nestedNestedModel!.nestedNestedModelName) ) then System.out.println( "I'm a nested nested model! My name is [" + $nestedNestedModel.nestedNestedModelName +"] " ); end The following error occurs: Caused by: java.lang.RuntimeException: Unable to Analyse Expression "NestedNestedModelName".equalsIgnoreCase(nestedModel != null && "NestedNestedModelName".equalsIgnoreCase(nestedModel.nestedNestedModel != null && "NestedNestedModelName".equalsIgnoreCase(nestedModel.nestedNestedModel.nestedNestedModelName): [Error: unbalanced braces ( ... )] [Near : {... me".equalsIgnoreCase(nestedModel != null && "Neste ....}] ^ [Line: 6, Column: 4] : [Rule name='Nested nested model rule - doesn't compile'] at org.drools.container.spring.beans.KnowledgeBaseBeanFactory.afterPropertiesSet(KnowledgeBaseBeanFactory.java:121) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417) ... 17 more The project needed to replicate the issue is attached to the issue -- 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

13 years, 1 month

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