Yes. We have observed these default services listed under faulty services
when we have enabled transports like tcp, mailto etc.
I think, this is something that we have to fix.
On Fri, Jan 21, 2011 at 12:25 PM, Tharindu Mathew wrote:
> Yes, that's the reason. But, just because the service does no
On Fri, Jan 21, 2011 at 12:58 PM, Anjana Fernando wrote:
> Hi,
>
> On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
> >
> >
> > On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma
> wrote:
> >>
> >> AFAIK, event.broker components has been refactored and merged with
> >> event.core. But o
Hi Ratha,
These bundles and features needs to be deployed into M2 repository first.
Then only we can write a pom to merge these features with the 3.0.0 repo.
Thanks
Sameera
On Fri, Jan 21, 2011 at 12:49 PM, Vijayaratha Vijayasingam
wrote:
> Hi,*
>
> *We would like to host the following p2 featu
>
> Anjana,
> We will be using data sources component for UM & Registry database
> connections. I guess problems you have mentioned will be solved by that.
OK, great, then its just a matter of correct default configuration.
Cheers,
Anjana.
> /sumedha
>
>>
>> [1] http://commons.apache.org/dbcp/co
Hi,
On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
>
>
> On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma wrote:
>>
>> AFAIK, event.broker components has been refactored and merged with
>> event.core. But org.wso2.carbon.registry.eventing component still has a
>> dependency on this b
On Fri, Jan 21, 2011 at 12:46 PM, Sumedha Rubasinghe wrote:
>
>
> On Fri, Jan 21, 2011 at 12:40 PM, Anjana Fernando wrote:
>
>> Hi,
>>
>> I noticed that most of the time, we are using the validation query in
>> an inefficient way. The current logic that is in Registry/UM is the
>> "testOnBorrow"
Hi,*
*We would like to host the following p2 features*.
bam-product-version-1.2.1*
*bam-data-publisher-features-3.0.1*
Need to update following four features
- org.wso2.carbon.bam.data.publishers.mediationstats.feature
- org.wso2.carbon.bam.data.publishers.servicestats.feature
Above fea
On Fri, Jan 21, 2011 at 12:40 PM, Anjana Fernando wrote:
> Hi,
>
> I noticed that most of the time, we are using the validation query in
> an inefficient way. The current logic that is in Registry/UM is the
> "testOnBorrow" approach. Here, each time a connection is acquired from
> the connection
Hi,
I noticed that most of the time, we are using the validation query in
an inefficient way. The current logic that is in Registry/UM is the
"testOnBorrow" approach. Here, each time a connection is acquired from
the connection pool, the validation query is run to validate it. So
most of the place
Yes, that's the reason. But, just because the service does not support
mailto doesn't mean it's a faulty service right?
On Fri, Jan 21, 2011 at 12:19 PM, Amila Maha Arachchi wrote:
> Hi Tharindu,
>
> The reason may be configuration errors in the mailto transport. Check the
> log when starting ESB
On Fri, Jan 21, 2011 at 11:19 AM, Rajika Kumarasiri wrote:
> Currently I see three broker specific components in carbon components
> trunk.
> 1. Message Broker
>
this will rename to qpid as Danushka as mentioned.
3. Message Box
this component keeps the message boxes to which you can add messages
Hi Tharindu,
The reason may be configuration errors in the mailto transport. Check the
log when starting ESB. It may give some warnings saying mailto transport is
not configured properly. Something like shown below.
[2011-01-21 12:14:39,768] WARN - MailTransportListener Disabling the mailto
tran
On Fri, Jan 21, 2011 at 9:58 AM, Amila Suriarachchi wrote:
>
>
> On Wed, Jan 19, 2011 at 1:46 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Tue, Jan 18, 2011 at 5:26 PM, Shammi Jayasinghe wrote:
>>
>>> Hi ,
>>>
>>> In the process of providing multi tenant support for CEP , there are two
>>> compon
On Fri, Jan 21, 2011 at 11:54 AM, Senaka Fernando wrote:
>
>
> On Fri, Jan 21, 2011 at 11:42 AM, Sameera Jayasoma wrote:
>
>>
>>
>> On Fri, Jan 21, 2011 at 11:34 AM, Senaka Fernando wrote:
>>
>>>
>>>
>>> On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
>>>
On Fri, Jan 21, 2
On Fri, Jan 21, 2011 at 11:42 AM, Sameera Jayasoma wrote:
>
>
> On Fri, Jan 21, 2011 at 11:34 AM, Senaka Fernando wrote:
>
>>
>>
>> On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
>>
>>>
>>>
>>> On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma wrote:
>>>
AFAIK, event.broker compo
On Fri, Jan 21, 2011 at 11:34 AM, Senaka Fernando wrote:
>
>
> On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
>
>>
>>
>> On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma wrote:
>>
>>> AFAIK, event.broker components has been refactored and merged with
>>> event.core. But org.wso2.carb
On Fri, Jan 21, 2011 at 11:34 AM, Rajika Kumarasiri wrote:
>
>
> On Fri, Jan 21, 2011 at 11:28 AM, Danushka Menikkumbura > wrote:
>
>> Well they look confusing until you understand what each of them really do
>> ;-).
>
>
> What I meant was their components name together it's very confusing. I do
On Fri, Jan 21, 2011 at 11:05 AM, Senaka Fernando wrote:
>
>
> On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma wrote:
>
>> AFAIK, event.broker components has been refactored and merged with
>> event.core. But org.wso2.carbon.registry.eventing component still has a
>> dependency on this broker
On Fri, Jan 21, 2011 at 11:28 AM, Danushka Menikkumbura
wrote:
> Well they look confusing until you understand what each of them really do
> ;-).
What I meant was their components name together it's very confusing. I do
not think a user need to understand the internals to know what a component
d
Well they look confusing until you understand what each of them really do
;-). Anyway we wont have a component called message-broker from now on. I am
renaming it to qpid.
Danushka
On Fri, Jan 21, 2011 at 11:19 AM, Rajika Kumarasiri wrote:
> Currently I see three broker specific components in c
Currently I see three broker specific components in carbon components trunk.
1. Message Broker
2. Broker
3. Message Box
4. Broker Manager
I think we need to come up with proper names for some of above components,
it seems the naming schema is very confusing right now. I am not sure if we
can refa
On Fri, Jan 21, 2011 at 11:01 AM, Sameera Jayasoma wrote:
> AFAIK, event.broker components has been refactored and merged with
> event.core. But org.wso2.carbon.registry.eventing component still has a
> dependency on this broker packages. Thats why this build is failing.
>
> Who is working on mig
AFAIK, event.broker components has been refactored and merged with
event.core. But org.wso2.carbon.registry.eventing component still has a
dependency on this broker packages. Thats why this build is failing.
Who is working on migrating the registry.event component?
Thanks
Sameera
--
Sameera Jay
On Fri, Jan 21, 2011 at 9:57 AM, Amila Jayasekara wrote:
>
>
> On Thu, Jan 20, 2011 at 11:24 PM, Senaka Fernando wrote:
>
>> On Thu, Jan 20, 2011 at 11:10 PM, Denis Weerasiri wrote:
>>
>>> Hi all,
>>> Can we ignore these errors? Anyway build process get halted for a long
>>> time. :(
>>>
>>
>>
On Fri, Jan 21, 2011 at 9:51 AM, Amila Suriarachchi wrote:
>
>
> On Wed, Jan 19, 2011 at 10:53 PM, Thilina Buddhika wrote:
>
>>
>>
>> On Wed, Jan 19, 2011 at 10:17 PM, Shammi Jayasinghe wrote:
>>
>>>
>>>
>>> On Wed, Jan 19, 2011 at 7:44 PM, Sameera Jayasoma wrote:
>>>
On Tuesday, January 18,
On Wed, Jan 19, 2011 at 1:46 PM, Hiranya Jayathilaka wrote:
>
>
> On Tue, Jan 18, 2011 at 5:26 PM, Shammi Jayasinghe wrote:
>
>> Hi ,
>>
>> In the process of providing multi tenant support for CEP , there are two
>> components (broker-manager and cep) that are needed to implement the
>> interface
On Thu, Jan 20, 2011 at 11:24 PM, Senaka Fernando wrote:
> On Thu, Jan 20, 2011 at 11:10 PM, Denis Weerasiri wrote:
>
>> Hi all,
>> Can we ignore these errors? Anyway build process get halted for a long
>> time. :(
>>
>
> This is something related to API doc generation. The same issue was
> disc
On Wed, Jan 19, 2011 at 10:53 PM, Thilina Buddhika wrote:
>
>
> On Wed, Jan 19, 2011 at 10:17 PM, Shammi Jayasinghe wrote:
>
>>
>>
>> On Wed, Jan 19, 2011 at 7:44 PM, Sameera Jayasoma wrote:
>>
>>> On Tuesday, January 18, 2011, Shammi Jayasinghe wrote:
>>> > Hi ,
>>> >
>>> > In the process of pro
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20110128T05Z
DTEND:20110128T06Z
DTSTAMP:20110120T195040Z
ORGANIZER;CN=Senaka Fernando:mailto:sen...@wso2.com
UID:k45gh6ij1ovij8eq461c9jj...@google.com
ATTENDE
On Thu, Jan 20, 2011 at 11:10 PM, Denis Weerasiri wrote:
> Hi all,
> Can we ignore these errors? Anyway build process get halted for a long
> time. :(
>
This is something related to API doc generation. The same issue was
discussed sometime back. It seems that the way we have configured the maven
Hi all,
Can we ignore these errors? Anyway build process get halted for a long time.
:(
[INFO]
[INFO] Building WSO2 Carbon - Registry Kernel
[INFO]task-segment: [clean, install]
[INFO]
Hi,
This issue is fixed now. Take a svn up inside
components\mediation-initializer\org.wso2.carbon.mediation.dependency.mgt
and rebuild.
Thank You.
On Thu, Jan 20, 2011 at 5:40 PM, Selvaratnam Uthaiyashankar
wrote:
> $subject
>
> [INFO] Compiling 28 source files to
> E:\src\java\carbon\componen
On Thu, Jan 20, 2011 at 1:56 PM, Prabath Abeysekera wrote:
> Hi devs,
>
> The pom.xml of the event component only indicates 6 out of its 14
> implemented modules, inside the tag. This results in some errors
> while building the event feature and I just wonder whether there is a
> specific require
$subject
[INFO] Compiling 28 source files to
E:\src\java\carbon\components\mediation-initializer\org.wso2.carbon.mediation.dependency.mgt\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
We need to copy the event-broker.xml to the repository/conf directory
of the ESV distribution.
Thanks,
Supun..
On Thu, Jan 20, 2011 at 4:48 PM, Miyuru Wanninayaka wrote:
> Hi all,
>
> I'm getting two exceptions while starting up ESB trunk (just built)
>
> miyuru@miyuru-laptop:~/code/wso2/carbon/
Hi all,
I'm getting two exceptions while starting up ESB trunk (just built)
miyuru@miyuru-laptop:~/code/wso2/carbon/trunk/products/esb/modules/distribution/target/wso2esb-4.0.0-SNAPSHOT/bin$
./wso2server.sh
[2011-01-20 16:44:39,940] INFO - Main Initializing system...
[2011-01-20 16:44:40,161] I
I'm using a Json client. Maybe the issue is related to that.
On Thu, Jan 20, 2011 at 1:58 PM, Charitha Kankanamge wrote:
> I tried invoking a proxy similar to your one but it worked without Soap
> tracer.
>
> http://ws.apache.org/ns/synapse"; name="TestProxy"
> transports="https,http" statistics=
I tried invoking a proxy similar to your one but it worked without Soap
tracer.
http://ws.apache.org/ns/synapse"; name="TestProxy"
transports="https,http" statistics="disable" trace="disable"
startOnLoad="true">
Hi devs,
The pom.xml of the event component only indicates 6 out of its 14
implemented modules, inside the tag. This results in some errors
while building the event feature and I just wonder whether there is a
specific requirement not to include the rest of those modules.
Regards,
--
Prabath
Well there should be a CNF error if you happen to run the message broker.
Danushka
On Thu, Jan 20, 2011 at 1:13 PM, Sumedha Rubasinghe wrote:
>
>
> On Thu, Jan 20, 2011 at 12:55 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>>
>>
>> On Wed, Jan 19, 2011 at 4:52 AM, Danushka Menik
It's an interesting error:
Whenever there is a log mediator or tcpmon or SOAP tracer on the flow works
just fine.
If not it fails. :S
On Thu, Jan 20, 2011 at 12:51 PM, Prabath Siriwardana wrote:
> Please log the full message with SOAP UI on and with out it - just
> before the SEND and see there
41 matches
Mail list logo
