April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JASSIST-165) VerifyError with addLocalVariable() and insertAfter() when the method body is in a try catch statement

by Hua Zhang (JIRA)

Hua Zhang created JASSIST-165: --------------------------------- Summary: VerifyError with addLocalVariable() and insertAfter() when the method body is in a try catch statement Key: JASSIST-165 URL: https://issues.jboss.org/browse/JASSIST-165 Project: Javassist Issue Type: Bug Affects Versions: 3.16.1-GA Environment: JDK 1.6, javassist3.16.1_GA Reporter: Hua Zhang Assignee: Shigeru Chiba Priority: Blocker CtClass cc = pool.get(className); CtMethod theMethod = ...; cc.defrost(); theMethod.addLocalVariable("__t", pool.get("long")); theMethod.insertBefore("{long __t = System.nanoTime();}"); theMethod.insertAfter("{System.out.println(System.nanoTime() - __t);}"); cc.freeze(); byte[] classFile = cc.toBytecode(); swapper.reload(className, classFile); // swapper is javassist.util.HotSwapper This code snippet can work for the method which doesn't contain try catch statement. However, if the method likes this: public void method(...) { try { ...... } catch (Exception e) { } } Error thrown: Exception in thread "HotSwap" java.lang.VerifyError: verifier detected internal inconsistency or security problem It is because __t is not visible in insertAfter() in this case. If modify the statement "theMethod.insertAfter("{System.out.println(System.nanoTime() - __t);}");" to be "theMethod.insertAfter("{System.out.println(System.nanoTime());}");" ( it removes the reference to variable __t), the code can work properly. Note I use insertAfter(String), not insertAfter(String, true). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
3
0 / 0

[JBoss JIRA] (AS7-4427) jboss-javaee6-webapp-archetype : upgrade hibernate-jpamodelgen and hibernate-jpa-2.0-api for .factorypath

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/AS7-4427?page=com.atlassian.jira.plugin.s... ] Fred Bricon moved JBIDE-11503 to AS7-4427: ------------------------------------------ Project: Application Server 7 (was: Tools (JBoss Tools)) Key: AS7-4427 (was: JBIDE-11503) Issue Type: Enhancement (was: Feature Request) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: 3.3.0.Beta1) Assignee: Pete Muir (was: Fred Bricon) Component/s: (was: maven) > jboss-javaee6-webapp-archetype : upgrade hibernate-jpamodelgen and hibernate-jpa-2.0-api for .factorypath > --------------------------------------------------------------------------------------------------------- > > Key: AS7-4427 > URL: https://issues.jboss.org/browse/AS7-4427 > Project: Application Server 7 > Issue Type: Enhancement > Reporter: Fred Bricon > Assignee: Pete Muir > Attachments: factorypath.pdf > > > hibernate-jpamodelgen has version 1.1.1.Final, and version 1.2.0.Final is available. > hibernate-jpa-2.0-api has version 1.0.0.Final, and version 1.0.1.Final is available. > I'll attach a screenshot to illustrate the current settings for .factorypath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4423) Error when clustering queues in domain mode

by Kairi Henry (JIRA)

