August 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1058) XAResource should have its timeout value resetted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1058?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1058: ------------------------------------------------ Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 999522|https://bugzilla.redhat.com/show_bug.cgi?id=999522] from POST to MODIFIED > XAResource should have its timeout value resetted > ------------------------------------------------- > > Key: JBJCA-1058 > URL: https://issues.jboss.org/browse/JBJCA-1058 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.19.Final, 1.1.0.CR1 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.20.Final, 1.1.0.CR2 > > > Once the connection is returned to the pool -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1070) Memory leak if hashCode of Transaction isn't stable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1070?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1070: ------------------------------------------------ Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 999522|https://bugzilla.redhat.com/show_bug.cgi?id=999522] from POST to MODIFIED > Memory leak if hashCode of Transaction isn't stable > --------------------------------------------------- > > Key: JBJCA-1070 > URL: https://issues.jboss.org/browse/JBJCA-1070 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.19.Final, 1.1.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.20.Final, 1.1.1.Final > > > Happens in TransactionSynchronizer -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1521) Deployment runtime-name is not being handled properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1521?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1521: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 964446|https://bugzilla.redhat.com/show_bug.cgi?id=964446] from ASSIGNED to MODIFIED > Deployment runtime-name is not being handled properly > ----------------------------------------------------- > > Key: WFLY-1521 > URL: https://issues.jboss.org/browse/WFLY-1521 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha4 > > > In case archive is deployed with runtime name that does not match archive name, it breaks CLI/GUI commands. > [standalone@localhost:9999 /] deploy --runtime-name=nnn.ear /home/baranowb/redhat/git/jboss-as-quickstart/ejb-in-ear/ear/target/jboss-as-ejb-in-ear-ear-xxxx.ear > [standalone@localhost:9999 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear/subdeployment=jboss-as-ejb-in-ear-ejb.jar/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(include-runtime=true) > { > "outcome" => "failed", > "rolled-back" => true > } > 14:05:23,235 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014612: Operation ("read-attribute") failed - address: ([ > ("deployment" => "jboss-as-ejb-in-ear-ear-xxxx.ear"), > ("subdeployment" => "jboss-as-ejb-in-ear-ejb.jar"), > ("subsystem" => "ejb3"), > ("stateful-session-bean" => "GreeterEJB") > ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.deployment.subunit."jboss-as-ejb-in-ear-ear-xxxx.ear"."jboss-as-ejb-in-ear-ejb.jar".component.GreeterEJB.START not found > at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:448) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT] > at org.jboss.as.ejb3.subsystem.deployment.AbstractRuntimeMetricsHandler.executeRuntimeStep(AbstractRuntimeMetricsHandler.java:69) > at > .... > However some seem unaffected: > [standalone@localhost:9990 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear:read-resource > { > "outcome" => "success", > "result" => { > "content" => [{"hash" => bytes { > 0x5c, 0x22, 0x14, 0x99, 0xff, 0x23, 0x45, 0xfc, > 0x15, 0xaf, 0x1b, 0x97, 0x8c, 0x14, 0x75, 0x06, > 0xa2, 0xeb, 0xfb, 0x58 > }}], > "enabled" => true, > "name" => "jboss-as-ejb-in-ear-ear-xxxx.ear", > "persistent" => true, > "runtime-name" => "nnn.ear", > "subsystem" => undefined, > "subdeployment" => { > "jboss-as-ejb-in-ear-web.war" => undefined, > "jboss-as-ejb-in-ear-ejb.jar" => undefined > } > } > } > [standalone@localhost:9990 /] -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1754) Cannot restart webapp bundle after activation failure

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1754?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1754: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from POST to MODIFIED > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: WFLY-1754 > URL: https://issues.jboss.org/browse/WFLY-1754 > Project: WildFly > Issue Type: Bug > Reporter: Thomas Diesler > Assignee: Emmanuel Hugonnet > > {code} > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) > at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) > at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) > {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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1978) undertow endless processing of jsp rendering

by Thomas Frühbeck (JIRA)

