4:30 p.m.
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6721:
---------------------------------
Priority: Critical (was: Major)
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:54 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Ian Springer updated JBAS-6721:
-------------------------------
Description:
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
was:
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:28 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6721:
---------------------------------
Description:
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
was:
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6721:
---------------------------------
Fix Version/s: JBossAS-5.1.0.CR1
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:46 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber reassigned JBAS-6721:
-----------------------------------------
Assignee: Emanuel Muckenhuber (was: Scott M Stark)
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber commented on JBAS-6721:
-------------------------------------------
1) I've updated the Queue and Topic service: the Name is now available and can be set
in the template. But is now STATISTIC, as it does not have a setter.
2) done
3) Yes, I've set the messageCounterHistoryDayLimit to STATISTIC, as it does not work -
if you specify a value for that the deployment fails, so until this is not fixed it should
be ignored.
4) clustered is now readOnly, but still available in the template.
Can we close this jira then ?
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Charles Crouch commented on JBAS-6721:
--------------------------------------
From todays call: make name prop CONFIGURATION but readonly
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:41 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6721:
------------------------------------
When I try to set the 'name' prop in the template when creating a new Queue, I get
the following exception when I call applyTemplate():
13:35:40,936 DEBUG [ApplicationServerComponent] Applying template [QueueTemplate] to
create ManagedComponent of type [ComponentType{type=JMSDestination, subtype
=Queue}]...
13:35:40,983 INFO [DeployHandler] Handle stream, deploymentTarget:
names=[ggg-service.xml], copyContent=true,
description=vfsfile:/C:/DOCUME~1/ips/LOCALS~1/Tem
p/JmsDestinationTemplate2472261140647743090-service.xml
13:35:40,983 INFO [DeployHandler] End handle stream, repositoryName:
vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml
13:35:40,983 INFO [DeployHandler] Begin start,
[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml]
13:35:41,015 ERROR [AbstractKernelController] Error installing to Configured:
name=jboss.messaging.destination:name=ggg,service=Queue state=Instantiated mode=Ma
nual requiredState=Configured
java.lang.RuntimeException: Exception setting attribute Name on mbean
jboss.messaging.destination:service=Queue,name=ggg
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:170)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
at
org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
at
org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.install(ServiceController.java:274)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:253)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:169)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.applyTemplate(AOPProxy$1.java)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.management.AttributeNotFoundException: Attribute 'Name' is not
writable
at
org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:431)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:166)
... 78 more
13:35:41,030 ERROR [AbstractKernelController] Error installing to Real:
name=vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml stat
e=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying:
jboss.messaging.destination:service=Queue,name=ggg
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:118)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:253)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:169)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.applyTemplate(AOPProxy$1.java)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Exception setting attribute Name on mbean
jboss.messaging.destination:service=Queue,name=ggg
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:170)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
at
org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
at
org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.install(ServiceController.java:274)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
... 61 more
Caused by: javax.management.AttributeNotFoundException: Attribute 'Name' is not
writable
at
org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:431)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:166)
... 78 more
13:35:41,030 INFO [DeployHandler] Failed to complete command: [start] for deployment:
names=[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg
-service.xml], copyContent=true
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml ->
org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.messaging.
destination:service=Queue,name=ggg
DEPLOYMENTS IN ERROR:
Deployment
"vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml"
is in error due to the following reason(s): javax.management.Attri
buteNotFoundException: Attribute 'Name' is not writable
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:869)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:255)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:169)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.applyTemplate(AOPProxy$1.java)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
13:35:41,030 INFO [DeployHandler] Stop,
[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml]
13:35:41,030 INFO [DeployHandler] End stop,
[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml]
13:35:41,030 INFO [DeployHandler] Remove,
[vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml]
13:35:41,030 ERROR [ApplicationServerComponent] Unable to apply template [QueueTemplate]
to create ManagedComponent of type ComponentType{type=JMSDestination, s
ubtype=Queue}.
java.lang.RuntimeException: Failed to process template.
at
org.jboss.profileservice.management.AbstractTemplateCreator.checkComplete(AbstractTemplateCreator.java:194)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:171)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.applyTemplate(AOPProxy$1.java)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR
DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml ->
org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.messaging.
destination:service=Queue,name=ggg
DEPLOYMENTS IN ERROR:
Deployment
"vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml"
is in error due to the following reason(s): javax.management.Attri
buteNotFoundException: Attribute 'Name' is not writable
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:169)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.applyTemplate(AOPProxy$1.java)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at
org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
... 18 more
Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of
incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml ->
org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.messaging.
destination:service=Queue,name=ggg
DEPLOYMENTS IN ERROR:
Deployment
"vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/ggg-service.xml"
is in error due to the following reason(s): javax.management.Attri
buteNotFoundException: Attribute 'Name' is not writable
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:869)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:255)
at
org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at
org.jboss.profileservice.management.AbstractTemplateCreator.start(AbstractTemplateCreator.java:169)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:117)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1018)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
... 18 more
13:35:41,046 WARN [CreateResourceRunner] Throwable was found in creation report for
request [1]: java.lang.RuntimeException: Failed to process template. - Enab
le DEBUG logging to see the stack trace.
13:35:41,046 INFO [CreateResourceRunner] Sending create response to server:
CreateResourceResponse[RequestId=1, Status=Failure]
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6721:
---------------------------------
Priority: Blocker (was: Critical)
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Blocker
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse
[
https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber resolved JBAS-6721.
---------------------------------------
Resolution: Done
a few Topic/Queue ManagedProperties have the wrong ViewUse
----------------------------------------------------------
Key: JBAS-6721
URL: https://jira.jboss.org/jira/browse/JBAS-6721
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Blocker
Fix For: JBossAS-5.1.0.CR1
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the
xml config file, e.g.:
<mbean xmbean-dd="xmdesc/Topic-xmbean.xml"
name="jboss.messaging.destination:service=Topic,name=MyTopic"
code="org.jboss.jms.server.destination.TopicService">
At least I think the name=MyTopic portion of the MBean name becomes the Topic's
name.
Actually 'name' should probably *only* be settable at the time of creation and
after that be read-only. In JON we allow the GUI user to set values on properties that are
both required and read-only and that currently have null values, but at other times, those
properties cannot be modified. We do this mainly for the creation use case - for example,
in the case of the 'name' prop, we would make it read-only and required, so the
user would be forced to specify a value at Topic/Queue creation time, but then would not
be able to change it once the Topic/Queue has been created.
2) 'createdProgrammatically' sounds like it should be read-only and hence
STATISTIC rather than RUNTIME
3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since
it can be set in the xml config file, e.g.:
<attribute name="MessageCounterHistoryDayLimit">10</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6329
days inactive
6335
days old
10 comments
3 participants
participants (3)
-
Charles Crouch (JIRA) -
Emanuel Muckenhuber (JIRA)
-
Ian Springer (JIRA)