stompserver service on ruby 3.0 crashes when a connection is created.

[Ertan Ataman]

Seems like stompserver package is incompatible with ruby3.0 since it runs flawlessly on ubuntu 20.04 but not on 22.04 or 23.04.
I also tried ruby3.1 via snap but sysctl does not use it.

myuser@myuser-Latitude-5511:~$ sudo service stompserver status
● stompserver.service - LSB: a stomp messaging server implemented in Ruby
     Loaded: loaded (/etc/init.d/stompserver; generated)
     Active: active (running) since Thu 2023-01-19 14:29:10 +03; 2s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 9895 ExecStart=/etc/init.d/stompserver start (code=exited, status=0/SUCCESS)
      Tasks: 1 (limit: 18552)
     Memory: 21.5M
        CPU: 136ms
     CGroup: /system.slice/stompserver.service
             └─9905 /usr/bin/ruby /usr/bin/stompserver -C /etc/stompserver/stompserver.conf

Oca 19 14:29:08 myuser-Latitude-5511 systemd[1]: Starting LSB: a stomp messaging server implemented in Ruby...
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9895]: * Starting stompserver stompserver
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9902]: Changing group to stompserver.
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9902]: Changing user to stompserver.
Oca 19 14:29:10 myuser-Latitude-5511 stompserver[9895]: ...done.
Oca 19 14:29:10 myuser-Latitude-5511 systemd[1]: Started LSB: a stomp messaging server implemented in Ruby.
myuser@myuser-Latitude-5511:~$ telnet localhost 61613
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
myuser@myuser-Latitude-5511:~$ sudo service stompserver status
● stompserver.service - LSB: a stomp messaging server implemented in Ruby
     Loaded: loaded (/etc/init.d/stompserver; generated)
     Active: active (exited) since Thu 2023-01-19 14:29:10 +03; 12s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 9895 ExecStart=/etc/init.d/stompserver start (code=exited, status=0/SUCCESS)
        CPU: 140ms

Oca 19 14:29:08 myuser-Latitude-5511 systemd[1]: Starting LSB: a stomp messaging server implemented in Ruby...
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9895]: * Starting stompserver stompserver
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9902]: Changing group to stompserver.
Oca 19 14:29:08 myuser-Latitude-5511 stompserver[9902]: Changing user to stompserver.
Oca 19 14:29:10 myuser-Latitude-5511 stompserver[9895]: ...done.
Oca 19 14:29:10 myuser-Latitude-5511 systemd[1]: Started LSB: a stomp messaging server implemented in Ruby.
myuser@myuser-Latitude-5511:~$ cat /var/log/stompserver/stompserver.log
MemoryQueue initialized
TopicManager initialized
QueueManager initialized
Stomp protocol handler starting on 127.0.0.1 port 61613
MemoryQueue initialized
TopicManager initialized
QueueManager initialized
Stomp protocol handler starting on 127.0.0.1 port 61613
/usr/bin/stompserver:36:in `block (3 levels) in <main>': class variable access from toplevel (RuntimeError)
 from /usr/bin/stompserver:35:in `instance_eval'
 from /usr/bin/stompserver:35:in `block (2 levels) in <main>'
 from /usr/lib/ruby/vendor_ruby/eventmachine.rb:1528:in `event_callback'
 from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run_machine'
 from /usr/lib/ruby/vendor_ruby/eventmachine.rb:196:in `run'
 from /usr/bin/stompserver:18:in `<main>'

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: stompserver 0.9.9gem-4.1
Uname: Linux 6.1.6-060106-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 19 14:23:07 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
InstallationDate: Installed on 2021-04-01 (658 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10
PackageArchitecture: all
SourcePackage: stompserver
UpgradeStatus: Upgraded to kinetic on 2023-01-19 (0 days ago)