[akka-user] Binding Actors to CPU or to a core

[Mahesh Govind]

Dear Experts,

Is it possible to bind a group of akka actors to a specific core or to a 
processor  .

I have a situation where the machine is having 2 processors with 6 
cores/processor , but I dont have any clue about the distribution of 
 actors .

Is there a java API equivalent of "taskset"  or similiar functionality ?

Regards
mahesh

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka based java web application deployment in Websphere 7

[Konrad Malawski]

Hi there,
As Akka is "just" a library, you should be able to run it in a websphere
container.

You should use the latest Akka 2.3.x, since 2.4.x requires JDK8.
If you're unable to upgrade the JDK, I think IBM may not yet have JDK8
right?
Then 2.3 series is your best bet.

If you intend to run this in production, then I would recommend a Lightbend
subscription,
Because 2.3 is not really getting any development unless critical issues.
Being a subscriber
You can count on some more help, from us, even though technically 2.3 has
been end-of-life already for a while if I remember correctly.

I'd like to just mention that this isn't really the optimal way, but I
understand it may be a situation of
"Either in websphere, or not at all". If able to, Akka deployed standalone
as runnable jar is the preferred way, as it's the most lightweight.


Hope this helps, happy hakking.

-- 
Konrad Malawski
Akka @ Lightbend


From: yayati.t...@gmail.com  
Reply: akka-user@googlegroups.com 

Date: 23 August 2016 at 03:17:35
To: Akka User List  
Subject:  [akka-user] Akka based java web application deployment in
Websphere 7

I have web application with following technologies, trying to figure out
> best version compatible with Websphere 7.0
>
> - Java 1.6
> - Akka 2.3.15
> - camel-netty4-http 2.17.2
>
> Has anyone deployed akka application in Websphere 7?
>
> Thanks, Yayati
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Akka based java web application deployment in Websphere 7

[yayati . tech]

I have web application with following technologies, trying to figure out 
best version compatible with Websphere 7.0

- Java 1.6
- Akka 2.3.15
- camel-netty4-http 2.17.2

Has anyone deployed akka application in Websphere 7?

Thanks, Yayati

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Pattern for ensuring fault tolerant PARENT actors

[Chandan Benjaram]

 

Hello all,

I am wondering how to ensure fault tolerant way to distribute work across 
remote actors!? also looking at online resource for akka implementation 
patterns. Thought I would ask source for the opinion here. 


*Here is an example:*

I want to calculate first 1K prime numbers. Assume I have 10 actors of same 
type (they take a number and return nth prime that has been passed to it. 
example 1st actor might get a req like give me 1-10 primes, 2nd might get 
11-20 primes, likewise 901-1K primes for 10th actor, *order doesn't matter*
).

this is fairly simple to solve with a single owner(parent) and 10(child) 
actors. 


However,  I would like to have the *parent* to be *fault tolerant™*. For 
example, the VM where the parent is running might dye at anytime(assume 
faulty hardware). In that case, I want to have a another VM(assume this is 
VM2) to *restart whole processing from the start*.


Any best practices around this need?

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Issue with default query parameters and custom unmarshalling

[andrew . meyer]

Good thought, though I checked and do not. Are you able to reproduce this 
behavior?

On Monday, August 22, 2016 at 11:26:02 AM UTC-5, 
andrew...@bottlerocketstudios.com wrote:
>
> I recently came across an issue when I had used `parameters(…)` with 
> custom unmarshalling and a default value. I found that 
> `parameters(“foo”.as[MyType] ?)` compiles, but the following did not: 
> `parameters(“foo”.as[MyType] ? MyType.default)`. The compiler says that 
> there are "too many parameters for method 'parameters(...' The only thing 
> that seemed to compile was placing a string on the right side of the `?` 
> instead of a concrete type. This took me about two hours to figure out 
> because it was not apparent in the documentation: 
> http://doc.akka.io/docs/akka/2.4/scala/http/routing-dsl/directives/parameter-directives/parameters.html
>
>  
>
> Note, knowing that `parameters(“foo” ? 0)` works for an Int, I tried the 
> following to no avail, thinking that the type could be inferred correctly 
> and unmarshalled: `parameters(“foo” ? MyType.default)`.
>
>  
>
> I would suggest an update to the referenced documentation to give an 
> example for using a default value while using a custom unmarshaller. Any 
> enlightenment on the reason for this, or if I am missing something, would 
> be super helpful! Thanks!
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Issue with default query parameters and custom unmarshalling

[Konrad Malawski]

Hmm... it could be.
Quick question – do you perhaps have the ask pattern imported in this file?

It could cause ambiguity with the ? from ask I just thought.

-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 22 August 2016 at 18:26:01, andrew.me...@bottlerocketstudios.com (
andrew.me...@bottlerocketstudios.com) wrote:

I recently came across an issue when I had used `parameters(…)` with custom
unmarshalling and a default value. I found that
`parameters(“foo”.as[MyType] ?)` compiles, but the following did not:
`parameters(“foo”.as[MyType] ? MyType.default)`. The compiler says that
there are "too many parameters for method 'parameters(...' The only thing
that seemed to compile was placing a string on the right side of the `?`
instead of a concrete type. This took me about two hours to figure out
because it was not apparent in the documentation:
http://doc.akka.io/docs/akka/2.4/scala/http/routing-dsl/directives/parameter-directives/parameters.html



