Age | Commit message (Collapse) | Author |
|
The guard is against a connection to a given peer already existing but
fails if diameter is not running on a remote node.
Note that the guard itself is to be made configurable in R15B03
(OTP-10493) to allow multiple connections per peer.
|
|
|
|
|
|
Configuration will allow relaxation of the guard against multiple
transport connections to the same peer.
|
|
It was broken by sequence masks and can be simplified using (the
new-ish) watchdog events.
|
|
|
|
This makes capabilities available to service_info as soon as
capabilities exchange has been completed. In particular, before state
OKAY is reached.
|
|
To retrieve service_opt() values. Don't document it yet.
|
|
Mostly to use it in the watchdog test suite that's been broken by
sequence masks. Do a bit of cleanup while we're at it.
|
|
|
|
It's neither used nor maintained.
|
|
There are plt/dialyze targets in src/Makefile.
|
|
|
|
Code should be loaded in this order:
diameter_session (sequence/1)
diameter_peer_fsm (calls to sequence/1)
diameter_service (sequence config, mask in receive_message/3)
diameter_watchdog (mask in peer start and receive_message/3)
diameter_config (accept sequence config)
Order of diameter and diameter_peer doesn't matter.
|
|
Allow 32-bit Hop-by-Hop and End-to-End identifiers to be modified by
replacing the topmost bits with a constant value. This allow services on
different nodes to generate globally unique identifiers by having each
node mask in its own constant.
|
|
* anders/diameter/service_info/OTP-10460:
Don't call service process for service_info
|
|
* anders/diameter/failover_error/OTP-10461:
Add missing clause for peer failover
|
|
* anders/diameter/event_timing/OTP-10459:
Send up event *after* inserting peer in table
|
|
* anders/diameter/watchdog_timeout/OTP-10444:
Exit peer_fsm with {shutdown, watchdog_timeout}, not shutdown
|
|
* anders/diameter/packet_callback/OTP-10441:
Use packet callbacks in traffic suite
Improve other diameter_app doc
Document eval_packet
Add eval_packet for examining outgoing messages after encode
|
|
* anders/diameter/capabilities_errors/OTP-10440:
Fix matching in case of erroneous capabilities config
Fix handling of Origin-State-Id config
|
|
* lukas/rcs-ppc-cross-tests/OTP-10265:
Skip ct_netconf tests if there is no crypto
Migrate timers from test_server to ct interface
Update tests to run with an oldshell emulator
Move crypto check so that tc is skipped and not failed
Update for new version of ppc compilation chain
Verify that ebin folder of applications exists
|
|
* egil/ensure-erl_crash.dump/OTP-10422:
test: Relax timeouts for heart_SUITE
erts: Fix crash dump write to port hack
erts: Fix lock check assertion
doc: Document ERL_CRASH_DUMP_SECONDS behaviour
test: Add test for heart restart on crash
test: Add test for heart restart on crash
erts: Change ERL_CRASH_DUMP_SECONDS behaviour
test: Refactor away ?line macros in heart_SUITE
erts: Search for heart in ports that are alive
heart: Refactor heart debugging
erts, heart: Ensure erl_crash.dump is written
|
|
Timeouts were set too narrow and timedout on slow machines
|
|
More future proof with R16
|
|
|
|
|
|
|
|
Some of the tests which tested shell output assumed that
when starting a shell using `erl` a shell with newshell
was used. This is not true for systems built with
--disable-termcap, so the on some embedded systems those
tests failed.
|
|
|
|
New prefix for command line utils
Disable morecore hook as it does not work with new cross chain
|
|
* heart reboot behaviour
* erl_crash.dump file write behaviour
|
|
* node_start_soon_after_crash tests that heart restarts
beam upon a crash and only lets beam write its crash
dump for a certain amount of time
|
|
* node_start_immediately_after_crash tests that heart restarts
beam upon a crash and will not generate a crash dump
|
|
Not setting ERL_CRASH_DUMP_SECONDS will now terminate beam
immediately on a crash without writing a crash dump file.
Setting ERL_CRASH_DUMP_SECONDS to 0 will also terminate beam
immediately on a crash without writing a crash dump file, i.e. same as not
setting ERL_CRASH_DUMP_SECONDS environment variable.
Setting ERL_CRASH_DUMP_SECONDS to a negative value will let the beam wait
indefinitely on the crash dump file being written.
Setting ERL_CRASH_DUMP_SECONDS to a positive value will let the beam wait
that many seconds on the crash dump file being written.
A positive value will set both an alarm in beam AND a heart timeout for restart
if heart is running.
This is due to the change of 'heart' behavior when 'heart' is
listening for a crash.
|
|
|
|
|
|
|
|
When a crash dump is about to be written and we have
heartbeat enabled on a system. We need time to write it
before heart explicitly kills the beam.
|
|
* egil/fix-boot_combo-test:
test: Fix smoke_test_SUITE
|
|
* lukas/erts/whitespace_nsis_fix/OTP-10481:
Fix bug when making nsis target
|
|
* Skip boot_combo tests where cannot start slave nodes
(The binary will not exist)
|
|
* lukas/erts/bucket_mask_fix/OTP-10374:
Add comment about eproviderfailedinit error
Increase sbct for win64 as block alignment is 16
|
|
|
|
|
|
|
|
|
|
|
|
Both prepare_request/prepare_retransmit and handle_request can
return {eval_packet, RC, PostF} where PostF will be evaluated on any
encoded packet before transmission.
|
|
So that the function is usable when we're already in the service
process. For example, in peer_up/peer_down callbacks.
|