March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-3364) Support PROPAGATION_NESTED in JTA implementation

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3364?page=com.atlassian.jira.plug... ] Dimitris Andreadis closed JBAS-3364. ------------------------------------ Resolution: Won't Fix > Support PROPAGATION_NESTED in JTA implementation > ------------------------------------------------ > > Key: JBAS-3364 > URL: https://jira.jboss.org/jira/browse/JBAS-3364 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Yegor Yenikyeyev > > Is it possible to support nested JTA transactions in one of upcoming version? For this moment i see the following in TxManager.java > if (current != null) > { > if (current.isDone()) > disassociateThread(ti); > else > throw new NotSupportedException > ("Transaction already active, cannot nest transactions."); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6434) REGRESSION: org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase

by Shelly McGowan (JIRA)

REGRESSION: org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase -------------------------------------------------------------------------- Key: JBAS-6434 URL: https://jira.jboss.org/jira/browse/JBAS-6434 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.1.0.Beta1 Reporter: Shelly McGowan Assignee: Shelly McGowan test423Compatibility fails with the JBossWS 3.1.0 upgrade: serialVersionUID error for org.jboss.ws.metadata.wsdl.Extendable, 423 -3164210175211099488, current: -169321949189958877 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2333) Coordination events should properly propagate to affected windows in a partial refresh context.

by Chris Laprun (JIRA)

Coordination events should properly propagate to affected windows in a partial refresh context. ----------------------------------------------------------------------------------------------- Key: JBPORTAL-2333 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2333 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.2 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.8 Final Right now, coordination events (change in a PRP, for example) forces a full page refresh. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2328) PRP test is broken in AJAX tests

by Chris Laprun (JIRA)

PRP test is broken in AJAX tests -------------------------------- Key: JBPORTAL-2328 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2328 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.7.1 Final Reporter: Chris Laprun Fix For: 2.7.2 Final "good" thing was that it wasn't working in 2.7.1 either... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-640) Shared protocols

by Bela Ban (JIRA)

Shared protocols ---------------- Key: JGRP-640 URL: http://jira.jboss.com/jira/browse/JGRP-640 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Like the shared transport, investigate whether we can share other protocols. E.g. FD, FD_SOCK (preventing duplicate server sockets and sockets), Discovery and so on. -- 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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-45) Integrate checkstyle

by Jesper Pedersen (JIRA)

Integrate checkstyle -------------------- Key: JBJCA-45 URL: https://jira.jboss.org/jira/browse/JBJCA-45 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Integrate checkstyle in the project such that all source files are formatted in the same way -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-44) Track component updates

by Jesper Pedersen (JIRA)

Track component updates ----------------------- Key: JBJCA-44 URL: https://jira.jboss.org/jira/browse/JBJCA-44 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Holder task for tracking all the 3rd party component updates -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6570) request.getRequestURL() returns jsp path instead of servlet path

by Pavneet Chadha (JIRA)

request.getRequestURL() returns jsp path instead of servlet path ---------------------------------------------------------------- Key: JBAS-6570 URL: https://jira.jboss.org/jira/browse/JBAS-6570 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Environment: Linux Enterprise 4 Server, Java 1.6 Reporter: Pavneet Chadha We are in process of migrating our application from Jboss 3.2.7running on Java 1.4.2 to JBoss 5.0.0 GA running on Java 1.6 version. There are multiple instances where we are using request.getRequestURL() in our JSP's. >From the site address as below: http://site-name.com/context/servlet1.jspx?param1=ab&param2=bc request.getRequestURL() returns : http://site-name.com/context/servlet1.jspx in JBoss 3.2.7. Using the same in JBoss 5.0.0 GA this returns: http://site-name.com/context/servlet1/servlet.jsp, the actual JSP serving the page. This is not expected behavior and is breaking our code in multiple places. I was unable to find any bug in the issues regarding this and hence I am posting this as a bug. Do let me know if this is expected behavior, or is there a existing workaround to get the same behavior as in JBoss 3.2.7. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-917) Problems after shunning

by Bela Ban (JIRA)

Problems after shunning ----------------------- Key: JGRP-917 URL: https://jira.jboss.org/jira/browse/JGRP-917 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Attachments: tmp.xml, tmp1.xml To reproduce: - draw-2.8 -props ./tmp.xml - draw-2.8 -props ./tmp1.xml - Kill first instance (CTRL-C) and restart - First instance continually tries to send messages to an old node: 123552 [TRACE] FD_ALL: - linux-2842 sent heartbeat to cluster 123732 [WARN] UDP: - no physical address for 1413155d-4e6d-4641-7ea1-bc6091e9d6b1, dropping message 124530 [WARN] UDP: - no physical address for 1413155d-4e6d-4641-7ea1-bc6091e9d6b1, dropping message 124725 [WARN] UDP: - no physical address for 1413155d-4e6d-4641-7ea1-bc6091e9d6b1, dropping message 124933 [WARN] UDP: - no physical address for 1413155d-4e6d-4641-7ea1-bc6091e9d6b1, dropping message 125731 [WARN] UDP: - no physical address for 1413155d-4e6d-4641-7ea1-bc6091e9d6b1, dropping message -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JGRP-919) UUID.cache: timed purging of old mappings

by Bela Ban (JIRA)

UUID.cache: timed purging of old mappings ----------------------------------------- Key: JGRP-919 URL: https://jira.jboss.org/jira/browse/JGRP-919 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 When a channel is closed, the logical name / UUID mapping is removed by calling UUID.remove(). However, if we have a View V which contains A and B, but B was closed, then V will get printed with A's logical name but B's UUID ! This is not incorrect, but doesn't look nice. A delayed purging of B's logical name/UUID mapping would allows us to still print the logical name of B instead of its UUID, even though B was closed. SOLUTION(S): - Delay every remove(): place the to be removed element into a queue, from which we purge an element E only if E is older than X milliseconds. - Alternative: remove only at JVM termination, or when cache is more than X elements big -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
2
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 March 2009