Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start a pipeline with a Notification data sink #3004

Closed
michaelreisvoid opened this issue Jul 8, 2024 · 4 comments
Closed

Cannot start a pipeline with a Notification data sink #3004

michaelreisvoid opened this issue Jul 8, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@michaelreisvoid
Copy link

Apache StreamPipes version

Other StreamPipes version (please specify below)

Affected StreamPipes components

Backend, Processing Elements, UI

What happened?

in version 0.95, when I create a pipeline with a Notification data sink, or an Email Notification data sink, I can't start the pipeline, an error is displayed.

How to reproduce?

Create a pipeline with a Notification data sink, and then try to start the pipeline.

Expected behavior

Pipeline is started and notifications are stored.

Additional technical information

This happens with 0.95
This does not happen with 0.93

The following stacktrace is logged:

extensions-all-jvm-1  | java.lang.NullPointerException: Cannot invoke "org.apache.streampipes.model.staticproperty.FreeTextStaticProperty.getValue()" because the return value of "org.apache.streampipes.sdk.extractor.AbstractParameterExtractor.getStaticPropertyByName(String, java.lang.Class)" is null
extensions-all-jvm-1  | 	at org.apache.streampipes.sdk.extractor.AbstractParameterExtractor.singleValueParameter(AbstractParameterExtractor.java:122)
extensions-all-jvm-1  | 	at org.apache.streampipes.wrapper.standalone.StreamPipesNotificationSink.onInvocation(StreamPipesNotificationSink.java:87)
extensions-all-jvm-1  | 	at org.apache.streampipes.sinks.internal.jvm.notification.InternalStreamPipesNotificationSink.onInvocation(InternalStreamPipesNotificationSink.java:57)
extensions-all-jvm-1  | 	at org.apache.streampipes.wrapper.standalone.StreamPipesDataSink.onPipelineStarted(StreamPipesDataSink.java:37)

Are you willing to submit a PR?

None

@michaelreisvoid michaelreisvoid added the bug Something isn't working label Jul 8, 2024
@tenthe
Copy link
Contributor

tenthe commented Jul 9, 2024

Hi @michaelreisvoid,

thanks for opening the issue.

I attempted to reproduce the problem on a new instance of StreamPipes version 0.95.0. I created a machine data simulator adapter and a Notifications sink, and the pipeline started and worked as expected.

Could you clarify your setup? Did you set up a new StreamPipes instance, or did you migrate from version 0.93.0 to 0.95.0? If you migrated, did you update all of the Docker services or only the backend?
Were there any error logs during the migration process?

@michaelreisvoid
Copy link
Author

Hi @tenthe ,
thanks for the followup

I am using the release directly, running locally with docker compose:
cd ~/apache-streampipes-0.95.0/installer/compose
docker compose up
so everything should be up to date. I just ran a docker system prune -a to be extra sure, and the error still occurs.

I was using the mqtt adaptor, but I just tried with the machine data simulator, and still run into the same issue.

I can create the pipeline, Enable live preview works, the exception just happens when trying to start the pipeline. A colleague of mine also has the same issue.
We just connect an adaptor to a Notification, and this happens every time.

@michaelreisvoid
Copy link
Author

michaelreisvoid commented Jul 9, 2024

@tenthe

Ok, I also pruned all of my volumes, repeated the steps, and now it works as expected.
Personally this now becomes a non-issue, but it seems there is some sort of a consistency problem when using the same volumes from one version to the next

@tenthe
Copy link
Contributor

tenthe commented Jul 10, 2024

@michaelreisvoid, ok. Thanks for the information, also if you have any further questions please feel free to ask.

If anyone else is facing this issue during the update from 0.93.0 to 0.95.0, please feel free to reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants