Thanks @andreaTP ! Yes, we're using the scala-java8-compat module for all Java APIs already. So that work should be minimal. We may have to downgrade the collection conversions to 2.11 (which will leave the code showing deprecated APIs in 2.12). Also in some cases we may have to resort to anonymous inner classes instead of using a Java8 function directly. But I see these as rather minimal. I'd say try to change sbt to add 2.11 compilation first. Then see what breaks. Address issues one-by-one. Thanks!
New PR passes all build
Hi Can you please merge the PR paypal/squbs#709 and create a release ? I need it to use in my application
Thanks @akara
But the snapshot version is available only for scala 2.12 and not for scala 2.11.
The sbt build in travis is not publishing for all versions in crossScalaVersion, the command should be as below in travis config
sbt ++$TRAVIS_SCALA_VERSION clean publishSignedGave a PR, can you please merge it to release the snapshot again ? Sorry about multiple commits and PR, sbt cross compile and travis is completely new for me.
I think we are ready for release of squbs 0.12.0. There is one PR though with Java Time duration #706 still open. Do we want to release w/o this PR or should we wait to resolve the remaining comments on the PR?
@anilgursel If you agree, please approve the PR. I'll approve on my side and then merge. Will issue a subsequent PR by today.
Done!
Let me see whether I can do something around it.
Alright, I've converged the PR from @jiminhsieh with the Scala 2.11 changes and standardized the
Duration conversions according to what is in scala-java8-compat (later versions than we can use). If @jiminhsieh. This is paypal/squbs#714. @agursel, @sebady, @crankydillo please consider. I'd normally rather wait for @jiminhsieh to come back with fixes but given we're near a release, it is just a fast-track alternative.
And ignore this one.
And it does contain all your contributions.
Thanks!
@akara In my squbs project, have configured a HTTP service . which will accept requests and sends to an Actor and echo it back. A simple POC. When i startup the service, the cpu (2-core) went to 90% and then back to normal. When we send 10/15 parallel request to the service, it will again go back more than 90%. May i know the reason plz?
My config as below:
http {
server {
idle-timeout = 310s
request-timeout = 55s
}
client {
idle-timeout = 500s
}
host-connection-pool {
max-connections = 100
min-connections = 0
max-retries = 0
idle-timeout = infinite
pool-implementation = new
max-open-requests = 128
}
}
server {
idle-timeout = 310s
request-timeout = 55s
}
client {
idle-timeout = 500s
}
host-connection-pool {
max-connections = 100
min-connections = 0
max-retries = 0
idle-timeout = infinite
pool-implementation = new
max-open-requests = 128
}
}
I haven't override the default dispatcher & default blocking dispatcher
Can you check with @Harikiranvuyyuru real quick whether he has the process? If not I'll have to figure it out.
since @jiminhsieh may be busy
@akara As your guess, I am quite busy recently. 🙁 I don’t have much time to investigate the rest. Anyway, thanks for the cleaning up the rest at paypal/squbs#716. :)
yes, we have quite a few use cases that uses Kafka. We use Alpakka Kafka Connector https://doc.akka.io/docs/akka-stream-kafka/current/ along with Perpetual Stream https://squbs.readthedocs.io/en/latest/perpetualstream/
I am getting confuse between akka and scubs ..Do you have any archive which i can refer
squbs is built on Akka. What Perpetual Stream provides is a way to hook into squbs application startup/shutdown lifecycle. For instance, one may not prefer to start consuming from Kafka until rest of the application is up and ready.. or to gracefully shutdown the stream when the app is shutting down. PerpetualStream integrates with lifecycle events automatically and starts/shutsdown the stream based on those.