Skip to content

Instantly share code, notes, and snippets.

@kabir
kabir / gist:5823452
Last active December 18, 2015 18:09
sfcoy eclipse settings
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130521-0416
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
@kabir
kabir / gist:3783311
Created September 25, 2012 17:31
Differences with 7.1.2.Final
These are all with Report on differences in the model when the management versions are different? y/[n]: y
>>>>>DOMAIN
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [launch-type]
<<ok
Different 'nillable' for attribute 'local-host-name'. Current: true; legacy: false
@kabir
kabir / gist:3762099
Created September 21, 2012 15:15
Core resource model comparison
STANDALONE
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.4.0 =======
--- Problems for relative address to root []:
Missing attributes in current: [profile-name]; missing in legacy [running-mode]
>>> Legacy was wrong - profile name was only used in domain servers, DP made no distinction
Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false
>>> Legacy was wrong
[[email protected]:9999 /] :read-resource
{
"outcome" => "success",
"result" => {
"deployment" => undefined,
"management-major-version" => 1,
"management-minor-version" => 2,
"name" => "Unnamed Domain",
"path" => undefined,
"product-name" => undefined,
[[email protected]:9999 /] :read-children-names(child-type=host)
{
"outcome" => "success",
"result" => [
"SlaveA",
"master"
]
}
[[email protected]:9999 /] /host=master:read-
<?xml version='1.0' encoding='UTF-8'?>
<host xmlns="urn:jboss:domain:1.3" name="${jboss.slave.name}">
<management>
<security-realms>
<security-realm name="ManagementRealm">
<server-identities>
<!-- Replace this with either a base64 password of your own, or use a vault with a vault expression -->
<secret value="dGVzdA=="/>
[Host Controller] 14:24:37,840 ERROR [org.jboss.remoting.remote.connection] (Remoting "ip-10-62-85-118:MANAGEMENT" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
[Host Controller] 14:24:37,849 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.
[Host Controller] 14:24:37,916 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
[Host Controller] JBAS014775: New missing/unsatisfied dependencies:
[Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (missing) dependents: [service jboss.remoting.authentication_provider.management, service jboss.domain.controller.connection]
[Host Controller]
[Host Controller] 14:24:37,944 INFO [org.jboss.as.controller] (MSC ser