May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8366) Failure to deploy a war file with JBoss 5.0

by Sasha Matison (JIRA)

Failure to deploy a war file with JBoss 5.0 ------------------------------------------- Key: JBAS-8366 URL: https://jira.jboss.org/browse/JBAS-8366 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.GA Environment: Windows 2003 R2 SP2, JBoss AS 5.0, JDK 1.6_16 Reporter: Sasha Matison Assignee: Scott M Stark Priority: Blocker While deploying our war file with JBoss AS 5.0 we are getting the following error: org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser We are shipping the product with a version of Xerces-j 2.9.1. Removing this version from the product is not an option. Note that the war file used to work with JBoss 4.x. This issue is blocking JBoss 5.0 testing. Please advise on the solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

4
5
0 / 0

[JBoss JIRA] (JBRULES-3363) Add support to inline constraints on multi-function accumulate

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3363: -------------------------------------- Summary: Add support to inline constraints on multi-function accumulate Key: JBRULES-3363 URL: https://issues.jboss.org/browse/JBRULES-3363 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.4.0.Beta1 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.4.0.Beta2 FROM MARK: =========== Edson, While I don't want to change to acc/for keyword quite yet, until we are sure what drastic changes we want to make to syntax. I think we can evolve accumulate() 1) make the first ", " optionall [,;]. Where the documented new separate is ";" 2) functions are still "," separated 3) allow an optional second ";" after this boolean expression, an eval without the eval wrapper. 3. can be done now with a separate eval(....) after the accumulate. But I think good to encapsulate the intent of the guard within the accumulate itself, it's also another opportunity to remove the "eval" keyword for a common use case. For now we'll just rewrite the accumulate to place an eval() CE after the acc. It's a small win, which I think will make the DRL look nicer, especially for CEP use cases. ============ FROM EDSON: ============ Mark, (1) and (2) are ok. Regarding (3), we can embed the expression in the accumulate node itself. No need for a separate node. And if we use ; as the separator, we don't need the eval() keyword. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
7
0 / 0

