[JBoss JIRA] (AS7-4306) stop-context enable-context disable-context all return 'Operation handler failed: null' unless virtualhost='default-host'
by Simeon Pinder (JIRA)
Simeon Pinder created AS7-4306:
----------------------------------
Summary: stop-context enable-context disable-context all return 'Operation handler failed: null' unless virtualhost='default-host'
Key: AS7-4306
URL: https://issues.jboss.org/browse/AS7-4306
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.1.Final
Environment: Standalone AS7 instance using -c standalone-ha.xml profile.
Using jboss-cli.sh to manage modcluster subsystem.
Using modcluster 1.2.0.Final
Reporter: Simeon Pinder
Assignee: Alexey Loubyansky
i)Setup httpd, modcluster and as7 standalone instance and deploy cluster enabled webapp so that requests for http://(as7 server):8080/app.html is correctly served up by http://(httpd server)/app.html.
ii)Log into AS7 and attempt to run stop-context | enable-context | disable-context via cli with a host OTHER than 'virtual-host' and the commands fail with the following:
/subsystem=modcluster/:disable-context(virtualhost=vitalstatistix.conchfritter.com,context=/helloworld)
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: null",
"rolled-back" => true
}
--
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
12 years, 1 month
[JBoss JIRA] (AS7-4404) Servlet statistics don't work
by Tomaz Cerar (JIRA)
Tomaz Cerar created AS7-4404:
--------------------------------
Summary: Servlet statistics don't work
Key: AS7-4404
URL: https://issues.jboss.org/browse/AS7-4404
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Web
Affects Versions: 7.1.1.Final
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Fix For: 7.1.2.Final-redhat1
Running:
{noformat}
/host=master/server=server-one/deployment=test.war/:read-resource(recursive=true,include-runtime=true)
{
"outcome" => "success",
"result" => undefined,
"failure-description" => undefined
}
{noformat}
results in
{noformat}
[Server:server-one] 16:03:50,320 ERROR [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 8) JBAS014612: Operation ("read-attribute") failed - address: ([
[Server:server-one] ("deployment" => "test.war"),
[Server:server-one] ("subsystem" => "web"),
[Server:server-one] ("servlet" => "ArquillianServletRunner")
[Server:server-one] ]): java.lang.UnsupportedOperationException
[Server:server-one] at org.jboss.dmr.ModelNode.checkProtect(ModelNode.java:1560) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
[Server:server-one] at org.jboss.dmr.ModelNode.get(ModelNode.java:795) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
{noformat}
without runtime=true it works without any problems
same goes if you go to /host=master/server=server-one/deployment=test.war/servlet=ArquillianServletRunner and run ls
--
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
12 years, 1 month
[JBoss JIRA] (AS7-3142) VirtualFile error messages
by Ben Software Engineer (Created) (JIRA)
VirtualFile error messages
--------------------------
Key: AS7-3142
URL: https://issues.jboss.org/browse/AS7-3142
Project: Application Server 7
Issue Type: Support Patch
Components: VFS
Affects Versions: 7.1.0.CR1b
Environment: Windows 7, JDK 6, Eclipse Indigo
Reporter: Ben Software Engineer
Assignee: John Bailey
I'm migrating a app from JBoss 5.0.1 to JBoss 7.1 and getting an error when starting deployment of the EAR. It is almost impossible for me to troubleshoot as the error message is to vague. Please add the virtual file name and any other information that would make this error useful, thank you.
[org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."xxx-ear.ear"."xxx.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."xxx-ear.ear"."xxx.war".PARSE: Failed to process phase PARSE of subdeployment "oflows.war" of deployment "xxx-ear.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:105)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 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
12 years, 1 month
[JBoss JIRA] (JBAS-9481) race condition can break HASingleton functionality
by Dennis Reed (JIRA)
Dennis Reed created JBAS-9481:
---------------------------------
Summary: race condition can break HASingleton functionality
Key: JBAS-9481
URL: https://issues.jboss.org/browse/JBAS-9481
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.1.0.GA
Reporter: Dennis Reed
Assignee: Paul Ferraro
Attachments: test.jar
HASingletonImpl#registerDRMListener has a race condition with partitionTopologyChanged, which can cause views to be processed
out of order, and HASingletons to be started when they should be stopped, or stopped when they should be started.
The problem is that the thread calling registerDRMListener (which calls partitionTopologyChanged) is not synchronized against other threads that call partitionTopologyChanged.
This was introduced by the fix for https://issues.jboss.org/browse/JBAS-2647.
To fix the issue, partitionTopology must process the view saved in viewReference in the correct order, and registerDRMListener's
call to partitionTopology must be synchronized against other threads calling it (without causing a regression of JBAS-2647).
--
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
12 years, 1 month
[JBoss JIRA] (JBRULES-3446) Upgrade to spring 3.0.6.RELEASE to stop spring version mix in drools-camel-server
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created JBRULES-3446:
-----------------------------------------
Summary: Upgrade to spring 3.0.6.RELEASE to stop spring version mix in drools-camel-server
Key: JBRULES-3446
URL: https://issues.jboss.org/browse/JBRULES-3446
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
{code}
drools-camel-server [master $] $ mvn dependency:tree
...
[INFO] --- maven-dependency-plugin:2.2:tree (default-cli) @ drools-camel-server ---
...
[INFO] +- org.drools:drools-spring:jar:5.4.0-SNAPSHOT:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | \- org.springframework:spring-context:jar:2.5.6:compile
...
[INFO] +- org.apache.camel:camel-spring:jar:2.9.0:compile
[INFO] | \- org.springframework:spring-tx:jar:3.0.6.RELEASE:compile
....
[INFO] +- org.springframework:spring-core:jar:2.5.6:compile
[INFO] +- org.springframework:spring-aop:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] +- org.springframework:spring-test:jar:2.5.6:test
[INFO] +- org.apache.cxf:cxf-bundle-jaxrs:jar:2.4.4:compile
...
[INFO] | +- org.springframework:spring-asm:jar:3.0.6.RELEASE:compile
[INFO] | +- org.springframework:spring-expression:jar:3.0.6.RELEASE:compile
...
{code}
--
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
12 years, 1 month
[JBoss JIRA] (AS7-4375) Integrate CLI GUI with jconsole
by Stan Silvert (JIRA)
Stan Silvert created AS7-4375:
---------------------------------
Summary: Integrate CLI GUI with jconsole
Key: AS7-4375
URL: https://issues.jboss.org/browse/AS7-4375
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.1.Final
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final
JConsole has a plugin mechanism that allows adding tabs by a third party. CLI GUI can be easily refactored to integrate with JConsole and allow a developer or administrator to fully monitor and control a server or domain controller. It can also monitor several servers/domains at once using jconsole's multiple document interface.
This integration includes reusing the underlying remoting-jmx connection. The ability to access this connection is provided by REMJMX-39.
--
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
12 years, 1 month
[JBoss JIRA] (AS7-4402) FilePersistentObjectStore establishDirectory() is not thead safe
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4402:
-------------------------------------
Summary: FilePersistentObjectStore establishDirectory() is not thead safe
Key: AS7-4402
URL: https://issues.jboss.org/browse/AS7-4402
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
FilePersistentObjectStore.start() can be called concurrently (perhaps on different instances) as different SFSB component services concurrently start. This can lead to races where multiple threads detect a dir does not exist and call File.mkdirs(), with only one getting a "true" return value from that call (the thread that actually created the dirs). When that happens the other thread(s) can fail like this:
15:35:01,170 ERROR org.jboss.msc.service.fail MSC00001: Failed to start service jboss.deployment.unit."persistentcontext-test.jar".component.StatefulTransientBean.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."persistentcontext-test.jar".component.StatefulTransientBean.START: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
Caused by: java.lang.RuntimeException: JBAS014540: Failed to create passivation directory: /home/bstansberry/dev/jboss/jboss-as/testsuite/integration/basic/target/jbossas/standalone/data/ejb3/sessions
at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.establishDirectory(FilePersistentObjectStore.java:212)
at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.start(FilePersistentObjectStore.java:197)
at org.jboss.as.ejb3.cache.impl.backing.SimpleBackingCacheEntryStore.start(SimpleBackingCacheEntryStore.java:191)
at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.start(SerializationGroupMemberContainer.java:303)
at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.start(PassivatingBackingCacheImpl.java:297)
at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.start(AbstractCache.java:93)
at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.start(StatefulSessionComponent.java:299)
at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
Solution is to just not throw that exception if the directory exists following the mkdirs() call, whether or not the call returned true.
--
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
12 years, 1 month
