April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8780) "No original methods found" error when deploying EJBs that extend base classes

by Richard Kennard (JIRA)

"No original methods found" error when deploying EJBs that extend base classes ------------------------------------------------------------------------------ Key: JBAS-8780 URL: https://issues.jboss.org/browse/JBAS-8780 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.Final Reporter: Richard Kennard Assignee: Ales Justin Priority: Critical An error, new to JBoss 6 (works okay in JBoss 5.1.0)... "java.lang.IllegalStateException: No original methods found" ...halts deployment when you try to deploy an EJB that subclasses a base class with public methods. For example, if you have a base class 'PersistentEntityBean' that has a bunch of methods related to loading/saving/deleting, and then you extend that base class with 'EmployerBean' simply to override loading/saving (but without adding any extra methods), it will fail to deploy. A workaround (from the forum) appears to be to override *every* subclassed method and just call 'super'. However this error even occurs for public final methods, which clearly cannot be overridden. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
26
0 / 0

[JBoss JIRA] Created: (JBAS-9292) Show effective ports for server configurations

by Heiko Braun (JIRA)

Show effective ports for server configurations ---------------------------------------------- Key: JBAS-9292 URL: https://issues.jboss.org/browse/JBAS-9292 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1849) Byte messages redelivered incorrectly if DefaultRedeliveryDelay=0 used

by Doug Grove (JIRA)

Byte messages redelivered incorrectly if DefaultRedeliveryDelay=0 used ---------------------------------------------------------------------- Key: JBMESSAGING-1849 URL: https://issues.jboss.org/browse/JBMESSAGING-1849 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.7.GA Reporter: Doug Grove Priority: Minor Attachments: test-queue-service.xml If DefaultRedeliveryDelay is set to 0 in messaging-service.xml (which is the default value) and the first delivery attempt fails, then all subsequent redeliveries (up to DefaultMaxDeliveryAttempts) are wrong. The result in redelivery is that the byte array returned from BytesMessage.readBytes(byte[]) contains only zeros (the length of the array is correct). Setting DefaultRedeliveryDelay to a value of 1 produces the expected behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1908) updated Drools docs content from SOA 4.2.CP03 Rules Guide

by Darrin Mison (JIRA)

updated Drools docs content from SOA 4.2.CP03 Rules Guide --------------------------------------------------------- Key: JBRULES-1908 URL: https://jira.jboss.org/jira/browse/JBRULES-1908 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs-expert Reporter: Darrin Mison Assignee: Mark Proctor I revised the language of the "Insertion" section while fixing a couple of reported grammatical errors for the 4.2.CP03 SOA Rules Guide. The original language is the same in: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... , so these changes would also apply to the most recent docs. Updated content below, the section ids are different but you get the idea ;-) <section id="sect-JBoss_Rules_Reference_Manual-WorkingMemory_and_StatefulStateless_Sessions-Insertion"> <title>Insertion</title> <para> <firstterm>Insertion</firstterm> is the act of telling the WorkingMemory about the facts. </para> <important> <para> In many Expert Systems the term used for this concept is <firstterm>assert</firstterm> or <firstterm>assertion</firstterm>. However as the keyword <methodname>assert</methodname> is already used in many languages, Drools uses the keyword & term <methodname>insert</methodname>. You will often encounter these terms used interchangably in discussion of Rules Engines. </para> </important> <para> When inserted, the rule is examined for matches against the rules. The work of determining what rules to fire is done during insertion, but no rules are executed at this time. The rules are executed when <methodname>fireAllRules()</methodname> is called, and it should only be called after you have inserted all your facts. </para> <para> It is a common misconception that rule matching occurs when <methodname>fireAllRules()</methodname> is called. </para> <para> When an Object is inserted it returns a FactHandle. This FactHandle is the token used to represent your inserted Object inside the WorkingMemory, it is also how you will interact with the Working Memory when you wish to retract or modify an object. </para> <programlisting language="java">Cheese stilton = new Cheese("stilton"); FactHandle stiltonHandle = session.insert( stilton );</programlisting> <para> As mentioned in <xref linkend="sect-JBoss_Rules_Reference_Manual-The_Drools_Rule_Engine-RuleBase" /> a Working Memory can operate in two assertions modes: <firstterm>equality</firstterm> and <firstterm>identity</firstterm>. Identity is the default mode. The assertion mode determines how the Working Memory stores the facts and how it compares the newly inserted fact to previously inserted ones. If the Working Memory determines the fact to "be the same" as an already inserted one it will ignore the new fact and return the FactHandle for the previously inserted one. </para> <variablelist> <varlistentry> <term>Identity</term> <listitem> <para> Identity Mode uses an <classname>IdentityHashMap</classname>to store all asserted Objects. New facts being inserted are compared to existing facts "by reference". A new FactHandle will be returned if the object being inserted is not a reference to an object that has been inserted previously. </para> </listitem> </varlistentry> <varlistentry> <term>Equality</term> <listitem> <para> Equality Mode uses a <classname>HashMap</classname> to store all asserted Objects. New facts being inserted are compared to existing facts "by value". A new FactHandle will be returned if the content of the object is not identical to that of a previously inserted object. </para> </listitem> </varlistentry> </variablelist> </section> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2112) Cannot build Drools IDE w/ OpenJDK 6 (vm crashes)

