Petals ESB Container

Display a more explicit error message when a endpoint is missing / not callable

Details

  • Type: Improvement Request Improvement Request
  • Status: Inaccurate Inaccurate
  • Priority: Blocker Blocker
  • Resolution: Cannot Reproduce
  • Affects Version/s: 3.1
  • Fix Version/s: None
  • Component/s: Logging, Router, Topology/network, Transporter
  • Security Level: Public
  • Description:

    It would be great if we had a more explicit (or concise) message indicating the abscence of an endpoint when trying to call a non existing / non connected / non callable endpoint.

  • Environment:
    PetalsESB 3.1

Activity

Ascending order - Click to sort in descending order
Charles Casadei made changes - Fri, 20 Aug 2010 - 17:16:30 +0200
Field Original Value New Value
Link This issue blocks SPVEOLIAE-40 [ SPVEOLIAE-40 ]
Hide
Permalink
mjambert added a comment - Tue, 26 Apr 2011 - 16:40:45 +0200

Could you elaborate please on what is not correct ?
What is the current message ?
What message would you expect ?

Show
mjambert added a comment - Tue, 26 Apr 2011 - 16:40:45 +0200 Could you elaborate please on what is not correct ? What is the current message ? What message would you expect ?
Hide
Permalink
Sébastien André added a comment - Wed, 27 Apr 2011 - 11:52:11 +0200

I have two service assemblies, when I deploy only one (endpoint missing) I get this stack trace:

[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 Intercepting message processing on ACCEPT_RESPONSE
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Message in with Id 'petals:uid:B16E5F93D497F9FABF94371481408295266' to send
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Operation : {http://company.com/}operation
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Message property 'javax.jbi.messaging.protocol.headers' : {}
ERROR:  'The original InputStream has been closed; cannot read from a closed InputStream.'
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 failed to log the content of the message to send: java.io.IOException: The original InputStream has been closed; cannot read from a closed InputStream.
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 Accepting a JBI message with Id : petals:uid:B16E5F93D497F9FABF94371481408295266
[Petals.Container.Components.petals-se-xslt]-FINE 2010-08-06 14:27:20,220 Accepting a JBI message with Id : petals:uid:B16E5F93D497F9FABF94371492362909267
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Process an exchange as CONSUMER with id : petals:uid:B16E5F93D497F9FABF94371481408295266
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Intercepting message processing on SEND_RESPONSE
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Router: processing asynchronously the pattern
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Send an asynchronous exchange with id : petals:uid:B16E5F93D497F9FABF94371466630799265
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Remove Context with original exchange id : petals:uid:B16E5F93D497F9FABF94371466630799265
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Intercepting message processing on ACCEPT_RESPONSE

[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Message in with Id 'petals:uid:B16E5F93D497F9FABF94371466630799265' to send
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Operation : {http://company.com/}operation
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,222 Message property 'javax.jbi.messaging.protocol.headers' : {}
ERROR:  'No byte read.'
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,223 failed to log the content of the message to send: java.io.IOException: No byte read.
[Petals.Container.Components.petals-bc-soap]-FINE 2010-08-06 14:27:20,223 Receive an Active status message
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,224 The MEP 'http://www.w3.org/2004/08/wsdl/in-out' does not accept a null response
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,224 Error while creating SOAP response
org.apache.axis2.AxisFault: The MEP 'http://www.w3.org/2004/08/wsdl/in-out' does not accept a null response
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.processJBIResponse(RequestProcessor.java:404)
	at org.ow2.petals.binding.soap.listener.incoming.SOAPProcessor.process(SOAPProcessor.java:150)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:173)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:123)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:121)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doGet(WelcomeServlet.java:80)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doPost(WelcomeServlet.java:131)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,226 Error while closing JBI MessageExchange.
javax.jbi.messaging.MessagingException: The MessageExchange state does not allow this operation.
	at org.ow2.petals.jbi.messaging.exchange.MessageExchangeImpl.setStatus(MessageExchangeImpl.java:560)
	at org.ow2.petals.jbi.messaging.exchange.MessageExchangeDecorator.setStatus(MessageExchangeDecorator.java:500)
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.closeMessageExchange(RequestProcessor.java:111)
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.processJBIResponse(RequestProcessor.java:418)
	at org.ow2.petals.binding.soap.listener.incoming.SOAPProcessor.process(SOAPProcessor.java:150)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:173)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:123)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:121)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doGet(WelcomeServlet.java:80)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doPost(WelcomeServlet.java:131)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

In our application, error management is based on log messages, is it possible to print "Endpoint JBI 'XXXX' not found on the bus" instead?

