[ 
https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897412#comment-17897412
 ] 

Arashpreet Singh commented on OFBIZ-13152:
------------------------------------------

This is not the case for cryptic name only, this error always happen when the 
very first request failed on server. 

And for this particular case(cryptic name), sometimes user enter special 
characters in the name by mistakes and ofbiz got stuck at time. 

> Inconsistent Error Handling for Entity Creation via Exported Service
> --------------------------------------------------------------------
>
>                 Key: OFBIZ-13152
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13152
>             Project: OFBiz
>          Issue Type: Bug
>          Components: rest-api
>            Reporter: Arashpreet Singh
>            Assignee: Jacques Le Roux
>            Priority: Major
>         Attachments: trunk-logs.txt
>
>
> There appears to be a problem with the OFBiz error-handling mechanism when 
> creating an entity using an exported service. Initially, if incorrect input 
> data is provided, OFBiz correctly returns a meaningful error message from the 
> backend. However, upon resubmitting the same request without any changes, 
> instead of returning the same meaningful error, the system responds with a 
> 500 internal server error and an HTML response.
> Interestingly, when OFBiz is restarted, the first request with the same 
> incorrect data again returns a proper, meaningful error message. But all 
> subsequent requests with the same data continue to produce a 500 response, 
> which is not ideal for consistent error reporting.
> This issue impacts debugging and error handling for services that rely on 
> accurate back-end responses. The expected behavior would be to consistently 
> return the meaningful error for all requests, regardless of whether OFBiz has 
> been restarted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to