Having problems implementing pac4j-lagom (java) OAuth in my project:
Configure your OAuth 2 library with your client_id, client_secret, and redirect_uri. Tell it to use https://launchpad.37signals.com/authorization/new to request authorization and https://launchpad.37signals.com/authorization/token to get access tokens
Hi Team; I've hunted the internet, this channel, and have yet to find a clue, so here goes:
Kafka Server closed unexpectedly.
...has become the bane of my existence. I am 100% sure it's not a problem in lagom 1.6.4, but in my use of it. It's possible it's this machine (maybe it's been crippled somehow by IT). However I need to get to the bottom of it.
runAllabove that "closed" message.
<your-project-root>/target/lagom-dynamic-projects/lagom-internal-meta-project-kafkafolder in case it was zookeeper.
Might I ask advice on tracking this down?
<x>-impl/src/main/resources/application.conffiles. However, when I start the service with
sbt runAll, I still see akka.persistence.cassandra.query.EventsByTagStage logs saying "starting with EC delay 5000ms", and the timing doesn't seem to have changed at all for events being picked up in my read-side processor. Any suggestions as to what I might be doing wrong?
I'm using shopping-cart example from lagom-samples. While running on single node cluster I observe that, on making multiple concurrent requests akka.actor.default-dispatcher count (observed from visualVM) keeps increasing (proportional to concurrent requests) and they remain in PARK state even after request is served.
is this an expected behaviour? How do we control this and reuse the same actors or kill the actors after request has been served.
bytea, can this be because my key's are UUID and using the native postgres uuid type?
@Id @Type(type="pg-uuid") private UUID eventId;
prices-service-6fd9b54cb4-8flx7 prices-service 14:43:09.499 [r-11] [error] c.l.l.i.b.k.KafkaSubscriberActor [akkaAddress=akka://email@example.com:25520, sourceThread=application-akka.actor.default-dispatcher-5, akkaSource=akka://firstname.lastname@example.org:25520/user/KafkaBackoffConsumer1-price-commands/KafkaConsumerActor1-price-commands, sourceActorSystem=application, akkaTimestamp=14:43:09.498UTC] - Topic subscription interrupted due to failure: [java.util.concurrent.CompletionException: java.lang.ClassCastException: class scala.collection.immutable.HashMap cannot be cast to class prices.api.Price (scala.collection.immutable.HashMap and prices.api.Price are in unnamed module of loader 'app')] `
Caused by: javax.naming.NameNotFoundException: DefaultDB not found-- it seems that I have to make a non-lazy reference to
persistentEntityRegistryto make this error go away, but the Lagom 1.6.x docs don't seem to indicate I need to use this anymore anywhere (previously I remember having to do
persistentEntityRegistry.register(entity)) -- is that still needed even though it's missing from the docs? https://www.lagomframework.com/documentation/1.6.x/scala/UsingAkkaPersistenceTyped.html -- note that I do see the
persistentEntityRegistrybeing included in the service impl class on that page, but since I never needed it in my service I didn't put it there.
first-time-bucketis set too far back. After looking through the logs and the offset-store tables, it seems that some parts always use this timestamp. I built a small service that has an entity with tagged events , a read side, and defines a topic. After adding some events and restarting the services, there is always at least one line in the logs like:
starting with EC delay 0ms: fromOffset [51e38000-b8fe-11eb-8080-808080808080 (2021-05-20 00:00:00:000)] toOffset [None](the time is my currently configured first-time-bucket). I am curious what part of lagom causes this, and why there is no correct offset is used. Can you explain this behaviour?
lazy val aService = (project in file("s")) .enablePlugins(LagomJava) .settings( resolvers += ..., maintainer += ..., libraryDependencies ++= Seq( "..." % "...-impl" % "..." ) )