May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2004) redeployment error when a node is brought down in cluster

by Prabhat Jha (JIRA)

redeployment error when a node is brought down in cluster --------------------------------------------------------- Key: JBPORTAL-2004 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2004 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.4 Final Reporter: Prabhat Jha Assigned To: Thomas Heute Here is the setup: Apache mod_jk in front of a 2-node portal cluster. While there are around 500 clients hitting apache, one node is brought down and brought up again. Below is what you get. This very well could not problem with cache or JBossTS. [JBoss] 00:15:32,802 ERROR [MainDeployer] Could not start deployment: file:/tmp/pjha/as422/server/all/tmp/deploy/tmp65058failover-portlet-exp.war/WEB-INF/ [JBoss] org.jboss.deployment.DeploymentException: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state; - nested throwable: (java.lang.RuntimeException: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state) [JBoss] at org.jboss.portal.core.deployment.jboss.ObjectDeployment.start(ObjectDeployment.java:101) [JBoss] at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) [JBoss] at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:211) [JBoss] at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) [JBoss] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) [JBoss] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) [JBoss] at sun.reflect.GeneratedMethodAccessor183.invoke(Unknown Source) [JBoss] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [JBoss] at java.lang.reflect.Method.invoke(Method.java:585) [JBoss] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) [JBoss] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) [JBoss] Caused by: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state [JBoss] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1401) [JBoss] at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) [JBoss] at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) [JBoss] at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175) [JBoss] ... 121 more [JBoss] Caused by: java.lang.RuntimeException: [JBoss] at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1182) [JBoss] at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75) [JBoss] at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114) [JBoss] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247) [JBoss] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86) [JBoss] at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) [JBoss] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389) [JBoss] ... 124 more [JBoss] Caused by: org.jboss.cache.ReplicationException: rsp=sender=10.18.1.130:33003, retval=null, received=false, suspected=true [JBoss] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4436) [JBoss] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4358) [JBoss] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4469) [JBoss] at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110) [JBoss] at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88) [JBoss] at org.jboss.cache.interceptors.OptimisticReplicationInterceptor.broadcastPrepare(OptimisticReplicationInterceptor.java:181) [JBoss] at org.jboss.cache.interceptors.OptimisticReplicationInterceptor.invoke(OptimisticReplicationInterceptor.java:90) [JBoss] at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) [JBoss] at org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:873) [JBoss] at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1156) [JBoss] ... 130 more [JBoss] Caused by: org.jboss.cache.SuspectException: Response suspected: sender=10.18.1.130:33003, retval=null, received=false, suspected=true [JBoss] at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4430) -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1781) enable optimistic locking when using jboss cache as second level cache

by Prabhat Jha (JIRA)

enable optimistic locking when using jboss cache as second level cache ---------------------------------------------------------------------- Key: JBPORTAL-1781 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1781 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.2 Final Reporter: Prabhat Jha Assigned To: Sohil Shah Just creating this jira so that we can track what we discussed. Corresponding forum entry at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101418#4101418. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-27) Duplicate postConstruct lifecycle metadata for simple app client

by Scott M Stark (JIRA)

Duplicate postConstruct lifecycle metadata for simple app client ---------------------------------------------------------------- Key: JBMETA-27 URL: http://jira.jboss.com/jira/browse/JBMETA-27 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta9 Reporter: Scott M Stark Assigned To: Alexey Loubyansky Fix For: 1.0.0.Beta10 I'm seeing 3 LifecycleCallbackMetaData postConstructs show up in the JBossClientMetaData for a simple client like the following. There should only be one. public class HelloWorldClient { @EJB private static HelloWorldService helloWorldService; @Resource(name="msg") private static String msg; private static String result; @Resource(mappedName="ConnectionFactory") private static ConnectionFactory connectionFactory; @Resource(name="messageReplier") private static Destination destination; private static int postConstructCalls = 0; public static int getPostConstructCalls() { return postConstructCalls; } ... @PostConstruct public static void postConstruct() { postConstructCalls++; } } -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBMETA-32) Add a container name to the JBossEnterpriseBeanMetaData for the container mc registration

by Scott M Stark (JIRA)

Add a container name to the JBossEnterpriseBeanMetaData for the container mc registration ----------------------------------------------------------------------------------------- Key: JBMETA-32 URL: http://jira.jboss.com/jira/browse/JBMETA-32 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta10 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: 1.0.0.Beta11 We need a getContainerName accessor on the JBossEnterpriseBeanMetaData that provides the name of the ejb container used to register the container with the mc.This needs to be used by the dependency policy/mc integration layer that installs the containers. -- 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

1
1
0 / 0