[ https://issues.jboss.org/browse/WFLY-1978?page=com.atlassian.jira.plugin.... ] Thomas Frühbeck commented on WFLY-1978: --------------------------------------- The reason seem to have been a bad character. During SQL import of data a german 'ß' (%DF) has been imported with wrong charset - UTF8 I assume. Rendering looped endless on this string. > undertow endless processing of jsp rendering > -------------------------------------------- > > Key: WFLY-1978 > URL: https://issues.jboss.org/browse/WFLY-1978 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Reporter: Thomas Frühbeck > Assignee: Stuart Douglas > Attachments: Undertow_servlet_spec_Loop.html.gz > > > a working jsp page takes infinite time to render on some condition - reason unclear. > Profiler CPU breakdown attached. -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1978) undertow endless processing of jsp rendering

by Thomas Frühbeck (JIRA)

[ https://issues.jboss.org/browse/WFLY-1978?page=com.atlassian.jira.plugin.... ] Thomas Frühbeck updated WFLY-1978: ---------------------------------- Attachment: Undertow_servlet_spec_Loop.html.gz jprofiler cpu chart when looping > undertow endless processing of jsp rendering > -------------------------------------------- > > Key: WFLY-1978 > URL: https://issues.jboss.org/browse/WFLY-1978 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Reporter: Thomas Frühbeck > Assignee: Stuart Douglas > Attachments: Undertow_servlet_spec_Loop.html.gz > > > a working jsp page takes infinite time to render on some condition - reason unclear. > Profiler CPU breakdown attached. -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1978) undertow endless processing of jsp rendering

by Thomas Frühbeck (JIRA)

Thomas Frühbeck created WFLY-1978: ------------------------------------- Summary: undertow endless processing of jsp rendering Key: WFLY-1978 URL: https://issues.jboss.org/browse/WFLY-1978 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 8.0.0.Beta1 Reporter: Thomas Frühbeck Assignee: Stuart Douglas a working jsp page takes infinite time to render on some condition - reason unclear. Profiler CPU breakdown attached. -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-245) Drools sees a type as a package

by georg tornqvist (JIRA)

[ https://issues.jboss.org/browse/DROOLS-245?page=com.atlassian.jira.plugin... ] georg tornqvist edited comment on DROOLS-245 at 8/31/13 7:43 AM: ----------------------------------------------------------------- Here it comes! As you see the domain names of the imports are different from the original post. These are the original ones. Georg //created on: 26-aug-2013 package io31 import nl.zorgregistratie.www.azr._3_2.basisschema.schema._1_0.* import nl.zorgregistratie.www.azr._3_2.io31.schema._1_0.Client; import java.util.Date; //list any import classes here. //declare any global variables here global Date systeemDatum rule "Your First Rule" //dialect "mvel" ruleflow-group "rulegroepIO31" lock-on-active when exists Client() then System.out.println("############# Client met bsn is gevonden!! ##################"); end was (Author: gegtot): Here it comes! Georg //created on: 26-aug-2013 package io31 import nl.zorgregistratie.www.azr._3_2.basisschema.schema._1_0.* import nl.zorgregistratie.www.azr._3_2.io31.schema._1_0.Client; import java.util.Date; //list any import classes here. //declare any global variables here global Date systeemDatum rule "Your First Rule" //dialect "mvel" ruleflow-group "rulegroepIO31" lock-on-active when exists Client() then System.out.println("############# Client met bsn is gevonden!! ##################"); end > Drools sees a type as a package > -------------------------------- > > Key: DROOLS-245 > URL: https://issues.jboss.org/browse/DROOLS-245 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: georg tornqvist > Assignee: Mark Proctor > > Hi, > I want Drools to reason over an axis2 type, but the Drools compiler sees the type as a package, see error message below. > Strictly speaking, the Drools compiler may be right. The type "Client" encapsulates a "Factory" class, making hierarchically speaking the class "Client" a package. > Although I'm fairly new to Drools, I'm pretty sure that the behavior I'm experiencing is not right. The Drools version used in the WSO2BRS-2.0.0 is able to reason over the very same axis2 types. > Error importing : 'nl.domain.www.schema.Client' > Rule Compilation error : [Rule name='Your First Rule'] > io31/Rule_Your_First_Rule_16db2a632a4b4efd96dde4c6d6a55cdf.java (2:57) : Only a type can be imported. > nl.domain.www.schema.Client resolves to a package -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-245) Drools sees a type as a package

by georg tornqvist (JIRA)

[ https://issues.jboss.org/browse/DROOLS-245?page=com.atlassian.jira.plugin... ] georg tornqvist commented on DROOLS-245: ---------------------------------------- Here it comes! Georg //created on: 26-aug-2013 package io31 import nl.zorgregistratie.www.azr._3_2.basisschema.schema._1_0.* import nl.zorgregistratie.www.azr._3_2.io31.schema._1_0.Client; import java.util.Date; //list any import classes here. //declare any global variables here global Date systeemDatum rule "Your First Rule" //dialect "mvel" ruleflow-group "rulegroepIO31" lock-on-active when exists Client() then System.out.println("############# Client met bsn is gevonden!! ##################"); end > Drools sees a type as a package > -------------------------------- > > Key: DROOLS-245 > URL: https://issues.jboss.org/browse/DROOLS-245 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: georg tornqvist > Assignee: Mark Proctor > > Hi, > I want Drools to reason over an axis2 type, but the Drools compiler sees the type as a package, see error message below. > Strictly speaking, the Drools compiler may be right. The type "Client" encapsulates a "Factory" class, making hierarchically speaking the class "Client" a package. > Although I'm fairly new to Drools, I'm pretty sure that the behavior I'm experiencing is not right. The Drools version used in the WSO2BRS-2.0.0 is able to reason over the very same axis2 types. > Error importing : 'nl.domain.www.schema.Client' > Rule Compilation error : [Rule name='Your First Rule'] > io31/Rule_Your_First_Rule_16db2a632a4b4efd96dde4c6d6a55cdf.java (2:57) : Only a type can be imported. > nl.domain.www.schema.Client resolves to a package -- 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

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1920) Access control constraints for the audit logging resources

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1920?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved WFLY-1920. ------------------------------ Resolution: Done > Access control constraints for the audit logging resources > ---------------------------------------------------------- > > Key: WFLY-1920 > URL: https://issues.jboss.org/browse/WFLY-1920 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > Currently the constraints related to audit logging don't do anything -- they are just stubs written pending the audit logging patch. So these need completion. > I believe this is just implementing the TODOs in AuditConstraint and NonAuditConstraint and then updating the tests to check the roles work properly. I envisioned the TODO as being a simple test of the target resource address, i.e. does it start with /host=*/core-service=management/access=audit. -- 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

7 years, 6 months

1
0
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2013