December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-157) Server Shutdown Latency and Session replication and Forwarding

by Shankar Pattabiraman (JIRA)

Server Shutdown Latency and Session replication and Forwarding -------------------------------------------------------------- Key: JBCLUSTER-157 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-157 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: Java 1.5.0_05, Win XP,Red Hat 3 JBoss 4.0.5 Apache Reporter: Shankar Pattabiraman Assigned To: Brian Stansberry Priority: Minor Setup a cluster with 2 nodes. Be in a session where a server is servicing. Try to give a Control Z to kill the server while servicing. The latency involved in shutting down the server never gives a chance for the server to switch to the other. The session in the latency period of shutdown never gets successfully switched to the other node in the cluster. Apache-2 Node Jboss Cluster and a Trivial JEE Application. Check this out whether it is a configuration issue or a real issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5009) HttpNamingContextFactory does neither support multiple URLs, nor load balancing nor failover

by Galder Zamarreno (JIRA)

HttpNamingContextFactory does neither support multiple URLs, nor load balancing nor failover -------------------------------------------------------------------------------------------- Key: JBAS-5009 URL: http://jira.jboss.com/jira/browse/JBAS-5009 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Naming Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA Reporter: Galder Zamarreno Assigned To: Brian Stansberry HttpNamingContextFactory doesn't have to logic built into it to parse multiple URLs. Also, the naming proxy you'll get won't have automatic loadbalancing, failure detection and failover in it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-686) Bidirectional @OneToOne with CascadeType.ALL and optional=false on the non-owning side:

by Jeremy Norris (JIRA)

Bidirectional @OneToOne with CascadeType.ALL and optional=false on the non-owning side: --------------------------------------------------------------------------------------- Key: EJBTHREE-686 URL: http://jira.jboss.com/jira/browse/EJBTHREE-686 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD, EJB 3.0 RC7 - FD, EJB 3.0 RC6 - PFD Reporter: Jeremy Norris Consider the following two classes: ----- class X: @Entity @Table(name="x") public class X { private Integer id; private Y y; public X() { this.y = new Y(this); } @Id @GeneratedValue @Column(name = "id", nullable=false, updatable=false) public Integer getId() { return id; } protected void setId(Integer id) { this.id = id; } @OneToOne(cascade={CascadeType.ALL}, mappedBy="x") public Y getY() { return y; } protected void setY(Y y) { this.y = y; } } ----- class Y: @Entity @Table(name="y") public class Y { private Integer id; private X x; protected Y() { } public Y(X x) { this.x = x; x.setY(this); } @Id @GeneratedValue @Column(name = "id", nullable=false, updatable=false) public Integer getId() { return id; } protected void setId(Integer id) { this.id = id; } @OneToOne @JoinColumn(name="x_id", nullable=false) public X getX() { return x; } protected void setX(X x) { this.x = x; } } ----- X is persisted as follows: // Note: The constructor creates a new dependent Y instance, and hooks it up appropriately: X x = new X(); em.persist(x); ----- This works fine and persists as expected. However, if I add "optional=false" to the X.@OneToOne declaration, it fails with the following exception: javax.ejb.EJBTransactionRolledbackException: javax.persistence.PersistenceException: org.hibernate.PropertyValueException: not-null property references a null or transient value: ... Y.x Y.x definitely set. Also, "x == x.getY().getX()" is true. (Interestingly, this only happens if I put the "optional=false" on the X side. "optional=false" on the Y side is fine). This seems like a bug unless there is something I don't understand about "optional", but it seems pretty simply - The spec says the following about this attribute: (Optional) Whether the association is optional. If set to false then a non-null relationship must always exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (GPD-140) when working with large process definitions, screen jumps to top whenever new nodes added in designer

by Ross McDonald (JIRA)

when working with large process definitions, screen jumps to top whenever new nodes added in designer ----------------------------------------------------------------------------------------------------- Key: GPD-140 URL: http://jira.jboss.com/jira/browse/GPD-140 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta2 Environment: osx macbook pro, eclipse 3.3.0, designer plugin 3.1.0 beta 1, beta 2, CR1 Reporter: Ross McDonald Assigned To: Koen Aers Priority: Trivial Hi, when working with large process diagrams, if I am scrolled down to the bottom of the view, and add a new node, when the screen is updated it jumps back up to the top, so I need to scroll down again. Obviously when adding many nodes, this costs time, its just a trivial thing. Cheers Ross -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1037) process image rendered incorrectly for large process definition

by Ross McDonald (JIRA)

process image rendered incorrectly for large process definition --------------------------------------------------------------- Key: JBPM-1037 URL: http://jira.jboss.com/jira/browse/JBPM-1037 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Environment: mac osx, tomcat 5.0.28 Reporter: Ross McDonald Assigned To: Tom Baeyens Priority: Minor Hi, then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node, cheers Ross -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
15
0 / 0

[JBoss JIRA] Created: (GPD-123) Ability to zoom

by Matthew Sandoz (JIRA)

Ability to zoom --------------- Key: GPD-123 URL: http://jira.jboss.com/jira/browse/GPD-123 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta1 Reporter: Matthew Sandoz Assigned To: Koen Aers Priority: Minor It would be nice especially for large flows to be able to zoom in and out of the process designer view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-27) Make transitions identifiable by position

by Koen Aers (JIRA)

Make transitions identifiable by position ----------------------------------------- Key: GPD-27 URL: http://jira.jboss.com/jira/browse/GPD-27 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Priority: Minor Try and implement a strategy where transitions are identified by their position in the list of transitions rather than by a name. This should be done to eliminate the need for a transition name. When this is done the bendpoints in the gpd.xml file can be associated with their transition based on the position. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-14) Lay out Algorithm

by Koen Aers (JIRA)

Lay out Algorithm ----------------- Key: GPD-14 URL: http://jira.jboss.com/jira/browse/GPD-14 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers Integrate a layout algorithm that is used when users add nodes to the xml directly to lay out the newly created components in an orderly fashion on the graphical canvas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (GPD-146) improve feedback when creating self referencing transitions

by Koen Aers (JIRA)

improve feedback when creating self referencing transitions ----------------------------------------------------------- Key: GPD-146 URL: http://jira.jboss.com/jira/browse/GPD-146 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM JPDL Designer 3.1.0.GA Reporter: Koen Aers Assigned To: Koen Aers Priority: Minor At the moment creating self referencing transitions is done by clicking twice on the source/target node. In the future some feedback (a dummy transition) should make this proces more obvious -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-150) In-place label edit box offset in scrolled editor

by David Good (JIRA)

In-place label edit box offset in scrolled editor ------------------------------------------------- Key: GPD-150 URL: http://jira.jboss.com/jira/browse/GPD-150 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: Eclipse 3.3, Windows XP SP2, JDK 6 Reporter: David Good Assigned To: Koen Aers Priority: Minor When editing a diagram larger than the editor window, clicking on a node label causes the edit box to appear in an offset position (see attachment) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007