March 2012 - jboss-jira - Jboss List Archives

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-764: ------------------------------------- Summary: Checkstyle 5.5 Key: JBJCA-764 URL: https://issues.jboss.org/browse/JBJCA-764 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-763) Track component updates

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-763: ------------------------------------- Summary: Track component updates Key: JBJCA-763 URL: https://issues.jboss.org/browse/JBJCA-763 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4122) Adding a deployment scanner fails with NPE

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4122: ------------------------------- Summary: Adding a deployment scanner fails with NPE Key: AS7-4122 URL: https://issues.jboss.org/browse/AS7-4122 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Environment: EAP6, ER3 Reporter: Heiko Rupp Assignee: Brian Stansberry [standalone@localhost:9999 subsystem=deployment-scanner] ./scanner=foo:add(path=/tmp) { "outcome" => "failed", "failure-description" => {"JBAS014671: Failed services" => {"jboss.server.deployment.scanner.foo" => "org.jboss.msc.service.StartException in service jboss.server.deployment.scanner.foo: java.lang.NullPointerException"}}, "rolled-back" => true } server console log shows 14:26:24,968 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 5846ms - Started 134 of 205 services (70 services are passive or on-demand) 14:26:56,316 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.server.deployment.scanner.foo: org.jboss.msc.service.StartException in service jboss.server.deployment.scanner.foo: java.lang.NullPointerException at org.jboss.as.server.deployment.scanner.DeploymentScannerService.start(DeploymentScannerService.java:165) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [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) [classes.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] Caused by: java.lang.NullPointerException at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.establishDeployedContentList(FileSystemDeploymentService.java:289) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.establishDeployedContentList(FileSystemDeploymentService.java:293) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:195) at org.jboss.as.server.deployment.scanner.DeploymentScannerService.start(DeploymentScannerService.java:151) ... 5 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (JGRP-1425) FD_ALL : add specific interval for timeoutchecker task

by Francois Billard (JIRA)

Francois Billard created JGRP-1425: -------------------------------------- Summary: FD_ALL : add specific interval for timeoutchecker task Key: JGRP-1425 URL: https://issues.jboss.org/browse/JGRP-1425 Project: JGroups Issue Type: Enhancement Affects Versions: 3.x Reporter: Francois Billard Assignee: Bela Ban FD_ALL run 2 task : - task heartbeat_sender_future to send hearbeat - task timeout_checker_future to check timestamp of hearbeat received the thread interval parameter is the same for theses two tasks (FD_ALL.interval) when you have a long interval, the task timeoutchecker are discovering the loss of a member too late. the improvement is to decorrelate these two intervals to let timeoutchecker task stick the real member loss -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JGRP-1429) The timeout of VERIFY_SUSPECT protocol is not guaranteed

by Benoit Leblanc (JIRA)

Benoit Leblanc created JGRP-1429: ------------------------------------ Summary: The timeout of VERIFY_SUSPECT protocol is not guaranteed Key: JGRP-1429 URL: https://issues.jboss.org/browse/JGRP-1429 Project: JGroups Issue Type: Bug Affects Versions: 3.0.5 Reporter: Benoit Leblanc Assignee: Bela Ban The verification of a suspected member can take more than timeout. It depend of being followed closely by other suspected members or not. Let's timeout = 2000ms. - At T: Member A is suspected (by Failure Detection protocol). - At T + 1500ms: Member B is suspected too. Member A is declared as definitively dead 3500ms later. The "worst case" occurs when a continuous flow of suspected members arrive with an interval between 0 and 2000ms (timeout). Suspected members are never removed from view. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-4055) Re-creating a resource adapter fails with message: "JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.MyAdapter is already registered"

by Robert Reimann (JIRA)

Robert Reimann created AS7-4055: ----------------------------------- Summary: Re-creating a resource adapter fails with message: "JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.MyAdapter is already registered" Key: AS7-4055 URL: https://issues.jboss.org/browse/AS7-4055 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Reporter: Robert Reimann Assignee: Alexey Loubyansky Re-creating a resource adapter using (:add, :remove, :add) fails as shown below. {noformat} [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=MyAdapter:add(archive=my-adapter.ear) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=MyAdapter:remove {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=MyAdapter:add(archive=my-adapter.ear) { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.MyAdapter is already registered", "rolled-back" => true } {noformat} After a server restart the resource adapter can be added reusing the previously removed name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBWEB-234) processParameters does not take request encoding charset

by Philippe Guinot (JIRA)

Philippe Guinot created JBWEB-234: ------------------------------------- Summary: processParameters does not take request encoding charset Key: JBWEB-234 URL: https://issues.jboss.org/browse/JBWEB-234 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-7.0.12.GA Environment: JBoss AS 7.1.1-SNAPSHOT (5 March 2012) Reporter: Philippe Guinot Assignee: Remy Maucherat The UTF-8 -encoded POST requests params are not processed correctly with JBoss Web 7.0.12. After some investigations, I notice that in the org.apache.tomcat.util.http.Parameters class of JBoss Web 7.0.12.Final, the method processParameters( byte bytes[], int start, int len ) gives null as encoding, while JBoss Web 7.1.10.Final passed the attribute value of the encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-4121) TS:

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4121: --------------------------------- Summary: TS: Key: AS7-4121 URL: https://issues.jboss.org/browse/AS7-4121 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.1.Final Environment: Sun JDK 1.7.0, try mike.lab.bos.redhat.com Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: No Release We are probably going to have problem with XSLT transformation in JDK 7: {code} [ERROR] Failed to execute goal org.codehaus.mojo:xml-maven-plugin:1.0:transform (ts.config-as.ip) on project jboss-as-testsuite: Execution ts.config-as.ip of goal org.codehaus.mojo:xml-maven-plugin:1.0:transform failed: The value of param managementIPAddress must be a valid Java Object -> [Help 1] {code} This happened on Mike where I installed Sun JDK 1.7.0. Here's some info: http://dev-answers.blogspot.com/2006/07/xalan-parameter-must-be-valid-jav... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] (AS7-2842) TS: integration-tests.sh/bat starts smoke tests by default

by Radoslav Husar (Created) (JIRA)

TS: integration-tests.sh/bat starts smoke tests by default ---------------------------------------------------------- Key: AS7-2842 URL: https://issues.jboss.org/browse/AS7-2842 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Beta1 Reporter: Radoslav Husar Assignee: Ondrej Zizka Fix For: 7.1.0.CR1 And this does not make sense. Integration tests are not smoke tests, thus they should not run when running integration testsuite. The fix is: -Dts.noSmoke can be appended by default in the script unless smoke tests are explicitly requested -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
6
0 / 0

[JBoss JIRA] (AS7-4032) Managed server can't be :stop :removed within a batch

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4032: ------------------------------- Summary: Managed server can't be :stop :removed within a batch Key: AS7-4032 URL: https://issues.jboss.org/browse/AS7-4032 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry Hava a running managed server in domain mode [domain@localhost:9999 server-config=blabla] batch [domain@localhost:9999 server-config=blabla #] :stop #1 /host=master/server-config=blabla:stop [domain@localhost:9999 server-config=blabla #] :remove #2 /host=master/server-config=blabla:remove [domain@localhost:9999 server-config=blabla #] run-batch Failed to execute batch: JBAS014654: Composite operation was rolled back If you do those :stop , :remove operations outside of a batch it works [domain@localhost:9999 server-config=blabla] :stop { "outcome" => "success", "result" => "STOPPING" } [domain@localhost:9999 server-config=blabla] :remove { "outcome" => "success", "result" => {"outcome" => "success"}, "server-groups" => undefined } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
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 March 2012