Show
Sébastien André added a comment - Wed, 27 Apr 2011 - 11:52:11 +0200 I have two service assemblies, when I deploy only one (endpoint missing) I get this stack trace: 
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 Intercepting message processing on ACCEPT_RESPONSE
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Message in with Id 'petals:uid:B16E5F93D497F9FABF94371481408295266' to send
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Operation : {http://company.com/}operation
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,220 Message property 'javax.jbi.messaging.protocol.headers' : {}
ERROR:  'The original InputStream has been closed; cannot read from a closed InputStream.'
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 failed to log the content of the message to send: java.io.IOException: The original InputStream has been closed; cannot read from a closed InputStream.
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,220 Accepting a JBI message with Id : petals:uid:B16E5F93D497F9FABF94371481408295266
[Petals.Container.Components.petals-se-xslt]-FINE 2010-08-06 14:27:20,220 Accepting a JBI message with Id : petals:uid:B16E5F93D497F9FABF94371492362909267
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Process an exchange as CONSUMER with id : petals:uid:B16E5F93D497F9FABF94371481408295266
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Intercepting message processing on SEND_RESPONSE
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Router: processing asynchronously the pattern
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Send an asynchronous exchange with id : petals:uid:B16E5F93D497F9FABF94371466630799265
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Remove Context with original exchange id : petals:uid:B16E5F93D497F9FABF94371466630799265
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,221 Intercepting message processing on ACCEPT_RESPONSE

[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Message in with Id 'petals:uid:B16E5F93D497F9FABF94371466630799265' to send
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,221 Operation : {http://company.com/}operation
[Petals.Container.Components.petals-se-eip]-FINEST 2010-08-06 14:27:20,222 Message property 'javax.jbi.messaging.protocol.headers' : {}
ERROR:  'No byte read.'
[Petals.Container.Components.petals-se-eip]-FINE 2010-08-06 14:27:20,223 failed to log the content of the message to send: java.io.IOException: No byte read.
[Petals.Container.Components.petals-bc-soap]-FINE 2010-08-06 14:27:20,223 Receive an Active status message
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,224 The MEP 'http://www.w3.org/2004/08/wsdl/in-out' does not accept a null response
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,224 Error while creating SOAP response
org.apache.axis2.AxisFault: The MEP 'http://www.w3.org/2004/08/wsdl/in-out' does not accept a null response
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.processJBIResponse(RequestProcessor.java:404)
	at org.ow2.petals.binding.soap.listener.incoming.SOAPProcessor.process(SOAPProcessor.java:150)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:173)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:123)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:121)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doGet(WelcomeServlet.java:80)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doPost(WelcomeServlet.java:131)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
[Petals.Container.Components.petals-bc-soap]-WARNING 2010-08-06 14:27:20,226 Error while closing JBI MessageExchange.
javax.jbi.messaging.MessagingException: The MessageExchange state does not allow this operation.
	at org.ow2.petals.jbi.messaging.exchange.MessageExchangeImpl.setStatus(MessageExchangeImpl.java:560)
	at org.ow2.petals.jbi.messaging.exchange.MessageExchangeDecorator.setStatus(MessageExchangeDecorator.java:500)
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.closeMessageExchange(RequestProcessor.java:111)
	at org.ow2.petals.binding.soap.listener.incoming.RequestProcessor.processJBIResponse(RequestProcessor.java:418)
	at org.ow2.petals.binding.soap.listener.incoming.SOAPProcessor.process(SOAPProcessor.java:150)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.process(PetalsReceiver.java:173)
	at org.ow2.petals.binding.soap.listener.incoming.PetalsReceiver.invokeBusinessLogic(PetalsReceiver.java:123)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:121)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doGet(WelcomeServlet.java:80)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.WelcomeServlet.doPost(WelcomeServlet.java:131)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
In our application, error management is based on log messages, is it possible to print "Endpoint JBI 'XXXX' not found on the bus" instead?
Hide
Permalink
mjambert added a comment - Thu, 28 Apr 2011 - 14:17:15 +0200

cannot deploy sa provided within support ticket (legacy calls to svn-esb.cge.fr in eip su).
do not know how to reproduce this with the info I have.

Show
mjambert added a comment - Thu, 28 Apr 2011 - 14:17:15 +0200 cannot deploy sa provided within support ticket (legacy calls to svn-esb.cge.fr in eip su). do not know how to reproduce this with the info I have.
Christophe DENEUX made changes - Thu, 7 Mar 2013 - 12:25:18 +0100
Assignee Marc Jambert [ mjambert ]
Priority Blocker [ 1 ]
Component/s Logging [ 10255 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Inaccurate Inaccurate
250d 21h 1m
1
mjambert
Thu, 28 Apr 2011 - 14:17:15 +0200



People

Dates

  • Created:
    Fri, 20 Aug 2010 - 17:16:13 +0200
    Updated:
    Thu, 7 Mar 2013 - 12:25:18 +0100
    Resolved:
    Thu, 28 Apr 2011 - 14:17:15 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.