[
https://jira.jboss.org/jira/browse/TEIID-601?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-601:
--------------------------------------
Made the following changes to ensure proper behavior when a process is killed:
use an exception holder for the initexception in the adminapi servicedata
fix the jgroups remote method call exception handling and message
remove all children on a process add - so that a new process after a kill does not keep
the stale entries of the old
make only local updates to the registry - to ensure that only authoritative changes are
sent across the cluster
process polling needs to catch messaging exceptions
We still however need to check for duplicate hostcontroller/process launches to fully
address this defect.
Check for duplicate process at the statup and avoid it
------------------------------------------------------
Key: TEIID-601
URL:
https://jira.jboss.org/jira/browse/TEIID-601
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.1.0
Environment: Fedora 10, JBEDSP server snapshot from 13 May
Reporter: Paul Nittel
Priority: Critical
Fix For: 6.1.1
Attachments: console.log, pnittel_localdomain_MMProcess.log,
SQuirreLExceptions.txt
I've set up a JBEDSP server on my laptop. I have been able to connect from the
Console, but not really able to do much querying. This morning, I am no longer able to
connect to the server (I tried SQuirreL and Console).
Steve H. reviewed the server log and found the following to be central to the issue at
hand. NOTE: I am NOT running this in a cluster.
Exception in thread "ServiceMonitoringThread" No response for remote method
call
at
com.metamatrix.common.messaging.jgroups.JGroupsMessageBus$2.invoke(JGroupsMessageBus.java:145)
at $Proxy27.checkState(Unknown Source)
at com.metamatrix.platform.registry.ProcessMonitor$2.run(ProcessMonitor.java:125)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
May 14, 2009 16:15:48.437 [Worker3_SocketWorker1|0] ERROR <ROUTER|0> Unexpected
exception for session 1900
java.lang.NullPointerException
at
com.metamatrix.platform.registry.ServiceRegistryBinding.setService(ServiceRegistryBinding.java:298)
at
com.metamatrix.platform.registry.ServiceRegistryBinding.markServiceAsBad(ServiceRegistryBinding.java:314)
at
com.metamatrix.platform.service.proxy.SingleInvokationProxy.invoke(SingleInvokationProxy.java:89)
at $Proxy24.validateSession(Unknown Source)
at
com.metamatrix.common.comm.platform.socket.server.ServerWorkItem.run(ServerWorkItem.java:93)
at
com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira