December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1283) "Powered by JBoss" overlayed on lower column headers in CMS Admin portlet

by oberiko (JIRA)

"Powered by JBoss" overlayed on lower column headers in CMS Admin portlet ------------------------------------------------------------------------- Key: JBPORTAL-1283 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1283 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4.1 SP1 Environment: Windows XP SP2, JBoss Portal 2.4.1-GA (default bundled installation w/ JBoss AS), Firefox 2.0.0.1, screen resolution 1280 x 1024 Reporter: oberiko Assigned To: Julien Viet The CMS Admin portlet has the "Powered by JBoss Portal" text in the same location (overlayed) with the lower column headers (action, name, type, created, etc.). This is on starting JBoss Portal for the first time, so the CMS Admin portlet is empty. -- 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

18 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1176) Error Displaying Flash in JBoss Portal 2.4.1.CR2

by Mitch De Felice (JIRA)

Error Displaying Flash in JBoss Portal 2.4.1.CR2 ------------------------------------------------ Key: JBPORTAL-1176 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1176 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4.1 SP1 Environment: Release ID: JBoss [Zion] 4.0.5.GA Home Dir: E:\Apache Group\jboss-portal-2.4.1-CR2 Java version: 1.4.2_09,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Server VM 1.4.2_09-b05,Sun Microsystems Inc. OS-System: Windows 2000 5.0,x86 Database: Oracle 9i Reporter: Mitch De Felice Assigned To: Julien Viet I'm having two problems with running the flash plugin in Jboss Portel window. 1. When I try to set the height and width on the object tag to a 100%, the window goes totally blank, like I didn't have any statements in the jsp. However, if I set the width="100%" and set a specific height="450" the flash plugin will be displayed. <center> <object width="100%" height="100%"> <param name="movie" value="<%= request.getAttribute("flashurl") %>"/> <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="100%"/> </object> </center> 2. The second problem that I'm seeing when trying to view a flash plungin in a Portlet Window is when I specify the classid on the object tag, the footer of the Portlet Window gets clipped off. <center> <object width="100%" height="455" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" > <param name="movie" value="<%= request.getAttribute("flashurl") %>"/> <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="455"/> </object> </center> I need to specify the classid so as the flash plugin can make an Ajax call back into the server. -- 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

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1525) RichFaces : finish integration : features, examples...

by Antoine Herzog (JIRA)

RichFaces : finish integration : features, examples... ------------------------------------------------------ Key: JBPORTAL-1525 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1525 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6 CR3 Environment: JBoss Portal 2.6CR3 (on a JBoss AS 4.0.5) Rich Faces 3.0.0 and 3.0.2 (fixed version) Reporter: Antoine Herzog Assigned To: Julien Viet RichFaces has provided a sample application to work in a JBoss Portal Portlet. There was quiet a lot of tuning and adaptation (RichFaces side only ?). It seems that it work with the JBoss Portal 2.6.0 as released. But they may be some things to do in JBoss Portal side. - Use of RichFaces for admin portlets etc... (as it is now inside JBoss products) - At least, integrate a sample RichFaces Portlet, to show how nice it is, and how it works etc... -- 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

18 years, 3 months

5
14
0 / 0

[JBoss JIRA] Created: (JGRP-654) Scheduler thread goes in infinite loop after getting interrupted by the priority task

by vivek v (JIRA)

Scheduler thread goes in infinite loop after getting interrupted by the priority task ------------------------------------------------------------------------------------- Key: JGRP-654 URL: http://jira.jboss.com/jira/browse/JGRP-654 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1 Environment: Linux, JGroups v. 2.6.1 Reporter: vivek v Assigned To: Bela Ban This seems like a bug in Scheduler class. The scheduler thread goes into infinite loop and never recovers after being interrupted by the priority task (upon deadlock detection). Here is what I think happens (with both deadlock_detection and concurrent_processing enabled for RpcDispatcher), 1) The tasks are added to the Scheduler Queue 2) If the deadlock_detection is turned on and there is a kind of deadlock (2-way method calls) the RequestCorrelator.receiveMessage() calls scheduler.addPrio(req) method 3) The addPrio(Runnable task) method adds the priority task to the head of the queue and calls the interrupt method on the Scheduler thread. 4) In the run() method of Scheduler we peek the queue, take the task from head and run it 5) "sched_thread.isInterrupted()" in the run method returns true and throws InterruptedException 6) Since, interrupted exception is thrown we bypass the "queue.removeElement(current_task)" - and the task is not removed from the queue. 7) The catch block of InterruptedException sets the current_task.suspended=true, but never resets the interrupt flag 8) Now we keep going through the same loop for the same task in the queue in the run() method as we never resets the interrupt flag. I hope this is a correct diagnosis of this "TimeoutException" problem we have been seeing for last 2-3 months. I'm not sure if there are some nested Rpc calls in our system, but with deadlock-detection turned on they should be resolved. As tasks are never moved out of the queue, all the tasks just keep adding up (I see my queue over 2300 elements) and thus, we get TimeoutException for all the incoming calls. I think we need to call "sched_thread.interrupted()" in the InterruptedException catch block so we can remove items from the queue as we process them. I've tried with this change (added Thread.interrupted at the end of InterruptedException catch block) in my local jgroups-all.jar and it seems to work fine for a long time now (3-4 hours, earlier it used to fail within 2 hours). I haven't found any workaround for this problem if the deadlock detection logic is exercised. -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-886) Add authentication to "local" protocol