[JBoss JIRA] (AS7-4686) CLONE - Problems in asynchronous invocation of bean with security domain definition after authenticated remote call to another bean

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-4686?page=com.atlassian.jira.plugin.s... ] Stuart Douglas moved JBPAPP-8888 to AS7-4686: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4686 (was: JBPAPP-8888) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 5) Component/s: EJB Security (was: EJB) (was: Security) Security: (was: Public) Fix Version/s: 7.1.2.Final-redhat1 (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Problems in asynchronous invocation of bean with security domain definition after authenticated remote call to another bean > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4686 > URL: https://issues.jboss.org/browse/AS7-4686 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Security > Affects Versions: 7.1.1.Final > Reporter: Ondřej Chaloupka > Assignee: Stuart Douglas > Labels: eap6_need_triage > Fix For: 7.1.2.Final-redhat1 > > > I have a security test which invokes bean asynchronously (https://github.com/ochaloup/jboss-as/blob/6cfe25f2bc05ca03592b465470b33e4...). > The test is run (deployed) by arquillian on server. > The test passes when I run it as single test. > But when the test runs after a test which uses authentication on remote call (like org.jboss.as.test.integration.ejb.security.AnnSBTest, https://github.com/ochaloup/jboss-as/blob/6cfe25f2bc05ca03592b465470b33e4...) then the asynchronous test fails. > I was trying to debug the call and it seems to me that the security context seems not to be correctly passed to the bean. > So I tried to rewrite the asynchronous test for not using asynchronous calls (I've removed them: https://github.com/ochaloup/jboss-as/blob/6fc6d199f1d9a9e8324a5c12dbaaf2f...) and after the change everything works fine. It works to be called as single test and as well as a subsequent test of an AnnSBTest. > I've already discussed this issue with Daran via email and he asked me for check whether the preceding test are cleaning up after themselves. I'm filling this jira because after checking it I do not have any suspicion that some test does not clean resources. As well the test rewritten to not asynchronous calls works fine. > You can try to run my "reproducer" - clone my my branch: JBQA-5483-test-migration-asynchronous (git clone git://github.com/ochaloup/jboss-as.git -b JBQA-5483-test-migration-asynchronous) and run > ./build.sh clean install -e -DallTests -Dskip-download-sources -U -B -fae -Dmaven.test.skip.exec=true && ./integration-tests.sh clean install -Dts.noSmoke -Dts.basic -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3466) sum with no matching values results in NPE on reverse

by Chris Dolan (JIRA)

Chris Dolan created JBRULES-3466: ------------------------------------ Summary: sum with no matching values results in NPE on reverse Key: JBRULES-3466 URL: https://issues.jboss.org/browse/JBRULES-3466 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.4.0.CR1 Environment: drools-planner 5.4.0-SNAPSHOT, snapshot downloaded on Apr 9, 2012 Reporter: Chris Dolan Assignee: Geoffrey De Smet I have a rule with this element in the when clause: {noformat} $beforePrediction : Number() from accumulate( JobSlot(job != NULL_JOB, $j : job, $service == service, $ordinal > ordinal) and $p : Prediction(job == $j, service == $service), sum($p.getMillisMid()) ) {noformat} When I execute this I have cases where there are no matching Prediction instances, so the sum is zero. Later on retract, I get this: {noformat} Caused by: java.lang.NullPointerException: null at org.drools.base.accumulators.SumAccumulateFunction.reverse(SumAccumulateFunction.java:83) at org.drools.base.accumulators.JavaAccumulatorFunctionExecutor.reverse(JavaAccumulatorFunctionExecutor.java:130) at org.drools.rule.Accumulate.reverse(Accumulate.java:208) {noformat} The relevant code is this: {noformat} public void accumulate(Serializable context, Object value) { SumData data = (SumData) context; data.total += ((Number) value).doubleValue(); } {noformat} and this: {noformat} public void reverse(Object workingMemoryContext, Object context, Tuple leftTuple, InternalFactHandle handle, Declaration[] declarations, Declaration[] innerDeclarations, WorkingMemory workingMemory) throws Exception { final Object value = ((JavaAccumulatorFunctionContext) context).reverseSupport.remove( Integer.valueOf( handle.getId() ) ); this.function.reverse( ((JavaAccumulatorFunctionContext) context).context, value ); } {noformat} A breakpoint reveals that handle is a Prediction instance. Somehow that handle was not added to reverseSupport, apparently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
11
0 / 0

[JBoss JIRA] (JBMESSAGING-1916) Please fix / change Bridge mechanism for WebSphereMQ to JBM

by Rick Wagner (JIRA)

Rick Wagner created JBMESSAGING-1916: ---------------------------------------- Summary: Please fix / change Bridge mechanism for WebSphereMQ to JBM Key: JBMESSAGING-1916 URL: https://issues.jboss.org/browse/JBMESSAGING-1916 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Environment: Jboss Messaging, as used with SOA-P Reporter: Rick Wagner We were asked to help provide a Bridge for a WebSphereMQ user. The customer tried to use the provided documentation and configuration, it did not work. GSS tried to build a bridge from the provided components and documentation, it did not work. (We encountered several ways to make it fail, though.) Please find a way to make a bridge with WSMQ easy to configure and reliable. One such mechanism is attached, please consider productizing it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
5
0 / 0

[JBoss JIRA] (AS7-4685) module schemas are missing from documentation

by Philippe Marschall (JIRA)

Philippe Marschall created AS7-4685: --------------------------------------- Summary: module schemas are missing from documentation Key: AS7-4685 URL: https://issues.jboss.org/browse/AS7-4685 Project: Application Server 7 Issue Type: Enhancement Components: Build System, Documentation Affects Versions: 7.1.1.Final Reporter: Philippe Marschall Assignee: Paul Gier Priority: Minor The schemas for the jboss module system are missing from the docs/schemas folder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4417) permissions for security roles are not redefined by jboss-ejb3.xml

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-4417?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-4417. --------------------------------- Resolution: Done > permissions for security roles are not redefined by jboss-ejb3.xml > ------------------------------------------------------------------ > > Key: AS7-4417 > URL: https://issues.jboss.org/browse/AS7-4417 > Project: Application Server 7 > Issue Type: Bug > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Labels: descriptor, security > Fix For: 7.1.2.Final-redhat1 > > > When I have defined permissions using security roles in ejb-jar.xml (ejb-spec) for certain methods and if I define them differently in jboss-ejb3.xml (jboss-spec) the permissions remain as their are defined in ejb-jar.xml. But I would expect that ejb-spec will redefine the permissions (because merging is not possible). > For details see written tests here: https://github.com/rhatlapa/jboss-as/commit/62adba59b288a53672a6b08c8a710... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4638) Add ability to exclude a subsystems DUP's via jboss-deployment-structure.xml

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4638: ----------------------------------- Summary: Add ability to exclude a subsystems DUP's via jboss-deployment-structure.xml Key: AS7-4638 URL: https://issues.jboss.org/browse/AS7-4638 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
2
0 / 0

[JBoss JIRA] (JBADMCON-170) Jboss Migration from 4.5.3 GA to Jboss Enterprise Edition.

by Surendra Ipperla (JIRA)

Surendra Ipperla created JBADMCON-170: ----------------------------------------- Summary: Jboss Migration from 4.5.3 GA to Jboss Enterprise Edition. Key: JBADMCON-170 URL: https://issues.jboss.org/browse/JBADMCON-170 Project: JBoss Admin Console Issue Type: Enhancement Reporter: Surendra Ipperla We would like to Migrate the Jboss 4.2.3 GA to Jboss Enterprise Edition. Coping the Server folder (<jboss install dir>/server/<server name>) to the Enterprise edition will be enough. If we done in this way is there will be any side effects. Or Do we need to do any configuration changes. Please provide us information and steps to be followed in this Migration Process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-3863) jgroups protocol order not retained

by Heiko Braun (JIRA)

Heiko Braun created AS7-3863: -------------------------------- Summary: jgroups protocol order not retained Key: AS7-3863 URL: https://issues.jboss.org/browse/AS7-3863 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.1.Final the xml config: {noformat} <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/> <protocol type="MPING" socket-binding="jgroups-mping"/> <protocol type="MERGE2"/> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="BARRIER"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST2"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> </stack> {noformat} the DMR response: {noformat} "protocol" => { "FD_SOCK" => undefined, "FD" => undefined, "VERIFY_SUSPECT" => undefined, "BARRIER" => undefined, "FRAG2" => undefined, "MERGE2" => undefined, "pbcast.GMS" => undefined, "UNICAST2" => undefined, "UFC" => undefined, "MFC" => undefined, "pbcast.NAKACK" => undefined, "pbcast.STABLE" => undefined, "MPING" => undefined }, {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2012