April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6824) jboss-as-cli_1_2.xsd targets 1.1 namespace

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-6824: -------------------------------------- Summary: jboss-as-cli_1_2.xsd targets 1.1 namespace Key: AS7-6824 URL: https://issues.jboss.org/browse/AS7-6824 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.3.Final (EAP) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 8.0.0.Alpha1 The jboss-as-cli_1_2.xsd targets the 1.1 namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1611) Update logging to follow TAG-2 message format

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/JGRP-1611?page=com.atlassian.jira.plugin.... ] Jason Greene updated JGRP-1611: ------------------------------- Fix Version/s: (was: 3.2) > Update logging to follow TAG-2 message format > --------------------------------------------- > > Key: JGRP-1611 > URL: https://issues.jboss.org/browse/JGRP-1611 > Project: JGroups > Issue Type: Task > Reporter: James Perkins > Assignee: Bela Ban > Priority: Minor > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1475) Convert project to use i18n logging and exceptions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/JGRP-1475?page=com.atlassian.jira.plugin.... ] Jason Greene commented on JGRP-1475: ------------------------------------ I dont think we can call this done if it doesnt meet the TAG-2 message format. You could call it rejected though :) > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: JGRP-1475 > URL: https://issues.jboss.org/browse/JGRP-1475 > Project: JGroups > Issue Type: Task > Reporter: James Perkins > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2 > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1475) Convert project to use i18n logging and exceptions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/JGRP-1475?page=com.atlassian.jira.plugin.... ] Jason Greene reopened JGRP-1475: -------------------------------- > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: JGRP-1475 > URL: https://issues.jboss.org/browse/JGRP-1475 > Project: JGroups > Issue Type: Task > Reporter: James Perkins > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2 > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6755) JaxRsComponentDeployer should use GetRestful.getSubResourceClasses()

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/AS7-6755?page=com.atlassian.jira.plugin.s... ] Weinan Li commented on AS7-6755: -------------------------------- Hi Stuart, I've submitted the PR here: https://github.com/jbossas/jboss-eap/pull/88/files Could you please help to check if my modifications are enough? Thanks! > JaxRsComponentDeployer should use GetRestful.getSubResourceClasses() > -------------------------------------------------------------------- > > Key: AS7-6755 > URL: https://issues.jboss.org/browse/AS7-6755 > Project: Application Server 7 > Issue Type: Feature Request > Components: REST > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-93) Building rule file that contains event declaration with @duration ends with NPE

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-93?page=com.atlassian.jira.plugin.... ] Petr Široký updated DROOLS-93: ------------------------------ Description: Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). The rule file looks like this: {code} package org.jboss.drools.example.kbase declare org.jboss.drools.example.kbase.SimpleFact @role(event) @duration(duration) end {code} Exception thrown when building the file: {code} java.lang.NullPointerException at org.drools.compiler.compiler.PackageBuilder.processTypeFields(PackageBuilder.java:2206) at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2123) at org.drools.compiler.compiler.PackageBuilder.mergePackage(PackageBuilder.java:1254) at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2000) at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:273) at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:249) at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:87) at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:76) at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:140) at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:39) at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:207) at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:160) at org.kie.internal.utils.KieHelper.build(KieHelper.java:25) {code} was: Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). The rule file looks like this: {code} package org.jboss.drools.example.kbase declare org.jboss.drools.example.kbase.SimpleFact @role(event) @duration(duration) end {code} > Building rule file that contains event declaration with @duration ends with NPE > ------------------------------------------------------------------------------- > > Key: DROOLS-93 > URL: https://issues.jboss.org/browse/DROOLS-93 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Alpha1 > Reporter: Petr Široký > Assignee: Mark Proctor > Attachments: drools93-reproducer.zip > > > Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). > The rule file looks like this: > {code} > package org.jboss.drools.example.kbase > declare org.jboss.drools.example.kbase.SimpleFact > @role(event) > @duration(duration) > end > {code} > Exception thrown when building the file: > {code} > java.lang.NullPointerException > at org.drools.compiler.compiler.PackageBuilder.processTypeFields(PackageBuilder.java:2206) > at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2123) > at org.drools.compiler.compiler.PackageBuilder.mergePackage(PackageBuilder.java:1254) > at org.drools.compiler.compiler.PackageBuilder.processTypeDeclarations(PackageBuilder.java:2000) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:273) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildTypeDeclarations(CompositeKnowledgeBuilderImpl.java:249) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:87) > at org.drools.compiler.compiler.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:76) > at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:140) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:39) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:207) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:160) > at org.kie.internal.utils.KieHelper.build(KieHelper.java:25) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-93) Building rule file that contains event declaration with @duration ends with NPE

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-93?page=com.atlassian.jira.plugin.... ] Petr Široký updated DROOLS-93: ------------------------------ Attachment: drools93-reproducer.zip Simple maven reproducer attached. > Building rule file that contains event declaration with @duration ends with NPE > ------------------------------------------------------------------------------- > > Key: DROOLS-93 > URL: https://issues.jboss.org/browse/DROOLS-93 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Alpha1 > Reporter: Petr Široký > Assignee: Mark Proctor > Attachments: drools93-reproducer.zip > > > Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). > The rule file looks like this: > {code} > package org.jboss.drools.example.kbase > declare org.jboss.drools.example.kbase.SimpleFact > @role(event) > @duration(duration) > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-93) Building rule file that contains event declaration with @duration ends with NPE

