[JBoss JIRA] (FORGE-1273) REST NOT_FOUND should be NO_CONTENT
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1273?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1273:
------------------------------------------
Hum... the web is full of talks about this issue (eg. http://stackoverflow.com/questions/2195639/restful-resource-not-found-404...).
I've attached two screenshots of Bill Burke's book about JAX-RS (I have it in Kindle format so I couldn't copy/paste the code). When an entity is not found, or a query returns nothing, JPA returns null : it's not an exception, it's a normal case where no data is returned. A 404 is when the resource is not found (eg. you have a typo in your curl and the GET method is not invoked). A 204 is saying that the resource exists, you invoked it, everything is ok but it returned null (or no content)
> REST NOT_FOUND should be NO_CONTENT
> -----------------------------------
>
> Key: FORGE-1273
> URL: https://issues.jboss.org/browse/FORGE-1273
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.4.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
> Attachments: rest.tiff, rest2.tiff
>
>
> Hi,
> In the REST endpoint generated code we have the following methods that return a Status.NOT_FOUND status in case the entity is not found :
> {code}
> @DELETE
> @Path("/{id:[0-9][0-9]*}")
> public Response deleteById(@PathParam("id") Long id)
> {
> Book entity = em.find(Book.class, id);
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> em.remove(entity);
> return Response.noContent().build();
> }
> @GET
> @Path("/{id:[0-9][0-9]*}")
> @Produces("application/xml")
> public Response findById(@PathParam("id") Long id)
> {
> TypedQuery<Book> findByIdQuery = em.createQuery("SELECT DISTINCT b FROM Book b WHERE b.id = :entityId ORDER BY b.id", Book.class);
> findByIdQuery.setParameter("entityId", id);
> Book entity;
> try
> {
> entity = findByIdQuery.getSingleResult();
> }
> catch (NoResultException nre)
> {
> entity = null;
> }
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> return Response.ok(entity).build();
> }
> {code}
> In both cases it should be a Status.NO_CONTENT. The resource exists (otherwise it would have been impossible to invoke it) it just happens that it returns an empty body (with a no content status)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1273) REST NOT_FOUND should be NO_CONTENT
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1273?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1273:
-------------------------------------
Attachment: rest.tiff
rest2.tiff
> REST NOT_FOUND should be NO_CONTENT
> -----------------------------------
>
> Key: FORGE-1273
> URL: https://issues.jboss.org/browse/FORGE-1273
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.4.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
> Attachments: rest.tiff, rest2.tiff
>
>
> Hi,
> In the REST endpoint generated code we have the following methods that return a Status.NOT_FOUND status in case the entity is not found :
> {code}
> @DELETE
> @Path("/{id:[0-9][0-9]*}")
> public Response deleteById(@PathParam("id") Long id)
> {
> Book entity = em.find(Book.class, id);
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> em.remove(entity);
> return Response.noContent().build();
> }
> @GET
> @Path("/{id:[0-9][0-9]*}")
> @Produces("application/xml")
> public Response findById(@PathParam("id") Long id)
> {
> TypedQuery<Book> findByIdQuery = em.createQuery("SELECT DISTINCT b FROM Book b WHERE b.id = :entityId ORDER BY b.id", Book.class);
> findByIdQuery.setParameter("entityId", id);
> Book entity;
> try
> {
> entity = findByIdQuery.getSingleResult();
> }
> catch (NoResultException nre)
> {
> entity = null;
> }
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> return Response.ok(entity).build();
> }
> {code}
> In both cases it should be a Status.NO_CONTENT. The resource exists (otherwise it would have been impossible to invoke it) it just happens that it returns an empty body (with a no content status)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1273) REST NOT_FOUND should be NO_CONTENT
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1273?page=com.atlassian.jira.plugin... ]
Vineet Reynolds commented on FORGE-1273:
----------------------------------------
Hey [~agoncal],
I'm not sure a 204 (or any 2xx response code) would be in line with other REST APIs that I've studied. The 204 would indicate that everything is correct, while the 404 would indicate that the client performed an incorrect operation by requesting the representation for a resource that doesn't exist.
I hope this convinces you. If not I'll appeal to a higher authority :) I'll be looking at error mapping shortly, and one of the small changes I intend to make it easier for the generated REST APIs to provide information about errors. I'm using [this article from ApiGee|https://blog.apigee.com/detail/restful_api_design_what_about_errors] as a guideline (can be ignored though where convenient), and I think we'd find it difficult to convince end-users to map missing resource exceptions to a 204.
By the way, many thanks for bringing all this up. Not only does this serve as a review, it also ensures that design decisions like these are captured somewhere. Of course, when we have better site documentation, this would automatically find it's place there.
> REST NOT_FOUND should be NO_CONTENT
> -----------------------------------
>
> Key: FORGE-1273
> URL: https://issues.jboss.org/browse/FORGE-1273
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.4.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Hi,
> In the REST endpoint generated code we have the following methods that return a Status.NOT_FOUND status in case the entity is not found :
> {code}
> @DELETE
> @Path("/{id:[0-9][0-9]*}")
> public Response deleteById(@PathParam("id") Long id)
> {
> Book entity = em.find(Book.class, id);
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> em.remove(entity);
> return Response.noContent().build();
> }
> @GET
> @Path("/{id:[0-9][0-9]*}")
> @Produces("application/xml")
> public Response findById(@PathParam("id") Long id)
> {
> TypedQuery<Book> findByIdQuery = em.createQuery("SELECT DISTINCT b FROM Book b WHERE b.id = :entityId ORDER BY b.id", Book.class);
> findByIdQuery.setParameter("entityId", id);
> Book entity;
> try
> {
> entity = findByIdQuery.getSingleResult();
> }
> catch (NoResultException nre)
> {
> entity = null;
> }
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> return Response.ok(entity).build();
> }
> {code}
> In both cases it should be a Status.NO_CONTENT. The resource exists (otherwise it would have been impossible to invoke it) it just happens that it returns an empty body (with a no content status)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1273) REST NOT_FOUND should be NO_CONTENT
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1273?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1273:
-----------------------------------
Fix Version/s: 2.x Future
> REST NOT_FOUND should be NO_CONTENT
> -----------------------------------
>
> Key: FORGE-1273
> URL: https://issues.jboss.org/browse/FORGE-1273
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.4.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Hi,
> In the REST endpoint generated code we have the following methods that return a Status.NOT_FOUND status in case the entity is not found :
> {code}
> @DELETE
> @Path("/{id:[0-9][0-9]*}")
> public Response deleteById(@PathParam("id") Long id)
> {
> Book entity = em.find(Book.class, id);
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> em.remove(entity);
> return Response.noContent().build();
> }
> @GET
> @Path("/{id:[0-9][0-9]*}")
> @Produces("application/xml")
> public Response findById(@PathParam("id") Long id)
> {
> TypedQuery<Book> findByIdQuery = em.createQuery("SELECT DISTINCT b FROM Book b WHERE b.id = :entityId ORDER BY b.id", Book.class);
> findByIdQuery.setParameter("entityId", id);
> Book entity;
> try
> {
> entity = findByIdQuery.getSingleResult();
> }
> catch (NoResultException nre)
> {
> entity = null;
> }
> if (entity == null)
> {
> return Response.status(Status.NOT_FOUND).build();
> }
> return Response.ok(entity).build();
> }
> {code}
> In both cases it should be a Status.NO_CONTENT. The resource exists (otherwise it would have been impossible to invoke it) it just happens that it returns an empty body (with a no content status)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1273) REST NOT_FOUND should be NO_CONTENT
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1273:
----------------------------------------
Summary: REST NOT_FOUND should be NO_CONTENT
Key: FORGE-1273
URL: https://issues.jboss.org/browse/FORGE-1273
Project: Forge
Issue Type: Enhancement
Components: Scaffold
Affects Versions: 1.4.2.Final
Reporter: Antonio Goncalves
Hi,
In the REST endpoint generated code we have the following methods that return a Status.NOT_FOUND status in case the entity is not found :
{code}
@DELETE
@Path("/{id:[0-9][0-9]*}")
public Response deleteById(@PathParam("id") Long id)
{
Book entity = em.find(Book.class, id);
if (entity == null)
{
return Response.status(Status.NOT_FOUND).build();
}
em.remove(entity);
return Response.noContent().build();
}
@GET
@Path("/{id:[0-9][0-9]*}")
@Produces("application/xml")
public Response findById(@PathParam("id") Long id)
{
TypedQuery<Book> findByIdQuery = em.createQuery("SELECT DISTINCT b FROM Book b WHERE b.id = :entityId ORDER BY b.id", Book.class);
findByIdQuery.setParameter("entityId", id);
Book entity;
try
{
entity = findByIdQuery.getSingleResult();
}
catch (NoResultException nre)
{
entity = null;
}
if (entity == null)
{
return Response.status(Status.NOT_FOUND).build();
}
return Response.ok(entity).build();
}
{code}
In both cases it should be a Status.NO_CONTENT. The resource exists (otherwise it would have been impossible to invoke it) it just happens that it returns an empty body (with a no content status)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1272) rest-endpoint-from-entity --targets option only auto-completes entity classes in project.model package
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1272?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1272:
-----------------------------------
Steps to Reproduce:
Using the shell:
{code}
new-project --named demo --topLevelPackage org.demo.app
jpa-setup
jpa-new-entity --named Customer --targetPackage org.demo.app.afolderjpa-jpa-new-entity --named Client --targetPackage org.demo.app.model
{code}
Then:
{code}
rest-endpoint-from-entity --targets <TAB>
{code}
Only org.demo.app.model should be displayed.
was:
Using the shell:
{code}
new-project --named demo --topLevelPackage org.demo.app
jpa-setup
jpa-new-entity --named Customer --targetPackage org.demo.app.afolderjpa-jpa-new-entity --named Client --targetPackage org.demo.app.model
{code}
{code}
rest-endpoint-from-entity --target <TAB>
{code}
Only org.demo.app.model should be displayed.
> rest-endpoint-from-entity --targets option only auto-completes entity classes in project.model package
> ------------------------------------------------------------------------------------------------------
>
> Key: FORGE-1272
> URL: https://issues.jboss.org/browse/FORGE-1272
> Project: Forge
> Issue Type: Bug
> Components: Usability
> Affects Versions: 2.0.0.Alpha13
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> In Eclipse UI, the entity combo is empty
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1271) Adding code conventions to generated code
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1271:
----------------------------------------
Summary: Adding code conventions to generated code
Key: FORGE-1271
URL: https://issues.jboss.org/browse/FORGE-1271
Project: Forge
Issue Type: Feature Request
Components: Resources API, Scaffold
Affects Versions: 2.x Future
Reporter: Antonio Goncalves
Discussion on : https://community.jboss.org/message/842429
Developers look at Forge as the "way to write Java EE code" or if you like "if those guys write code like this, then we should".
I am digging into some details of the generated code (I am writing a blog about several architectural styles starting with Forge) and I feel coding convention should be homogenized. I know extensions are written by different individuals, but some basic coding conventions should be applied. For example, when you generate a web app with REST and Faces scaffolding, you get some difference :
* Faces Backing Bean use query builder (e.g {{getAll}} method is {{entityManager.createQuery(criteria.select(criteria.from(Book.class))).getResultList();}} and
* REST Endpoint use dynamic queries (the {{listAll}} method is {{"SELECT DISTINCT b FROM Book b ORDER BY b.id"))}}
Method names are different and do the same :
* JSF : {{getAll}}
* REST : {{listAll}}
Attributes
* {{private EntityManager em;}}
* {{private EntityManager entityManager;}} // em would be better
Or the use of {{this}} keyword (JSF beans use {{this.entityManager}} instead of directly {{em}} in REST)
And there are several examples like this. If Forge is seen as "the way of writing code" maybe something should be created to get homogenized code. PMD, Checkstyle, human review and so one.....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1270) Forge 2.0.0.Aplha13 doesn't start on Windows
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1270?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1270:
-------------------------------------------
Hey Fred,
Please forgive the current state of our last release, and of the snapshots. We are having some issues with the JBoss parent and are still sorting out the repercussions of that. Let's get together tomorrow and get this figured out.
Sorry for the trouble!
~Lincoln
> Forge 2.0.0.Aplha13 doesn't start on Windows
> --------------------------------------------
>
> Key: FORGE-1270
> URL: https://issues.jboss.org/browse/FORGE-1270
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha13
> Environment: Win 7-64b, JDK 1.7.0_45, forge 2.0.0.Alpha13
> Reporter: Fred Bricon
> Priority: Blocker
>
> * Start forge
> * Forge banner is shown
> * Prompt never shows up
> See threaddump :
> {noformat}
> 2013-10-20 10:37:12
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode):
> "Reference Reaper" daemon prio=6 tid=0x000000000c994000 nid=0x259c in Object.wait() [0x000000000d9af000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at org.jboss.modules.ref.References$ReaperThread.run(References.java:68)
> "Service Thread" daemon prio=6 tid=0x000000000a9c8000 nid=0x1b68 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=10 tid=0x000000000a9c6000 nid=0x2380 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=10 tid=0x000000000a9c1000 nid=0x1bdc waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Attach Listener" daemon prio=10 tid=0x000000000a9bf000 nid=0x209c waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=10 tid=0x000000000a9b8000 nid=0x22e0 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=8 tid=0x000000000a969800 nid=0x1b58 in Object.wait() [0x000000000bc8f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)
> "Reference Handler" daemon prio=10 tid=0x000000000a95e000 nid=0x1b80 in Object.wait() [0x000000000be2f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d66050f0> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:503)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> - locked <0x00000007d66050f0> (a java.lang.ref.Reference$Lock)
> "main" prio=6 tid=0x00000000023af000 nid=0x1124 waiting on condition [0x00000000027df000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:177)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:122)
> at org.jboss.forge.bootstrap.Bootstrap.start(Bootstrap.java:170)
> at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88)
> "VM Thread" prio=10 tid=0x000000000a958800 nid=0x24a0 runnable
> "GC task thread#0 (ParallelGC)" prio=6 tid=0x000000000229e800 nid=0x1d70 runnable
> "GC task thread#1 (ParallelGC)" prio=6 tid=0x00000000022a0800 nid=0x7e8 runnable
> "GC task thread#2 (ParallelGC)" prio=6 tid=0x00000000022a2000 nid=0x1694 runnable
> "GC task thread#3 (ParallelGC)" prio=6 tid=0x00000000022a3800 nid=0xe70 runnable
> "VM Periodic Task Thread" prio=10 tid=0x000000000a9de000 nid=0x1e7c waiting on condition
> JNI global references: 134
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (FORGE-1270) Forge 2.0.0.Aplha13 doesn't start on Windows
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1270?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III edited comment on FORGE-1270 at 10/21/13 12:01 AM:
----------------------------------------------------------------------
Hey Fred,
Please forgive the current state of our last release, and of the snapshots. We are having some issues with the JBoss parent POM and are still sorting out the repercussions of that. Let's get together tomorrow and get this figured out.
Sorry for the trouble!
~Lincoln
was (Author: lincolnthree):
Hey Fred,
Please forgive the current state of our last release, and of the snapshots. We are having some issues with the JBoss parent and are still sorting out the repercussions of that. Let's get together tomorrow and get this figured out.
Sorry for the trouble!
~Lincoln
> Forge 2.0.0.Aplha13 doesn't start on Windows
> --------------------------------------------
>
> Key: FORGE-1270
> URL: https://issues.jboss.org/browse/FORGE-1270
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.0.0.Alpha13
> Environment: Win 7-64b, JDK 1.7.0_45, forge 2.0.0.Alpha13
> Reporter: Fred Bricon
> Priority: Blocker
>
> * Start forge
> * Forge banner is shown
> * Prompt never shows up
> See threaddump :
> {noformat}
> 2013-10-20 10:37:12
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode):
> "Reference Reaper" daemon prio=6 tid=0x000000000c994000 nid=0x259c in Object.wait() [0x000000000d9af000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at org.jboss.modules.ref.References$ReaperThread.run(References.java:68)
> "Service Thread" daemon prio=6 tid=0x000000000a9c8000 nid=0x1b68 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=10 tid=0x000000000a9c6000 nid=0x2380 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=10 tid=0x000000000a9c1000 nid=0x1bdc waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Attach Listener" daemon prio=10 tid=0x000000000a9bf000 nid=0x209c waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=10 tid=0x000000000a9b8000 nid=0x22e0 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=8 tid=0x000000000a969800 nid=0x1b58 in Object.wait() [0x000000000bc8f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)
> "Reference Handler" daemon prio=10 tid=0x000000000a95e000 nid=0x1b80 in Object.wait() [0x000000000be2f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007d66050f0> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:503)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> - locked <0x00000007d66050f0> (a java.lang.ref.Reference$Lock)
> "main" prio=6 tid=0x00000000023af000 nid=0x1124 waiting on condition [0x00000000027df000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:177)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:122)
> at org.jboss.forge.bootstrap.Bootstrap.start(Bootstrap.java:170)
> at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88)
> "VM Thread" prio=10 tid=0x000000000a958800 nid=0x24a0 runnable
> "GC task thread#0 (ParallelGC)" prio=6 tid=0x000000000229e800 nid=0x1d70 runnable
> "GC task thread#1 (ParallelGC)" prio=6 tid=0x00000000022a0800 nid=0x7e8 runnable
> "GC task thread#2 (ParallelGC)" prio=6 tid=0x00000000022a2000 nid=0x1694 runnable
> "GC task thread#3 (ParallelGC)" prio=6 tid=0x00000000022a3800 nid=0xe70 runnable
> "VM Periodic Task Thread" prio=10 tid=0x000000000a9de000 nid=0x1e7c waiting on condition
> JNI global references: 134
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months