kodepett
I check my logs today in production and found below error logs indicating the crashing of my phoenix server endpoint.
request_id=FfJ7ijs3cGTfqa8AHM_B [error] 3914- fatal: :expected_element_start_tag
[error] pid<0.21588.4> running DebitorWeb.Endpoint (connection pid<0.21587.4>, stream id 1) terminated
I think :expected_element_start_tag per what I stumbled upon is related to xmerl - I’m using SweetXml which is a wrapper around xmerl.
Will I be right in concluding that this is what is causing the crashing of the Endpoint - can I simply wrap the library in a try and catch block to resolve this issue.
Thanks.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 5 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
idi527
Ah, I see. Then, I guess, yes, trapping is one of the possible approaches. You can also try parsing in a separate process which is not linked but monitored by the request processes.
kodepett
I want to avoid the spawned process crashing- per how cowboy handles request, if the process crashes, only the crash report is logged. I want to be able to catch xmerl exception, log it with the exact xml string and possibly proceed to run other api calls.
idi527
But they are logged with a stacktrace by default, no? And why would you want to trap them?
kodepett
That sounds comforting, I was a bit worried it was affecting the entire endpoint. BTW - it’s a transactional processing system and I will be much more comfortable trapping and logging all exceptions rather than have it crashed. Please advise if wrapping SweetXml in try and catch will help.
idi527
What for exactly? I’d prefer a crashing endpoint (note this is not the whole application, but a single connection/stream process pair crashing) with a log trace.