[JBoss JIRA] (JBIDE-18219) build info such as used git revisions/tags are not archived for our builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18219?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-18219 at 9/1/14 12:53 PM:
-------------------------------------------------------------
For JBT, we copy entire build folders so we get all the metadata. For example:
http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-...
http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0....
Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows:
{code:title=jenkins job name :: github branch@SHA :: github commit/SHA}
jbosstools-vpe_41 :: origin/jbosstools-4.1.x@86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3...
{code}
For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files:
JBDS entries are simple:
{code:title=github branch@SHA}
origin/jbosstools-4.2.x@5327ccb62016547090c569dafa272f99e59b4bc8
{code}
But JBT ones are more complex because of how they're collected:
{code:title=project name , plugin whose MANIFEST.MF is checked , plugin version , SHA , github branch@SHA , github URL for the source zip with SHA , source zip w/o path }
jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730... , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip
...
jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a50... , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip
{code}
The list of plugins whose manifests should be checked is here:
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
was (Author: nickboldt):
For JBT, we copy entire build folders so we get all the metadata. For example:
http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-...
http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0....
Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows:
{code:title=jenkins job name :: github branch@SHA :: github commit/SHA}
jbosstools-vpe_41 :: origin/jbosstools-4.1.x@86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3...
{code}
For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files:
JBDS entries are simple:
{code:title=github branch@SHA}
origin/jbosstools-4.2.x@5327ccb62016547090c569dafa272f99e59b4bc8
{code}
But JBT ones are more complex because of how they're collected:
{code:title=project-name , plugin-whose-MANIFEST.MF-is-checked , plugin-version , SHA , github branch@SHA , github URL for the source zip with SHA , source zip w/o path }
jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730... , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip
...
jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a50... , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip
{code}
> build info such as used git revisions/tags are not archived for our builds
> --------------------------------------------------------------------------
>
> Key: JBIDE-18219
> URL: https://issues.jboss.org/browse/JBIDE-18219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR1
>
>
> JBIDE-6958 and JBIDE-7444 was done to ensure we had the revision info and other results for a release, but seems we haven't archived this consinstelt over the years.
> We should review what info we definitely need but in general I would think archiving as much build info as possible would be a good practice anyway - at least for the releases (alpha, beta, final, GA etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18141) Include latest Tern 0.5.0.201408272110 and Angular JS 0.5.0.201408281218 into jbosstools TPs
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18141?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18141:
----------------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
> Include latest Tern 0.5.0.201408272110 and Angular JS 0.5.0.201408281218 into jbosstools TPs
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18141
> URL: https://issues.jboss.org/browse/JBIDE-18141
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
> Attachments: tern-version.png
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.5.0. It contains the important fixes required for JBIDE-17992:
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:* http://oss.opensagres.fr/tern.repository/0.5.0-SNAPSHOT/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/tern/0.5.0.2014...
> *Sources:* https://github.com/angelozerr/tern.java
> *Affected projects:* jbosstools-jst, jbosstools-aerogear
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.tools.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.group [0.4.0.201408101311]
> < tern-jsdt-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.4.0.201408101311]
> < tern.server.nodejs [0.4.0.201408101311]
> < tern-feature.feature.group [0.4.0.201408101311]
> < tern.core [0.4.0.201408101311]
> < tern.eclipse.ide.jsdt [0.4.0.201408101311]
> < tern-jsdt-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.ui [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.jar [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.jar [0.4.0.201408101311]
> < tern-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.ui [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.ui [0.4.0.201408101311]
> < tern.eclipse.ide.core [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.4.0.201408101311]
> < tern.eclipse [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.4.0.201408101311]
> > tern.eclipse.ide.tools.feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.group [0.5.0.201408272110]
> > tern-feature.feature.group [0.5.0.201408272110]
> > tern.server.nodejs [0.5.0.201408272110]
> > tern.core [0.5.0.201408272110]
> > tern.eclipse.ide.jsdt [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.5.0.201408272110]
> > tern.eclipse [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.ui [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.ui [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.tools.feature.feature.jar [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.core [0.5.0.201408272110]
> > tern.eclipse.ide.ui [0.5.0.201408272110]
> > tern-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.5.0.201408272110]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 25 unique IUs
> {code}
> Verification Steps:
> # EXEC: Open Installation Details dialog
> # EXEC: Go to Plugins tab
> # EXEC: Filter 'tern."
> # ASSERT: Dialog contains
> !tern-version.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18219) build info such as used git revisions/tags are not archived for our builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18219?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18219:
------------------------------------
For JBT, we copy entire build folders so we get all the metadata. For example:
http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-...
http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0....
Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows:
{code:title=jenkins job name :: github branch@SHA :: github commit/SHA}
jbosstools-vpe_41 :: origin/jbosstools-4.1.x@86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3...
{code}
For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files:
JBDS entries are simple:
{code:title=github branch@SHA}
origin/jbosstools-4.2.x@5327ccb62016547090c569dafa272f99e59b4bc8
{code}
But JBT ones are more complex because of how they're collected:
{code:title=project-name , plugin-whose-MANIFEST.MF-is-checked , plugin-version , SHA , github branch@SHA , github URL for the source zip with SHA , source zip w/o path }
jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730... , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip
...
jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a50... , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip
{code}
> build info such as used git revisions/tags are not archived for our builds
> --------------------------------------------------------------------------
>
> Key: JBIDE-18219
> URL: https://issues.jboss.org/browse/JBIDE-18219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR1
>
>
> JBIDE-6958 and JBIDE-7444 was done to ensure we had the revision info and other results for a release, but seems we haven't archived this consinstelt over the years.
> We should review what info we definitely need but in general I would think archiving as much build info as possible would be a good practice anyway - at least for the releases (alpha, beta, final, GA etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17987) Bogus syntax warning for EL 3.0 list literal
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17987?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17987.
-------------------------------
Verified with JBDS 8.0.0.CR1-v20140831-0335-B201
> Bogus syntax warning for EL 3.0 list literal
> --------------------------------------------
>
> Key: JBIDE-17987
> URL: https://issues.jboss.org/browse/JBIDE-17987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Rich DiCroce
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.CR1
>
>
> Assume you have an XHTML page that contains a JSF tag, and you want to use the EL 3.0 list literal to set an attribute on that tag, e.g.
> {code:xml}
> <my:tag someListProperty="#{[1, 2, 3]}"/>
> {code}
> The syntax is valid, but JBT reports the warning "EL syntax error: Expecting expression."
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12352) Remote management connection to servers cannot be established with IPv6
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12352?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-12352:
---------------------------------------
A remote server over IPV6 can be set as follows:
- configure a remote RSE server (I have tried a SSH-Only server)
- set Host name to ip6-localhost (::1)
- set Behavior Profile to Remote
- check "Listen on all interfaces to allow remote web connections" and "Expose your management port as the server's hostname"
- add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to the launch configuration
The launch configuration should contain the following options:
Start command:
{code}
java "-Dprogram.name=JBossTools: jboss-eap" -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=<SERVER_HOME>/standalone/log/boot.log" "-Dlogging.configuration=file:<SERVER_HOME>/standalone/configuration/logging.properties" "-Djboss.home.dir=<SERVER_HOME>" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=ip6-localhost -jar <SERVER_HOME>/jboss-modules.jar -mp "<SERVER_HOME>/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b ip6-localhost --server-config=standalone.xml -Djava.util.logging.manager=org.jboss.logmanager.LogManager&
{code}
Stop command:
{code}
<SERVER_HOME>/bin/jboss-cli.sh --controller=IP6-LOCALHOST:9999 --connect command=:shutdown
{code}
Sometimes it is necessary to start the server twice because it can't load the org.jboss.logmanager.LogManager class.
I think, the solution is to add jboss-logmanager-XXX.jar to bootclasspath (-Xbootclasspath/p:<path_to_jboss-logmanager.jar>)
The -Djboss.default.multicast.address=ff01::1 argument is related to clustering.
> Remote management connection to servers cannot be established with IPv6
> -----------------------------------------------------------------------
>
> Key: JBIDE-12352
> URL: https://issues.jboss.org/browse/JBIDE-12352
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.1.Final
> Environment: JBDS 5.0.1
> Fedora 17 32bit
> OpenJDK 1.6
> Reporter: Martin Malina
> Priority: Critical
> Fix For: 4.2.x, 4.3.0.Alpha1
>
>
> After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX.
> When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error:
> {code}
> Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.3.GA
> Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.3.GA
> Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.7.GA
> Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months