juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ShengTao Dong (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-245) Subscription Listener complains
Date Mon, 25 Oct 2010 09:51:21 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924514#action_12924514
] 

ShengTao Dong commented on JUDDI-245:
-------------------------------------

Which version code this patch has been patched? We are using the version 3.0.1, there still
some issues like this.

The log is:
WARN [org.apache.juddi.subscription.SubscriptionNotifier] Skipping current notification cycle
because the registry is too busy.
2010-10-22 07:46:17,738 WARN [org.apache.juddi.subscription.SubscriptionNotifier] NotificationTimer
is lagging 551 milli seconds behind. A lag time which exceeds an acceptable lagtime of 500ms
indicates that the registry server is under stress. We are therefore skipping this notification
cycle. 

We need the notification occur every time, no skip in any conditon, is there  a property we
can set to make this happen?

> Subscription Listener complains
> -------------------------------
>
>                 Key: JUDDI-245
>                 URL: https://issues.apache.org/jira/browse/JUDDI-245
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0beta
>            Reporter: Kurt T Stam
>            Assignee: Tom Cunningham
>             Fix For: 3.0rc1
>
>
> ISSUE 1:
> 2009-05-31 21:46:19,732 INFO [org.apache.juddi.Registry] - Creating new jUDDI registry...2009-05-31
21:46:19,775 ERROR [org.apache.juddi.api.impl.UDDISubscriptionListenerImpl] - Cannot locate
configuration source juddi.propertiesorg.apache.commons.configuration.ConfigurationException:
Cannot locate configuration source juddi.properties        at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:215)
       at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:195)
       at org.apache.commons.configuration.AbstractFileConfiguration.<init>(AbstractFileConfiguration.java:140)
       at org.apache.commons.configuration.PropertiesConfiguration.<init>(PropertiesConfiguration.java:
> 242)        at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:78)
>         at org.apache.juddi.config.AppConfig.<init>(AppConfig.java:64)        at
org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:175)        at org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:197)
       at org.apache.juddi.subscription.SubscriptionNotifier.<init>(SubscriptionNotifier.java:62)
       at org.apache.juddi.Registry.start(Registry.java:37)
>         at org.apache.juddi.api.impl.BaseService.<init>(BaseService.java:35)  
     at org.apache.juddi.api.impl.AuthenticatedService.<init>(AuthenticatedService.java:34)
       at org.apache.juddi.api.impl.UDDISubscriptionListenerImpl.<init>(UDDISubscriptionListenerImpl.ja
> va:41)
> ISSUE 2:
> 2009-05-31 17:43:27,712 WARN [org.apache.juddi.subscription.SubscriptionNotifier] - NotificationTimer
is lagging 157755 milli seconds behind. A lag time which exceeds an acceptable lagtime of
20ms indicates that the registry server is under stress. We are therefore skipping this notification
cycle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message