[JBoss Cache: Core Edition] - Re: Synchronous replication result with suspect member
by afelle1
Stack trace on machine A:
anonymous wrote : 2008-09-29 00:02:21,740 ERROR [org.jasig.cas.ticket.registry.JBossCacheTicketRegistry] - org.jboss.cache.ReplicationException: rsp=sender=XXX.XXX.XXX.XXX:XXXX, retval=null, received=false, suspected=false
| org.jboss.cache.ReplicationException: rsp=sender=XXX.XXX.XXX.XXX:XXXX, retval=null, received=false, suspected=false
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4338)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4260)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4372)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
| at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:124)
| at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:88)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:364)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
| at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5710)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3782)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3720)
| ... X more
| Caused by: org.jboss.cache.lock.TimeoutException: Response timed out: sender=XXX.XXX.XXX.XXX:XXXX, retval=null, received=false, suspected=false
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4336)
| ... 72 more
|
Stack trace on machine B:
anonymous wrote : 2008-09-29 08:14:34,471 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - AuthenticationHandler: org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler successfully authenticated the user which prov
| ided the following credentials: kattest
| 2008-09-29 08:14:36,869 ERROR [org.jasig.cas.ticket.registry.JBossCacheTicketRegistry] - org.jboss.cache.ReplicationException: rsp=sender=YYY.YYY.YYY.YYY:YYYY, retval=null, received=false, suspected=true
| org.jboss.cache.ReplicationException: rsp=sender=YYY.YYY.YYY.YYY:YYYY, retval=null, received=false, suspected=true
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4338)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4260)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4372)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
| at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:124)
| at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:88)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:364)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
| at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5710)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3782)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3720)
| ... N more
| Caused by: org.jboss.cache.SuspectException: Response suspected: sender=YYY.YYY.YYY.YYY:YYYY, retval=null, received=false, suspected=true
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4332)
| ... 72 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179888#4179888
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179888
17 years, 6 months
[EJB/JBoss] - JBoss hangs while trying to retrieve values from Entity bean
by vckrishnan
Hi All,
I have a very strange problem with JBoss 4.0.5 GA. I am migrating an application from Weblogic to Jboss. In my application there is a search functionality which involves using entity beans. When i perform this search functionality Jboss gets hangs for certain search terms, for some terms i am getting results. I am not able to figure out the issue with ThreadDump
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
oracle.net.ns.Packet.receive(Unknown Source)
oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527)
org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:236)
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:177)
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:88)
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:646)
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:628)
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:406)
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEntity(CachedConnectionInterceptor.java:252)
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:243)
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:126)
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:276)
org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:104)
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:68)
org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:527)
org.jboss.ejb.Container.invoke(Container.java:954)
sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:112)
org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
$Proxy361.getValue(Unknown Source)
com.isbr.fwk.valpha.AlphaEjbDaoImpl.getValue(Unknown Source)
com.isbr.fwk.valpha.AlphaEjbDaoImpl.getValue(Unknown Source)
com.isbr.fwk.valpha.AlphaDaoImpl.getValue(Unknown Source)
com.isbr.fwk.util.EntityValueList.next(Unknown Source)
com.isbr.cos.ejb.srrequestbytrivialname.SrRequestByTrivialNameImpl.getSampleNumbers(Unknown Sourc
I doubt the application is getting hangs when Jboss trying to unmarshall the primarykey while trying to identify the actual entity bean. Also Jboss is taking much time for identifying the very first bean, rest of the bean are returned in very less time.
My application is using EJB 2.0, JBoss 4.0.5, JDK 1.5 and Oracle 10g
Could any help me in resolving this issue?
Thanks in advance
--Krishna.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179887#4179887
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179887
17 years, 6 months
[JBoss Cache: Core Edition] - Synchronous replication result with suspect member
by afelle1
QUESTION: Whenever putting an attribute / node into the cache and a replication exception occurs due to time out or a remote machine being suspect, is the attribute / node put into the cache on the other machines that did respond?
We have our cache configured for synchronous replication with a cluster of 5 initial members. Occasionally, we receive a stack trace in the error log for replication errors involving one of the members being timed out or suspected, however I am unsure as to the state of the cache. These occur whenever we are putting a new attribute within the cache, so I want to know whether the attribute was put into the cache on all machines except for the suspected / timed out machine or if wasn't put into the cache on any of the machines.
JGroups configuration (sans TCP and TCPPING)
<MERGE2 min_interval="5000" max_interval="10000" />
| <FD_SOCK />
| <FD shun="true" timeout="2500" max_tries="5" />
| <VERIFY_SUSPECT timeout="1500" />
| <UNICAST retransmit_timeout="300,600,1200,2400,4800,9600" />
| <pbcast.STABLE desired_avg_gossip="20000" stability_delay="1500" />
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" />
| <pbcast.STATE_TRANSFER />
Stack Trace
anonymous wrote : 2008-09-29 00:02:21,740 ERROR [org.jasig.cas.ticket.registry.JBossCacheTicketRegistry] - org.jboss.cache.ReplicationException: rsp=sender=XXX.XXX.XXX.XXX:XXXX, retval=null, received=false, suspected=false
| org.jboss.cache.ReplicationException: rsp=sender=XXX.XXX.XXX.XXX:XXXX, retval=null, received=false, suspected=false
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4338)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4260)
| at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4372)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
| at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
| at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:124)
| at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:88)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:364)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
| at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5710)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3782)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3720)
Thank you for any assistance!
Andrew
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179886#4179886
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179886
17 years, 6 months
[Clustering/JBoss] - Scheduling app to run on one node only
by markad2
We're in a 2-node cluster environment with various scheduled services. A new application has a requirement to run only one node once a day - our other scheduled apps are fine with running on both nodes and needs to stay that way. In this app's case, the scheduled service is duplicating data in a database due to it running twice daily vs. just once.
Can I modify my .sar's META-INF/jboss-service.xml (vs. having to modify any JBoss configuration) so this particular app only runs one node? Here's the existing .sar jboss-service.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <server>
| <mbean code="org.jboss.varia.scheduler.Scheduler" name="com.mycompany.myapp:service=MyScheduledService">
| <attribute name="StartAtStartup">true</attribute>
| <attribute name="SchedulableClass">com.mycompany.myapp.MyScheduledService</attribute>
| <attribute name="InitialStartDate">NOW</attribute>
| <attribute name="SchedulePeriod">86400000</attribute> <!-- every 24 hours -->
| <attribute name="InitialRepetitions">-1</attribute>
| <depends>
| jboss.jca:service=DataSourceBinding,name=jdbc/MyDataSource
| </depends>
| </mbean>
| </server>
|
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179882#4179882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179882
17 years, 6 months