[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
[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
[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
[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
[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