February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3120) AS 7 doesn't support -Djava.rmi.server.hostname

by Alexis Hassler (Created) (JIRA)

AS 7 doesn't support -Djava.rmi.server.hostname ----------------------------------------------- Key: AS7-3120 URL: https://issues.jboss.org/browse/AS7-3120 Project: Application Server 7 Issue Type: Enhancement Components: JMX Affects Versions: 7.1.0.Beta1b Environment: behind a firewall, with NAT Reporter: Alexis Hassler Assignee: John Bailey The -Djava.rmi.server.hostname system property is important when running JBoss behind a firewall. In the current version AS 7, the JMX server host is set from the management interface, but it doesn't work behind a firewall, with NAT. -- 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, 2 months

6
8
0 / 0

[JBoss JIRA] Created: (AS7-1908) Provide tooling for converting AS7-specific JGroups configuration to native JG config

by Radoslav Husar (JIRA)

Provide tooling for converting AS7-specific JGroups configuration to native JG config ------------------------------------------------------------------------------------- Key: AS7-1908 URL: https://issues.jboss.org/browse/AS7-1908 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Trivial We should be able to tests people's JG in AS7 configuration using standalone JGroups. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
17
0 / 0

[JBoss JIRA] (AS7-3474) JSR88 undeployment does not work

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created AS7-3474: ----------------------------------- Summary: JSR88 undeployment does not work Key: AS7-3474 URL: https://issues.jboss.org/browse/AS7-3474 Project: Application Server 7 Issue Type: Bug Components: JSR88 Affects Versions: 7.1.0.CR1b Reporter: Wolfgang Knauf Assignee: Thomas Diesler Attachments: JSR88Test.zip This is a followup of some mailing list discussion, tested against 7.1.0CR1 and 7.1.0 snapshot from 2012-01-13. It seems that JSR88 undeployment is not working under certain circumstances. Attached is a full sample. ====================== It works, when doing this: After deploy, I get a TargetModuleID from the ProgressObject. TargetModuleID[] modules = myProgressObject.getResultTargetModuleIDs(); If i perform an undeploy directly after deploying *using this TargetModuleID array*, it works. This is an array with one item. The output of "toString" for this items is this: [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7&serverHost=localhost&serverPort=9999,parent=null,type=ear,id=file:/C:/DOCUME~1/Knuffi/LOCALS~1/Temp/Stateless.ear] ====================== But in my undeploy job, I call "DeploymentManager.getAvailableModules" and search a file matching my name. So I find this module ("toString" output): [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7&serverHost=localhost&serverPort=9999,parent=null,type=ear,id=file:/C:/DOCUME~1/Knuffi/LOCALS~1/Temp/Stateless.ear] It seems to be identical to the above output, but undeploying a TargetModule array with this one item does not work: there is no status output on the server, though the client side seems to complete successfully. ====================== Attached ("JSR88Test.zip") is my deployer code as a self running sample, including the EAR file for deployment. To run it: 1) Import project in Eclipse. 2) Update build paths. 3) Compile (ignore my two warnings - they are just markers for myself) 4) edit "build.xml" and modify the property "serverRootDirectory" to point to your JBoss installation 5) open "build.xml" using Eclipse and run the target "deploy.j2ee.ear". The archive "Stateless.ear" (included in project root directory) should be deployed. 6) run the target "undeploy.j2ee.ear" => EAR should be undeployed, but this does not work. If you add an undeploy call directly after deployment in step 6 using the deployed TargetModuleID, it works. But it does not work when undeploying later (which should probably be the standard use case ;-)) -- 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, 2 months

2
9
0 / 0

[JBoss JIRA] (AS7-3458) CLI: remove native security realm fails

by Maas van den Berg (JIRA)

Maas van den Berg created AS7-3458: -------------------------------------- Summary: CLI: remove native security realm fails Key: AS7-3458 URL: https://issues.jboss.org/browse/AS7-3458 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1b Reporter: Maas van den Berg Assignee: Alexey Loubyansky Priority: Minor Fix For: 7.1.0.Final {noformat} /core-service=management/management-interface=native-interface:undefine-attribute(name=security-realm) {noformat} fails with {noformat} "outcome" => "failed", "failure-description" => "JBAS014746: port may not be null", "rolled-back" => true {noformat} while {noformat} /core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm) {noformat} succeeds Looks like input validation does not take "Alternatives" into account... -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3206) Upgrade to a GA of JBoss SASL

