*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Wed Mar 7 06:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Wed Mar 7 04:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Wed Mar 7 02:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Wed Mar 7 00:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 22:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 20:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 18:30:43 UTC 2012
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 16:30:43 UTC 2012
> Doesn't contributing to the RegistryStartup service, which has an ordered
> configuration, does exactly what's been asked here?
Yes it does, but it is a lot messier, you need an inner class, and so on.
Specialy when you are using @Startup and then you need an order.
Whole purpose of the @Star
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 14:30:43 UTC 2012
If I remember correctly, we had this discussion already. IMO, @Startup
shouldn't have any order. If you need some kind of order, do it as Thiago
suggested or build your own service with ordered configuration which you
inject into a startup method.
On Tue, Mar 6, 2012 at 2:48 PM, Thiago H. de Paula
On Tue, 06 Mar 2012 10:32:58 -0300, Dragan Sahpaski (Commented) (JIRA)
wrote:
[
https://issues.apache.org/jira/browse/TAP5-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223254#comment-13223254
]
Dragan Sahpaski commented on TAP5-1842:
I would like to improve @Startup annotation to support the id and the
constraints attributes, jira issue
https://issues.apache.org/jira/browse/TAP5-1842
See my implementation:
https://github.com/dstepanov/tapestry5/commit/21f90340d98e3aa778f65ca6a46767ad7662c8ff
If there is someone who thinks
*** ASF Nagios ***
Notification Type: PROBLEM
Host: tapestry.zones.apache.org
Address: 140.211.11.200
Service: HTTP - Tapestry Demo
State: CRITICAL
Info: CRITICAL - Socket timeout after 16 seconds
Date/Time: Tue Mar 6 12:30:43 UTC 2012
14 matches
Mail list logo
