May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-331) Infinite loop in JBossAppMetaDataParser

by Stuart Douglas (JIRA)

Infinite loop in JBossAppMetaDataParser --------------------------------------- Key: JBMETA-331 URL: https://issues.jboss.org/browse/JBMETA-331 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ear Reporter: Stuart Douglas Priority: Critical JBossAppMetaDataParser goes into an infinite loop on line 143, as the next element is never read from the stream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-789) JPA subsystem: empty default DS

by Heiko Rupp (JIRA)

JPA subsystem: empty default DS ------------------------------- Key: AS7-789 URL: https://issues.jboss.org/browse/AS7-789 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Rupp Assignee: Jason Greene Resource description for the JPA subsystem says default-datasource is required [domain@localhost:9999 subsystem=jpa] :read-resource-description(include-runtime=true,recursive=true) { "outcome" => "success", "result" => { "description" => "The configuration of the JPA subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:jpa:1.0", "attributes" => {"default-datasource" => { "description" => "The name of the default global datasource.", "type" => STRING, "required" => true, "min-length" => 0, "access-type" => "read-write", "storage" => "configuration" }}, "operations" => undefined, "children" => undefined }, "compensating-operation" => undefined } But reading the resource shows an empty value This looks wrong, as an empty value is for sure no valid data source name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-716) "server-config/jvm<name>:remove()" creates inconsistent state

by Heiko Braun (JIRA)

"server-config/jvm<name>:remove()" creates inconsistent state ------------------------------------------------------------- Key: AS7-716 URL: https://issues.jboss.org/browse/AS7-716 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 After removing the jvm resource I get this: [domain@localhost:9999 /] /host=local/server-config=server-one:read-resource(recursive=true) { "outcome" => "success", "result" => { "path" => undefined, "system-property" => undefined, "interface" => undefined, "jvm" => {}, "socket-binding-group" => undefined, "socket-binding-port-offset" => undefined, "name" => "server-one", "group" => "main-server-group", "auto-start" => true }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-692) Ability to modify server-group, subresource jvm

by Heiko Braun (JIRA)

Ability to modify server-group, subresource jvm ----------------------------------------------- Key: AS7-692 URL: https://issues.jboss.org/browse/AS7-692 Project: Application Server 7 Issue Type: Feature Request Components: 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

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2976) DefaultMarshaller does not use supplied ObjectMarshallingStrategies

by Laird Nelson (JIRA)

DefaultMarshaller does not use supplied ObjectMarshallingStrategies ------------------------------------------------------------------- Key: JBRULES-2976 URL: https://issues.jboss.org/browse/JBRULES-2976 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.M1, 5.2.0.M2, 5.2.0.CR1 Reporter: Laird Nelson Assignee: Mark Proctor DefaultMarshaller.java does not use the supplied ObjectMarshallingStrategy as far as I can tell. When you create a Marshaller like this: {code} final Marshaller marshaller = MarshallerFactory.newMarshaller(knowledgeBase, new ObjectMarshallingStrategy[] { myStrategy }); assert marshaller != null; {code} And then use it like this (or similar): {code} final ByteArrayOutputStream baos = new ByteArrayOutputStream(); final ObjectOutputStream oos = new ObjectOutputStream(baos); final DroolsObjectOutputStream doos = new DroolsObjectOutputStream(oos); marshaller.marshall(doos, this.droolsSession); {code} ...the supplied strategy's read() and write() methods are never called. This is because DefaultMarshaller.java line 132 does not use the DefaultMarshaller's strategy, but the strategy of the incoming StatefulKnowledgeSession instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3034) CompositeMaxDurationTrigger is not determining times correctly

by Mark Proctor (JIRA)

CompositeMaxDurationTrigger is not determining times correctly -------------------------------------------------------------- Key: JBRULES-3034 URL: https://issues.jboss.org/browse/JBRULES-3034 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor the logic for CompositeMaxDurationTrigger is wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2796) NullPointerException in FromNode.destroyCreatedHandles

by Tommy Odom (JIRA)

NullPointerException in FromNode.destroyCreatedHandles ------------------------------------------------------ Key: JBRULES-2796 URL: https://jira.jboss.org/browse/JBRULES-2796 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Reporter: Tommy Odom Assignee: Mark Proctor I received this NullPointerException after upgrading to drools 5.1.1. The NullPointerException is being thrown when the rule executes "update($build);" where $build is set in the LHS from a Build in working memory. I'm not sure if the bug is that matches may be null and a null check needs to be added or if something else is going on causing the tuple to not be found. Caused by: java.lang.NullPointerException at org.drools.reteoo.FromNode.destroyCreatedHandles(FromNode.java:336) at org.drools.reteoo.FromNode.retractLeftTuple(FromNode.java:326) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateRetractLeftTuple(CompositeLeftTupleSinkAdapter.java:238) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.propagateRetractRightTuple(CompositeLeftTupleSinkAdapter.java:155) at org.drools.reteoo.JoinNode.retractRightTuple(JoinNode.java:151) at org.drools.reteoo.ModifyPreviousTuples.retractTuples(ModifyPreviousTuples.java:126) at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:176) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1442) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1349) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:183) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:196) at buildSchedulerV2.Rule_Combine_Builds_0.defaultConsequence(Rule_Combine_Builds_0.java:36) at buildSchedulerV2.Rule_Combine_Builds_0DefaultConsequenceInvoker.evaluate(Rule_Combine_Builds_0DefaultConsequenceInvoker.java:49) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] Commented: (JBWEB-11) 505 error when connection from a .NET client

by brian pemberton (JIRA)

[ https://issues.jboss.org/browse/JBWEB-11?page=com.atlassian.jira.plugin.s... ] brian pemberton commented on JBWEB-11: -------------------------------------- Douglas, Your solution worked well for me, thanks. Too bad that C# and JBoss don't play nice out of the box, but them is the breaks. Only the first two lines of your code are strictly necessary, I think. Thanks again. > 505 error when connection from a .NET client > -------------------------------------------- > > Key: JBWEB-11 > URL: https://issues.jboss.org/browse/JBWEB-11 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat > Affects Versions: JBossWeb embedded - AS 4.0.1 > Reporter: Thomas Diesler > Assignee: Remy Maucherat > > People with .NET clients have no luck connection to JBossWS since .NET defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? > See: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862668#3862668 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-768) Provide WebApp / OSGi integration example

by Thomas Diesler (JIRA)

Provide WebApp / OSGi integration example ----------------------------------------- Key: AS7-768 URL: https://issues.jboss.org/browse/AS7-768 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-767) Provide EJB3 / OSGi integration example

by Thomas Diesler (JIRA)

Provide EJB3 / OSGi integration example --------------------------------------- Key: AS7-767 URL: https://issues.jboss.org/browse/AS7-767 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011