January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-281) Investigate whether sent messages need to be buffered in NAKACK

by Bela Ban (JIRA)

Investigate whether sent messages need to be buffered in NAKACK --------------------------------------------------------------- Key: JGRP-281 URL: http://jira.jboss.com/jira/browse/JGRP-281 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1, 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 NAKACK buffers sent messages in sent-table and received messages in received-table. We might be able to discard sent-table entirely because received-table will contain a message sent by oneself ! Once we have loopback in place by default, we can be sure that any message sent by P will be in P's received-table. -- 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

18 years, 8 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-3658) Remote classloading service - Redesign

by Dimitris Andreadis (JIRA)

Remote classloading service - Redesign -------------------------------------- Key: JBAS-3658 URL: http://jira.jboss.com/jira/browse/JBAS-3658 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 We need to redesign the remote classloading service such that there is more control at the deployment layer on what is exposed. I will create a forum thread where this can be discussed in more detail. Requirement 1: Provide sensible defaults, which probably means no remote classloading by default Requirement 2: Individual deployments can choose whether remote classloading is enabled and what is available remotely Requirement 3: Allow "aspects" of the deployment to enhance what can be downloaded remotely, e.g. RMI/IIOP generated proxies or AOP remoting proxies Requirement 4: Use the spec defined RMIClassloaderSPI (exposed via an MBean) to make this configurable Requirement 5: Alternate implementations, e.g. exposure of remote classloading via a servlet in Tomcat or a custom resource url that triggers the use of invokers to do remote classloading. -- 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

18 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1148) SEAM / JSF / Portlet: Compatibility problem

by JP Barbe (JIRA)

SEAM / JSF / Portlet: Compatibility problem ------------------------------------------- Key: JBPORTAL-1148 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1148 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.CR1 Environment: Windows XP MyFaces 1.1.5 SEAM 1.0.1 Reporter: JP Barbe Assigned To: Julien Viet When I use a seam tag into a jsf page, I have the following exception (You can see config files after the exception): 2006-11-30 17:20:57,934 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seam-desk]] No active conversation context java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.Process.instance(Process.java:32) at org.jboss.seam.core.TaskInstance.instance(TaskInstance.java:51) at org.jboss.seam.contexts.BusinessProcessContext.getTaskInstance(BusinessProcessContext.java:213) at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:51) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:155) at org.jboss.seam.Component.getInstance(Component.java:1245) at org.jboss.seam.Component.getInstance(Component.java:1230) at org.jboss.seam.contexts.Lifecycle.resumeConversation(Lifecycle.java:328) at org.jboss.seam.jsf.AbstractSeamPhaseListener.restoreAnyConversationContext(AbstractSeamPhaseListener.java:42) at org.jboss.seam.jsf.SeamPortletPhaseListener.beforePhase(SeamPortletPhaseListener.java:51) at org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener.beforePhase(SeamExtendedManagedPersistencePortletPhaseListener.java:37) at org.apache.myfaces.lifecycle.LifecycleImpl.informPhaseListenersBefore(LifecycleImpl.java:520) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:342) at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:396) at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) at com.eads.desk.core.portlet.DeskAccessPortlet.doView(DeskAccessPortlet.java:30) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) #### Here is the faces-config.xml file: <faces-config> <lifecycle> <phase-listener> org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener </phase-listener> </lifecycle> <navigation-rule> <from-view-id>/view/deskAccess.jsp</from-view-id> <navigation-case> <from-outcome>trManager</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> <redirect /> </navigation-case> </navigation-rule> <navigation-rule> <navigation-case> <from-action>#{pooledTask.assignToCurrentActor}</from-action> <from-outcome>taskAssignedToActor</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> </navigation-case> </navigation-rule> </faces-config> #### web.xml: <?xml version="1.0" encoding="UTF-8"?> <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">  <listener> <listener-class>org.jboss.seam.servlet.SeamListener</listener-class> </listener> </web-app> ### I have seen an issue (Key: JBSEAM-347) but I don't anderstand the solution proposed or if a solution exists ! (http://jira.jboss.org/jira/browse/JBSEAM-347) Thanks. JP. -- 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot

by Ovidiu Feodorov (JIRA)

Starting two node clusters simultaneously may end in failed messaging server node boot -------------------------------------------------------------------------------------- Key: JBMESSAGING-693 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in RequestHandler java.lang.IllegalStateException: Don't know about node id: 1 at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597) at org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526) at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623) at org.jgroups.blocks.RequestCorrelator.access -- 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

18 years, 8 months

6
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-750) Remove manually spawning of servers from runtest and build.xml

by Tim Fox (JIRA)

Remove manually spawning of servers from runtest and build.xml -------------------------------------------------------------- Key: JBMESSAGING-750 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-750 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Both runtest and tests/build.xml still use startrmiserver to start (and stop) remote servers prior (and after) to test run. The test framework now has the ability to start servers programmatically so this should be unnecessary. Removing it wil aid clarity of test scripts -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-697) Convert crash tests to use new server management framework

by Tim Fox (JIRA)

Convert crash tests to use new server management framework ---------------------------------------------------------- Key: JBMESSAGING-697 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-697 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Now the testing framework supports the ability to kill and restart servers we should transfer the crash tests across to this new way of doing things -- 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

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-737) Automate MemoryLeak tests on cruisecontrol

by Clebert Suconic (JIRA)

Automate MemoryLeak tests on cruisecontrol ------------------------------------------ Key: JBMESSAGING-737 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-737 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov MemoryLeak tests are dependent on JBossProfiler library. I need to verify binary dependencies on cruisecontrol box. -- 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

18 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBFORUMS-165) jboss.com forums migration

by Ryszard Kozmik (JIRA)

jboss.com forums migration -------------------------- Key: JBFORUMS-165 URL: http://jira.jboss.com/jira/browse/JBFORUMS-165 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha We need to update migration scripts and test them properly. -- 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

18 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (GPD-24) add convenient way to create loop transitions

by Koen Aers (JIRA)

add convenient way to create loop transitions --------------------------------------------- Key: GPD-24 URL: http://jira.jboss.com/jira/browse/GPD-24 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 the current workaround is to write the self-transition in xml. but this results in some *really* weird bendpoints when going back to the graphical view -- 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

18 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-925) PojoCache to re-try if UpgradeException occur

by Ben Wang (JIRA)

PojoCache to re-try if UpgradeException occur --------------------------------------------- Key: JBCACHE-925 URL: http://jira.jboss.com/jira/browse/JBCACHE-925 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.BETA1 Currently, PojoCache attach & detach is prone to encoutner UpgradeException on __JBossInternal__ node. This is becuase of the flat space approach that we use such that all the POJO are stored there. As a result, UpgradeException can happen and we should catch it and re-try it. -- 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

18 years, 8 months

3
6
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 January 2007