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: Kurt T Stam
             Fix For: 3.0


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.

Reply via email to