Note, knowing that `parameters(“foo” ? 0)` works for an Int, I tried the
following to no avail, thinking that the type could be inferred correctly
and unmarshalled: `parameters(“foo” ? MyType.default)`.



I would suggest an update to the referenced documentation to give an
example for using a default value while using a custom unmarshaller. Any
enlightenment on the reason for this, or if I am missing something, would
be super helpful! Thanks!
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups
"Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Issue with default query parameters and custom unmarshalling

[andrew . meyer]

Also, I am using Scala 2.11.7 and Akka 2.4.8 (so it's not an issue with 
Scala 2.10).

On Monday, August 22, 2016 at 11:26:02 AM UTC-5, 
andrew...@bottlerocketstudios.com wrote:
>
> I recently came across an issue when I had used `parameters(…)` with 
> custom unmarshalling and a default value. I found that 
> `parameters(“foo”.as[MyType] ?)` compiles, but the following did not: 
> `parameters(“foo”.as[MyType] ? MyType.default)`. The compiler says that 
> there are "too many parameters for method 'parameters(...' The only thing 
> that seemed to compile was placing a string on the right side of the `?` 
> instead of a concrete type. This took me about two hours to figure out 
> because it was not apparent in the documentation: 
> http://doc.akka.io/docs/akka/2.4/scala/http/routing-dsl/directives/parameter-directives/parameters.html
>
>  
>
> Note, knowing that `parameters(“foo” ? 0)` works for an Int, I tried the 
> following to no avail, thinking that the type could be inferred correctly 
> and unmarshalled: `parameters(“foo” ? MyType.default)`.
>
>  
>
> I would suggest an update to the referenced documentation to give an 
> example for using a default value while using a custom unmarshaller. Any 
> enlightenment on the reason for this, or if I am missing something, would 
> be super helpful! Thanks!
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Issue with default query parameters and custom unmarshalling

[andrew . meyer]

Update, the following also compiles: `parameters("foo" ?[MyType] 
MyType.default)`. Could the original problem simply be a compiler bug?

On Monday, August 22, 2016 at 11:26:02 AM UTC-5, 
andrew...@bottlerocketstudios.com wrote:
>
> I recently came across an issue when I had used `parameters(…)` with 
> custom unmarshalling and a default value. I found that 
> `parameters(“foo”.as[MyType] ?)` compiles, but the following did not: 
> `parameters(“foo”.as[MyType] ? MyType.default)`. The compiler says that 
> there are "too many parameters for method 'parameters(...' The only thing 
> that seemed to compile was placing a string on the right side of the `?` 
> instead of a concrete type. This took me about two hours to figure out 
> because it was not apparent in the documentation: 
> http://doc.akka.io/docs/akka/2.4/scala/http/routing-dsl/directives/parameter-directives/parameters.html
>
>  
>
> Note, knowing that `parameters(“foo” ? 0)` works for an Int, I tried the 
> following to no avail, thinking that the type could be inferred correctly 
> and unmarshalled: `parameters(“foo” ? MyType.default)`.
>
>  
>
> I would suggest an update to the referenced documentation to give an 
> example for using a default value while using a custom unmarshaller. Any 
> enlightenment on the reason for this, or if I am missing something, would 
> be super helpful! Thanks!
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] How do we handel OversizedPayloadException in Akka

[Viktor Klang]

There are 2 problems here:
1) Sending arbitrarily large messages
2) Relying on the detection of message loss

I'd suggest storing the data and sending messages with data
identifiers/URLs, possibly using AtLeastOnceDelivery if that is desired.

-- 
Cheers,
√

On Aug 22, 2016 6:44 PM, "Akka Team"  wrote:

> Hi Anup,
>
> The one execption that is thrown is handled by the supervisor of that
> actor, which in turn restarts that actor. That means a reconnect in this
> case. We don't throw the OverSizedPayloadException because we don't want a
> reconnect in that case.
>
> There is no way to get this exception on your callstack no matter how you
> try (because it is on an unrelated thread of an unrelated non-parent
> actor). The operation "!" (or tell()) simply never throws. This is by
> design.
>
> -Endre
>
> On Mon, Aug 22, 2016 at 6:40 PM, Anup M  wrote:
>
>> But a few lines down the code, I see a bunch of throw clauses.   My point
>> is that if such an exception occurs, currently it is just logged, there is
>> no failure or error anywhere, just a message in the log.  Now that becomes
>> a hard to track issue
>>
>>
>> On Monday, August 22, 2016 at 10:00:12 PM UTC+5:30, Akka Team wrote:
>>
>>>
>>>
>>> Basically the exception is logged and then it is business as usual.  I am 
>>> wondering why the exception is not re-thrown.  This can cause some kind of 
>>> silent failures in production applications


>>> Because it is not on your call-stack but on another thread. There is
>>> nowhere to throw. This is multi-threaded software, simply throwing stuff
>>> around does not work. This is one of the primary reasons why supervision
>>> exists for actors.
>>>
>>> -Endre
>>>
>>>



 On Wednesday, August 17, 2016 at 3:23:21 PM UTC+5:30, √ wrote:
