October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1016) Refactoring EJB 3

by Carlo de Wolf (JIRA)

Refactoring EJB 3 ----------------- Key: EJBTHREE-1016 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1016 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

16 years, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-594) Intermittently, a Null pointer exception is thrown when trying to remove non-existent entry in ReplicatedHashMap

by Dipak Kothari (JIRA)

Intermittently, a Null pointer exception is thrown when trying to remove non-existent entry in ReplicatedHashMap ---------------------------------------------------------------------------------------------------------------- Key: JGRP-594 URL: http://jira.jboss.com/jira/browse/JGRP-594 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: Linux Reporter: Dipak Kothari Assigned To: Bela Ban Intermittently, when an entry is removed from a ReplicatedHashMap (where the entry does not exist) the following exception is thrown: java.lang.RuntimeException: remove(APMExample.Services.examples.ServerA09) failed at org.jgroups.blocks.ReplicatedHashMap.remove(ReplicatedHashMap.java:405) at com.ubs.apm.control.service.nameservice.jgroup.JGroupNameService.unRegisterService(JGroupNameService.java:132) at com.ubs.apm.control.sensors.ControlSensorManager.cleanup(ControlSensorManager.java:468) at com.ubs.apm.control.sensors.ControlSensorManager.<init>(ControlSensorManager.java:125) at com.ubs.apm.control.sensors.ControlSensorManager.<init>(ControlSensorManager.java:106) at com.ubs.apm.control.example.ManagedServer.init(ManagedServer.java:20) at com.ubs.apm.control.example.ManagedServer.main(ManagedServer.java:45) Caused by: java.lang.RuntimeException: failed executing request [req_id=1189617222436 caller=14.64.61.201:6825 14.64.61.201:6838: sender=14.64.61.201:6838, retval=null, received=false, suspected=false .... many such lines ... 14.64.61.201:6860: sender=14.64.61.201:6860, retval=null, received=false, suspected=false 14.64.61.201:6847: sender=14.64.61.201:6847, retval=null, received=false, suspected=false request_msg: [dst: <null>, src: 14.64.61.201:6825 (2 headers), size=143 bytes] rsp_mode: GET_NONE done: true timeout: 5000 expected_mbrs: 0 ([14.64.61.201:6815, 14.64.61.201:6816, 14.64.61.201:6824, 14.64.61.201:6825, 14.64.61.201:6826, 14.64.61.201:6827, 14.64.61.201:6828, 14.64.61.201:6829, 14.64.61.201:6830, 14.64.61.201:6831, 14.64.61.201:6833, 14.64.61.201:6834, 14.64.61.201:6835, 14.64.61.201:6836, 14.64.61.201:6837, 14.64.61.201:6838, 14.64.61.201:6839, 14.64.61.201:6842, 14.64.61.201:6843, 14.64.61.201:6844, 14.64.61.201:6845, 14.64.61.201:6846, 14.64.61.201:6847, 14.64.61.201:6848, 14.64.61.201:6849, 14.64.61.201:6850, 14.64.61.201:6851, 14.64.61.201:6852, 14.64.61.201:6853, 14.64.61.201:6854, 14.64.61.201:6855, 14.64.61.201:6856, 14.64.61.201:6857, 14.64.61.201:6858, 14.64.61.201:6859, 14.64.61.201:6860, 14.64.61.201:6861, 14.64.61.201:6862, 14.64.61.201:6863, 14.64.61.201:6864, 14.64.61.201:6865, 14.64.61.201:6866])] at org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:433) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:199) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:167) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:163) at org.jgroups.blocks.ReplicatedHashMap.remove(ReplicatedHashMap.java:402) ... 6 more Caused by: java.lang.RuntimeException: failure adding msg [dst: <null>, src: 14.64.61.201:6825 (2 headers), size=143 bytes] to the retransmit table for 14.64.61.201:6825 at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:636) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:438) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:782) at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:221) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339) at org.jgroups.JChannel.downcall(JChannel.java:1240) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:752) at org.jgroups.blocks.RequestCorrelator.sendRequest(RequestCorrelator.java:301) at org.jgroups.blocks.GroupRequest.doExecute(GroupRequest.java:440) at org.jgroups.blocks.GroupRequest.execute(GroupRequest.java:190) at org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:430) ... 10 more Caused by: java.lang.NullPointerException at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:632) ... 21 more -- 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

16 years, 2 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAOP-388) Allow specification of the exception for after-throwing bindings

by Flavia Rainone (JIRA)

