August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (SWAP-22) myportlet

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/SWAP-22?page=all ] Roy Russo deleted SWAP-22: -------------------------- > myportlet > --------- > > Key: SWAP-22 > URL: http://jira.jboss.com/jira/browse/SWAP-22 > Project: PortletSwap > Issue Type: Release > Security Level: Public(Everyone can see) > Reporter: Roy Russo > Assigned To: Roy Russo > > myportlet description -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (SWAP-22) myportlet

by Roy Russo (JIRA)

myportlet --------- Key: SWAP-22 URL: http://jira.jboss.com/jira/browse/SWAP-22 Project: PortletSwap Issue Type: Release Security Level: Public (Everyone can see) Components: Portlet_Contrib Reporter: Roy Russo Assigned To: Roy Russo myportlet description -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2921) Use JBossSerialization for serializing sessions and attributes before putting them in the cache

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2921?page=all ] Hany Mesha reassigned JBAS-2921: -------------------------------- Assignee: Hany Mesha (was: Brian Stansberry) > Use JBossSerialization for serializing sessions and attributes before putting them in the cache > ----------------------------------------------------------------------------------------------- > > Key: JBAS-2921 > URL: http://jira.jboss.com/jira/browse/JBAS-2921 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Fix For: JBossAS-5.0.0.Beta > > > Use JBossSerialization in JBossCacheService externalizeSession(), loadSession(), getMarshalledValue() and getUnmarshalledValue(). -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3110) Workaround to avoid OutOfMemoryErrors during jboss boot, under Sun 64-bit linux jdk

by Frank Grimes (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3110?page=comments#action_12341305 ] Frank Grimes commented on JBAS-3110: ------------------------------------ FYI, according to the release notes, this has been fixed in jdk1.5.0_08. http://java.sun.com/j2se/1.5.0/ReleaseNotes.html http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6373059 "OutOfMemoryError on ZipFile.open" > Workaround to avoid OutOfMemoryErrors during jboss boot, under Sun 64-bit linux jdk > ----------------------------------------------------------------------------------- > > Key: JBAS-3110 > URL: http://jira.jboss.com/jira/browse/JBAS-3110 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: System service > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 SP1 > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.4.GA, JBossAS-5.0.0.Beta > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > This is just a work-around for avoiding OutOfMemoryErrors during jboss boot, when running under Sun 64-bit linux jdk. It doesn't guarantee the OOME will not happen, but this is better than nothing, until Sun fixes the broken jdk. > The fix has been tested in HEAD for 3 months without any problems reported so we apply it to the 4.0.x branch, too. > For more info, read the linked forum post. -- 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

19 years, 11 months

1
0
0 / 0

WebHosting Profesional.

by Hostex

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-597) javax.persistence.SequenceGenerator mapped to "seqhilo" and not "sequence" by org.hibernate.cfg.AnnotationBinder

by Ortwin Glück (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-597?page=comments#action_12341304 ] Ortwin Glück commented on EJBTHREE-597: --------------------------------------- We just migrated from RC3 to RC8 and this issue is byting our arses. It's a really stupid behaviour that should at least have a big WARNING in the migration docs!!! > javax.persistence.SequenceGenerator mapped to "seqhilo" and not "sequence" by org.hibernate.cfg.AnnotationBinder > ---------------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-597 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-597 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC7 - FD > Environment: JBoss 4.0.4.GA (using EJB3 packaged in that version of JBoss), Windows XP SP1, Java 1.5.04, Oracle 9 > Reporter: David Richmond > > @javax.persistence.SequenceGenerator(name = "Question_id_sequence", sequenceName = "S_QUESTION") > is mapped to a "seqhilo" generator by org.hibernate.cfg.AnnotationBinder (line 332) which causes strange ids to be generated. These ids appear to have no relation to the actual sequence state, even though "select S_QUESTION.nextVal from dual" is generated by Hibernate through JDBC. The ids start at 50 for an intial deployment, 150 after a redeployment, then 250 for the following deployment, etc, etc. > If stored procedures are used which use the S_QUESTION sequence to insert rows into the same table then a conflict will happen sometime in the future, since Hibernate does not use the value from the sequence. > If I replace the above @javax.persistence.SequenceGenerator definition with: > @org.hibernate.annotations.GenericGenerator(name="Question_id_sequence", strategy = "sequence", > parameters = { @Parameter(name="sequence", value="S_QUESTION") } ) > the actual S_QUESTION.nextVal value is used correctly by Hibernate. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-396) fix logging

by Michael Neale (JIRA)

fix logging ----------- Key: JBRULES-396 URL: http://jira.jboss.com/jira/browse/JBRULES-396 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (BPEL-174) resume process execution after system restart

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-174?page=comments#action_12341292 ] Alejandro Guizar commented on BPEL-174: --------------------------------------- Designed the query to retrieve enabled onMessage event handlers (a.k.a. onEvent) Fixed a mapping bug in OnEvent.variable > resume process execution after system restart > --------------------------------------------- > > Key: BPEL-174 > URL: http://jira.jboss.com/jira/browse/BPEL-174 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > Right now the relation servlet only opens message listeners for activities that create process instances. It must also load existing tokens pointing to inbound message activities and open their corresponding request listeners. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (BPEL-189) alarm event

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-189?page=all ] Alejandro Guizar resolved BPEL-189. ----------------------------------- Resolution: Done implemented time-driven activities on top of the jbpm scheduler service > alarm event > ----------- > > Key: BPEL-189 > URL: http://jira.jboss.com/jira/browse/BPEL-189 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > enhance scope for handling time-driven events; ws-bpel 2.0 section 12.6.2 -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (BPEL-188) pick alarm

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-188?page=all ] Alejandro Guizar resolved BPEL-188. ----------------------------------- Resolution: Done implemented time-driven activities on top of the jbpm scheduler service > pick alarm > ---------- > > Key: BPEL-188 > URL: http://jira.jboss.com/jira/browse/BPEL-188 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > enhance pick activity for processing alarms in addition to messages; ws-bpel 2.0 section 11.5 -- 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

19 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006