>
> No, that's not what I mean to say. I mean to say that relying on that
> specific exception and doing stuff in response to it is out of reach since
> it is raised by the remoting subsystem outside of your call stack.
>
> On Wed, Aug 17, 2016 at 11:42 AM, prakash chinnaswamy <
> prakash.chi...@gmail.com> wrote:
>
>> So you mean to say we cannot handle any run time exception?
>>
>> On Wed, Aug 17, 2016 at 12:43 PM, Viktor Klang 
>> wrote:
>>
>>> Then you need to prevalidate the message. Don't rely on
>>> serialization size since that is a function of the serializer used.
>>>
>>> --
>>> Cheers,
>>> √
>>>
>>> On Aug 17, 2016 7:53 AM, "prakash chinnaswamy" <
>>> prakash.chi...@gmail.com> wrote:
>>>
 Viktor. Tuning is not a possible solution in our case . we need to
 inform the clint that the size is large and try with pagination. So we 
 need
 to handel this exception.


 On Tuesday 16 August 2016, Viktor Klang 
 wrote:

> Prakash,
>
> I think a possible solution is two-fold: start using a more
> efficient means of serialization (which reduces payload sizes), and 
> don't
> rely on exception throwing to track lost messages (Akka is 
> at-most-once
> delivery).
>
> On Tue, Aug 16, 2016 at 1:40 PM, prakash chinnaswamy <
> prakash.chinnaswamy...@gmail.com> wrote:
>
>> Viktor
>>
>> Could on get in what contest you are asking. Just add more
>> information we use Scala and it is a rest application where this
>> application will talk to a play server (having a remote actor). When 
>> trying
>> to send a large record we get this error. We would like to handle 
>> this
>> error and send a warning message to the client.
>>
>> On Tue, Aug 16, 2016 at 5:00 PM, Viktor Klang <
>> viktor.kl...@gmail.com> wrote:
>>
>>> Hi Prakash,
>>>
>>> Do you use Java Serialization?
>>>
>>> On Tue, Aug 16, 2016 at 12:21 PM, prakash chinnaswamy <
>>> prakash.chinnaswamy...@gmail.com> wrote:
>>>
 We have a distributed application on akka cluster. Actor “A”
 sends message of large size to a remote actor. And we get the 
 following
 Warning.


 2016-08-10 23:08:29,737 [EndpointWriter] ERROR - Transient
 association error (association remains live) 
 akka.remote.OversizedPayloadException:
 Discarding oversized payload sent to Actor[akka.tcp://
 abcd@127.0.0.1:51665/temp/$b]: max allowed size 128000 bytes,
 actual size of encoded class 
 common.data.model.configuration.UserList
 was 571444 bytes.


 We are aware that we can increase the value in the
 

Re: [akka-user] Akka configured seed nodes are leaving cluster and unreachable/reachable warning message is getting logged.

[Justin du coeur]

On Mon, Aug 22, 2016 at 11:09 AM, vipin mandloi 
wrote:

> Please let me know if i am missing any configuration.
>

It's not a matter of *missing* -- the problem is that this:


> *My application.conf is configured as below-*
>
>
>   cluster {
> auto-down-unreachable-after = 10s
>   }
>

Should never, ever, *ever* be used except for initial testing.  Auto-down
is intended just as a way to get you started, but it's very primitive and
dumb, and must *never* be used in production.  Auto-downing is always
likely to cause cluster disasters, and having such a short auto-down
timeout essentially guarantees it.

Basically, you're getting split-brain -- you need to replace auto-down with
a more-sophisticated downing strategy.  See this section of the
documentation

for more information.

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] How do we handel OversizedPayloadException in Akka

[Akka Team]

Hi Anup,

The one execption that is thrown is handled by the supervisor of that
actor, which in turn restarts that actor. That means a reconnect in this
case. We don't throw the OverSizedPayloadException because we don't want a
reconnect in that case.

There is no way to get this exception on your callstack no matter how you
try (because it is on an unrelated thread of an unrelated non-parent
actor). The operation "!" (or tell()) simply never throws. This is by
design.

-Endre

On Mon, Aug 22, 2016 at 6:40 PM, Anup M  wrote:

> But a few lines down the code, I see a bunch of throw clauses.   My point
> is that if such an exception occurs, currently it is just logged, there is
> no failure or error anywhere, just a message in the log.  Now that becomes
> a hard to track issue
>
>
> On Monday, August 22, 2016 at 10:00:12 PM UTC+5:30, Akka Team wrote:
>
>>
>>
>> Basically the exception is logged and then it is business as usual.  I am 
>> wondering why the exception is not re-thrown.  This can cause some kind of 
>> silent failures in production applications
>>>
>>>
>> Because it is not on your call-stack but on another thread. There is
>> nowhere to throw. This is multi-threaded software, simply throwing stuff
>> around does not work. This is one of the primary reasons why supervision
>> exists for actors.
>>
>> -Endre
>>
>>
>>>
>>>
>>>
>>> On Wednesday, August 17, 2016 at 3:23:21 PM UTC+5:30, √ wrote:

 No, that's not what I mean to say. I mean to say that relying on that
 specific exception and doing stuff in response to it is out of reach since
 it is raised by the remoting subsystem outside of your call stack.

 On Wed, Aug 17, 2016 at 11:42 AM, prakash chinnaswamy <
 prakash.chi...@gmail.com> wrote:

