On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <r...@wso2.com> wrote:

> Fixed the serviceId getting NULL by setting it to the ClusterContext and
> committed it..
>

Fine then :)

>
> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <r...@wso2.com>
> wrote:
>
>> Hi Lahiru,
>>
>> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
>> to removed. Is this done purposely? If so, can we update the getServiceId()
>> (which referred by several other places)  in monitors to return the correct
>> serviceId by reading ClusterContext?
>>
>> Due to this, ClusterMonitor returns serviceId as null and it causes issue
>> in the cluster monitor creation and in the event publishing..
>>
>> Thanks,
>> Reka
>>
>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <r...@wso2.com>
>> wrote:
>>
>>> Hi
>>>
>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <isu...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <isu...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <r...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> After fixing few issues, i could get the application undeployment
>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>> fine...Will continue testing with a complex application...
>>>>>>
>>>>> Great! I will test the same with a complex application.
>>>>>
>>>> Getting the following exception with a complex app (when sending
>>>> cluster activated event), will check and fix asap.
>>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>>>     at
>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>     at
>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>     at
>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>     at
>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>     at
>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>     at
>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>     at
>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>     at java.lang.Thread.run(Thread.java:662)
>>>>
>>>
>>> I too got this issue as well as a NPE while getting locks..Later found
>>> that serviceId was null when getting the locks..I have fixed ServiceId
>>> issue..Can you try now and see whether you are still getting this issue?
>>>
>>> Thanks,
>>> Reka
>>>
>>>>
>>>>
>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <isu...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>> currerntly under investigation.
>>>>>>>>
>>>>>>> Got the same issue, will check in this.
>>>>>>>
>>>>>>>>
>>>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>>>> now shall we merge docker-grouping-merge branch to master branch now? 
>>>>>>>> WDYT?
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>> rraju1...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>> clusters wiped out?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>> chami...@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is 
>>>>>>>>>>> done
>>>>>>>>>>> through the Gson library, so we would have some difficulty in 
>>>>>>>>>>> getting that
>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>> --
>>>>>> <%2B94776442007>
>>>>>> <%2B94776442007>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <%2B94776442007>
>>>>>> +94 716 358 048
>>>>>>
>>>>>> --
>>>>>> <%2B94776442007>
>>>>>> <%2B94776442007>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <%2B94776442007>
>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>


-- 
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Reply via email to