April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2864) TS: Option to fail if AS is running (~ a port is open)

by Ondrej Zizka (Created) (JIRA)

TS: Option to fail if AS is running (~ a port is open) ------------------------------------------------------ Key: AS7-2864 URL: https://issues.jboss.org/browse/AS7-2864 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka -- 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

14 years, 2 months

5
5
0 / 0

[JBoss JIRA] (AS7-3968) Add support for multiple JNDI addresses in provider URL for JMS

by Ed Keen (JIRA)

Ed Keen created AS7-3968: ---------------------------- Summary: Add support for multiple JNDI addresses in provider URL for JMS Key: AS7-3968 URL: https://issues.jboss.org/browse/AS7-3968 Project: Application Server 7 Issue Type: Feature Request Components: JMS, Remoting Affects Versions: 7.1.0.Final Reporter: Ed Keen Assignee: Andy Taylor Previous versions of JBoss supported the ability to specify multiple servers in the provider URL for JMS-related JNDI lookups performed outside the server container (see http://docs.jboss.org/jbossclustering/cluster_guide/5.1/html-single/index...). This functionality does not exist in 7.1.0.Final, and should be added to support integration with other legacy systems that expect this behavior. -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-818) Fix or remove @Ignore in WebAppTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in WebAppTestCase --------------------------------------- Key: AS7-818 URL: https://issues.jboss.org/browse/AS7-818 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Kabir Khan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
10
0 / 0

[JBoss JIRA] (AS7-3614) The Ordering of tests in integration/basic seems to affect the successfulness of the tests.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3614: ------------------------------------- Summary: The Ordering of tests in integration/basic seems to affect the successfulness of the tests. Key: AS7-3614 URL: https://issues.jboss.org/browse/AS7-3614 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Darran Lofthouse Assignee: Andrew Rubinger Fix For: 7.1.0.Final The following early staged of a test run show a clean run: - ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.as.test.integration.management.cli.HelpTestCase Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.658 sec Running org.jboss.as.test.integration.management.cli.JmsTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.259 sec Running org.jboss.as.test.integration.web.security.WebSecurityJBossWebXmlSecurityRolesTestCase Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.345 sec Running org.jboss.as.test.integration.web.security.WebSecurityFORMTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.913 sec Running org.jboss.as.test.integration.web.security.WebSecurityBASICTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.895 sec Running org.jboss.as.test.integration.web.security.WebSecurityJBossSimpleRoleMappingTestCase Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.576 sec Running org.jboss.as.test.integration.web.security.servlet3.WebSecurityProgrammaticLoginTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.226 sec Running org.jboss.as.test.integration.web.security.WebSecurityCERTTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.006 sec Running org.jboss.as.test.integration.web.security.tg.TransportGuaranteeTestCase Running locally with a different order I regularly see the following test fail: - ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.as.test.integration.web.security.WebSecurityJBossWebXmlSecurityRolesTestCase Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.028 sec Running org.jboss.as.test.integration.web.security.servlet3.WebSecurityProgrammaticLoginTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.833 sec Running org.jboss.as.test.integration.web.security.WebSecurityCERTTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec Running org.jboss.as.test.integration.web.security.WebSecurityFORMTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.462 sec Running org.jboss.as.test.integration.web.security.tg.TransportGuaranteeTestCase Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.321 sec Running org.jboss.as.test.integration.web.security.WebSecurityJBossSimpleRoleMappingTestCase Tests run: 3, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.382 sec <<< FAILURE! The logs seem to indicate a failure to deploy the security domain for the failed test, reviewing the TransportGuaranteeTestCase it does appear that maybe the domain is not removed. Adding a line within WebSecurityJBossSimpleRoleMappingTestCase to remove the domain before adding the domain caused that test to pass. This has been quite tricky to track what is actually happening, I would suggest either trying to use unique names per test so conflicts can not occur or increased validation at the end of the test case to ensure clean up is complete and to fail in the test that leaks the conflicting resource rather than failing a subsequent test. -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-4563) Inconsistent infinispan configuration

by Heiko Braun (JIRA)

Heiko Braun created AS7-4563: -------------------------------- Summary: Inconsistent infinispan configuration Key: AS7-4563 URL: https://issues.jboss.org/browse/AS7-4563 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Stan Silvert Priority: Critical Fix For: 7.1.2.Final-redhat1 It's possible to create an infinispan configuration that prevents the server from booting: 1) start standalone 2) create a cache container (just the container) 3) stop and restart the server You'll get {noformat} Message: JBAS014724: Missing required attribute(s): DEFAULT_CACHE, NAME at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_1_3.parseContainer(InfinispanSubsystemXMLReader_1_3.java:111) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_1_3.readElement(InfinispanSubsystemXMLReader_1_3.java:46) at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_1_3.readElement(InfinispanSubsystemXMLReader_1_3.java:24) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:907) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:333) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:129) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:101) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] ... 3 more {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

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9034) Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference

