Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: V3.7.0.0, V3.8.0.0, V3.9.0.0, V3.10.0.0, V3.12.0.0
-
Fix Version/s: V3.12.0.12, V3.12.2.0, V3.13.0.0
-
Component/s: None
-
Labels:None
-
Sprint:PI Sprint 2018 KW 17/18
-
Account:SPC Profinet Slave (SPCPROFINE)
Description
After executing the Profinet "faulty" netload tests several times (more than 5 times) the following erroneous behavior was observed:
The protocol stack is no longer able to establish a Profinet communication. It is still recheable via DCP and ARP but RPC based services are not responded at all.
The issue can not be reproduced if the amount of configured submodules does not lead to a fragmented RPC service.
Attachments
Issue Links
- blocks
-
PSTCP-285 Hanging application can lead to unresponsive TCP/IP stack
- Closed
-
PSPNS-2730 Update IP stack to V2.3.0.1
- Closed
-
PSPNS-2736 Update DCERPC to V4.2.0.3
- Closed
- is blocked by
-
PSDCERPC-77 Memory leak in handling for incomming RPC call
- Closed
- relates to
-
PSPNS-2726 update to Hilscher TCP Stack V2.4.0.6
- Closed