[JBossCache] - Fails to run on Jboss4.2.2
by emailmsgbox
Hi,
I want to switch from jboss4.0.4(jdk1.5) with jbossCache 1.4.0.SP1
To jboss4.2.2(jdk1.5) (jbossCache 1.4.0.SP5)
With the same code
I use POJO-Cache and I do Post compile waving with ant aopc
| package com.test;
| import org.jboss.cache.aop.annotation.PojoCacheable;
| import java.io.Serializable;
| @PojoCacheable
| public class A implements Serializable //extends BaseDataObject{
| private int intVal;
| private boolean boolVal;
| private String StringVal;
|
| public int getIntVal() { return intVal; }
| public void setIntVal(int intVal) {this.intVal = intVal; }
| public boolean isBoolVal() { return boolVal; }
| public void setBoolVal(boolean boolVal) { this.boolVal = boolVal; }
| public String getStringVal() {return StringVal; }
| public void setStringVal(String stringVal) {StringVal = stringVal; }
|
|
|
And when doing this without any cache use , just this
| (1) A aa = new A();
| (2) aa.setBoolVal(true);
|
In the line (2) I get
anonymous wrote :
| java.lang.ClassCastException: com.test.A
| org.jboss.aspects.patterns.observable.SubjectInterceptor.invoke(SubjectInterceptor.java:50)
| com.test.A$boolVal_Set.invokeNext(A$boolVal_Set.java)
| com.test.A.boolVal_w_$aop(A.java)
| com.test.A.setBoolVal(A.java:35)
| com.test.mbean.TestService.test2(ConferenceService.java:352)
| sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| java.lang.reflect.Method.invoke(Unknown Source)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
| org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
| ...
|
I tried jbossCache 1.4.0.SP6-8 with no success
Ideas? :-(
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122585#4122585
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122585
18 years, 6 months
[JBoss jBPM] - Re: problem when traversing to end state
by tom.baeyens＠jboss.com
i didn't see the process execution problem yet.
i do see in the stack trace a deserialization problem of a hibernate object. but i don't see the link with the process execution problem yet.
Caused by: java.lang.ClassCastException: cannot assign instance of org.hibernate.exception.NestableDelegate to field org.hibernate.exception.NestableRuntimeException.delegate of type org.hibernate.exception.NestableDelegate in instance of org.hibernate.SessionException
| at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(Ljava.lang.Object;[Ljava.lang.Object;
| )V(Unknown Source)
| ...
| at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
| at weblogic.rmi.extensions.server.CBVInputStream.readObjectInternal(CBVInputStream.java:71)
| ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122580#4122580
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122580
18 years, 6 months
[JBoss Messaging] - Clustered environment with non persistent messages ?
by kemp40
Hi,
We are running under JBoss 4.0.5 using JBossMQ as a messaging engine. 0ur platform is based on very extensive messaging - there are about 400 producers multiplexing jms messages to about 400 consumers which listen on bind queues (queue per consumer). There are no selectors used due to performance tip (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBMPerf point 5.) - routing is done on the application level. The messages also must be persisted â data loss is unacceptable.
Because our traffic load increases constantly we are slowly just about to lean against the performance wall. So we are seriously thinking about switching to JBossMessaging(1.4) to benefit from performance enhancements but also, which is more important we want to avoid persisting messages â because as every child knows - persistence is a performance killer for JMS. In order to avoid data loss we are thinking of configuring clustered environment with distributed queues â thanks to that while one node crushes enqueued messages are still available. Surly if all nodes crush the data loss is inevitable â but we can cope with that ⦠but the target is bright : performance.
So after this long introduction the questions are:
+ Is it possible to configure clustered environment with not-persistent messages ?
+ What happens with the messages when one of nodes crushes â can we avoid data loss ?
Thanks in advance for any help !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122578#4122578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122578
18 years, 6 months