[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-6202:
-------------------------------------
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.2.0.Alpha1
>
> 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: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-6212) Invalid expression support for some transaction subsystem attributes
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6212:
-------------------------------------
Summary: Invalid expression support for some transaction subsystem attributes
Key: AS7-6212
URL: https://issues.jboss.org/browse/AS7-6212
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Transactions
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
The transaction subsystem specifies that expressions are allowed for attributes USEHORNETQSTORE and JTS. This can't work because the xml schema uses an empty element to indicate these are "true". That kind of xml grammar cannot support expressions.
--
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
12 years
[JBoss JIRA] (JGRP-1556) Incorrect error log message in RequestCorrelator
by Michal Linhard (JIRA)
Michal Linhard created JGRP-1556:
------------------------------------
Summary: Incorrect error log message in RequestCorrelator
Key: JGRP-1556
URL: https://issues.jboss.org/browse/JGRP-1556
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2.4
Reporter: Michal Linhard
Assignee: Bela Ban
Priority: Minor
I have this when running JDG 6.1.0.ER6 with JGroups 3.2.4
{code}
08:31:41,460 ERROR [org.jgroups.blocks.RequestCorrelator] failed sending rsp: return value (SuccessfulResponse{responseValue=null} ) is not serializable
{code}
which is of course not the cause of the error.
This message is logged when any Throwable is caught
https://github.com/belaban/JGroups/blob/26b7c60d511baf199674b45d3d402dfbb...
in my case it was once NullPointerException and once InterruptedException probably caused by caches and externalizers shutting down.
I'd recommend rewording of the message if the exception is not NotSerializableException or the like to avoid confusion.
--
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
12 years
[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6202:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
> 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.2.0.Alpha1
>
> 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: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler reopened AS7-6202:
---------------------------------
Yes, indeed this should not trigger OSGi.
> 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
> 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: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBMESSAGING-1802) Sending MapMessage with large String value is broken
by Justin Bertram (JIRA)
[ https://issues.jboss.org/browse/JBMESSAGING-1802?page=com.atlassian.jira.... ]
Justin Bertram commented on JBMESSAGING-1802:
---------------------------------------------
[~jsight], my point was that this is not a bug, but an intentional decision. You can certainly argue about the logic of the decision, but the fact remains that it's not a bug. To my knowledge, this is not required to support JMS 1.1.
Also, it's unlikely this is going to change now that HornetQ is the JMS broker of choice in the JBoss community and in JBoss EAP. EAP 4.3 (which only uses JBoss Messaging) will reach EOL in January 2013 and anybody using EAP 5 can move to 5.1.2 and install HornetQ. Of course, there is no option to use JBoss Messaging in EAP 6.
> Sending MapMessage with large String value is broken
> ----------------------------------------------------
>
> Key: JBMESSAGING-1802
> URL: https://issues.jboss.org/browse/JBMESSAGING-1802
> Project: JBoss Messaging
> Issue Type: Feature Request
> Affects Versions: 1.4.0.SP3.CP10, 1.4.6.GA
> Reporter: Justin Bertram
> Assignee: Yong Hao Gao
> Fix For: 1.4.8.SP10
>
>
> Sending a javax.jms.MapMessage that has a String value >= 65536 characters fails.
--
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
12 years