Index Changes

Difference between version and version     

Back to Logging Codes By Component, or Logging Codes By Component Info


At line 47 changed 1 line.
| SCHEDBC-6007 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Cannot find Scheduler consumer endpoint {0} from Component context
| SCHEDBC-6007 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint | Cannot find Scheduler consumer endpoint {0} from Component context
At line 51 added 7 lines.
| SCHEDBC-6011 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint | Interuppted, so abort waiting for Message Exchange ACK/NACK
| SCHEDBC-6012 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}"
| SCHEDBC-6013 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz
| SCHEDBC-6014 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Failed {0} attempt(s) to consume provider endpoint with this trigger message "{1}"; SUSPEND is NOT however supported by this component
| SCHEDBC-6015 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Failed to consume provider endpoint with this trigger message "{0}"
| SCHEDBC-6016 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob | Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3}
| SCHEDBC-6017 | WARNING | org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint | Interrupted, so abort waiting in throttling queue

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-15) was last changed on 24-Mar-09 11:31 AM, -0700 by EdWong