[JBoss JIRA] Assigned: (JBCACHE-63) JBossCache benchmarks

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-63?page=all ] Manik Surtani reassigned JBCACHE-63: ------------------------------------ Assignee: Mircea Markus (was: Phillip Thurmond) > JBossCache benchmarks > --------------------- > > Key: JBCACHE-63 > URL: http://jira.jboss.com/jira/browse/JBCACHE-63 > Project: JBoss Cache > Issue Type: Task > Affects Versions: 1.2.4SP1 > Reporter: Bela Ban > Assigned To: Mircea Markus > Fix For: 2.2.0.GA > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Also bench against other caches -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1222) POC - Refactor of MethodCall class

by Mircea Markus (JIRA)

POC - Refactor of MethodCall class ---------------------------------- Key: JBCACHE-1222 URL: http://jira.jboss.com/jira/browse/JBCACHE-1222 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Mircea Markus Priority: Minor Fix For: 2.2.0.GA prototype: Instead of using reflection for calling methods on cache, all those called methods(the CacheImpl._xyz methods) might be moved to their own classes. Benefits: - no more reflection calls (small as reflection optimized) - the rollback and do methods would be in same place - easier to read code - code would be easy to test -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5267) JBOSS endorsed lib Xerces and class loading

by laurent duparchy (JIRA)

JBOSS endorsed lib Xerces and class loading ------------------------------------------- Key: JBAS-5267 URL: http://jira.jboss.com/jira/browse/JBAS-5267 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-4.0.3 SP1 Environment: jdk 1.5 Reporter: laurent duparchy Assigned To: Scott M Stark We have a class that converts HTML to PDF using Xalan and Apache FOP. The process involves xerces lib also. we have a requirement to use libs compatible with our FOP release. (xerces 2.7.1, xalan 2.7.0 etc). When those libs and bundle in a WAR, it works fine, class loading seems OK and our libs are correctly loaded by our class. No interferences with jboss libraries. But when we bundle the libs in a EAR and a EJB jar (ClassPath set in Manifest) we can't get out a ClassCast exception. We've tried all options of isolations without success. I've found a clue for you at IBM. Not sure if it can apply to jboss http://www.ibm.com/developerworks/websphere/library/techarticles/0310_sea... -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1143) ClassTypeResolver throws an Error

by Michael Neale (JIRA)

ClassTypeResolver throws an Error --------------------------------- Key: JBRULES-1143 URL: http://jira.jboss.com/jira/browse/JBRULES-1143 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 4.0.0.GA Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE would be nicer if it was a better exception (or reported it a bit better) - perhaps. Its pretty buried. -- 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

1
2
0 / 0

[JBoss JIRA] Closed: (JBREM-238) JBossRemoting testsuite needs to generate artificats in the output folder

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-238?page=all ] Ron Sigal closed JBREM-238. --------------------------- Resolution: Done Updated jrunit to look at system property jrunit.logdir, which determines where report files will go. Update build.xml to set jrunit.logdir appropriately. > JBossRemoting testsuite needs to generate artificats in the output folder > ------------------------------------------------------------------------- > > Key: JBREM-238 > URL: http://jira.jboss.com/jira/browse/JBREM-238 > Project: JBoss Remoting > Issue Type: Task > Components: general > Reporter: Adrian Brock > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.4.0.GA > > > The JBossRemoting testsuite is dumping its artifacts in the root of the project rather than output. > e.g. cvs diff: > ? MultiThreadPerformanceTestCase_benchmark.txt > ? MultiThreadedRMIPerformanceTestCase_benchmark.txt > ? PerformanceClientSideTestCase_benchmark.txt > ? PerformanceServerSideTestCase_benchmark.txt > ? PerformanceTestCase_benchmark.txt > ? RMIPerformanceTestCase_benchmark.txt > ? data > ? debug_output.log > ? start_1132237128739.txt > ? start_1132237129627.txt > etc. > Eventually somebody is going to commit these to cvs by mistake. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1525) MVELCalendarCoercionTest and MVELDateCoercionTest do not passed on 4.0.x

by Nicolas Heron (JIRA)

MVELCalendarCoercionTest and MVELDateCoercionTest do not passed on 4.0.x ------------------------------------------------------------------------ Key: JBRULES-1525 URL: http://jira.jboss.com/jira/browse/JBRULES-1525 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.5 Environment: Maven 2.0.8, Java 5, Linux Mandriva 2008.0 Reporter: Nicolas Heron Assigned To: Mark Proctor Fix For: 4.0.6 I took the latest 4.0.x version and did everything needed to build the solution but When using maven, I always have the same errors in those 2 tests : testString(org.drools.base.mvel.MVELCalendarCoercionTest) testString(org.drools.base.mvel.MVELDateCoercionTest) -- 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
19
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 May 2008