Allow specification of the exception for after-throwing bindings ---------------------------------------------------------------- Key: JBAOP-388 URL: http://jira.jboss.com/jira/browse/JBAOP-388 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 We need to provide an optional attribute to the throwing tag (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type. This task includes updating: - advice validation algorithm - overloaded advice selection algorithm - documentation (tutorial, reference manual, 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

16 years, 2 months

2
23
0 / 0

[JBoss JIRA] Created: (EJBTHREE-788) Default SFSB timeout should be longer than the default tomcat HttpSession timeout.

by Gavin King (JIRA)

Default SFSB timeout should be longer than the default tomcat HttpSession timeout. ---------------------------------------------------------------------------------- Key: EJBTHREE-788 URL: http://jira.jboss.com/jira/browse/EJBTHREE-788 Project: EJB 3.0 Issue Type: Bug Reporter: Gavin King Priority: Critical This bites every user who tries to use Seam. -- 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

16 years, 3 months

6
18
0 / 0

[JBoss JIRA] Created: (JBAS-3767) Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI

by Elias Ross (JIRA)

Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI ------------------------------------------------------------------------------- Key: JBAS-3767 URL: http://jira.jboss.com/jira/browse/JBAS-3767 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Elias Ross Assigned To: Scott M Stark A common application integration pattern is to create MBean services that bind objects (or themselves) to JNDI. These objects bound to JNDI are then used in EJBs. It seems generally useful to provide a class with JBoss, similar to ServiceMBeanSupport, which allows users to bind objects to the local JNDI. A lot of JBoss services do bind objects to JNDI and could probably extend from this base class. http://wiki.jboss.org/wiki/Wiki.jsp?page=BindMBeanToJNDI Additional ideas: Create an attribute "BindObject". Then users could do something like: <attribute name="BindObject" attributeClass="..." serialDataType="javaBean"> </attribute> -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4355) jbossall-client.jar should only point to external client jar files.

by Dimitris Andreadis (JIRA)

jbossall-client.jar should only point to external client jar files. ------------------------------------------------------------------- Key: JBAS-4355 URL: http://jira.jboss.com/jira/browse/JBAS-4355 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assigned To: Rajesh Rajasekaran Fix For: JBossAS-4.2.1.CR1 We should have the flexibility to alter individual client jar libraries, without having to regenerate jbossall-client.jar -- 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

16 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-4900) cannot redeploy after deployment error

by Thomas Diesler (JIRA)

cannot redeploy after deployment error -------------------------------------- Key: JBAS-4900 URL: http://jira.jboss.com/jira/browse/JBAS-4900 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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

16 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (JGRP-604) ENCRYPT: issues with keystore

by Bela Ban (JIRA)

ENCRYPT: issues with keystore ----------------------------- Key: JGRP-604 URL: http://jira.jboss.com/jira/browse/JGRP-604 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Attachments: tmp2.xml If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception: 09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message javax.crypto.BadPaddingException: Given final block not properly padded at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275) at javax.crypto.Cipher.doFinal(DashoA12275) at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837) at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830) at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673) at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533) at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573) at org.jgroups.protocols.UNICAST.up(UNICAST.java:247) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704) 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:309) 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:1512) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) To reproduce: - Create a configuration with the following entries present: <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> <FRAG2 frag_size="60000"/> - Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2). Note that this error does not occur with <ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/> -- 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

16 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1055) minimize/maximize causes portlet to return to initial state

by Johnny Healey (JIRA)

minimize/maximize causes portlet to return to initial state ----------------------------------------------------------- Key: JBPORTAL-1055 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1055 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.4 Final Environment: CentOS release 4.4 (Final), jdk1.5.0_06 Reporter: Johnny Healey Assigned To: Julien Viet This has been noticed in a handful of custom portlets, but can be duplicated in the "event test" page that ships with the portal. "Test Event A" can change the color of the text in "Test Event B", but minimizing or maximizing "Test Event B" causes the text to return to the original color, black. -- 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

16 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1004) Jboss Portal to support virtual hosts

by Sverker Abrahamsson (JIRA)

Jboss Portal to support virtual hosts ------------------------------------- Key: JBPORTAL-1004 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1004 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sverker Abrahamsson JBoss Portal is today unable to support multiple virtual hosts, i.e. it's not possible to create a portal bound to the address www.foo.com and one that is bound to www.bar.com. This is a major problem for real world usage of JBoss Portal -- 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

16 years, 3 months

5
14
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007