[JBoss JIRA] Created: (AS7-1220) Add native management (ModelControllerClient) API docs to the Admin Guide
by Brian Stansberry (JIRA)
Add native management (ModelControllerClient) API docs to the Admin Guide
--------------------------------------------------------------------------
Key: AS7-1220
URL: https://issues.jboss.org/browse/AS7-1220
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
There's some brief docs on configuring the native management interface. There is a separate JIRA for some fundamental docs on jboss-dmr. There will be a page in the "Core management concepts" section on what management resources, attributes and operations are.
This task is to reference those elements and bring together a coherent picture of how to use the ModelControllerClient API.
A subtask would be to add docs on the helper classes in controller-client, although I'm fine with deferring that bit until later in the AS 7.1 cycle,
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (AS7-1751) infinispan setup to support environment variables within the standalone.xml file
by Dan Sirbu (JIRA)
infinispan setup to support environment variables within the standalone.xml file
--------------------------------------------------------------------------------
Key: AS7-1751
URL: https://issues.jboss.org/browse/AS7-1751
Project: Application Server 7
Issue Type: Enhancement
Components: Clustering
Affects Versions: 7.0.1.Final
Reporter: Dan Sirbu
Assignee: Paul Ferraro
Fix For: 7.0.2.Final
When I kickstart the inifispan subsystem by using the start=EAGER option, saw that there are multiple "clusters" that get kickstarted as:
GMS: address=traffic_instance_PL-3-31315, cluster=hibernate
........................................, cluster=web
and others.
Now, if I do have mutliple blades e.g. SC-1, SC-2, PL-3, PL-4 and then I would like to define two clusters e.g. "oam" , "traffic" where "oam" should be assigned for SC-x and "traffic" for PL-x, then I will certainly need to go in the standalone-ha.xml file and change all the "cache-container name" entries in order to have "oam" cluster distinguished from "traffic" cluster, right ?
If so, it would be better if for example I could pass an jvm option via e.g. -DCLUSTER="oam" and then in the standalone-ha.xml file have this set as: "cache-container name=${CLUSTER}-"
In this way, I can obtain a dynamic config at runtime.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-3820) Deployment fail if destination server is not available at startup of client server using "EJB invocations from a remote server instance"
by Markus Lindblom (JIRA)
Markus Lindblom created AS7-3820:
------------------------------------
Summary: Deployment fail if destination server is not available at startup of client server using "EJB invocations from a remote server instance"
Key: AS7-3820
URL: https://issues.jboss.org/browse/AS7-3820
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Final
Environment: RHEL 5.5
Reporter: Markus Lindblom
Assignee: jaikiran pai
Using the instructions for EJB invocations from a remote server instance results in failed deployment on the client server if the destination server is not started with the following stacktrace
03:34:20,825 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ejb3.dd-based-ejb-client-context."ExpertClientServer.ear": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."ExpertClientServer.ear": 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(Unknown Source) [rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)
at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:124)
at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:86)
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] (AS7-3765) Deployment of Nexus 2.0 war fails
by Nicklas Karlsson (JIRA)
Nicklas Karlsson created AS7-3765:
-------------------------------------
Summary: Deployment of Nexus 2.0 war fails
Key: AS7-3765
URL: https://issues.jboss.org/browse/AS7-3765
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Final
Reporter: Nicklas Karlsson
Assignee: Jason Greene
Dropping the Nexus 2.0 war into upstream master AS7 results in a hang (.isdeploying marker file) and the log output
{code}
14:22:06 /:@ INFO JBAS015876: Starting deployment of "nexus-2.0.war"
14:22:14 /:@ WARN Class Path entry activation.jar in "/C:/Java/dev/AS7/build/target/jboss-as-7.1.0.Final-SNAPSHOT/bin/content/nexus-2.0.war/WEB-INF/lib/mail-1.4.jar" does not point to a valid jar for a Class-Path reference.
14:22:15 /:@ WARN JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
14:22:15 /:@ INFO JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
14:22:16 /:@ INFO Configuring Nexus in vanilla WAR...
14:22:16 /:@ INFO Setting Plexus basedir context variable to (discovered from Servlet container): C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF
14:22:16 /:@ INFO ===================================
14:22:16 /:@ INFO Application context "nexus" dump:
14:22:16 /:@ INFO "nexus-work"="C:\Users\karlsnic/sonatype-work/nexus" (raw: "${user.home}/sonatype-work/nexus", src: propsFile(C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF\plexus.properties, size:5))
14:22:16 /:@ INFO "runtime"="C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF" (raw: "${bundleBasedir}", src: propsFile(C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF\plexus.properties, size:5))
14:22:16 /:@ INFO "application-conf"="C:\Users\karlsnic/sonatype-work/nexus/conf" (raw: "${nexus-work}/conf", src: propsFile(C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF\plexus.properties, size:5))
14:22:16 /:@ INFO "nexus-app"="C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF" (raw: "${runtime}", src: propsFile(C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF\plexus.properties, size:5))
14:22:16 /:@ INFO "security-xml-file"="C:\Users\karlsnic/sonatype-work/nexus/conf/security.xml" (raw: "${nexus-work}/conf/security.xml", src: propsFile(C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF\plexus.properties, size:5))
14:22:16 /:@ INFO "bundleBasedir"="C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF" (raw: "C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF", src: static("bundleBasedir"="C:\Java\dev\AS7\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\temp1a9b1390bbbbec8d\nexus-2.0.war-87bcc73f67f0dfd8\WEB-INF"))
14:22:16 /:@ INFO Total of 6 entries.
14:22:16 /:@ INFO ===================================
14:22:16 /:@ INFO
{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
14 years, 4 months
[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
by Bill Burke (JIRA)
[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ]
Bill Burke commented on AS7-3199:
---------------------------------
Also, there is no TCK test for this, nor is the spec clear on whether or not multiple Applications can be deployed per WAR, or whether it is illegal for an implementation to only allow one Application per WAR.
> RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
> ---------------------------------------------------------------------------------------------
>
> Key: AS7-3199
> URL: https://issues.jboss.org/browse/AS7-3199
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Stuart Douglas
> Attachments: ExampleJAXRS.war
>
>
> If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed."
> This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for
> more than one application to be deployed +at the same effective servlet mapping+".
> If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months