Hi Senduran,
Thanks for the quick response. I tested the msf4j with carbon-transports
version 2.0.3-SNAPSHOT in Carbon-Kernel 5.1.0-alpha2 using the stock-quote
sample and it works fine.
@Samiyuru: I have update the PR [1] with the carbon-transports and
carbon-messaging to 2.0.3 and 1.0.3
Hi Senduran,
We don't use carbon-transport directly. But we depend on MSF4j which depend
on carbon-transport. We'll check and let you know.
Regards,
Asitha
On Tue, May 17, 2016 at 1:19 PM, Niranjan Karunanandham
wrote:
> Hi Senduran,
>
> We need to test it with the kernel
Hi Senduran,
We need to test it with the kernel if the startup resolver and other things
are working fine with msf4j.
Regards,
Nira
On Tue, May 17, 2016 at 12:32 PM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:
> Hi Niranjan / Samiyuru
>
> MSF4J's test are running successfully with
Hi Niranjan / Samiyuru
MSF4J's test are running successfully with the latest carbon-transport
(2.0.3-snapshot) and carbon messaging 1.0.3.
Is there any additional tests we need to perform before releasing the
carbon transport.
@Hasitha, Asitha
Please check your latest development with carbon
Hi Niranjan
Transport Properties will get its default value if the file is not
available. But I have missed to initialize the transport properties. Now it
is changed to initialize with an empty set.
I'll try running the MSF4J test cases.
Yes, if this doesn't solves, I will create a jira and
Hi Samiyuru / Senduran,
On Tue, May 17, 2016 at 11:35 AM, Samiyuru Senarathne
wrote:
> Transport config yaml file is loaded from transport component. So setting
> defaults in MSF4J level is not successful. IMO its better to set defaults
> in transport level to support
Transport config yaml file is loaded from transport component. So setting
defaults in MSF4J level is not successful. IMO its better to set defaults
in transport level to support initialization without a config file or with
a config file with only a sub set of the configurations.
Best Regards,
Hi all,
As per the offline discussion with Samiyuru, we need to modify the unit
test for HttpServerTest to read from the config files which has the new
default values.
@Samiyuru: In-order to support msf4j to run in standalone mode, don't we
need to make changes to the msf4j code to set default
Hi Niranjan,
MSF4J core unit tests use 2 transport config files [1]. You can add the new
config to these files.
[1] https://github.com/wso2/msf4j/tree/master/core/src/test/resources
Best Regards,
Samiyuru
On Tue, May 17, 2016 at 10:27 AM, Niranjan Karunanandham
wrote:
>
Hi all,
I looked into the unit tests that are failing in msf4j[1] after upgrading
carbon-transports to v 2.0.3-SNAPSHOT and noticed that this is happening
when initializing the MicroserviceRunner instance. As per the error [2],
this is coming from carbon-transports. As per the offline discussion
Hi Senduran,
I tried to build msf4j with your changes but its tests are failing with NPE
and java.lang.NoClassDefFoundError. Has there been any major changes in
carbon-transports from 2.0.1 to 2.0.3-SNAPSHOT? We need to fixes these
issues.
@Hasitha: Till these issues are sorted will you be able
Noted. The PR i sent for msf4j is to the master branch so it could be
tested directly with the changes that has been applied to the
carbon-transports.. Anyway I will test it and get back to you.
Regards,
Nira
On Mon, May 16, 2016 at 11:55 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:
Hi Niranjan / Hasitha
We have upgraded carbon transport's kernel version to 5.1.0-alpha2 and done
the fixes for the new start up resolver (based on [1] ). The changes are
pushed to the master branch (2.0.3-snapshot)
Please test it and let us know whether it resolves the issues. so that we
can
Hi all,
I have modified carbon-datasources [1] and msf4j [2] with carbon-kernel
5.1.0-alpha2 (in staging). I verified msf4j modifying by changing
carbon-transports v2.0.1 [3] with startup resolver changes.
[1] - https://github.com/wso2/carbon-datasources/pull/14
[2] -
Can we have a quick resolution to this issue.
Regards
Nandika
On Mon, May 9, 2016 at 11:09 AM, Niranjan Karunanandham
wrote:
> Hi Sameera,
>
> I have fixed this for carbon-datasources in PR [1].
>
> [1] - https://github.com/wso2/carbon-datasources/pull/14
>
> Regards,
> Nira
Hi Sameera,
I have fixed this for carbon-datasources in PR [1].
[1] - https://github.com/wso2/carbon-datasources/pull/14
Regards,
Nira
On Mon, May 9, 2016 at 10:43 AM, Afkham Azeez wrote:
> Transport folks, please note. I think a release is planned but we will
> need to hold
Transport folks, please note. I think a release is planned but we will need
to hold it back until these changes are made.
On Sun, May 8, 2016 at 12:39 PM, Niranjan Karunanandham
wrote:
> Hi Hasitha,
>
> There were some improvements done to the startup resolver as mentioned in
Hi Niranjan,
Thanks. I think we need to update transports, msf4j git repositories as
well. We do this on Monday.
Thanks,
Sameera.
On Sun, May 8, 2016 at 12:39 PM, Niranjan Karunanandham
wrote:
> Hi Hasitha,
>
> There were some improvements done to the startup resolver as
Hi Hasitha,
There were some improvements done to the startup resolver as mentioned in
[1]. I faced a similar issue[2] when testing the Kernel 5.1.0-alpha2 (which
is in staging) with carbon-datasources and I was able to fix it by
following the doc and updating the datasource.core pom.xml [3] and
Hi Sameera,
We are getting following error when server startup.
osgi> [2016-05-07 20:21:11,972] ERROR
{org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
Error occurred in Startup Order Resolver.
org.wso2.carbon.kernel.internal.startupresolver.StartOrderResolverException:
20 matches
Mail list logo