February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5726) Using "attribute" tag causes injection of null values

by Anders Welen (JIRA)

[ https://issues.jboss.org/browse/AS7-5726?page=com.atlassian.jira.plugin.s... ] Anders Welen commented on AS7-5726: ----------------------------------- Hmm... Sorry I should have mention that it is when executing "undeploy" (or shutdown) as the problem shows as a warning. WARN [org.jboss.msc.inject] (MSC service thread 1-8) MSC000100: Unexpected failure to uninject public void Test.setText(java.lang.String): java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_27] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_27] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_27] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_27] at org.jboss.msc.inject.MethodInjector.uninject(MethodInjector.java:119) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StopTask.uninject(ServiceControllerImpl.java:1919) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1893) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27] Caused by: java.lang.NullPointerException: Parameter can not be null at Test.setText(Test.java:11) ... 10 more Why does the JMX impl. in JBoss 7 always try to inject NULL values into configured MBean attributes at undeployment? > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: AS7-5726 > URL: https://issues.jboss.org/browse/AS7-5726 > Project: Application Server 7 > Issue Type: Bug > Components: JMX > Affects Versions: 7.1.3.Final (EAP) > Reporter: Anders Welen > Assignee: Tomek Adamski > Priority: Minor > Fix For: Open To Community > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6568) TimerService.*SecondTestCase often fails intermittently

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6568?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-6568: ------------------------------------- I have not seen this outside your pull request. It looks more likely that something in the PR is breaking timer persistence, so the saved timers are not loaded when the server is started the second time. > TimerService.*SecondTestCase often fails intermittently > ------------------------------------------------------- > > Key: AS7-6568 > URL: https://issues.jboss.org/browse/AS7-6568 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.3.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > Two of the timer service tests in AS7 testsuite often fails due to a timeout. At least it looks like a timeout issue unless there is something else rotten in them. The tests wait 30s for the invocation of a timer which seems not to be sufficient sometimes. Need to say that 30s is a quite long timeout. It is weird. See the following PR for an example of such failures at the lightning. > https://github.com/jbossas/jboss-as/pull/4093 > Affected tests: > TimerServicePersistenceSecondTestCase.testTimerServiceCalled > TimerServiceSerializationSecondTestCase.testTimerServiceRestoredWithCorrectInfo > I will try to reproduce it on QE Hudson as the tests pass nicely when running locally on my laptop. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6627) TransactionTestCase.testUserTransaction failing intermittenly

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6627?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6627: ----------------------------- Affects Version/s: 7.2.0.Alpha1 8.0.0.Alpha1 > TransactionTestCase.testUserTransaction failing intermittenly > ------------------------------------------------------------- > > Key: AS7-6627 > URL: https://issues.jboss.org/browse/AS7-6627 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.2.0.Alpha1, 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Thomas Diesler > > org.jboss.as.test.integration.osgi.jta.TransactionTestCase quite often > {noformat} > java.lang.AssertionError: Service registered: javax.transaction.UserTransaction > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:621) > at org.jboss.as.test.osgi.FrameworkUtils.waitForServiceReference(FrameworkUtils.java:106) > at org.jboss.as.test.osgi.FrameworkUtils.waitForService(FrameworkUtils.java:81) > at org.jboss.as.test.osgi.FrameworkUtils.waitForService(FrameworkUtils.java:76) > at org.jboss.as.test.integration.osgi.jta.TransactionTestCase.testUserTransaction(TransactionTestCase.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > {noformat} > more info: > http://teamcity.cafe-babe.org/project.html?projectId=project2&buildTypeId... -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6627) TransactionTestCase.testUserTransaction failing intermittenly

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6627: -------------------------------- Summary: TransactionTestCase.testUserTransaction failing intermittenly Key: AS7-6627 URL: https://issues.jboss.org/browse/AS7-6627 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Tomaz Cerar Assignee: Thomas Diesler org.jboss.as.test.integration.osgi.jta.TransactionTestCase quite often {noformat} java.lang.AssertionError: Service registered: javax.transaction.UserTransaction at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertNotNull(Assert.java:621) at org.jboss.as.test.osgi.FrameworkUtils.waitForServiceReference(FrameworkUtils.java:106) at org.jboss.as.test.osgi.FrameworkUtils.waitForService(FrameworkUtils.java:81) at org.jboss.as.test.osgi.FrameworkUtils.waitForService(FrameworkUtils.java:76) at org.jboss.as.test.integration.osgi.jta.TransactionTestCase.testUserTransaction(TransactionTestCase.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) {noformat} more info: http://teamcity.cafe-babe.org/project.html?projectId=project2&buildTypeId... -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6626) Provide deployment manifest information via the CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6626?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6626: --------------------------------------- A possible place where this could fit would be the current CLI "deployment-info" command. Low-level management API support would of course be a pre-requisite. If work is begun on this, please create subtasks for the low-level work, the CLI work, and a task for console support. > Provide deployment manifest information via the CLI > --------------------------------------------------- > > Key: AS7-6626 > URL: https://issues.jboss.org/browse/AS7-6626 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Brian Stansberry > > We've gotten a user request for providing the contents of a deployment's MANIFEST.MF via the CLI. > The request is to include an option to get the manifest info for a single deployment, and also the info for all deployments. > This task needs to be evaluated in relationship to the larger request to provide read (and possibly in some cases write) access to all files within a deployment. The manifest is essentially just one file with a standard location. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6626) Provide deployment manifest information via the CLI

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6626: ------------------------------------- Summary: Provide deployment manifest information via the CLI Key: AS7-6626 URL: https://issues.jboss.org/browse/AS7-6626 Project: Application Server 7 Issue Type: Feature Request Components: CLI, Domain Management Reporter: Brian Stansberry We've gotten a user request for providing the contents of a deployment's MANIFEST.MF via the CLI. The request is to include an option to get the manifest info for a single deployment, and also the info for all deployments. This task needs to be evaluated in relationship to the larger request to provide read (and possibly in some cases write) access to all files within a deployment. The manifest is essentially just one file with a standard location. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5342) SAR MBean String attributes cannot be longer than about 3650 characters

by Tomek Adamski (JIRA)

[ https://issues.jboss.org/browse/AS7-5342?page=com.atlassian.jira.plugin.s... ] Tomek Adamski reassigned AS7-5342: ---------------------------------- Assignee: Tomek Adamski > SAR MBean String attributes cannot be longer than about 3650 characters > ----------------------------------------------------------------------- > > Key: AS7-5342 > URL: https://issues.jboss.org/browse/AS7-5342 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMX > Affects Versions: 7.1.1.Final > Reporter: John Mazzitelli > Assignee: Tomek Adamski > Labels: rhq > > I have a SAR. One of the MBean attributes is a String (actually, for my real use-case the value is a Properties object, but due to JIRA AS7-5336, there are other problems, but let's just go with String attribute type, because the same problem I will describe happens with that type, too) > If the string value is longer than around 3650 characters the beginning of the string is stripped (I can't nail it down to a specific value, but its around that number, give or take 10 characters or so) > For example, if I have this in jboss-service.xml: > <attribute name="MyStrAttrib"> > This is a really long string. > ...[lots of characters here]... > It has more than 3650 > characters in it. > </attribute> > What my MBean setter (setMyStrAttrib(String s)) will be passed is something like "aracters in it." The characters at index 0 through ~3650 are missing, I only have the parts after it. > In my real example, the reason why the string is so long is that its a Properties string with lots of name/value pairs. I ended up working around AS7-5336 but then I hit this issue. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5726) Using "attribute" tag causes injection of null values

by Tomek Adamski (JIRA)

[ https://issues.jboss.org/browse/AS7-5726?page=com.atlassian.jira.plugin.s... ] Tomek Adamski commented on AS7-5726: ------------------------------------ Cannot reproduce error. > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: AS7-5726 > URL: https://issues.jboss.org/browse/AS7-5726 > Project: Application Server 7 > Issue Type: Bug > Components: JMX > Affects Versions: 7.1.3.Final (EAP) > Reporter: Anders Welen > Assignee: Tomek Adamski > Priority: Minor > Fix For: Open To Community > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5726) Using "attribute" tag causes injection of null values

by Tomek Adamski (JIRA)

[ https://issues.jboss.org/browse/AS7-5726?page=com.atlassian.jira.plugin.s... ] Tomek Adamski edited comment on AS7-5726 at 2/25/13 3:18 PM: ------------------------------------------------------------- Cannot reproduce error: attributes are inserted correctly. was (Author: tomekadamski): Cannot reproduce error. > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: AS7-5726 > URL: https://issues.jboss.org/browse/AS7-5726 > Project: Application Server 7 > Issue Type: Bug > Components: JMX > Affects Versions: 7.1.3.Final (EAP) > Reporter: Anders Welen > Assignee: Tomek Adamski > Priority: Minor > Fix For: Open To Community > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-52) Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-52?page=com.atlassian.jira.plugin.... ] Geoffrey De Smet resolved DROOLS-52. ------------------------------------ Resolution: Done Fixed on master. http://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/693538735 Turns out that there's a very easy fix for this in the felix-maven-plugin: <configuration>  <excludeDependencies>true</excludeDependencies> </configuration> Note: the alternative, of converting the <Export-Package> to <Private-Package>, did not work. > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class > ---------------------------------------------------------------------- > > Key: DROOLS-52 > URL: https://issues.jboss.org/browse/DROOLS-52 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Blocker > > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class. > It looks like drools-compiler is fat jar. Fat jars (even shaded fat jars) are evil. See slide 39-42: > http://ge0ffrey.github.com/maven-dependency-puzzlers/maven-dependency-puz... > Certain platforms (android, ...) don't even allow to deploy such jars. Others (osgi, ...) throw warnings. -- 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

13 years, 2 months

1
0
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 February 2013