January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4455) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Brian Stansberry (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: JBAS-4455 URL: http://jira.jboss.com/jira/browse/JBAS-4455 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Galder Zamarreno Priority: Minor The HA proxies don't allow failover once a tx has reached a server. This can lead to this kind of situation: EJB A deployed on nodes 1 and 2. EJB B deployed on nodes 1 and 2. 1) Start tx, invoke on A.1. 2) Lookup B. 3) Invoke on B. LB policy picks B.2 4) Node 2 is dead for some reason so call fails. 5) Can't fail over because tx context won't allow a failover after a call has reached a server. But, B.1 is fine and is running on the only node the tx has invoked on. :( Approach to improving this. This is based on JRMPInovkerProxyHA methods, but the idea is generic: In invocationHasReachedAServer, instead of storing null as the value, you store the target (key is the tx). In invoke, if there's a tx, you add that target (if there is one) to the invocation as transient metadata The LB policy gets passed the invocation as an arg when it chooses a target (this is already in the API) LB policy checks for the metadata. If there, and that target is in its target list, return that target -- 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, 4 months

3
12
0 / 0

[JBoss JIRA] Created: (JBAS-5117) Update jboss metadata to 1.0.0.Beta5 (from 1.0.0.Beta4)

by Dimitris Andreadis (JIRA)

Update jboss metadata to 1.0.0.Beta5 (from 1.0.0.Beta4) ------------------------------------------------------- Key: JBAS-5117 URL: http://jira.jboss.com/jira/browse/JBAS-5117 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Dimitris Andreadis Assigned To: Scott M Stark Priority: Critical Fix For: JBossAS-5.0.0.Beta4 Need another metadata release to resolve JBAS-5097. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-944) Support in Rule Workbench for custom colors

by Andrew (JIRA)

Support in Rule Workbench for custom colors ------------------------------------------- Key: JBRULES-944 URL: http://jira.jboss.com/jira/browse/JBRULES-944 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Environment: Eclipse SDK 3.2.1 Reporter: Andrew Assigned To: Mark Proctor As far as I can find, the Rule Workbench plug-in for eclipse doesn't support custom colors. I use a black background and since the Rule Workbench uses black text, the editor is completely useless to me. Support for changing the colors in the DRL editor would be greatly appreciated. -- 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, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-5124) Handling merging of JBossGenericBeanMetaData and JBossSessionBeanMetaData

by Scott M Stark (JIRA)

Handling merging of JBossGenericBeanMetaData and JBossSessionBeanMetaData ------------------------------------------------------------------------- Key: JBAS-5124 URL: http://jira.jboss.com/jira/browse/JBAS-5124 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta4 An annotation only deployment like: @Stateful(name="Stateful3Bean") @Remote({Stateful3IF.class}) public class Stateful3Bean implements Stateful3IF { ... with a jboss.xml like: <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <unauthenticated-principal>guest</unauthenticated-principal> <enterprise-beans> <ejb> <ejb-name>Stateful3Bean</ejb-name> <jndi-name>com_sun_ts_tests_ejb30_pkg_scope_Stateful3Bean</jndi-name> </ejb> <ejb> <ejb-name>Stateless3Bean</ejb-name> <jndi-name>com_sun_ts_tests_ejb30_pkg_scope_Stateless3Bean</jndi-name> </ejb> </enterprise-beans> </jboss> has a JBossGenericBeanMetaData and JBossSessionBeanMetaData. The JBossGenericBeanMetaData should be merged into the JBossSessionBeanMetaData in the merged 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMETA-2) ClassCastException: org.jboss.metadata.ejb.spec.EntityBeanMetaData

by Scott M Stark (JIRA)

ClassCastException: org.jboss.metadata.ejb.spec.EntityBeanMetaData ------------------------------------------------------------------ Key: JBMETA-2 URL: http://jira.jboss.com/jira/browse/JBMETA-2 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Environment: org.jboss.test.metadata.ejb.EjbJar21UnitTestCase.testMultipleMerge() Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: 1.0.0.Beta5 A merge of an ejb2.1 descriptor with a 4.0 jboss descriptor with 2 session and 1 entity beans is failing with: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.EntityBeanMetaData at org.jboss.metadata.ejb.jboss.JBossSessionBeanMetaData.merge(JBossSessionBeanMetaData.java:820) at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeansMetaData.merge(JBossEnterpriseBeansMetaData.java:153) at org.jboss.metadata.ejb.jboss.JBossMetaData.merge(JBossMetaData.java:722) at org.jboss.test.metadata.ejb.EjbJar21UnitTestCase.testMultipleMerge(EjbJar21UnitTestCase.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1215) NullEvictionPolicy

by Brian Stansberry (JIRA)

NullEvictionPolicy ------------------ Key: JBCACHE-1215 URL: http://jira.jboss.com/jira/browse/JBCACHE-1215 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor An eviction policy that allows returns 'true' to EvictionPolicy.canIgnoreEvent(). Other methods are no-ops or equivalent defaults. Use case is situations where there are multiple eviction regions in a cache, some of which should never evict anything. You could use an LRUPolicy with maxAge=0, maxNodes=0 to accomplish a similar thing, but then you incur wasted overhead of generating, queuing up and processing node events. NullEvictionPolicy just bypasses everything. Some usages: Hibernate timestamp caching. The timestamp region should never be evicted. HttpSession caching with FIELD. I'll probably need to use JBC eviction for the JBossInternal_ area to passivate pojos. But passivating the sessions themselves should not be managed by JBC. So I could use NullEvictionPolicy for the session storage area. Could also be inserted as a global default if JBC detects that the _default_ region wasn't configured while a subregion was. I coded this up one night a while ago and forgot about it. Could be added to 2.1.0.GA if not too late; otherwise later. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5130) Update JBoss

by Dimitris Andreadis (JIRA)

Update JBoss ------------- Key: JBAS-5130 URL: http://jira.jboss.com/jira/browse/JBAS-5130 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBBUILD-294) Create hudson instance for maven build in app server head.

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-294?page=all ] Paul Gier closed JBBUILD-294. ----------------------------- Resolution: Done Hudson build has been created and is running successfully. > Create hudson instance for maven build in app server head. > ---------------------------------------------------------- > > Key: JBBUILD-294 > URL: http://jira.jboss.com/jira/browse/JBBUILD-294 > Project: JBoss Build System > Issue Type: Task > Components: Maven > Affects Versions: Maven Build 1.1 > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Setup a hudson instance for Maven. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-258) Create functional pom for each module in head

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-258?page=all ] Paul Gier closed JBBUILD-258. ----------------------------- Resolution: Done Basic poms have been created for the app server. Several tasks still remain to complete the maven migration, but the basic pom structure is in place. > Create functional pom for each module in head > --------------------------------------------- > > Key: JBBUILD-258 > URL: http://jira.jboss.com/jira/browse/JBBUILD-258 > Project: JBoss Build System > Issue Type: Feature Request > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > A working pom should be created for each as module. This means all main and test code compiles, tests run where applicable, and appropriate artifacts (jars, etc) are generated. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-259) Migrate AOP builds to maven

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-259?page=all ] Paul Gier closed JBBUILD-259. ----------------------------- Resolution: Out of Date AOP is now a separate project from the app server. So it's mavenization can be completed independently. > Migrate AOP builds to maven > --------------------------- > > Key: JBBUILD-259 > URL: http://jira.jboss.com/jira/browse/JBBUILD-259 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > Time Spent: 1 day > Remaining Estimate: 1 week > > Migrate AOP builds to maven. -- 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, 4 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 January 2008