Hi Udara,
It can be found in [1]. Could you please verify?
[1]
https://github.com/wso2/private-paas/commit/c033cb4e7c7d9ace3e95f3dabc8e42e70e202f8a
Thanks,
Reka
On Wed, May 28, 2014 at 8:58 PM, Udara Liyanage wrote:
> Hi Reka
>
> I built the packs today evening.
>
>
>
> On Wed, May 28, 2014
Hi Reka
I built the packs today evening.
On Wed, May 28, 2014 at 8:55 PM, Reka Thirunavukkarasu wrote:
> The jaggery error is already fixed. Can you take an update?
>
> Thanks,
> Reka
>
>
> On Wed, May 28, 2014 at 8:49 PM, Isuru Haththotuwa wrote:
>
>> In MT scenario, you need to wait till the
The jaggery error is already fixed. Can you take an update?
Thanks,
Reka
On Wed, May 28, 2014 at 8:49 PM, Isuru Haththotuwa wrote:
> In MT scenario, you need to wait till the instances are active to
> subscribe.
>
>
> On Wed, May 28, 2014 at 8:42 PM, Udara Liyanage wrote:
>
>> Hi,
>>
>> I got
Hi Isuru,
I logged into the instances and look for puppet log. Looks like problem
with the puppet.
Domain puppet.udara.com
* Restarting puppet agent
...done.
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service hostname start
Since the script you a
In MT scenario, you need to wait till the instances are active to subscribe.
On Wed, May 28, 2014 at 8:42 PM, Udara Liyanage wrote:
> Hi,
>
> I got the fallowing error when subscribing to a ESB cartridge.
>
>
> nt.output.adaptor.jms.internal.util.JMSConnectionFactory}
> TID: [0] [STRATOS] [2014
Hi,
I got the fallowing error when subscribing to a ESB cartridge.
nt.output.adaptor.jms.internal.util.JMSConnectionFactory}
TID: [0] [STRATOS] [2014-05-28 15:07:25,261] INFO
{controller.cartridgeSubscribeSubmit} -
:[{"activeInstances" : 0, "cartridgeAlias" : "-",
"cart