> So you mean to say we cannot handle any run time exception?
>
> On Wed, Aug 17, 2016 at 12:43 PM, Viktor Klang 
> wrote:
>
>> Then you need to prevalidate the message. Don't rely on serialization
>> size since that is a function of the serializer used.
>>
>> --
>> Cheers,
>> √
>>
>> On Aug 17, 2016 7:53 AM, "prakash chinnaswamy" <
>> prakash.chi...@gmail.com> wrote:
>>
>>> Viktor. Tuning is not a possible solution in our case . we need to
>>> inform the clint that the size is large and try with pagination. So we 
>>> need
>>> to handel this exception.
>>>
>>>
>>> On Tuesday 16 August 2016, Viktor Klang  wrote:
>>>
 Prakash,

 I think a possible solution is two-fold: start using a more
 efficient means of serialization (which reduces payload sizes), and 
 don't
 rely on exception throwing to track lost messages (Akka is at-most-once
 delivery).

 On Tue, Aug 16, 2016 at 1:40 PM, prakash chinnaswamy <
 prakash.chinnaswamy...@gmail.com> wrote:

> Viktor
>
> Could on get in what contest you are asking. Just add more
> information we use Scala and it is a rest application where this
> application will talk to a play server (having a remote actor). When 
> trying
> to send a large record we get this error. We would like to handle this
> error and send a warning message to the client.
>
> On Tue, Aug 16, 2016 at 5:00 PM, Viktor Klang <
> viktor.kl...@gmail.com> wrote:
>
>> Hi Prakash,
>>
>> Do you use Java Serialization?
>>
>> On Tue, Aug 16, 2016 at 12:21 PM, prakash chinnaswamy <
>> prakash.chinnaswamy...@gmail.com> wrote:
>>
>>> We have a distributed application on akka cluster. Actor “A”
>>> sends message of large size to a remote actor. And we get the 
>>> following
>>> Warning.
>>>
>>>
>>> 2016-08-10 23:08:29,737 [EndpointWriter] ERROR - Transient
>>> association error (association remains live) 
>>> akka.remote.OversizedPayloadException:
>>> Discarding oversized payload sent to Actor[akka.tcp://
>>> abcd@127.0.0.1:51665/temp/$b]: max allowed size 128000 bytes,
>>> actual size of encoded class 
>>> common.data.model.configuration.UserList
>>> was 571444 bytes.
>>>
>>>
>>> We are aware that we can increase the value in the configuration(
>>> http://doc.akka.io/docs/akka/2.2.3/scala/remot
>>> ing.html#Remote_Configuration).
>>>
>>>
>>> But we wanted to handel this OversizedPayloadException and send
>>> the message to the client.
>>>
>>>
>>> Regards,
>>>
>>> Prakash
>>>
>>> --
>>> >> Read the docs: http://akka.io/docs/
>>> >> Check the FAQ: http://doc.akka.io/docs/akka/c
>>> urrent/additional/faq.html
>>> 

Re: [akka-user] How do we handel OversizedPayloadException in Akka

[Anup M]

But a few lines down the code, I see a bunch of throw clauses.   My point 
is that if such an exception occurs, currently it is just logged, there is 
no failure or error anywhere, just a message in the log.  Now that becomes 
a hard to track issue

On Monday, August 22, 2016 at 10:00:12 PM UTC+5:30, Akka Team wrote:
>
>
>
> Basically the exception is logged and then it is business as usual.  I am 
> wondering why the exception is not re-thrown.  This can cause some kind of 
> silent failures in production applications
>>
>>
> Because it is not on your call-stack but on another thread. There is 
> nowhere to throw. This is multi-threaded software, simply throwing stuff 
> around does not work. This is one of the primary reasons why supervision 
> exists for actors.
>
> -Endre
>  
>
>>
>>
>>
>> On Wednesday, August 17, 2016 at 3:23:21 PM UTC+5:30, √ wrote:
>>>
>>> No, that's not what I mean to say. I mean to say that relying on that 
>>> specific exception and doing stuff in response to it is out of reach since 
>>> it is raised by the remoting subsystem outside of your call stack.
>>>
>>> On Wed, Aug 17, 2016 at 11:42 AM, prakash chinnaswamy <
>>> prakash.chi...@gmail.com> wrote:
>>>
 So you mean to say we cannot handle any run time exception?

 On Wed, Aug 17, 2016 at 12:43 PM, Viktor Klang  
 wrote:

> Then you need to prevalidate the message. Don't rely on serialization 
> size since that is a function of the serializer used.
>
> -- 
> Cheers,
> √
>
> On Aug 17, 2016 7:53 AM, "prakash chinnaswamy" <
> prakash.chi...@gmail.com> wrote:
>
>> Viktor. Tuning is not a possible solution in our case . we need to 
>> inform the clint that the size is large and try with pagination. So we 
>> need 
>> to handel this exception.
>>
>>
>> On Tuesday 16 August 2016, Viktor Klang  wrote:
>>
>>> Prakash,
>>>
>>> I think a possible solution is two-fold: start using a more 
>>> efficient means of serialization (which reduces payload sizes), and 
>>> don't 
>>> rely on exception throwing to track lost messages (Akka is at-most-once 
>>> delivery).
>>>
>>> On Tue, Aug 16, 2016 at 1:40 PM, prakash chinnaswamy <
>>> prakash.chinnaswamy...@gmail.com> wrote:
>>>
 Viktor 

 Could on get in what contest you are asking. Just add more 
 information we use Scala and it is a rest application where this 
 application will talk to a play server (having a remote actor). When 
 trying 
 to send a large record we get this error. We would like to handle this 
 error and send a warning message to the client.

 On Tue, Aug 16, 2016 at 5:00 PM, Viktor Klang <
 viktor.kl...@gmail.com> wrote:

> Hi Prakash,
>
> Do you use Java Serialization?
>
> On Tue, Aug 16, 2016 at 12:21 PM, prakash chinnaswamy <
> prakash.chinnaswamy...@gmail.com> wrote:
>
>> We have a distributed application on akka cluster. Actor “A” 
>> sends message of large size to a remote actor. And we get the 
>> following 
>> Warning.
>>
>>
>> 2016-08-10 23:08:29,737 [EndpointWriter] ERROR - Transient 
>> association error (association remains live) 
>> akka.remote.OversizedPayloadException: Discarding oversized payload 
>> sent to 
>> Actor[akka.tcp://abcd@127.0.0.1:51665/temp/$b]: max allowed size 
>> 128000 bytes, actual size of encoded class 
>> common.data.model.configuration.UserList was 571444 bytes.
>>
>>
>> We are aware that we can increase the value in the configuration(
>> http://doc.akka.io/docs/akka/2.2.3/scala/remoting.html#Remote_Configuration
>> ). 
>>
>>
>> But we wanted to handel this OversizedPayloadException and send 
>> the message to the client. 
>>
>>
>> Regards,
>>
>> Prakash
>>
>> -- 
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: 
>> https://groups.google.com/group/akka-user
>> --- 
>> You received this message because you are subscribed to the 
>> Google Groups "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to akka-user+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> 

Re: [akka-user] How do we handel OversizedPayloadException in Akka

[Akka Team]

Basically the exception is logged and then it is business as usual.  I
am wondering why the exception is not re-thrown.  This can cause some
kind of silent failures in production applications
>
>
Because it is not on your call-stack but on another thread. There is
nowhere to throw. This is multi-threaded software, simply throwing stuff
around does not work. This is one of the primary reasons why supervision
exists for actors.

-Endre


>
>
>
> On Wednesday, August 17, 2016 at 3:23:21 PM UTC+5:30, √ wrote:
>>
>> No, that's not what I mean to say. I mean to say that relying on that
>> specific exception and doing stuff in response to it is out of reach since
>> it is raised by the remoting subsystem outside of your call stack.
>>
>> On Wed, Aug 17, 2016 at 11:42 AM, prakash chinnaswamy <
>> prakash.chi...@gmail.com> wrote:
>>
>>> So you mean to say we cannot handle any run time exception?
>>>
>>> On Wed, Aug 17, 2016 at 12:43 PM, Viktor Klang 
>>> wrote:
>>>
 Then you need to prevalidate the message. Don't rely on serialization
 size since that is a function of the serializer used.

 --
 Cheers,
 √

 On Aug 17, 2016 7:53 AM, "prakash chinnaswamy" <
 prakash.chi...@gmail.com> wrote:

> Viktor. Tuning is not a possible solution in our case . we need to
> inform the clint that the size is large and try with pagination. So we 
> need
> to handel this exception.
>
>
> On Tuesday 16 August 2016, Viktor Klang  wrote:
>
>> Prakash,
>>
>> I think a possible solution is two-fold: start using a more efficient
>> means of serialization (which reduces payload sizes), and don't rely on
>> exception throwing to track lost messages (Akka is at-most-once 
>> delivery).
>>
>> On Tue, Aug 16, 2016 at 1:40 PM, prakash chinnaswamy <
>> prakash.chinnaswamy...@gmail.com> wrote:
>>
>>> Viktor
>>>
>>> Could on get in what contest you are asking. Just add more
>>> information we use Scala and it is a rest application where this
>>> application will talk to a play server (having a remote actor). When 
>>> trying
>>> to send a large record we get this error. We would like to handle this
>>> error and send a warning message to the client.
>>>
>>> On Tue, Aug 16, 2016 at 5:00 PM, Viktor Klang <
>>> viktor.kl...@gmail.com> wrote:
>>>
 Hi Prakash,

 Do you use Java Serialization?

 On Tue, Aug 16, 2016 at 12:21 PM, prakash chinnaswamy <
 prakash.chinnaswamy...@gmail.com> wrote:

> We have a distributed application on akka cluster. Actor “A” sends
> message of large size to a remote actor. And we get the following 
> Warning.
>
>
> 2016-08-10 23:08:29,737 [EndpointWriter] ERROR - Transient
> association error (association remains live) 
> akka.remote.OversizedPayloadException:
> Discarding oversized payload sent to Actor[akka.tcp://
> abcd@127.0.0.1:51665/temp/$b]: max allowed size 128000 bytes,
> actual size of encoded class common.data.model.configuration.UserList
> was 571444 bytes.
>
>
> We are aware that we can increase the value in the configuration(
> http://doc.akka.io/docs/akka/2.2.3/scala/remot
> ing.html#Remote_Configuration).
>
>
> But we wanted to handel this OversizedPayloadException and send
> the message to the client.
>
>
> Regards,
>
> Prakash
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/c
> urrent/additional/faq.html
> >> Search the archives: https://groups.google.com/grou
> p/akka-user
> ---
> You received this message because you are subscribed to the Google
> Groups "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



 --
 Cheers,
 √

 --
 >> Read the docs: http://akka.io/docs/
 >> Check the FAQ: http://doc.akka.io/docs/akka/c
 urrent/additional/faq.html
 >> Search the archives: https://groups.google.com/grou
 p/akka-user
 ---
 You received this message because you are subscribed to a topic in
 the Google Groups "Akka User List" group.
 To unsubscribe from this topic, visit
 

[akka-user] Issue with default query parameters and custom unmarshalling

[andrew . meyer]

 

I recently came across an issue when I had used `parameters(…)` with custom 
unmarshalling and a default value. I found that 
`parameters(“foo”.as[MyType] ?)` compiles, but the following did not: 
`parameters(“foo”.as[MyType] ? MyType.default)`. The compiler says that 
there are "too many parameters for method 'parameters(...' The only thing 
that seemed to compile was placing a string on the right side of the `?` 
instead of a concrete type. This took me about two hours to figure out 
because it was not apparent in the documentation: 
http://doc.akka.io/docs/akka/2.4/scala/http/routing-dsl/directives/parameter-directives/parameters.html

 

Note, knowing that `parameters(“foo” ? 0)` works for an Int, I tried the 
following to no avail, thinking that the type could be inferred correctly 
and unmarshalled: `parameters(“foo” ? MyType.default)`.

 

I would suggest an update to the referenced documentation to give an 
example for using a default value while using a custom unmarshaller. Any 
enlightenment on the reason for this, or if I am missing something, would 
be super helpful! Thanks!

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] How do we handel OversizedPayloadException in Akka

[Anup M]

In the akka source code (Endpoint.scala), this is how the code is


if (pduSize > transport.maximumPayloadBytes) {
  val reason = new OversizedPayloadException(s"Discarding oversized 
payload sent to ${s.recipient}: max allowed size 
${transport.maximumPayloadBytes} bytes, actual size of encoded 
${s.message.getClass} was ${pdu.size} bytes.")
  log.error(reason, "Transient association error (association remains 
live)")
  true


Basically the exception is logged and then it is business as usual.  I am 
wondering why the exception is not re-thrown.  This can cause some kind of 
silent failures in production applications




On Wednesday, August 17, 2016 at 3:23:21 PM UTC+5:30, √ wrote:
>
> No, that's not what I mean to say. I mean to say that relying on that 
> specific exception and doing stuff in response to it is out of reach since 
> it is raised by the remoting subsystem outside of your call stack.
>
> On Wed, Aug 17, 2016 at 11:42 AM, prakash chinnaswamy <
> prakash.chi...@gmail.com > wrote:
>
>> So you mean to say we cannot handle any run time exception?
>>
>> On Wed, Aug 17, 2016 at 12:43 PM, Viktor Klang > > wrote:
>>
>>> Then you need to prevalidate the message. Don't rely on serialization 
>>> size since that is a function of the serializer used.
>>>
>>> -- 
>>> Cheers,
>>> √
>>>
>>> On Aug 17, 2016 7:53 AM, "prakash chinnaswamy" >> > wrote:
>>>
 Viktor. Tuning is not a possible solution in our case . we need to 
 inform the clint that the size is large and try with pagination. So we 
 need 
 to handel this exception.


 On Tuesday 16 August 2016, Viktor Klang  wrote:

> Prakash,
>
> I think a possible solution is two-fold: start using a more efficient 
> means of serialization (which reduces payload sizes), and don't rely on 
> exception throwing to track lost messages (Akka is at-most-once delivery).
>
> On Tue, Aug 16, 2016 at 1:40 PM, prakash chinnaswamy <
> prakash.chinnaswamy...@gmail.com> wrote:
>
>> Viktor 
>>
>> Could on get in what contest you are asking. Just add more 
>> information we use Scala and it is a rest application where this 
>> application will talk to a play server (having a remote actor). When 
>> trying 
>> to send a large record we get this error. We would like to handle this 
>> error and send a warning message to the client.
>>
>> On Tue, Aug 16, 2016 at 5:00 PM, Viktor Klang > > wrote:
>>
>>> Hi Prakash,
>>>
>>> Do you use Java Serialization?
>>>
>>> On Tue, Aug 16, 2016 at 12:21 PM, prakash chinnaswamy <
>>> prakash.chinnaswamy...@gmail.com> wrote:
>>>
 We have a distributed application on akka cluster. Actor “A” sends 
 message of large size to a remote actor. And we get the following 
 Warning.


 2016-08-10 23:08:29,737 [EndpointWriter] ERROR - Transient 
 association error (association remains live) 
 akka.remote.OversizedPayloadException: Discarding oversized payload 
 sent to 
 Actor[akka.tcp://abcd@127.0.0.1:51665/temp/$b]: max allowed size 
 128000 bytes, actual size of encoded class 
 common.data.model.configuration.UserList was 571444 bytes.


 We are aware that we can increase the value in the configuration(
 http://doc.akka.io/docs/akka/2.2.3/scala/remoting.html#Remote_Configuration
 ). 


 But we wanted to handel this OversizedPayloadException and send the 
 message to the client. 


 Regards,

 Prakash

 -- 
 >> Read the docs: http://akka.io/docs/
 >> Check the FAQ: 
 http://doc.akka.io/docs/akka/current/additional/faq.html
 >> Search the archives: 
 https://groups.google.com/group/akka-user
 --- 
 You received this message because you are subscribed to the Google 
 Groups "Akka User List" group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to akka-user+unsubscr...@googlegroups.com.
 To post to this group, send email to akka-user@googlegroups.com.
 Visit this group at https://groups.google.com/group/akka-user.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Cheers,
>>> √
>>>
>>> -- 
>>> >> Read the docs: http://akka.io/docs/
>>> >> Check the FAQ: 
>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>> >> Search the archives: 
>>> https://groups.google.com/group/akka-user
>>> --- 
>>> You received this message because you are subscribed to a topic in 
>>> the 

[akka-user] Akka configured seed nodes are leaving cluster and unreachable/reachable warning message is getting logged.

[vipin mandloi]

Hello All,

I am setting akka cluster *(using akka library version 2.3.9* ) with one 
master actor and multiple worker actor. Master Actor is configured with 
pool cluster aware router.

I am deploying application with forming 4 cluster nodes. *Initially all the 
nodes are joining to cluster properly but after few minutes nodes are 
leaving to cluster and forming their own cluster. *

Getting below *warn *message when i add another node in the cluster.


*[WARN*] [08/22/2016 04:52:42.145] 
[ClusterSystem-akka.remote.default-remote-dispatcher-8] 
[akka.tcp://ClusterSystem@host:port/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%host%port-4]
 
Association with remote system [akka.tcp://ClusterSystem@host:port] has 
failed, address is now gated for [5000] ms. Reason is: [Failed to write 
message to the transport].


And *after few minutes of joining, * frequent unreachable reachable 
*warning *message is getting logged.


*[WARN] *[08/22/2016 05:42:13.586] 
[ClusterSystem-akka.actor.default-dispatcher-8] 
[akka.tcp://ClusterSystem@host:port/system/cluster/core/daemon] Cluster 
Node [akka.tcp://ClusterSystem@host:port] - Marking node(s) as UNREACHABLE 
[Member(address = akka.tcp://ClusterSystem@xldcarcsi01:port, status = Up)]
[INFO] [08/22/2016 05:42:14.586] 
[ClusterSystem-akka.actor.default-dispatcher-6] 
[Cluster(akka://ClusterSystem)] Cluster Node 
[akka.tcp://ClusterSystem@host:port] - Marking node(s) as REACHABLE 
[Member(address = akka.tcp://ClusterSystem@host:port, status = Up), 
Member(address = akka.tcp://ClusterSystem@xldcarcsi01:port, status = Up)]
*[WARN]* [08/22/2016 05:42:14.592] 
[ClusterSystem-akka.remote.default-remote-dispatcher-10] 
[akka.tcp://ClusterSystem@host:port/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40host%3Aport-0]
 
Association with remote system [akka.tcp://ClusterSystem@host:port] has 
failed, address is now gated for [5000] ms. Reason is: [Failed to write 
message to the transport].
*[WARN]* [08/22/2016 05:42:14.593] 
[ClusterSystem-akka.remote.default-remote-dispatcher-10] 
[akka.tcp://ClusterSystem@host:port/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40xldcarcsi01%3Aport-1]
 
Association with remote system [akka.tcp://ClusterSystem@xldcarcsi01:port] 
has failed, address is now gated for [5000] ms. Reason is: [Failed to write 
message to the transport].
[WARN] [08/22/2016 05:42:18.584] 
[ClusterSystem-akka.actor.default-dispatcher-2] 
[akka.tcp://ClusterSystem@host:port/system/cluster/core/daemon] Cluster 
Node [akka.tcp://ClusterSystem@host:port] - Marking node(s) as UNREACHABLE 
[Member(address = akka.tcp://ClusterSystem@host:port, status = Up)]




Please let me know if i am missing any configuration.


*My application.conf is configured as below-*

my-dispatcher {
type = PinnedDispatcher 
executor = "thread-pool-executor"
thread-pool-executor {
core-pool-size-min = 1
core-pool-size-factor = 2.0
core-pool-size-max = 2
}
throughput = 3
mailbox-capacity = 3
}

akka {
 
 bounded-mailbox {
 mailbox-type = "akka.dispatch.BoundedMailbox"
 mailbox-capacity = 2
 mailbox-push-timeout-time = 100ms
  }

  actor {
provider = "akka.cluster.ClusterActorRefProvider"
serializers {
akka-cluster = "akka.cluster.protobuf.ClusterMessageSerializer"
}
serialization-bindings {
"akka.cluster.ClusterMessage" = akka-cluster
"org.springframework.context.support.ClassPathXmlApplicationContext" = 
akka-cluster
} 
  }
  remote {
log-remote-lifecycle-events = off   
netty.tcp {
  hostname = ${akka.node.hostname}
  port = ${akka.node.port}
}
  }
 
  cluster {
seed-nodes = [${akka.seed.nodes}]
 
  roles = ["master"]
  
auto-down-unreachable-after = 10s
  }  
}
akka.actor.deployment {
  /singleton/MyConsumerActor/workerRouter {
router = consistent-hashing-pool
nr-of-instances = 100
cluster {
  enabled = on
  max-nr-of-instances-per-node = 3
  allow-local-routees = on
  use-role = master
}
  }
}
*//tried with customizing transport-failure-detector*
akka.remote.transport-failure-detector {
heartbeat-interval = 1000s 
acceptable-heartbeat-pause = 6000s 
}



Thanks,
Vipin Mandloi

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Using Akka actors for processing files

[Justin du coeur]

Well, the most important part is that, given the scale, you want at least
one Actor *per file*.  Likely more than one -- depending on the DB you are
using, you may well want a separate Actor for the DB operations, assigned
to a different Dispatcher.  (DB operations are often blocking, and it's
important that blocking operations be on an Actor that is using an
appropriate Dispatcher for that.)

You *could* implement each step as a separate Actor, if that makes sense
from a logic POV, but I don't see any obvious benefit to that.  It's much
more important to have separate Actors per-file, so that they can
parallelize.  (Unless you actually want that to be sequential, but it's
going to be hard to achieve scale that way.)

On Sun, Aug 21, 2016 at 9:09 AM, Akash Thomas 
wrote:

> Hi All,
>
> I am new to Akka and Actor model. I have the below use case - can you
> review and suggest how to split the tasks between actors?
>
> *Use case*
>
> *Step 1* : receive a file list from an external service
> *Step 2 : **for each file in the list *
> *  {*
>  a. download file through rest api
>  b. extract content from file
>  c. perform few operations on the content and store
> results in DB
>  d. store content itself to DB
>  e. store downloaded file to file system
>  f. update status in DB
> *}*
>
> This has to be done in scale. Roughly for a million documents a day.
>
> Do you think each step inside the loop can be implemented as a separate
> actor? Is that approach correct?
>
> Thanks
> Akash.
>
>
>
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Streams Graph Editor tool

[Sergey Sopin]

Thanks! I will try.

понедельник, 22 августа 2016 г., 14:32:53 UTC+3 пользователь Konrad 
Malawski написал:
>
> Sorry, I haven't been using Windows since years hm.
>
> I know Endre used raw Inkscape to do some of our drawings for our docs.
>
>
> -- 
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 22 August 2016 at 13:14:17, Sergey Sopin (sopi...@gmail.com 
> ) wrote:
>
> Hi again, 
>
> Omnigraffle is very good program, but I use Windows :(
> Can you recommend something for it? 
>
> Thanks!
>
> Regards,
> Sergey
>
> воскресенье, 17 июля 2016 г., 16:05:59 UTC+3 пользователь Konrad Malawski 
> написал: 
>>
>> You may enjoy these Omnigraffle stencils: 
>> https://www.graffletopia.com/stencils/1493 by Derek Wyatt
>>
>> -- 
>> Konrad `ktoso` Malawski
>> Akka  @ Lightbend 
>>
>> On 16 July 2016 at 17:44:18, Sergey Sopin (sopi...@gmail.com) wrote:
>>
>> Hi, 
>>
>> Is there any tool which allows to draw graphs as they were shown in akka 
>> docs? I mean that allows using the same blocks and elements.
>>
>> Thanks a lot!
>>
>> Best regards,
>> Sergey
>> --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "Akka User List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to akka-user+...@googlegroups.com.
>> To post to this group, send email to akka...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: 
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups 
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to akka-user+...@googlegroups.com .
> To post to this group, send email to akka...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Streams Graph Editor tool

[Konrad Malawski]

Sorry, I haven't been using Windows since years hm.

I know Endre used raw Inkscape to do some of our drawings for our docs.


-- 
Konrad `ktoso` Malawski
Akka  @ Lightbend 

On 22 August 2016 at 13:14:17, Sergey Sopin (sopin1...@gmail.com) wrote:

Hi again,

Omnigraffle is very good program, but I use Windows :(
Can you recommend something for it?

Thanks!

Regards,
Sergey

воскресенье, 17 июля 2016 г., 16:05:59 UTC+3 пользователь Konrad Malawski
написал:
>
> You may enjoy these Omnigraffle stencils: https://www.
> graffletopia.com/stencils/1493 by Derek Wyatt
>
> --
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 16 July 2016 at 17:44:18, Sergey Sopin (sopi...@gmail.com )
> wrote:
>
> Hi,
>
> Is there any tool which allows to draw graphs as they were shown in akka
> docs? I mean that allows using the same blocks and elements.
>
> Thanks a lot!
>
> Best regards,
> Sergey
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+...@googlegroups.com .
> To post to this group, send email to akka...@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
> --
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups
"Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Streams Graph Editor tool

[Sergey Sopin]

Hi again,

Omnigraffle is very good program, but I use Windows :(
Can you recommend something for it? 

Thanks!

Regards,
Sergey

воскресенье, 17 июля 2016 г., 16:05:59 UTC+3 пользователь Konrad Malawski 
написал:
>
> You may enjoy these Omnigraffle stencils: 
> https://www.graffletopia.com/stencils/1493 by Derek Wyatt
>
> -- 
> Konrad `ktoso` Malawski
> Akka  @ Lightbend 
>
> On 16 July 2016 at 17:44:18, Sergey Sopin (sopi...@gmail.com ) 
> wrote:
>
> Hi, 
>
> Is there any tool which allows to draw graphs as they were shown in akka 
> docs? I mean that allows using the same blocks and elements.
>
> Thanks a lot!
>
> Best regards,
> Sergey
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: 
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups 
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to akka-user+...@googlegroups.com .
> To post to this group, send email to akka...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.