by Darran Lofthouse (Created) (JIRA)

Upgrade to a GA of JBoss SASL ----------------------------- Key: AS7-3206 URL: https://issues.jboss.org/browse/AS7-3206 Project: Application Server 7 Issue Type: Task Components: Remoting, Security Reporter: Darran Lofthouse Assignee: David Lloyd Priority: Blocker The JBoss SASL library is still Beta so we need to tag and release a GA, if any post or close to Final issues are found we can use a SP but at this stage SASL development should be complete for AS 7.1 -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1796) Fix the Pojo description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix the Pojo description providers for the improved validation in jboss-as-subsystem-test ----------------------------------------------------------------------------------------- Key: AS7-1796 URL: https://issues.jboss.org/browse/AS7-1796 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Ales Justin Fix For: 7.1.0.Alpha1 I added a test called PojoSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } {code} Returning null basically turns off validation of the providers. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
10
0 / 0

[JBoss JIRA] (AS7-3656) ServiceName of DataSource dependency in jdbc-store is wrong

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3656: --------------------------------- Summary: ServiceName of DataSource dependency in jdbc-store is wrong Key: AS7-3656 URL: https://issues.jboss.org/browse/AS7-3656 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Final -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3478) read-operation-description incorrect for distributed-cache

by Stan Silvert (JIRA)

Stan Silvert created AS7-3478: --------------------------------- Summary: read-operation-description incorrect for distributed-cache Key: AS7-3478 URL: https://issues.jboss.org/browse/AS7-3478 Project: Application Server 7 Issue Type: Bug Reporter: Stan Silvert Assignee: Richard Achmatowicz {noformat} /subsystem=infinispan/cache-container=hibernate/distributed-cache=distributed/:add(batching=false) { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: No child 'mode' exists", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {noformat} read-operation-description doesn't show "mode" as a required field and it doesn't restrict its values with "allowed" {noformat} /subsystem=infinispan/cache-container=hibernate/distributed-cache=*/:read-operation-description(name=add) { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Add a distributed cache to this cache container", "request-properties" => { ... "mode" => { "type" => STRING, "description" => "Sets the clustered cache mode, ASYNC for asynchronous operation, or SYNC for synchronous operation.", "expressions-allowed" => false, "required" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L }, ... } } {noformat} It should be: {noformat} "mode" => { "type" => STRING, "description" => "Sets the clustered cache mode, ASYNC for asynchronous operation, or SYNC for synchronous operation.", "expressions-allowed" => false, "required" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L "allowed" => [ "ASYNC", "SYNC" ] }, {noformat} -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] (AS7-3371) Low Performance of 7.1.0.CR1b - comparing with previous release

by Tomas Remes (JIRA)

Tomas Remes created AS7-3371: -------------------------------- Summary: Low Performance of 7.1.0.CR1b - comparing with previous release Key: AS7-3371 URL: https://issues.jboss.org/browse/AS7-3371 Project: Application Server 7 Issue Type: Enhancement Affects Versions: 7.1.0.CR1b Reporter: Tomas Remes Priority: Critical There is low (especially stress test) performance of AS 7.1.0.CR1b. Comparing to 7.1.0.Beta1 there is at least three times worse performance. You can see marked builds at https://hudson.qa.jboss.com/hudson/view/Weld/view/Weld-Performance-All/jo.... In artifacts there is the log.txt file, where you can check stress tests results. I have run it quite many times with same or mostly similar results. -- 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, 2 months

8
31
0 / 0

[JBoss JIRA] (AS7-3653) ClassNotFoundException: org.jboss.as.protocol.mgmt.ProtocolUtils

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-3653: ---------------------------------------- Summary: ClassNotFoundException: org.jboss.as.protocol.mgmt.ProtocolUtils Key: AS7-3653 URL: https://issues.jboss.org/browse/AS7-3653 Project: Application Server 7 Issue Type: Bug Reporter: Emanuel Muckenhuber Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.0.Final https://github.com/jbossas/jboss-as/commit/036238bd1e63cad0e42bea0058e736... - introduced class dependencies on the "org.jboss.as.protocol" module. Which can lead to java.lang.NoClassDefFoundError: org/jboss/as/protocol/mgmt/ProtocolUtils -- 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, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012