by David Lloyd (JIRA)

Add authentication to "local" protocol -------------------------------------- Key: JBREM-886 URL: http://jira.jboss.com/jira/browse/JBREM-886 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 -- 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1799) Documentation for Seam, JSF, and RichFaces portlets

by Wesley Hales (JIRA)

Documentation for Seam, JSF, and RichFaces portlets ---------------------------------------------------- Key: JBPORTAL-1799 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1799 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Wesley Hales Fix For: 2.6.3 Final -- 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

18 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBRULES-1377) Rete view in the IDE plugin is documented as using JUNG instead of GEF

by Carlos Bustamante (JIRA)

Rete view in the IDE plugin is documented as using JUNG instead of GEF ---------------------------------------------------------------------- Key: JBRULES-1377 URL: http://jira.jboss.com/jira/browse/JBRULES-1377 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0.3 Reporter: Carlos Bustamante Priority: Trivial In the documentation (manual), in section 5.1.8 "The Rete view", after the screenshot, it reads: "The graph is created with the Java Universal Network/Graph Framework (JUNG). The Rete View is an advanced feature which is still in experimental state. It uses Swing inside eclipse. In future it will maybe improved using SWT or GEF." This is out of date. The Rete view actually uses GEF since 4.0.0 version of Drools. -- 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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-636) NullPointerException in Multiplexer

by Robert Newson (JIRA)

NullPointerException in Multiplexer ----------------------------------- Key: JGRP-636 URL: http://jira.jboss.com/jira/browse/JGRP-636 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Robert Newson Assigned To: Bela Ban java.lang.NullPointerException at org.jgroups.mux.Multiplexer.handleStateRequest(Multiplexer.java:639) at org.jgroups.mux.Multiplexer.up(Multiplexer.java:352) at org.jgroups.JChannel.up(JChannel.java:1148) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:362) at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:427) at org.jgroups.protocols.pbcast.STATE_TRANSFER.requestApplicationStates(STATE_TRANSFER.java:233) at org.jgroups.protocols.pbcast.STATE_TRANSFER.handleStateReq(STATE_TRANSFER.java:367) at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:117) at org.jgroups.protocols.FRAG2.up(FRAG2.java:205) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:766) at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:161) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:579) at org.jgroups.protocols.UNICAST.up(UNICAST.java:250) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:714) at org.jgroups.protocols.BARRIER.up(BARRIER.java:122) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167) at org.jgroups.protocols.FD.up(FD.java:322) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:300) at org.jgroups.protocols.MERGE2.up(MERGE2.java:145) at org.jgroups.protocols.Discovery.up(Discovery.java:250) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1510) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1459) at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1737) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) at org.jgroups.protocols.TP.dispatchToThreadPool(TP.java:1060) at org.jgroups.protocols.TP.receive(TP.java:1031) at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:899) at java.lang.Thread.run(Thread.java:619) -- 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

18 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4637) Fix org.jboss.test.messaging.* tests

by Dimitris Andreadis (JIRA)

Fix org.jboss.test.messaging.* tests ------------------------------------ Key: JBAS-4637 URL: http://jira.jboss.com/jira/browse/JBAS-4637 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-sun-1.5/... The failing messaging tests need to be looked-up and further qualified or fixed. The failures are not necessarily messaging related: SecurityUnitTestCase 30 0 9 21.235 SecurityUnitTestCase(tests-jbossmessaging) 30 0 10 33.938 SessionCloseStressTestCase(tests-standard-stress) 1 1 0 0.000 UnackedUnitTestCase -- 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

18 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-661) Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException

by Galder Zamarreno (JIRA)

Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException --------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-661 URL: http://jira.jboss.com/jira/browse/EJBTHREE-661 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC7 - FD Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: EJB 3.0 RC9 - FD When setting up security in a EJB3 bean, it is mandatory adding the org.jboss.ejb3.security.SecurityDomain tag. Failure to do so results on a NullPointerException. AS should log a more meaningful message rather than a NullPointerException. -- 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

18 years, 3 months

6
11
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 December 2007