search

FraunhoferIOSB / FAAAST-Service

FA³ST - Fraunhofer Advanced Asset Administration Shell Tools (for Digital Twins)
Other
56 stars 11 forks source link

Fa³st Service does not start with OPC UA Endpoint when several ConceptDescriptions #800

Closed wildias12 closed 3 months ago

wildias12 commented 3 months ago

Description: The Fa³st Service fails to start correctly when there are a large number of ConceptDescriptions in the OPC UA endpoint. This issue was identified during testing, where the service could not handle a high volume of ConceptDescriptions.

Steps to Reproduce:

  1. Configure Fa³st Service with an AASX model containing multiple ConceptDescriptions.

  2. In my case, the applied model has 216 ConceptDescriptions.

Expected Behavior: The service should start correctly and handle a large number of ConceptDescriptions without errors.

Actual Behavior: The service fails to start, presenting errors that prevent it from functioning properly when there are many ConceptDescriptions.

Environment:

Relevant Logs: Below are the logs showing the errors encountered when starting the service with a large number of ConceptDescriptions:

Relevant Logs: image Log description: Service running with the intended model.

image Log description: Final command lines before the service fails to generate the OPC UA server.

mjacoby commented 3 months ago

Could you please provide an example model file to reproduce this issue? If this is not possible, please run FA³ST with the additional argument --loglevel-faaast TRACE and post the output.

wildias12 commented 3 months ago

Hi Jacoby, I hope this message finds you well. I am writing this report upon the request of your colleague, Tino Bischoff. As a partner of AIMEN and a collaborator on the European project Circular Tw4In, I have previously communicated the limitations encountered. Tino suggested that I report these issues to you. Attached, you will find the model used for testing, which is the model of a robot. Regarding the implementation of the argument "--loglevel-faaast TRACE," there was no noticeable difference from the print attached to the report. Should you require any further information from my side, please feel free to contact me. Thank you very much. Best regards,

De: Michael Jacoby @.> Enviado: 12 de junho de 2024 07:20 Para: FraunhoferIOSB/FAAAST-Service @.> Cc: wildias12 @.>; Author @.> Assunto: Re: [FraunhoferIOSB/FAAAST-Service] Fa³st Service does not start with OPC UA Endpoint when several ConceptDescriptions (Issue #800)

Could you please provide an example model file to reproduce this issue? If this is not possible, please run FA³ST with the additional argument --loglevel-faaast TRACE and post the output.

— Reply to this email directly, view it on GitHubhttps://github.com/FraunhoferIOSB/FAAAST-Service/issues/800#issuecomment-2162192390, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJDHASRBDPNPRUDHM6W7SB3ZG7SBLAVCNFSM6AAAAABJENQJR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGE4TEMZZGA. You are receiving this because you authored the thread.

mjacoby commented 3 months ago

I seems that you responded to the automated Github email and attached the example data there, i.e. it is not available online and I cannot access it. Please either upload the file via Browser on the Github issue or if you prefer (or it may contain sensitive information you do not want to be made public) send it via email to faaast@iosb.fraunhofer.de

mjacoby commented 3 months ago

@wildias12 Thank you for providing an example model via email. This issue was indeed caused by a bug in FA³ST but it is fixed on the main branch and in the latest snapshot release.

Please verify that it is now working as expected by either

wildias12 commented 3 months ago

Hi @mjacoby,

Thank you for the explanation. I tested with the recommended version, and it indeed allows reading the provided model now. I will continue to use the FA³ST service and will reach out again if I have any further questions.

Thanks for the quick resolution!