[teiid-issues] [JBoss JIRA] Resolved: (TEIID-601) Check for duplicate process at the statup and avoid it

[Ramesh Reddy (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-601.
--------------------------------

    Resolution: Done
      Assignee: Ramesh Reddy


During the startup of the server a "teiid.pid" file is written into the work directory and obtains lock on the file. This lock is checked each time the process is invoked and the whether to continue processing is will based on obtaining the lock on this file.

This may be expanded when shared installations and such is supported, until that time this effort is sufficient to satisfy this JIRA 

> 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
>            Assignee: Ramesh Reddy
>            Priority: Critical
>             Fix For: 6.2.0
>
>         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