]
Thomas Diesler edited comment on AS7-6202 at 12/18/12 3:02 PM:
---------------------------------------------------------------
The reason is that the FrameworkBootstrapService cannot start because of this missing
dependency
{code}
builder.addDependency(JBOSS_BINDING_NAME.append("osgi-http"),
SocketBinding.class, service.httpServerPortBinding);
{code}
the DC should have
{code}
<socket-binding name="osgi-http" interface="management"
port="8090"/>
{code}
The PR makes the dependency optional
was (Author: thomas.diesler):
The reason is that the FrameworkBootstrapService cannot start because of this missing
dependency
{code}
builder.addDependency(JBOSS_BINDING_NAME.append("osgi-http"),
SocketBinding.class, service.httpServerPortBinding);
{code}
the DC should have
{code}
<socket-binding name="osgi-http" interface="management"
port="8090"/>
{code}
Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
---------------------------------------------------------------
Key: AS7-6202
URL:
https://issues.jboss.org/browse/AS7-6202
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Reporter: Kabir Khan
Assignee: Thomas Diesler
Fix For: 7.1.4.Final (EAP)
Attachments: domain.xml, host.xml
I noticed this when working on the mixed-domain tests. The attached domain.xml and
host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups
protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers
auto-start="false".
To reproduce, start up a DC built from master using those files. Then start up a slave HC
built from 7.1.2.Final or 7.1.3.Final using a command like:
./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml
-Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999
Now in CLI:
{code}
[domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" =>
"file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}]
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
[domain@localhost:9999 /] /deployment=test.war:remove
[domain@localhost:9999 /]
/server-group=main-server-group/deployment=test.war:add(enabled=true)
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was
rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" =>
{"host" => {"kabirs-macbook-pro.local" =>
{"server-one" => {"response" => {
"outcome" => "failed",
"result" => undefined,
"failure-description" => {"JBAS014771: Services with
missing/unavailable dependencies" =>
["jboss.osgi.as.module.registration.\"deployment.test.war:main\"
Missing[jbosgi.Environment]"]},
"rolled-back" => true
}}}}}}
}
{code}
The console log for the slave shows
{code}
[Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-4) JBAS015876: Starting deployment of "test.war"
[Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7)
JBAS018210: Registering web context: /test
[Server:server-one] 17:21:22,771 INFO [org.jboss.as.server]
(host-controller-connection-threads - 1) JBAS015870: Deploy of deployment
"test.war" was rolled back with failure message {"JBAS014771: Services with
missing/unavailable dependencies" =>
["jboss.osgi.as.module.registration.\"deployment.test.war:main\"
Missing[jbosgi.Environment]"]}
[Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-3) JBAS015877: Stopped deployment test.war in 42ms
{code}
The deployment is very simple, and just contains an html file:
{code}
$unzip -l
testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
Archive:
testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
Length Date Time Name
-------- ---- ---- ----
210 12-17-12 16:34 index.html
-------- -------
210 1 file
{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: