August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCLUSTER-72) Certify JBoss Clustering Content on JBoss Labs

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-72?page=all ] Brian Stansberry updated JBCLUSTER-72: -------------------------------------- Fix Version/s: Q3Y6 > Certify JBoss Clustering Content on JBoss Labs > ---------------------------------------------- > > Key: JBCLUSTER-72 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-72 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Damon Sicore > Assigned To: Brian Stansberry > Fix For: Q3Y6 > > > See incorporated task for instructions. -- 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] Resolved: (JBCLUSTER-56) After 1st UnmarshallException all following client calls fail: Serivce unavailable

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-56?page=all ] Brian Stansberry resolved JBCLUSTER-56. --------------------------------------- Fix Version/s: Q3Y6 Resolution: Done In Branch_3_2 an UnmarshalException will no longer lead to failover or removal of a target from the FamilyClusterInfo. Don't know for sure if that resolves your issue, but it should and is as far as I'll go in Branch_3_2. > After 1st UnmarshallException all following client calls fail: Serivce unavailable > ---------------------------------------------------------------------------------- > > Key: JBCLUSTER-56 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-56 > Project: JBoss Clustering > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Solaris 9, Linux, java 1.4.2_07 and higher > Reporter: kleibl > Assigned To: Brian Stansberry > Fix For: Q3Y6 > > Attachments: failtest.zip > > Original Estimate: 3 days > Remaining Estimate: 3 days > > when called a method on a session bean that returns non serializable object in clustered deployment this throws java.rmi.UnmarshallException (this is correct). all subsequent calls from that client fail and throw: > Service unavailable. > org.jboss.invocation.ServiceUnavailableException: Service unavailable. > at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA.invoke(JRMPInvokerProxyHA.java:287) > at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:163) > at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:103) > at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.echo(Unknown Source) > at failtest.client.Tester$TestThread.run(Tester.java:184) > there is no additional communication between client and server. the calls end at the JRMPInvokerProxyHA. > this behviour doesn't occure in non clustered deployment. in that case the following client calls are working. > i tested it on jboss 3.2.5, 3.2.6, 3.2.7 > in 4.0.2 this error doesn't occure -- 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] Resolved: (JBCACHE-143) Refactor LocalAopTest

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-143?page=all ] Ben Wang resolved JBCACHE-143. ------------------------------ Resolution: Out of Date > Refactor LocalAopTest > --------------------- > > Key: JBCACHE-143 > URL: http://jira.jboss.com/jira/browse/JBCACHE-143 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Optional > Fix For: PojoCache > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Currently it is using TreeCacheAopTester as a proxy. There is no need for it now. This task can be done by an intern. -- 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: (JBCACHE-206) PojoCache remote getObject needs to populate the in-memory reference as well

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-206?page=all ] Ben Wang updated JBCACHE-206: ----------------------------- Fix Version/s: PojoCache 2.2.0 (was: PojoCache) > PojoCache remote getObject needs to populate the in-memory reference as well > ---------------------------------------------------------------------------- > > Key: JBCACHE-206 > URL: http://jira.jboss.com/jira/browse/JBCACHE-206 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Fix For: PojoCache 2.2.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, if we do a getObject from the remote node, it will create a new instance and attach that pojo instance with a CacheInterceptor such that all pojo operations will be intercepted and interact from the cache. However, we will also need to populate the in-memory copy as well such that when a removeObject is called (such that the pojo is detached from the cache), the pojo will still has the correct values. > Note this use case should be very rare. In general, if you do a removeObject, that usually means the pojos are ready for GCed. -- 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: (JBCACHE-466) Create api-less annotation for PojoCache

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-466?page=all ] Ben Wang updated JBCACHE-466: ----------------------------- Fix Version/s: PojoCache 2.2.0 (was: PojoCache) > Create api-less annotation for PojoCache > ---------------------------------------- > > Key: JBCACHE-466 > URL: http://jira.jboss.com/jira/browse/JBCACHE-466 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: PojoCache 2.2.0 > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Use annotation to signifyas per the spec documentation: @attach, @reattach -- 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: (JBCACHE-168) Querying for POJO object under PojoCache

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-168?page=all ] Ben Wang updated JBCACHE-168: ----------------------------- Fix Version/s: PojoCache 2.2.0 (was: PojoCache) > Querying for POJO object under PojoCache > ---------------------------------------- > > Key: JBCACHE-168 > URL: http://jira.jboss.com/jira/browse/JBCACHE-168 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Fix For: PojoCache 2.2.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Need to provide an API in TreeCacheAop that can query the current pojos. Currently, it is user's responsibility to track the pojo based on the fqn. > We can provide an extension based on findObjects that is can query all fqn with additional class argument, e.g., > findObjects(fqn, myPojo.class) -- 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: (JBCACHE-354) PojoCache Collection proxy will keep track of the original reference

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-354?page=all ] Ben Wang updated JBCACHE-354: ----------------------------- Fix Version/s: 2.0.0 (was: PojoCache) > PojoCache Collection proxy will keep track of the original reference > -------------------------------------------------------------------- > > Key: JBCACHE-354 > URL: http://jira.jboss.com/jira/browse/JBCACHE-354 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > When updating Collection proxy, we should also update the original local reference values. -- 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] Assigned: (JBCLUSTER-56) After 1st UnmarshallException all following client calls fail: Serivce unavailable

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-56?page=all ] Brian Stansberry reassigned JBCLUSTER-56: ----------------------------------------- Assignee: Brian Stansberry (was: Ben Wang) > After 1st UnmarshallException all following client calls fail: Serivce unavailable > ---------------------------------------------------------------------------------- > > Key: JBCLUSTER-56 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-56 > Project: JBoss Clustering > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Solaris 9, Linux, java 1.4.2_07 and higher > Reporter: kleibl > Assigned To: Brian Stansberry > Attachments: failtest.zip > > Original Estimate: 3 days > Remaining Estimate: 3 days > > when called a method on a session bean that returns non serializable object in clustered deployment this throws java.rmi.UnmarshallException (this is correct). all subsequent calls from that client fail and throw: > Service unavailable. > org.jboss.invocation.ServiceUnavailableException: Service unavailable. > at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA.invoke(JRMPInvokerProxyHA.java:287) > at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:163) > at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:103) > at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) > at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) > at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) > at $Proxy2.echo(Unknown Source) > at failtest.client.Tester$TestThread.run(Tester.java:184) > there is no additional communication between client and server. the calls end at the JRMPInvokerProxyHA. > this behviour doesn't occure in non clustered deployment. in that case the following client calls are working. > i tested it on jboss 3.2.5, 3.2.6, 3.2.7 > in 4.0.2 this error doesn't occure -- 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: (JBCACHE-467) ejb3 annotation integration

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-467?page=all ] Ben Wang updated JBCACHE-467: ----------------------------- Fix Version/s: PojoCache 2.1.0 (was: PojoCache) > ejb3 annotation integration > --------------------------- > > Key: JBCACHE-467 > URL: http://jira.jboss.com/jira/browse/JBCACHE-467 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: PojoCache 2.1.0 > > -- 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-3518) Port JBAS-3163 fix to Branch_3_2

by Brian Stansberry (JIRA)

Port JBAS-3163 fix to Branch_3_2 -------------------------------- Key: JBAS-3518 URL: http://jira.jboss.com/jira/browse/JBAS-3518 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-3.2.8.SP2 Will potentially also resolve JBCLUSTER-62 -- 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