[jboss-user] [Beginners Corner] - InvalidClassException when connecting standalone client to J
Hi all, We are using JBoss 4 as application server. We have a standalone client connecting to the server and this has worked fine up until a few days ago. Suddenly we keep getting exceptions. See below stacktrace. Any help with this much appreciated! I've tried google but without any luck. | java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -6756054858541526837, local class serialVersionUID = 4418622981026545151 | at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519) | at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546) | at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) | at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) | at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) | at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) | at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) | at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) | at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) | at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) | at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) | at org.jboss.remoting.Client.invoke(Client.java:525) | at org.jboss.remoting.Client.invoke(Client.java:488) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) | at $Proxy1.importAllCampaigns(Unknown Source) | at com.smtb.client.adwords.CampaignImport.Import(CampaignImport.java:101) | at com.smtb.client.adwords.CampaignImport.(CampaignImport.java:41) | at com.smtb.client.adwords.CampaignImport.main(CampaignImport.java:143) | null | java.lang.reflect.UndeclaredThrowableException | at $Proxy1.importAllCampaigns(Unknown Source) | at com.smtb.client.adwords.CampaignImport.Import(CampaignImport.java:101) | at com.smtb.client.adwords.CampaignImport.(CampaignImport.java:41) | at com.smtb.client.adwords.CampaignImport.main(CampaignImport.java:143) | Caused by: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: | java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -6756054858541526837, local class serialVersionUID = 4418622981026545151 | at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306) | at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) | at org.jboss.remoting.Client.invoke(Client.java:525) | at org.jboss.remoting.Client.invoke(Client.java:488) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security
[jboss-user] [Beginners Corner] - Migration to JBoss 4.2.2.GA (again)
Hi, I posted earlier about our problems migrating to JBoss 4.2.2.GA. To clarify my problem: We're using two postgresql databases. And I'm trying to access both databases in a single EJB3 Stateless Session Bean method (one database via JDBC through a DataSource and the other via another Stateless Session Bean and its EntityManager). I think before migration this only lead to a WARN in the JBoss server log: [TxConnectionManager] Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure Now I get an exception: | 2008-01-02 07:16:58,093 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.disallow] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.disallow] Adding multiple last resources is disallowed. Current resource is [EMAIL PROTECTED] | 2008-01-02 07:16:58,099 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: null | 2008-01-02 07:16:58,099 ERROR [org.hibernate.util.JDBCExceptionReporter] Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 7f01:ac47:477b38ef:148 status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 7f01:ac47:477b38ef:148 status: ActionStatus.ABORT_ONLY >)) | 2008-01-02 07:16:58,101 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: org.hibernate.exception.GenericJDBCException: Cannot open connection | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) | 2008-01-02 07:16:58,102 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) | 2008-01-02 07:16:58,103 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) | 2008-01-02 07:16:58,103 ERROR [STDERR] at $Proxy354.getBiddingStatePerDate(Unknown Source) | 2008-01-02 07:16:58,103 ERROR [STDERR] at com.smtb.bidengine.rule.position.PositionRuleMgr.executeAw(PositionRuleMgr.java:535) | 2008-01-02 07:16:58,103 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 2008-01-02 07:16:58,103 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 2008-01-02 07:16:58,103 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25
[jboss-user] [Beginners Corner] - Migrating to JBoss 4.2.2.GA
Hi, Before migrating we had a lot of WARN [TxConnectionManager] Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure in our jboss log files. Since we migrated it seems this warning instead generates an error. I've also seen in other discussions that this warning now (in JBoss 4.2) generates errors. I'm not really sure why we're getting the WARN/error in the first place. An example of when the WARN/error is thrown: A stateless EJB 3 session bean, where I use two other stateless beans to retrieve data from db. I try to retrieve the data from both stateless beans in the same method. And, voila, I get an error in JBoss 4.2 when retrieving data from the second stateless bean. I remember that the above mentioned WARN was generated when the method was done when we used an earlier version of JBoss. Anyone has an idea what I should do to correct this? /Best regards, Håkan Jacobsson - System developer in Sweden View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116354#4116354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116354 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Beginners Corner] - JBoss problem: "connection limit exceeded for non-superusers
Hi, Seems JBoss doesn't destroy idle connections - anyone know what might be the cause? I keep getting the message "connection limit exceeded for non-superusers" and our system goes down. This is a system which have been running for several years (we're using postgresql database). Any help as to what might be causing this problem (or a hint on where to start debugging) much appreciated! /Regards, Håkan Jacobsson - System developer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069087#4069087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069087 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