by Scott Marlow (JIRA)

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
8
0 / 0

[JBoss JIRA] (AS7-4664) Upgrade PicketLink Libraries to 2.1.0.Final

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-4664: ---------------------------------- Summary: Upgrade PicketLink Libraries to 2.1.0.Final Key: AS7-4664 URL: https://issues.jboss.org/browse/AS7-4664 Project: Application Server 7 Issue Type: Component Upgrade Components: Security Reporter: Anil Saldhana Assignee: Anil Saldhana 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

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2785) Documentation fixes w.r.t. events

by Wolfgang Laun (JIRA)

Documentation fixes w.r.t. events ---------------------------------- Key: JBRULES-2785 URL: https://jira.jboss.org/browse/JBRULES-2785 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.M1 Correct the documentation: (1) Explicit expiry time by @expires() in declare has precedence over implicit, dervide from rules. (Critical, because right now is documented the other way round.) (2) Document that declare without any fields must refer to an existing, imported type. (3) Document the semantics of timer, and that timer() can only be used in a STREAM session. Also, document that "int:" (as in "timer(int: 0 1m)") is optional. (4) Make it clear that window:length( N ) is also satisfied if there are less than N events. -- 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

14 years, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2681) Drools: Unable to load session snapshot

by Gustavo Tenrreiro (JIRA)

Drools: Unable to load session snapshot --------------------------------------- Key: JBRULES-2681 URL: https://jira.jboss.org/browse/JBRULES-2681 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Environment: Windows Server, SQL Server 2005, Tomcat 5.5, Hibernate, Bitronix Reporter: Gustavo Tenrreiro Assignee: Mark Proctor After an event is processed the session fails to load using JPA persistence. I ve attached a test case. It uses a Drools flow file, and a drl file. Both very simple.. The flow file has a "Start" then an action that prints a message to the console, then "End" The Drl has one rule that processes an event: import com.kgcontrols.services.company.standardsRequests.workflow.events.VoteCreatedEvent declare VoteCreatedEvent @role(event) end rule "testEvents" when VoteCreatedEvent() from entry-point "VoteCreatedStream" then System.out.println("--------------------------- YEAH the event got here"); end I can see the "YEAH the event go here" on the console so I know the rule fired. But after that, if I try to load the session from the database I get: 1. INFO 2010-09-02 08:28:56 [ERROR] com.kgcontrols.services.company.standardsRequ 2. ests.workflow.TimerRunner java.lang.reflect.InvocationTargetException 3. java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException 4. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 5. Service(KnowledgeStoreServiceImpl.java:106) 6. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.loadStatefu 7. lKnowledgeSession(KnowledgeStoreServiceImpl.java:74) 8. at org.drools.persistence.jpa.JPAKnowledgeService.loadStatefulKnowledgeS 9. ession(JPAKnowledgeService.java:118) 10. at com.kgcontrols.services.company.standardsRequests.workflow.JPAKnowle 11. dgeSessionLookup.loadSession(JPAKnowledgeSessionLookup.java:103) 12. at com.kgcontrols.services.company.standardsRequests.workflow.TimerRunn 13. er.run(TimerRunner.java:39) 14. at java.lang.Thread.run(Thread.java:619) 15. Caused by: java.lang.reflect.InvocationTargetException 16. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 17. 18. at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct 19. orAccessorImpl.java:39) 20. at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC 21. onstructorAccessorImpl.java:27) 22. at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 23. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 24. Service(KnowledgeStoreServiceImpl.java:91) 25. ... 5 more 26. Caused by: java.lang.RuntimeException: Unable to load session snapshot 27. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 28. ot(JPASessionMarshallingHelper.java:96) 29. at org.drools.persistence.session.SingleSessionCommandService.initKsessi 30. on(SingleSessionCommandService.java:196) 31. at org.drools.persistence.session.SingleSessionCommandService.<init>(Sin 32. gleSessionCommandService.java:159) 33. ... 10 more 34. Caused by: java.lang.NullPointerException 35. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:135) 36. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:121) 37. at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarsha 38. ller.java:461) 39. at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMars 40. haller.java:351) 41. at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshall 42. er.java:205) 43. at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarsh 44. aller.java:91) 45. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 46. ot(JPASessionMarshallingHelper.java:91) 47. ... 12 more -- 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

14 years, 2 months

7
18
0 / 0

[JBoss JIRA] (AS7-4408) CLONE - Enable JAAS support for the SASL Realms

by Jan Lanik (JIRA)

Jan Lanik created AS7-4408: ------------------------------ Summary: CLONE - Enable JAAS support for the SASL Realms Key: AS7-4408 URL: https://issues.jboss.org/browse/AS7-4408 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Jan Lanik Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- 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

14 years, 2 months

3
2
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 2012