Skip to main content

Blog Archive for felipegaucho during September 2009

Poison messages are basically delivery deadlocks caused by a continuous redelivery of a message to a JMS Queue or Topic. That usually happens due to a code bug or configuration problems in the project. How to reproduce poison messages The easiest way of reproducing the poison messages issue is to create a Message Driven Bean and then to throw an exception in its onMessage method, like the example...
Rule of thumb: Avoid to use {variables} as the first path of a Jersey's @Path I am working on the Arena PUJ Project, a RESTful web-service to support PUJ competitions. We are in the early stages of the project but we already got some resources published on the web. Let me show you a few URL samples: An insecure GET method to read all competitions promoted by a JUG: GET /{competition_id}/...
I have just two arguments to avoid using long as type of the primary keys of JPA Entities: Integers IDs allow tables with ~2 billion records. Yes, you read well: max(Integer) = 2,147,483,647 the JPA pagination methods only accepts Integers Query setFirstResult(int startPosition) an  Query setMaxResults(int maxResult) Summary:only adopt data types long for your tables...
I am working out a new pet project, an online system to support PUJ Competitions. It is still a work under progress and I plan to start to blog some technical results here, but until that glorious free time I would give you a glimpse about what is keeping my blog so quiet :) So, PUJ is an academic competition where undergraduate student submit their homeworks for the evaluation...