[EJB/JBoss] - Re: java.lang.ClassNotFoundException: org.jnp.interfaces.Nam
by thomas2008ch
Thanks for the info. I can go astep further. But now I get another exception as follow, seems it is a problem of compatability:
Caused by: java.io.InvalidClassException: org.jboss.ejb3.LocalProxy; local class incompatible: stream classdesc serialVersionUID = -6521545933800264895, local class serialVersionUID = -7089389644057030711
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:546)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:654)
... 3 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149325#4149325
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149325
17 years, 11 months
[JBoss Messaging] - Re: Could Transparent Failover cause subscriber to miss out
by timfox
"scotthkao" wrote : I read from the online document somewhere that one distinctive added feature of JBoss Messaging(JBM) is transparent failover, i.e. failover without the client-side code to handle connection exception. But I just wonder that could there be any message lost during the transparent failover of non-durable subscriptions?
| anonymous wrote :
| |
| | Only persistent messages in durable queues (durable subscriptions or non temporary queues) are guaranteed to survive failover.
| |
| | Non persistent messages are by their nature transient.
| |
| | anonymous wrote :
| | | On transparent failover in the case of non-durable subscription, is the connection exception listener triggered?
| | |
| |
| | If the exception listener was triggered it wouldn't be transparent ;) That's basically what transparent failover means.
| |
| |
| | anonymous wrote :
| | | How could the client-side code get to know the transparent failover has accomplished the failover successfully?
| | |
| |
| | If we informed you about failover completion it wouldn't be transparent. If you want to use a connection listener and handle failover manually then you can just turn off transparent failover. Sounds like this is what you want to do.
| |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149315#4149315
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149315
17 years, 11 months