[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
[JBoss JIRA] Created: (JBRULES-1358) DSL mapping not available in BRMS
by Ravi Shankar (JIRA)
DSL mapping not available in BRMS
---------------------------------
Key: JBRULES-1358
URL: http://jira.jboss.com/jira/browse/JBRULES-1358
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0.3
Reporter: Ravi Shankar
Hi,
In the BRMS I did not find conversation of DSL to actual valid DRL syntax. For example in the eclipse plugin I created the following as in when clause:
Shopping Basket price is more than or equal to {value}
and in the mapping I put the following java code:
originalBasket : ShoppingBasket(descriptor == "originalBasket", cartTotal.value >= {value}) bestDiscounted : ShoppingBasket(descriptor == "bestDiscounted") currentDiscounted : ShoppingBasket(descriptor == "currentDiscounted")
so that when converting a .dslr into a .drl the conversion happens from business user's friendly version to developer friendly code. But I do not find a place in BRMS to specify such mappings.
--
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
[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
[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
[JBoss JIRA] Created: (JBRULES-1433) java.lang.ClassCastException comparing BigDecimals (compareTo)
by José Arrarte (JIRA)
java.lang.ClassCastException comparing BigDecimals (compareTo)
--------------------------------------------------------------
Key: JBRULES-1433
URL: http://jira.jboss.com/jira/browse/JBRULES-1433
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.4, 4.0.3
Environment: java.runtime.name = Java(TM) SE Runtime Environment
sun.boot.library.path = C:\Archivos de programa\Java\jre1.6.0_03\bin
java.vm.version = 1.6.0_03-b05
java.vm.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
path.separator = ;
java.vm.name = Java HotSpot(TM) Client VM
file.encoding.pkg = sun.io
user.country = ES
sun.java.launcher = SUN_STANDARD
sun.os.patch.level = Service Pack 2
java.vm.specification.name = Java Virtual Machine Specification
java.runtime.version = 1.6.0_03-b05
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.endorsed.dirs = C:\Archivos de programa\Java\jre1.6.0_03\lib\endorsed
os.arch = x86
java.io.tmpdir = C:\DOCUME~1\Tito\CONFIG~1\Temp\
line.separator =
java.vm.specification.vendor = Sun Microsystems Inc.
user.variant =
os.name = Windows XP
sun.jnu.encoding = Cp1252
java.library.path = C:\Archivos de programa\Java\jre1.6.0_03\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Archivos de programa\Java\jre1.6.0_03\bin\client;C:\Archivos de programa\Java\jre1.6.0_03\bin;C:\Archivos de programa\Java\jre1.6.0_03\bin\client;C:\Archivos de programa\Java\jre1.6.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\ATI Technologies\ATI Control Panel;C:\Java\maven-2.0.8\bin;C:\Archivos de programa\Java\jdk1.6.0_03\bin;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;C:\Archivos de programa\Microsoft SQL Server\80\Tools\BINN;C:\UnixUtils\usr\local\wbin;C:\Archivos de programa\MySQL\MySQL Server 5.0\bin
java.specification.name = Java Platform API Specification
java.class.version = 50.0
sun.management.compiler = HotSpot Client Compiler
os.version = 5.1
user.home = C:\Documents and Settings\Tito
user.timezone =
java.awt.printerjob = sun.awt.windows.WPrinterJob
file.encoding = Cp1252
java.specification.version = 1.6
user.name = Tito
java.class.path = D:\workspaces\ruleTest\target\classes;C:\Documents and Settings\Tito\.m2\repository\org\drools\drools-compiler\4.0.4\drools-compiler-4.0.4.jar;C:\Documents and Settings\Tito\.m2\repository\org\drools\drools-core\4.0.4\drools-core-4.0.4.jar;C:\Documents and Settings\Tito\.m2\repository\org\mvel\mvel14\1.2.21\mvel14-1.2.21.jar;C:\Documents and Settings\Tito\.m2\repository\org\antlr\antlr-runtime\3.0\antlr-runtime-3.0.jar;C:\Documents and Settings\Tito\.m2\repository\org\eclipse\jdt\core\3.2.3.v_686_R32x\core-3.2.3.v_686_R32x.jar;C:\Documents and Settings\Tito\.m2\repository\janino\janino\2.5.10\janino-2.5.10.jar;C:\Documents and Settings\Tito\.m2\repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;C:\Documents and Settings\Tito\.m2\repository\xerces\xercesImpl\2.4.0\xercesImpl-2.4.0.jar
java.vm.specification.version = 1.0
sun.arch.data.model = 32
java.home = C:\Archivos de programa\Java\jre1.6.0_03
java.specification.vendor = Sun Microsystems Inc.
user.language = es
awt.toolkit = sun.awt.windows.WToolkit
java.vm.info = mixed mode, sharing
java.version = 1.6.0_03
java.ext.dirs = C:\Archivos de programa\Java\jre1.6.0_03\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
sun.boot.class.path = C:\Archivos de programa\Java\jre1.6.0_03\lib\resources.jar;C:\Archivos de programa\Java\jre1.6.0_03\lib\rt.jar;C:\Archivos de programa\Java\jre1.6.0_03\lib\sunrsasign.jar;C:\Archivos de programa\Java\jre1.6.0_03\lib\jsse.jar;C:\Archivos de programa\Java\jre1.6.0_03\lib\jce.jar;C:\Archivos de programa\Java\jre1.6.0_03\lib\charsets.jar;C:\Archivos de programa\Java\jre1.6.0_03\classes
java.vendor = Sun Microsystems Inc.
file.separator = \
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
sun.cpu.endian = little
sun.io.unicode.encoding = UnicodeLittle
sun.desktop = windows
sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
Reporter: José Arrarte
Firing this rule:
rule "Test Rule"
when
$dec : java.math.BigDecimal() from java.math.BigDecimal.TEN;
eval( $dec.compareTo(java.math.BigDecimal.ONE) > 0 )
then
System.out.println("OK!");
end
Returns this error:
org.drools.RuntimeDroolsException: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.math.BigDecimal
at org.drools.rule.EvalCondition.isAllowed(EvalCondition.java:76)
at org.drools.reteoo.EvalConditionNode.assertTuple(EvalConditionNode.java:145)
at org.drools.reteoo.SingleTupleSinkAdapter.propagateAssertTuple(SingleTupleSinkAdapter.java:20)
at org.drools.reteoo.FromNode.assertTuple(FromNode.java:90)
at org.drools.reteoo.SingleTupleSinkAdapter.createAndPropagateAssertTuple(SingleTupleSinkAdapter.java:55)
at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:116)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:22)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
at org.drools.reteoo.Rete.assertObject(Rete.java:175)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:192)
at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute(ReteooWorkingMemory.java:179)
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1315)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:433)
at com.sample.DroolsTest.main(DroolsTest.java:33)
Caused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.math.BigDecimal
at com.sample.Rule_Test_Rule_0Eval0Invoker.evaluate(Rule_Test_Rule_0Eval0Invoker.java:12)
at org.drools.rule.EvalCondition.isAllowed(EvalCondition.java:72)
... 14 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
17 years, 9 months
[JBoss JIRA] Created: (EJBTHREE-1153) Client container needs an java:comp/ORB binding
by Scott M Stark (JIRA)
Client container needs an java:comp/ORB binding
-----------------------------------------------
Key: EJBTHREE-1153
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1153
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Scott M Stark
Fix For: AS 5.0.0.CR1
EE.5.11ORB References
Some Java EE applications will need to make use of the CORBA ORB to perform certain operations. Such applications can find an appropriate object implementing the ORB interface by looking up the JNDI name java:comp/ORB or by requesting injection of an ORB object. The container is required to provide the java:comp/ORB name for all components except applets. Any such reference to a ORB object is only valid within the component instance that performed the lookup.
The following example illustrates how an application component acquires and uses an ORB object via injection.
@Resource ORB orb;
public void method(...) {
...
// Get the POA to use when creating object references.
POA rootPOA = (POA)orb.resolve_initial_references("RootPOA");
...
}
The following example illustrates how an application component acquires and uses an ORB object using a JNDI lookup.
public void method(...) {
...
// Obtain the default initial JNDI context.
Context initCtx = new InitialContext();
// Look up the ORB object.
ORB orb = (ORB)initCtx.lookup("java:comp/ORB");
// Get the POA to use when creating object references.
POA rootPOA = (POA)orb.resolve_initial_references("RootPOA");
--
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
[JBoss JIRA] Created: (JBMESSAGING-1172) Implement JDBCPersistenceManager
by Tim Fox (JIRA)
Implement JDBCPersistenceManager
--------------------------------
Key: JBMESSAGING-1172
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1172
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tyronne Wickramarathne
Fix For: 2.0.0 Beta
Although JDBC is not the main form of message persistence in JBM 2.0, we still need a JDBC PersistenceManager implementation, mainly we so we can work out of the box in the distro, without switching to the BDB persistence manager which we can't distribute due to licensing restrictions.
The JDBCPersistenceManager should use Hibernate dialects so we don't have to maintain separate configuration for each database.
The implementation should use two tables to store the message data, one for messages and one for message references. This would probably have a very similar structure to the JBM_MSG and JBM_MSG_REF tables currently used in JBM 1.4.
--
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