by Nick Boldt (JIRA)

Cannot build Drools IDE w/ OpenJDK 6 (vm crashes) ------------------------------------------------- Key: JBRULES-2112 URL: https://jira.jboss.org/jira/browse/JBRULES-2112 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Boldt Assignee: Mark Proctor Drools 5.0.x can compile with OpenJDK6; Drools 5.1 cannot. See attached logs. This prevents the JBoss Tools build from being able to run locally on Fedora w/ the out-of-box JVM (Open JDK 6). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-9032) @EJB injection with same "name" on two different fields leads to DuplicateServiceException

by jaikiran pai (JIRA)

@EJB injection with same "name" on two different fields leads to DuplicateServiceException ------------------------------------------------------------------------------------------ Key: JBAS-9032 URL: https://issues.jboss.org/browse/JBAS-9032 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Environment: JBoss AS7 master, JBoss AS 7.0 Beta1 Reporter: jaikiran pai Consider this servlet (or any other component): {code} public class MyServlet extends HttpServlet { @EJB (name="simpleName", beanName="SomeEJB") private SomeEJB bean; @EJB (name="simpleName", beanName="SomeEJB") private SomeEJB beanAgain; ... } {code} Notice that both the @EJB injection points expect the bean to be injected from bean in ENC at java:comp/env/simpleName. This however, leads to exception during deployment with the following message: {code} 16:06:43,846 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."myejbapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."myejbapp.war".INSTALL: Failed to process phase INSTALL of deployment "myejbapp.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.module.myejbapp.myejbapp.env/simpleName is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:143) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (LOGTOOL-15) Sources get generated in the target/classes directory with maven

by James Perkins (JIRA)

Sources get generated in the target/classes directory with maven ---------------------------------------------------------------- Key: LOGTOOL-15 URL: https://issues.jboss.org/browse/LOGTOOL-15 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.Beta6 The sources should be created in target/generated-sources, but get created in the target/classes directory if the target on the compiler is not set to 1.6. See if there is a way to always generate sources in a default directory rather than relying on the target version being set. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7427) AS won't boot with sun jmx enabled

by Jonathan Halliday (JIRA)

AS won't boot with sun jmx enabled ---------------------------------- Key: JBAS-7427 URL: https://jira.jboss.org/jira/browse/JBAS-7427 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Environment: sun jdk6, fedora, AS trunk r96005 Reporter: Jonathan Halliday Assignee: David Lloyd Fix For: JBossAS-6.0.0.Alpha1 [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_16/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar ========================================================================= Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@214a55f2, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") ... Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@5c1ae90c, cause: java.lang.AbstractMethodError -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-9308) Either implement or remove DomainUpdateListener

by Brian Stansberry (JIRA)

Either implement or remove DomainUpdateListener ----------------------------------------------- Key: JBAS-9308 URL: https://issues.jboss.org/browse/JBAS-9308 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Blocker Fix For: 7.0.0.CR1 The DomainUpdateListener stuff in controller-client got disabled in the move to the detyped API. It needs to either be implemented properly or removed from the API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
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 2011