February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-903) org.jboss.test.messaging.jms.clustering.MergeQueueTest.testMergeQueue2() fails on Linux

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.clustering.MergeQueueTest.testMergeQueue2() fails on Linux --------------------------------------------------------------------------------------- Key: JBMESSAGING-903 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-903 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.GA expected:<......> but was:<...1...> junit.framework.ComparisonFailure: expected:<......> but was:<...1...> at org.jboss.test.messaging.jms.clustering.MergeQueueTest.testMergeQueue2(MergeQueueTest.java:214) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-899) QueueTest::testClosedConsumerBeforeStart fails because a possible anti-pattern

by Clebert Suconic (JIRA)

QueueTest::testClosedConsumerBeforeStart fails because a possible anti-pattern ------------------------------------------------------------------------------ Key: JBMESSAGING-899 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-899 Project: JBoss Messaging Issue Type: Bug Reporter: Clebert Suconic Assigned To: Clebert Suconic Priority: Blocker Fix For: 1.2.0.GA If this anti-pattern is being used: MessageConsumer c2 = s2.createConsumer(queue); conn2.start(); c2.close(); c2 = s2.createConsumer(queue); We might loose messages until we restart the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-906) Decide on how to ship DistributeQueueExample (and smoke test): disable/null policy/default policy

by Ovidiu Feodorov (JIRA)

Decide on how to ship DistributeQueueExample (and smoke test): disable/null policy/default policy ------------------------------------------------------------------------------------------------- Key: JBMESSAGING-906 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-906 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-814) test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation) ------------------------------------------------------------------------------------------------ Key: EJBTHREE-814 URL: http://jira.jboss.com/jira/browse/EJBTHREE-814 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor EJB3 test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation) Testcase: testPassivation took 11.526 sec FAILED expected:<1> but was:<2> junit.framework.AssertionFailedError: expected:<1> but was:<2> at org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase.testPassivation(NestedBeanUnitTestCase.java:137) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-813) test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation) --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-813 URL: http://jira.jboss.com/jira/browse/EJBTHREE-813 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor JBAS EJB3 test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation) Testcase: testPassivation took 11.241 sec FAILED null junit.framework.AssertionFailedError at org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase.testPassivation(ExtendedPersistenceUnitTestCase.java:123) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4136) Update XDoclet to an official release

by Fernando Nasser (JIRA)

Update XDoclet to an official release ------------------------------------- Key: JBAS-4136 URL: http://jira.jboss.com/jira/browse/JBAS-4136 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Nasser Fix For: JBossAS-4.2.0.GA We are using a 1.2 beta3 XDoclet. Official 1.2.3 release is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4164) A way to do programmatic authentification to the web container (leaving credentials in session)

by Joan Pujol Espinar (JIRA)

A way to do programmatic authentification to the web container (leaving credentials in session) ------------------------------------------------------------------------------------------------ Key: JBAS-4164 URL: http://jira.jboss.com/jira/browse/JBAS-4164 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Reporter: Joan Pujol Espinar Assigned To: Scott M Stark I have read a lot of documentation an searched a lot in the forums but I haven't found how to do programmatic authentification to the web container. I can do programmatic authentification but then the credentials aren't stored in the web container session. It seems that I'm not alone, these are some posts at the Security forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73646 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102958 And if is that possibly it will be nice to have it in the FAQ Security FAQ?¿ (I tested Q3,Q21 of the FAQ and don't work for me) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBRULES-277) Import package name that has 2 sets of CAPS packages does not work

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-277?page=all ] Mark Proctor closed JBRULES-277. -------------------------------- Resolution: Done > Import package name that has 2 sets of CAPS packages does not work > ------------------------------------------------------------------ > > Key: JBRULES-277 > URL: http://jira.jboss.com/jira/browse/JBRULES-277 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.0 > Reporter: Michael Neale > Assigned To: Mark Proctor > Fix For: 3.1-m2 > > Attachments: La.java, Sample.drl > > > package me > > import com.la.BOO.GOO.La; > rule "new rule" > when > La() > then > System.out.println("foo"); > end > > This will give an error, as BOO.GOO causes it to throw up. > I suspect its JCI not looking past the "BOO" package as it thinks its a classname before, but I can't be sure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBRULES-277) Import package name that has 2 sets of CAPS packages does not work

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-277?page=all ] Mark Proctor updated JBRULES-277: --------------------------------- Fix Version/s: 3.1-m2 > Import package name that has 2 sets of CAPS packages does not work > ------------------------------------------------------------------ > > Key: JBRULES-277 > URL: http://jira.jboss.com/jira/browse/JBRULES-277 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.0 > Reporter: Michael Neale > Assigned To: Mark Proctor > Fix For: 3.1-m2 > > Attachments: La.java, Sample.drl > > > package me > > import com.la.BOO.GOO.La; > rule "new rule" > when > La() > then > System.out.println("foo"); > end > > This will give an error, as BOO.GOO causes it to throw up. > I suspect its JCI not looking past the "BOO" package as it thinks its a classname before, but I can't be sure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

Hazte con un buen servicio ... y no con un problema ... se tú también cliente FONOIP

by FonoIP

19 years, 3 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 February 2007