Kairi Henry created AS7-4423: -------------------------------- Summary: Error when clustering queues in domain mode Key: AS7-4423 URL: https://issues.jboss.org/browse/AS7-4423 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Environment: x86_64 GNU/Linux, java version "1.6.0_29", jboss 7.1.1 Reporter: Kairi Henry Assignee: Paul Ferraro When I configure the jms connections like below within the domain.xml. I am trying to have my queue recognize each other from to separate machines. <connector name="connector"> <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class> <param key="host" value="192.168.1.2"/> <param key="port" value="5445"/> </connector> -------------------------------- I get the following error. -------------------------------- [Server:blah-manager-server] 19:05:50,030 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 10) Operation ("add") failed - address: ([ [Server:blah-manager-server] ("subsystem" => "messaging"), [Server:blah-manager-server] ("hornetq-server" => "default"), [Server:blah-manager-server] ("connector" => "this_server_connector") [Server:blah-manager-server] ]) - failure description: "JBAS014746: factory-class may not be null" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] (JBRULES-3452) Bugs when refactoring class and field names in the eclipse plugin

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3452: ------------------------------------ Summary: Bugs when refactoring class and field names in the eclipse plugin Key: JBRULES-3452 URL: https://issues.jboss.org/browse/JBRULES-3452 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When the name of a java class (or one of its field) used in the DRLs is refactored, the corresponding name replacement in the DRLs themselves often makes them wrong/unusable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4424) mod_cluster to support custom JSESSION cookie name

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4424: ----------------------------------- Summary: mod_cluster to support custom JSESSION cookie name Key: AS7-4424 URL: https://issues.jboss.org/browse/AS7-4424 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Jean-Frederic Clere [~jfclere] jbossweb uses org.apache.catalina.JSESSIONID/jsessionid to set a different value, we should do the same. Workaround see https://community.jboss.org/message/728312#728312 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] (AS7-4418) Atrribute <factory-type> is not parsed correctly in configuration of connection-factory

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/AS7-4418?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on AS7-4418: ---------------------------------- Hi Jason, I started working on it in AS7-4394 > Atrribute <factory-type> is not parsed correctly in configuration of connection-factory > --------------------------------------------------------------------------------------- > > Key: AS7-4418 > URL: https://issues.jboss.org/browse/AS7-4418 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Labels: eap6_need_triage > Fix For: 7.1.2.Final-redhat1 > > > Attribute factory-type in configuration connection factory is not parsed correctly and default "CF" type is always used. > Following configuration should register XAConnectionFactory but attribute factory-type is ignored: > {code} > <connection-factory name="RemoteConnectionFactory"> > > <jms-connection-factories> > ... > <connection-factory name="RemoteConnectionFactory"> > <factory-type>XA_GENERIC</factory-type> > <connectors> > <connector-ref connector-name="netty"/> > </connectors> > <entries> > <entry name="RemoteConnectionFactory"/> > <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> > </entries> > <ha>true</ha> > </connection-factory> > ... > </jms-connection-factories> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (JBRULES-3451) Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph and warn about it

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3451: ----------------------------------------- Summary: Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph and warn about it Key: JBRULES-3451 URL: https://issues.jboss.org/browse/JBRULES-3451 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet See the screenshot of the difference between a good graph and a bad graph. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (AS7-4248) AS7 7.1.1.Final: java.lang.ClassCastException: org.jcp.xml.dsig.internal.dom.DOMXMLSignatureFactory cannot be cast to javax.xml.crypto.dsig.XMLSignatureFactory

by Gianluca Mazzaferro (JIRA)

Gianluca Mazzaferro created AS7-4248: ---------------------------------------- Summary: AS7 7.1.1.Final: java.lang.ClassCastException: org.jcp.xml.dsig.internal.dom.DOMXMLSignatureFactory cannot be cast to javax.xml.crypto.dsig.XMLSignatureFactory Key: AS7-4248 URL: https://issues.jboss.org/browse/AS7-4248 Project: Application Server 7 Issue Type: Bug Components: XML Frameworks Affects Versions: 7.1.1.Final Environment: jdk 1.6.0_31 Reporter: Gianluca Mazzaferro Assignee: Jason Greene Priority: Minor classcast solved by downgrade lib xmlsec-1.4.6.jar at module org\apache\santuario\xmlsec\main -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
4
0 / 0

[JBoss JIRA] (JBRULES-3436) missing closing brace cause IooB exception in Builder

by Wolfgang Laun (JIRA)

Wolfgang Laun created JBRULES-3436: -------------------------------------- Summary: missing closing brace cause IooB exception in Builder Key: JBRULES-3436 URL: https://issues.jboss.org/browse/JBRULES-3436 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.4.0.Beta2 Reporter: Wolfgang Laun Assignee: Mark Proctor For example: rule "get directory entries" when $d: Directory( $p: pathname, children == null ) then List kidFiles = browser.getEntries( $p ); modify( $d ){ setChildren( kidFiles ) ; ################################################ missing brace here end Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String index out of range: 88 at java.lang.String.substring(String.java:1934) at org.drools.rule.builder.dialect.DialectUtil.rewriteDescr(DialectUtil.java:581) at org.drools.rule.builder.dialect.DialectUtil.fixBlockDescr(DialectUtil.java:140) at org.drools.rule.builder.dialect.DialectUtil.fixBlockDescr(DialectUtil.java:98) at org.drools.rule.builder.dialect.asm.AbstractASMConsequenceBuilder.consequenceContext(AbstractASMConsequenceBuilder.java:44) at org.drools.rule.builder.dialect.asm.AbstractASMConsequenceBuilder.build(AbstractASMConsequenceBuilder.java:22) at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:99) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:2503) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:847) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:443) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:626) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:41) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] (JBRULES-3263) Implement evaluation of alpha nodes constraints with MVEL and ASM

by Mario Fusco (Created) (JIRA)

Implement evaluation of alpha nodes constraints with MVEL and ASM ----------------------------------------------------------------- Key: JBRULES-3263 URL: https://issues.jboss.org/browse/JBRULES-3263 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Replace the LiteralConstraint we have at the moment (based on a big number of very specialized Evaluators that imply a lot of code duplication) with one that only uses MVEL to evaluate the constraints in the alpha nodes. As a second step add a counter on each of this constraints and optimize the ones that are invoked more frequently by jitting them with ASM -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
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 April 2012