Hi,
There was a regression issue caused by fix for STRATOS-849 that caused
LB cartridge to be treated as a service cartridge [1]. This is fixed
now. The reason was "load.balancer.ref" property was missing in LB
cartridge when processing in LBCreationSubscriptionFilter.
Therefore I created a separ
I have fixed this issue and made a pull request for this.
https://github.com/apache/stratos/pull/72
This is happen due to we try to process instance status events in the
cartridge events. We don't need to process instance status events in the
cartridge end as they are published with the cartridge
Hi,
We have sorted out agent issues. Now the container is activated
successfully. We can see the active members in stratos admin console. There
is one more error to be sorted out. Pasted the agent log here.
[2014-09-29 15:45:56,378] INFO - [CartridgeAgent] Waiting for Cartridge
Agent to be initi
Hi all,
Kubernetes host registration issue is fixed in master branch now. This
was due to an merge conflict that occurred while merging with
docker-integration branch.
Thanks.
On Sun, Sep 28, 2014 at 12:07 PM, Rajkumar Rajaratnam
wrote:
> Hi Gayan,
>
> On TopicSubscriber.doSubscribe() method, d
Hi Gayan,
On TopicSubscriber.doSubscribe() method, don't we have to set the variable
"subscribed" to true once the subscription succeeded?
Thanks.
On Sat, Sep 27, 2014 at 9:09 PM, Sajith Kariyawasam wrote:
>
>
> On Sat, Sep 27, 2014 at 8:17 PM, Rajkumar Rajaratnam
> wrote:
>
>> Hi,
>>
>> Car
On Sat, Sep 27, 2014 at 8:17 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Cartridge Agent didn't start topology event receiver thread. There is no
> log regarding this. But CA starts instance notifier listener thread and
> tenant event receiver thread. There are logs for this.
>
> Strange!, topology
Hi,
Cartridge Agent didn't start topology event receiver thread. There is no
log regarding this. But CA starts instance notifier listener thread and
tenant event receiver thread. There are logs for this.
If CA starts topology event receiver thread, there should be a log
"Starting topology event m
Hi Raj,
Seems like that cartridge agent is not initiated.Are we receiving the
"CompleteTopologyEvent" event.
AFAIU cartridge agent set to initiated based on the complete topology event
consistency.
Thanks,
Gayan
On Sat, Sep 27, 2014 at 3:48 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Now cartridg
Hi,
Now cartridge agent is starting up successfully. But It is not publishing
any events. Here is the agent log.
Starting cartridge agent...
[2014-09-27 10:14:44,902] DEBUG - [CartridgeAgentConfiguration] Cannot read
log file path : Cannot find the value of required parameter: LOG_FILE_PATHS
[201
mqtttopic.properties file should be as
https://github.com/apache/stratos/blob/docker-integration/products/cartridge-agent/modules/distribution/src/main/conf/mqtttopic.properties
Thanks,
Gayan
On Sat, Sep 27, 2014 at 3:01 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> As per the offline discussion wi
Hi,
As per the offline discussion with Gayan, agent's mqtttopic.properties is
having wrong content as in the previous mail. But it should be like below,
mqtturl=tcp://10.111.11.221:1883
clientID=stratos
tempfilelocation=/tmp
Thanks Gayan for the info.
On Sat, Sep 27, 2014 at 2:27 PM, Rajkumar R
Hi,
connectionfactoryName=TopicConnectionFactory
java.naming.provider.url=tcp://10.111.11.221:1883
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
Thanks.
On Sat, Sep 27, 2014 at 2:14 PM, Gayan Gunarathne wrote:
> Hi Raj,
>
> What is the mqtturl specified in
Hi Raj,
What is the mqtturl specified in the mqtttopic.properties file?
Thanks,
Gayan
On Sat, Sep 27, 2014 at 1:02 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Until this is sorted out, I am doing a test in docker branch. Cartridge
> Agent is not starting up. It is giving the following error. But
Hi,
Until this is sorted out, I am doing a test in docker branch. Cartridge
Agent is not starting up. It is giving the following error. But I can
telnet to MB from the container.
Starting cartridge agent...
[2014-09-27 07:28:59,260] INFO - [CartridgeAgentConfiguration] INTERNAL
payload paramete
Hi,
When I merged docker-integration branch with master, there are lots of
changes in AutoScalerService.wsdl and CloudControllerService.wsdl. So
merging wsdl's can cause multiple errors. So what I did was, done the code
marge in Autoscaler component and build it and generate the wsdl and put it
in
On Sat, Sep 27, 2014 at 1:40 AM, Sajith Kariyawasam wrote:
> Seems to have a mismatch of argument types expects from the
> AutoscalerService.
>
> Could you please attach the wsdl of the AutoscalerService once you access
> the service as follows
> https://:/services/AutoscalerService?wsdl
>
> corr
Seems to have a mismatch of argument types expects from the
AutoscalerService.
Could you please attach the wsdl of the AutoscalerService once you access
the service as follows
https://:/services/AutoscalerService?wsdl
On Sat, Sep 27, 2014 at 1:18 AM, Rajkumar Rajaratnam
wrote:
>
>
> On Sat, Sep
On Sat, Sep 27, 2014 at 1:15 AM, Sajith Kariyawasam wrote:
>
>
> On Sat, Sep 27, 2014 at 1:12 AM, Rajkumar Rajaratnam
> wrote:
>
>> Hi,
>>
>> As you know docker-integration branch is merged into master branch. I am
>> doing test on the master branch now. I will keep post in this thread the
>> st
On Sat, Sep 27, 2014 at 1:12 AM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> As you know docker-integration branch is merged into master branch. I am
> doing test on the master branch now. I will keep post in this thread the
> status of the testing.
>
> I got the following exception when I register a ku
Hi,
As you know docker-integration branch is merged into master branch. I am
doing test on the master branch now. I will keep post in this thread the
status of the testing.
I got the following exception when I register a kubernetes group via rest
API. It is not happening in the docker-integration
20 matches
Mail list logo
