August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3579) Failure in org.jboss.test.web.test.ClusteredSingleSignOnUnitTestCase(tomcat-sso-cluster)

by Dimitris Andreadis (JIRA)

Failure in org.jboss.test.web.test.ClusteredSingleSignOnUnitTestCase(tomcat-sso-cluster) ---------------------------------------------------------------------------------------- Key: JBAS-3579 URL: http://jira.jboss.com/jira/browse/JBAS-3579 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.4.2_09 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Client VM Java VM Version 1.4.2_09-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Anil Saldhana Fix For: JBossAS-4.0.5.CR1 testWebappUndeploy Failure get of /war2/index.html redirected to login page junit.framework.AssertionFailedError: get of /war2/index.html redirected to login page at org.jboss.test.web.test.ClusteredSingleSignOnUnitTestCase.testWebappUndeploy(ClusteredSingleSignOnUnitTestCase.java:194) 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, 11 months

2
3
0 / 0

[JBoss JIRA] Updated: (BPEL-186) Write a blog entry about the 1.1 release

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-186?page=all ] Alejandro Guizar updated BPEL-186: ---------------------------------- Summary: Write a blog entry about the 1.1 release (was: Write a blog entry about the beta releases) > Write a blog entry about the 1.1 release > ---------------------------------------- > > Key: BPEL-186 > URL: http://jira.jboss.com/jira/browse/BPEL-186 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-132) semantics of partner role initialization

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-132?page=all ] Alejandro Guizar updated BPEL-132: ---------------------------------- Fix Version/s: jBPM BPEL 2.0 alpha (was: jBPM BPEL 1.1 beta 3) > semantics of partner role initialization > ---------------------------------------- > > Key: BPEL-132 > URL: http://jira.jboss.com/jira/browse/BPEL-132 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 2.0 alpha > > > Add the semantics of the initializePartnerRole attribute in partner links, as specified in section 7.2 of the BPEL spec. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3584) WARNing logged when deploy-hasingleton is undeployed twice

by Dimitris Andreadis (JIRA)

WARNing logged when deploy-hasingleton is undeployed twice ---------------------------------------------------------- Key: JBAS-3584 URL: http://jira.jboss.com/jira/browse/JBAS-3584 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.4.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.5.CR1 When jboss is shutdown MainDeployer.shutdown() iterates over the list of deployments in reverse order and undeploys them. deploy-hasingleton gets undeployed first, but then while deploy-hasingleton-service.xml gets undeployed it triggers a second undeploy of deploy-hasingleton which logs a WARNing: 20:50:28,325 WARN [MainDeployer] undeploy 'file:/X:/jboss/jboss-4.0.4.GA/server/all//deploy-hasingleton' : package not deployed -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBAS-2921) Use JBossSerialization for serializing sessions and attributes before putting them in the cache

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2921?page=all ] Hany Mesha updated JBAS-2921: ----------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89457 > Use JBossSerialization for serializing sessions and attributes before putting them in the cache > ----------------------------------------------------------------------------------------------- > > Key: JBAS-2921 > URL: http://jira.jboss.com/jira/browse/JBAS-2921 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Fix For: JBossAS-5.0.0.Beta > > > Use JBossSerialization in JBossCacheService externalizeSession(), loadSession(), getMarshalledValue() and getUnmarshalledValue(). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-455) java.lang.NullPointerException at org.drools.util.LinkedList.remove(Unknown Source) in 3.0.4 while not in 3.0.3

by Ruslan Sorokin (JIRA)

java.lang.NullPointerException at org.drools.util.LinkedList.remove(Unknown Source) in 3.0.4 while not in 3.0.3 --------------------------------------------------------------------------------------------------------------- Key: JBRULES-455 URL: http://jira.jboss.com/jira/browse/JBRULES-455 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Environment: WindowsXP, eclipse3.2 Reporter: Ruslan Sorokin Assigned To: Mark Proctor java.lang.NullPointerException at org.drools.util.LinkedList.remove(Unknown Source) at org.drools.reteoo.ObjectMatches.remove(Unknown Source) at org.drools.reteoo.JoinNode.modifyTuple(Unknown Source) at org.drools.reteoo.LeftInputAdapterNode.modifyObject(Unknown Source) at org.drools.reteoo.ObjectSource.propagateModifyObject(Unknown Source) at org.drools.reteoo.ObjectTypeNode.modifyObject(Unknown Source) at org.drools.reteoo.Rete.modifyObject(Unknown Source) at org.drools.reteoo.ReteooRuleBase.modifyObject(Unknown Source) at org.drools.reteoo.ReteooWorkingMemory.modifyObject(Unknown Source) at org.drools.base.DefaultKnowledgeHelper.modifyObject(Unknown Source) at TrafficControl.Rule_Approach_Continue_0.consequence(Rule_Approach_Continue_0.java:16) at TrafficControl.Rule_Approach_Continue_0ConsequenceInvoker.evaluate(Rule_Approach_Continue_0ConsequenceInvoker.java:36) at org.drools.common.DefaultAgenda.fireActivation(Unknown Source) at org.drools.common.DefaultAgenda.fireNextItem(Unknown Source) at org.drools.common.AbstractWorkingMemory.fireAllRules(Unknown Source) at org.drools.common.AbstractWorkingMemory.fireAllRules(Unknown Source) -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Commented: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=comments#action_123... ] Ales Justin commented on JBMICROCONT-25: ---------------------------------------- Applied isStatic and isPublic where it was tagged as fixme. Added if (name.equals(methods[i].getName()) && equals(paramTypes, methods[i].getParameterTypes()) && methods[i].isStatic() == isStatic && methods[i].isPublic() == isPublic) return methods[i]; into Config.locateMethodInfo(). Also added was default method with no such boolean params: public static MethodInfo findMethodInfo(ClassInfo classInfo, String name, String[] paramTypes) throws JoinpointException { return findMethodInfo(classInfo, name, paramTypes, false, true); } > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC_2_0_0RC1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3488) Test failure - org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase ----------------------------------------------------------------------------- Key: JBAS-3488 URL: http://jira.jboss.com/jira/browse/JBAS-3488 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.5.CR1 Reporter: Rajesh Rajasekaran Fix For: JBossAS-4.0.5.CR1 Testcase fails due to mismatch in the serialVersionUID for the following classes serialVersionUID error for com.sun.mail.imap.protocol.IMAPAddress, 402 8521988318229345991, current: -3835822029483122232 serialVersionUID error for javax.mail.MessagingException, 402 -6388198985190878204, current: -7569192289819959253 http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2... http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2... -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Assigned: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Ales Justin reassigned JBMICROCONT-25: -------------------------------------- Assignee: Ales Justin > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC_2_0_0RC1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-288) Underlying JChannel not closed in MuxChannel in certain scenarios

by Bela Ban (JIRA)

Underlying JChannel not closed in MuxChannel in certain scenarios ----------------------------------------------------------------- Key: JGRP-288 URL: http://jira.jboss.com/jira/browse/JGRP-288 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 Unit test MultiplexerTest.testDisconnect() fails to demonstrate the problem -- 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, 11 months

1
1
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 August 2006