by Petr Široký (JIRA)

Petr Široký created DROOLS-93: --------------------------------- Summary: Building rule file that contains event declaration with @duration ends with NPE Key: DROOLS-93 URL: https://issues.jboss.org/browse/DROOLS-93 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Alpha1 Reporter: Petr Široký Assignee: Mark Proctor Building kbase with simple rule file with event declaration that has a @duration attribute ends with NPE. When the @duration is removed, file is built correctly. See attached maven reproducer (just run mvn test). The rule file looks like this: {code} package org.jboss.drools.example.kbase declare org.jboss.drools.example.kbase.SimpleFact @role(event) @duration(duration) end {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6086) Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6086?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6086: ---------------------------------------------- Tushar Gandotra <tgandotr(a)redhat.com> changed the Status of [bug 922340|https://bugzilla.redhat.com/show_bug.cgi?id=922340] from VERIFIED to CLOSED > Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > --------------------------------------------------------------------------------------- > > Key: AS7-6086 > URL: https://issues.jboss.org/browse/AS7-6086 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 7.1.3.Final (EAP) > Environment: Doesn't matter. > Reporter: Krzysztof Noceń > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > Class: > {code} > org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > {code} > Method: > {code} > public void processMessage(ChannelAssociation, MessageInputStream) throws IOException; > {code} > This code fragment: > {code} > try { > methodParams[i] = unmarshaller.readObject(); > } catch (ClassNotFoundException cnfe) { > /.../ > return; > } > {code} > doesn't catch *java.lang.IllegalArgumentException*. > This causes the server hangs. > Example stacktrace: > {code} > java.lang.IllegalArgumentException: No enum const org.example.ExampleEnum.ENUM_VALUE > at java.lang.Enum.valueOf(Enum.java:196) > at org.jboss.marshalling.river.RiverUnmarshaller.resolveEnumConstant(RiverUnmarshaller.java:1549) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1293) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:164) > at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:182) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:429) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > {code} > I caught *java.lang.Exception*. It helps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6086) Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6086?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6086: ---------------------------------------------- Tushar Gandotra <tgandotr(a)redhat.com> made a comment on [bug 922340|https://bugzilla.redhat.com/show_bug.cgi?id=922340] This patch is applicable to JBoss Enterprise Application Platform (EAP) 6.0.1. It is available for download from the following location: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > --------------------------------------------------------------------------------------- > > Key: AS7-6086 > URL: https://issues.jboss.org/browse/AS7-6086 > Project: Application Server 7 > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 7.1.3.Final (EAP) > Environment: Doesn't matter. > Reporter: Krzysztof Noceń > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > Class: > {code} > org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler > {code} > Method: > {code} > public void processMessage(ChannelAssociation, MessageInputStream) throws IOException; > {code} > This code fragment: > {code} > try { > methodParams[i] = unmarshaller.readObject(); > } catch (ClassNotFoundException cnfe) { > /.../ > return; > } > {code} > doesn't catch *java.lang.IllegalArgumentException*. > This causes the server hangs. > Example stacktrace: > {code} > java.lang.IllegalArgumentException: No enum const org.example.ExampleEnum.ENUM_VALUE > at java.lang.Enum.valueOf(Enum.java:196) > at org.jboss.marshalling.river.RiverUnmarshaller.resolveEnumConstant(RiverUnmarshaller.java:1549) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1293) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:164) > at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:182) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:429) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > {code} > I caught *java.lang.Exception*. It helps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013