October 2007 - jboss-jira - Jboss List Archives

[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

17 years, 9 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

17 years, 9 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

17 years, 9 months

5
14
0 / 0

[JBoss JIRA] Created: (JBRULES-1276) Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown

by Willian Mitsuda (JIRA)

Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown ------------------------------------------------------------------------------------------------- Key: JBRULES-1276 URL: http://jira.jboss.com/jira/browse/JBRULES-1276 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.2 Reporter: Willian Mitsuda Assigned To: Mark Proctor I just installed the drools plugin and noted that it automatically enables a drools toolbar in every perspective. This is not a good UI policy because it looks like the plugin is trying to appear more important than the others. I have other plugins installed, and I don't like the drools button appearing by default in the C++ or the Profilling perspective, for example. It could be enabled by default just in the Drools perspective, since it exists, and the user could enable it on the others, if he desires. Also, since your actions are all about resource creation, you could hook them into the standard "new" dropdown, instead of creating your own actionset. This should make your plugin to appear more integrated to Eclipse. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1230) Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath

by Krishnan Sivaramakrishna Iyer (JIRA)

Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath ------------------------------------------------------------------------------------- Key: JBRULES-1230 URL: http://jira.jboss.com/jira/browse/JBRULES-1230 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.0.GA Environment: Windows XP, Dell Optiplex GX 270 Reporter: Krishnan Sivaramakrishna Iyer Assigned To: Mark Proctor Priority: Blocker hi all, In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_D... , it seems I am in the compiler option The only jars I am including are as follows :- drools-compiler-4.0.0.jar drools-core-4.0.0.jar drools-decisiontables-4.0.0.jar drools-jsr94-4.0.0.jar antlr-runtime-3.0.jar mvel14-1.2rc1.jar core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I don't specify this, it does not work ?.] I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also expects the core to be included. Any help is appreciated. TIA, Krishnan. Comments from Edson Tirelli Krishnan, You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix. []s Edson -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1015) Refactor cluster message notification

by Tim Fox (JIRA)

Refactor cluster message notification ------------------------------------- Key: JBMESSAGING-1015 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1015 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We need an abstract cluster message notification system in place. This should decouple the post office from having to handle all messages via groupMember. The groupMember should be moved out of post office. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-877) Optimise browsing

by Tim Fox (JIRA)

Optimise browsing ----------------- Key: JBMESSAGING-877 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-877 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. We should also investigate activating the browsing interceptor to batch messages. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-871) Optimisations

by Tim Fox (JIRA)

Optimisations ------------- Key: JBMESSAGING-871 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-871 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Super task for various performance related optimisations -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-878) Consider using multicast or reliable multicast for message delivery

by Tim Fox (JIRA)

Consider using multicast or reliable multicast for message delivery ------------------------------------------------------------------- Key: JBMESSAGING-878 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-878 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 We could use multicast or jgroups reliable multicast for delivery of messages from server to client when there are many subscribers - currently this is point to point. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-874) INVM persistent message optimisation

by Tim Fox (JIRA)

INVM persistent message optimisation ------------------------------------ Key: JBMESSAGING-874 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- 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, 9 months

2
4
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 October 2007