Skip to content

Instantly share code, notes, and snippets.

@AdamBien
Last active July 17, 2017 10:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AdamBien/974714ccaf26033697e9 to your computer and use it in GitHub Desktop.
Save AdamBien/974714ccaf26033697e9 to your computer and use it in GitHub Desktop.
20thAirhacksQ&A.md
@pejomstd
Copy link

pejomstd commented Nov 3, 2015

Hi,
I was playing around with JCashe and Hazelcast on Payara, works fine with Java SE classes, but not so nice with custom classes:
http://ironicprogrammer.blogspot.se/2015/10/playing-with-hazelcast-on-payara.html

My findings is using the internal HAzelcast gieves me classnotfoutex... due to Hazelcast not recognising my classes since it loads before.
This is a pain in the a** since it is then not possible to work with EntryProcessors, EntryListeners, Loares/Writers for either JCache or Hazelcasts distributed structures as IMap etc.

Do you have a better solution than to kick-start Hazelcast from the top to make it work in a Java EE environment?

@AlbozDroid
Copy link

Hi Adam,

We are building a Java EE web application which makes moderately to heavy use of DB resources.
A lot of the DB table is configuration stuff.
At the moment we are only able to have around 250 concurrent users in an 8 core 16 GB of RAM Server machine.
We have not done any JVM tuning, nor used batch processing with JPA, so far just plain JPA relationships with defaults.

My question is:
In your projects how many users do you support in a server with similar characteristics?
I know that this is difficult and changes from app to app but I would like to have some numbers on an average boring Java EE application.

How many concurrent users has it been able to support without/before any optimisation performed?

Thanks.

@nebrass
Copy link

nebrass commented Nov 3, 2015

Hello again 😆
What is the best api to implement SSE? REST+Ajax or Websockets ?

Thank you so much 😄

@bogeskov
Copy link

bogeskov commented Nov 9, 2015

Hello Adam

You've previously show neat tricks, like marshalling/unmarshalling json to pojo's.

Staying in the json realm :

Do you have an easy way to validate input/output (@XmlRootElements), when calling method annotated like this:

    @POST
    @Path("/")
    @Consumes(MediaType.APPLICATION_JSON)
    @Produces(MediaType.APPLICATION_JSON)
    public Out method(In in) {
...

Having looked at examples, I hope I've missed a trick - you can't have to jump through all those hoops.

It would be nice to know that when the method is invoked, all required fields are populated (doing null pointer checks, feels like you're doing it wrong).

See You

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment