Questions on connecting to as71 via jmx
by Rob Stryker
Hey all:
We in JBossTools have a feature for jmx and would like to extend it's
jmx support to as71, but it seems not to be working in my most simple
main class example. I've found links on using jconsole, but no links
for raw clients. I do remember that AS3-6 required loading some custom
classes, and setting a principal and a credential.
So far, I add the following to the classpath of a new plain old java
project:
jboss-logging-3.1.0.GA.jar
jboss-marshalling-1.3.9.GA.jar
jboss-marshalling-river-1.3.9.GA.jar
jboss-remoting-3.2.2.GA.jar
jboss-sasl-1.0.0.Final.jar
remoting-jmx-1.0.0.Final.jar
xnio-api-3.0.3.GA.jar
xnio-nio-3.0.3.GA.jar
Then I write the following main method:
try {
String url = "service:jmx:remoting-jmx://localhost:1090";
Map<String, String[]> environment = new HashMap<String,
String[]>();
JMXConnector connector = JMXConnectorFactory.connect(new
JMXServiceURL(url), environment);
MBeanServerConnection connection =
connector.getMBeanServerConnection();
Set beanInfo = connection.queryNames(new ObjectName("*:*"),
null); //$NON-NLS-1$
} catch( Exception e ) {
e.printStackTrace();
}
If the server is not running, the result is the program never closes.
There are three threads, two of which are remoting endpoints, and a
DestroyJavaVM Thread. Exception is as follows:
java.lang.RuntimeException: Operation failed with status WAITING
at
org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at MyMain.main(MyMain.java:17)
How do I properly recognize this "RuntimeException"? Is there some
superclass I can catch, or is this it? Finally, how do I properly clean
up the connections to ensure those threads disappear?
If the server *is* running, launched via standalone.xml, the result is
identical.
Does the default as71 come with JMX enabled and exposed? If not, what
needs to be done to expose it?
Thanks again
- Rob Stryker
11 years, 7 months
Compilation errors with jboss-as master
by David Bosschaert
Anyone else experiencing these errors as well when building master on
jboss-as?
David
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:44.448s
[INFO] Finished at: Tue Apr 17 07:50:57 IST 2012
[INFO] Final Memory: 114M/411M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project jboss-as-server: Compilation failure:
Compilation failure:
[ERROR] bootstrap class path not set in conjunction with -source 1.6
[ERROR]
/home/david/clones/bosschaert_jboss-as_170412/server/src/main/java/org/jboss/as/server/deployment/RootDeploymentUnitService.java:[25,42]
error: package com.sun.xml.internal.ws.api.message does not exist
[ERROR]
/home/david/clones/bosschaert_jboss-as_170412/server/src/main/java/org/jboss/as/server/deployment/RootDeploymentUnitService.java:[25,42]
error: package com.sun.xml.internal.ws.api.message does not exist
11 years, 7 months
CLI - Displaying allowed-values for attributes
by Jaikiran Pai
IIRC some releases back, if an attribute in a domain model resource,
allowed a certain set of values, then a read-resource-description via
the CLI would show the allowed values. But checking against the latest
upstream, I don't see it available any more. For example the
timeout-unit attribute of the strict-max-bean-instance-pool resource no
longer shows the allowed values:
[standalone@localhost:9999 /]
/subsystem=ejb3/strict-max-bean-instance-pool=slsb-strict-max-pool:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "A bean instance pool with a strict upper limit",
"attributes" => {
"timeout-unit" => {
"type" => STRING,
"description" => "The instance acquisition timeout unit",
"expressions-allowed" => false,
"nillable" => true,
"default" => "MINUTES",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
...
Was this change intentional? It would be nice to be able to know what
values are allowed for certain attributes. By the way, is it just the
CLI that would need a change for this or does this involve much more?
-Jaikiran
11 years, 7 months
Overriding Deployment Descriptors
by Stuart Douglas
We have had a few requests for the ability to override deployment descriptors without having to open up a deployment archive and manually change the descriptor. I think there are two different approach that we can use to accomplish this, and I am was wondering what other people thought.
1) Allow the user to specify alternate deployment descriptors as part of the deployment process
At deployment time the user would be able to select specific deployment descriptors to override. I don't really like this approach, as it means that this information must also be provided on every re-deployment. It is also not really compatible with the deployment scanner, and would require changes to every client that does deployment to properly support it.
2) Allow the user to specify deployment descriptor overrides before a deployment takes places. These descriptors would be stored in the content repository, and the corresponding information in the model. When a deployment is performed that matches the deployment name in the model the deployment descriptors from the content repository are merged into the deployment.
e.g. to add the descriptor you would do something like:
/dd-override:my-deployment-descriptor:add(deployment="test.ear", file="test.jar/META-INF/ejb-jar.xml", content=…)
or for domain mode
/server-group=foo/dd-override:my-deployment-descriptor:add(deployment="test.ear", file="test.jar/META-INF/ejb-jar.xml", content=…)
Then when test.ear is deployed the contents if the overridden deployment descriptor will be override test.jar/META-INF/ejb-jar.xml.
2) is the approach that I prefer, as I think it gives the most flexibility.
What does everyone think?
Stuart
11 years, 7 months
Is there a way to skip just one set of tests on AS 7?
by Andrig Miller
I'm building AS 7.1.x from master for two fixes that were merged in the last day.
I'm getting this failure:
[INFO] JBoss Application Server: Arquillian Managed Container FAILURE [1.802s]
There is a test failure in there, but I don't think it matters to what I'm doing. Is there a way to just skip that set of tests? In the testsuite users guide it shows that you can skip all tests, or you can run just specific tests, but it doesn't show how you can just skip on set of tests like the Arquillian Managed Container tests.
Of course these tests need to be fixed, but if I could just skip them, then I can move on with what I'm doing. I might just skip all the tests for now, and hope there isn't some issue that might affect what I'm doing, but that makes me a little uncomfortable.
Thanks.
--
Andrig (Andy) Miller
Global Platform Director for JBoss Middle-ware
Red Hat, Inc.
11 years, 7 months
Console 1.1.0 Update
by Heiko Braun
Notable changes in AS 7.1.1 at a glance:
Additional Subsystems:
- infinispan
- jgroups
- modcluster
- mail
Environment Properties:
The ability to view any system property that has been passed to the JVM when the server was started.
What's next?
In the next iteration we'll focus on accessibility issues (508 compliance), remaining translations and missing runtime operations (i.e. modcluster).
Thanks to Stan, Pavel and David for their contributions.
Regards, Heiko
11 years, 8 months
Re: [jboss-as7-dev] JGroups 3.0.9.Final released
by William DeCoste
Any chance we can get this into AS7.1.2 and EAP6.0? We need this patch
for OpenShift.
Thanks -Bill
On 4/4/12 6:47 AM, Bela Ban wrote:
> I let Bill answer this
>
> On 4/4/12 3:36 PM, Radoslav Husar wrote:
>> Sounds like this is required to get to EAP which OpenShift will be
>> using, so created a component upgrade Jira:
>> https://issues.jboss.org/browse/AS7-4398
>>
>> Rado
>>
>> On 04/04/2012 03:27 PM, Bela Ban wrote:
>>> FYI,
>>>
>>> contains only 2 issues: [1] fixes an issue in which an RSVP that's
>>> stopped prematurely waits for the completion of timeouts of pending
>>> RSVP
>>> messages (if there are any), and [2] adds external_port to the
>>> transport, which is required by the OpenShift folks to do NATting
>>> between different internal and external addresses *and* different
>>> ports.
>>>
>>> [1] https://issues.jboss.org/browse/JGRP-1444
>>> [2] https://issues.jboss.org/browse/JGRP-1441
>>>
>
--
Bill DeCoste
Principal Software Engineer, Red Hat
978-204-0920
wdecoste(a)redhat.com
11 years, 8 months
Re: [jboss-as7-dev] Build failed in Jenkins: JBoss-AS-7.0.x #2762
by Brian Stansberry
This looks to be an intermittent failure introduced by the last pull
request I merged.
If you hit this, just try building again. Let me know if it's a
consistent issue.
I'm looking into it, but don't want to immediately revert the PR unless
it's causing serious disruption. I'd rather try and sort it out for a while.
On 4/4/12 12:54 PM, jboss-qa-internal(a)redhat.com wrote:
> See<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/2762/changes>
>
> Changes:
>
> [bstansberry(a)jboss.com] PathManager framework and expose hardcoded paths in the model
>
> [bstansberry(a)jboss.com] AS7-4402 Don't fail on mkdirs() if another thread created the dir
>
> ------------------------------------------
> [...truncated 2138 lines...]
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> }
> },
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => 1,
> "rolled-back" => true
> }
> },
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> }
> },
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-1" => "JBAS014654: Composite operation was rolled back",
> "Operation step-2" => "JBAS014654: Composite operation was rolled back"
> }},
> "rolled-back" => true
> }
> ======================
> ========= New Test
>
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "result" => 1,
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> }
> },
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "result" => 1,
> "rolled-back" => true
> }
> },
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> }
> },
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-1" => "JBAS014654: Composite operation was rolled back",
> "Operation step-2" => "JBAS014654: Composite operation was rolled back"
> }},
> "rolled-back" => true
> }
> ======================
> ========= New Test
>
> ------
> ------
> ======================
> ========= New Test
>
> ------
> ------
> ======================
> ========= New Test
>
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> }},
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> }
> ======================
> ========= New Test
>
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "result" => 2,
> "rolled-back" => true
> }},
> "failure-description" => "JBAS014654: Composite operation was rolled back",
> "rolled-back" => true
> }
> ======================
> Tests run: 50, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 1.618 sec
> Running org.jboss.as.controller.registry.CoreManagementResourceRegistrationUnitTestCase
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
> Running org.jboss.as.controller.registry.ExtendWildCardRegistrationUnitTestCase
> Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
>
> Results :
>
> Failed tests: testLegacyPathServices(org.jboss.as.controller.services.path.PathsTestCase): expected:<{transition from REMOVING to REMOVED=service jboss.server.path.add3, transition from STARTING to UP=service jboss.server.path.add3}> but was:<{transition from REMOVING to REMOVED=service jboss.server.path.add3}>
>
> Tests run: 215, Failures: 1, Errors: 0, Skipped: 11
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [2.450s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.607s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.550s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.211s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [10.406s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.098s]
> [INFO] JBoss Application Server: Controller Core ......... FAILURE [17.821s]
> [INFO] JBoss Application Server: Domain Management ....... SKIPPED
> [INFO] JBoss Application Server: Domain HTTP Interface ... SKIPPED
> [INFO] JBoss Application Server: Deployment Repository ... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: Platform MBean integration SKIPPED
> [INFO] JBoss Application Server: Process Controller ...... SKIPPED
> [INFO] JBoss Application Server: Network ................. SKIPPED
> [INFO] JBoss Application Server: Threading Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Server .................. SKIPPED
> [INFO] JBoss Application Server: Subsystem Test Harness .. SKIPPED
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Naming Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Management Client Content SKIPPED
> [INFO] JBoss Application Server: Host Controller ......... SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi ConfigurationAdmin . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: sosreport scripts ....... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 45.012s
> [INFO] Finished at: Wed Apr 04 13:54:32 EDT 2012
> [INFO] Final Memory: 120M/471M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-controller: There are test failures.
> [ERROR]
> [ERROR] Please refer to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/controller/target...> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn<goals> -rf :jboss-as-controller
> Recording test results
> Archiving artifacts
>
> _______________________________________________
> builds mailing list
> builds(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/builds
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
11 years, 8 months
