[JBoss JIRA] (WFLY-4305) Script rumbles on after error
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-4305?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf updated WFLY-4305:
--------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/7228 (was: https://github.com/wildfly/wildfly/pull/7153)
> Script rumbles on after error
> -----------------------------
>
> Key: WFLY-4305
> URL: https://issues.jboss.org/browse/WFLY-4305
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Carlo de Wolf
> Assignee: Carlo de Wolf
> Fix For: 9.0.0.Beta1
>
>
> After a failure in the script it rumbles on.
> {noformat}
> (master) carlo@devel01:~/work/wildfly$ ./build.sh clean
> ./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found
> Archive: maven.zip
> End-of-central-directory signature not found. Either this file is not
> a zipfile, or it constitutes one disk of a multi-part archive. In the
> latter case the central directory and zipfile comment will be found on
> the last disk(s) of this archive.
> unzip: cannot find zipfile directory in one of maven.zip or
> maven.zip.zip, and cannot find maven.zip.ZIP, period.
> mv: cannot stat ‘apache-maven*’: No such file or directory
> build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-4325) Relative path error in context parameter on Windows
by Nicklas Karlsson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4325?page=com.atlassian.jira.plugin.... ]
Nicklas Karlsson commented on WFLY-4325:
----------------------------------------
Actually, I recall I stumbled on this again once more, I think I was using
Paths.get(URI) and passing in an uri converted in a servlet doing getClass().getResourceAsStream... etc
> Relative path error in context parameter on Windows
> ---------------------------------------------------
>
> Key: WFLY-4325
> URL: https://issues.jboss.org/browse/WFLY-4325
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.Beta1
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
>
> Deploying the Eclipse BIRT viewer with a context parameter containing a relative reference as a context parameter on a windows machine
> <param-value>../birtdata/logs</param-value>
> results in
> {quote}
> 2015-02-05 10:07:37,736 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./birt: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./birt: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:221)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> Caused by: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck
> at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> at java.nio.file.Paths.get(Paths.java:84)
> at java.util.logging.FileHandler.openFiles(FileHandler.java:438)
> at java.util.logging.FileHandler.<init>(FileHandler.java:318)
> at org.eclipse.birt.report.utility.LoggingUtil.initFileLogger(LoggingUtil.java:103)
> at org.eclipse.birt.report.utility.LoggingUtil.configureLoggers(LoggingUtil.java:76)
> at org.eclipse.birt.report.service.ReportEngineService.<init>(ReportEngineService.java:229)
> at org.eclipse.birt.report.service.ReportEngineService.initEngineInstance(ReportEngineService.java:271)
> at org.eclipse.birt.report.service.BirtViewerReportService.<init>(BirtViewerReportService.java:83)
> at org.eclipse.birt.report.listener.ViewerServletContextListener.contextInitialized(ViewerServletContextListener.java:57)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:192)
> ... 7 more
> {quote}
> This used to work on the 8.x-series
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBASMP-47) execute-commands on EAP6.1.0
by Lionel Orellana (JIRA)
[ https://issues.jboss.org/browse/JBASMP-47?page=com.atlassian.jira.plugin.... ]
Lionel Orellana commented on JBASMP-47:
---------------------------------------
7.2.0.Final fails with a similar error.
Unexpected element '{urn:jboss:cli:1.2}jboss-cli'
I got around it by forcing the dependency to 7.3.0.Final-redhat-14.
> execute-commands on EAP6.1.0
> ----------------------------
>
> Key: JBASMP-47
> URL: https://issues.jboss.org/browse/JBASMP-47
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Affects Versions: 7.4.Final
> Reporter: wiktorowski maximilien
> Assignee: James Perkins
> Fix For: 7.5.Final
>
>
> I'm trying to use execute-commands goal with EAP 6.1.0 and got :
> Failed to initialize CLI context: Failed to parse jboss-cli.xml: Unexpected element: resolve-parameter-values.
> CLI dependency should be updated:
> [INFO] Plugin Resolved: jboss-as-maven-plugin-7.4.Final.jar
> .....
> [INFO] Plugin Dependency Resolved: jboss-as-cli-7.1.2.Final.jar
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JGRP-1910) MERGE3: Do not lose any members from view during a series of merges
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1910?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JGRP-1910:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1189839|https://bugzilla.redhat.com/show_bug.cgi?id=1189839] from MODIFIED to ON_QA
> MERGE3: Do not lose any members from view during a series of merges
> -------------------------------------------------------------------
>
> Key: JGRP-1910
> URL: https://issues.jboss.org/browse/JGRP-1910
> Project: JGroups
> Issue Type: Bug
> Reporter: Radim Vansa
> Assignee: Bela Ban
> Fix For: 3.6.3
>
> Attachments: SplitMergeTest.java
>
>
> When connection between nodes is re-established, MERGE3 should merge the cluster together. This often does not involve a single MergeView but a series of such events. The problematic property of this protocol is that some of those views can lack certain members, though these are reachable.
> This causes problem in Infinispan since the cache cannot be fully rebalanced before another merge arrives, and all owners of certain segment can be gradually removed (and added again) to the view, while this is not detected as partition but crashed nodes -> losing all owners means data loss.
> Removing members from view should be the role of FDx protocols, not MERGEx.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-4382) Functionality to allow symbolic links
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4382?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4382:
--------------------------------------
Assignee: Jakub Pýcha (was: Tomaz Cerar)
> Functionality to allow symbolic links
> -------------------------------------
>
> Key: WFLY-4382
> URL: https://issues.jboss.org/browse/WFLY-4382
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Reporter: Erdal Yildiz
> Assignee: Jakub Pýcha
> Priority: Minor
>
> There should be a possibility to configure that wildfly follows symbolic links.
> Example which describes the problem:
> $wildflyHome/welcome-content/test/index.html --> localhost:8080/test/index.html ==> works.
> $wildflyHome/welcome-content/symlink/index.html --> localhost:8080/symlink/index.html ==> doesn't work.
> "symlink" is the symbolic link which is created by
> ln -s /path/to/symlink $wildflyHome/welcome-content
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-4325) Relative path error in context parameter on Windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4325?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-4325:
---------------------------------
Assignee: Tomaz Cerar (was: Jason Greene)
> Relative path error in context parameter on Windows
> ---------------------------------------------------
>
> Key: WFLY-4325
> URL: https://issues.jboss.org/browse/WFLY-4325
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.Beta1
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
>
> Deploying the Eclipse BIRT viewer with a context parameter containing a relative reference as a context parameter on a windows machine
> <param-value>../birtdata/logs</param-value>
> results in
> {quote}
> 2015-02-05 10:07:37,736 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./birt: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./birt: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:221)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> Caused by: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck
> at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> at java.nio.file.Paths.get(Paths.java:84)
> at java.util.logging.FileHandler.openFiles(FileHandler.java:438)
> at java.util.logging.FileHandler.<init>(FileHandler.java:318)
> at org.eclipse.birt.report.utility.LoggingUtil.initFileLogger(LoggingUtil.java:103)
> at org.eclipse.birt.report.utility.LoggingUtil.configureLoggers(LoggingUtil.java:76)
> at org.eclipse.birt.report.service.ReportEngineService.<init>(ReportEngineService.java:229)
> at org.eclipse.birt.report.service.ReportEngineService.initEngineInstance(ReportEngineService.java:271)
> at org.eclipse.birt.report.service.BirtViewerReportService.<init>(BirtViewerReportService.java:83)
> at org.eclipse.birt.report.listener.ViewerServletContextListener.contextInitialized(ViewerServletContextListener.java:57)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:192)
> ... 7 more
> {quote}
> This used to work on the 8.x-series
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-3764) Problem with Infinispan and transactions
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3764?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3764:
---------------------------------
Assignee: Paul Ferraro (was: Mircea Markus)
> Problem with Infinispan and transactions
> -----------------------------------------
>
> Key: WFLY-3764
> URL: https://issues.jboss.org/browse/WFLY-3764
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Web (Undertow)
> Affects Versions: 8.0.0.Final, 8.1.0.Final
> Environment: Operating System: Redhat 6
> jdk1.7.0_51
> x86_64
> Reporter: Joel Sebastian
> Assignee: Paul Ferraro
> Labels: domain, httpsession, infinispan, transactions, web
>
> We are using Jasing CAS 3.5.2 for Single Sign On purposes deployed on a server in a Wildfly 8.0.0 Final domain (yesterday we upgraded to 8.1.0 Final).
> The application is working just fine, but in sometimes we detect this error:
> 2014-08-22 00:30:50,365 ERROR [io.undertow.request] (default task-85) UT005023: Exception handling request to /SSO/login: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: Cookie name "comment" is a reserved token
> After this error the applications starts to fail with this error:
> 2014-08-22 00:31:24,387 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [15 seconds] on key [Urkr0TVHiwJ95KJnuhz9IB9n] for requestor [GlobalTransaction:<master:sso-server-1/web>:308:local]! Lock held by [GlobalTransaction:<master:sso-server-1/web>:296:local]
> 2014-08-22 00:31:24,407 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=308}, status=1} is not in a valid state to be invoking cache operations on.
> After this happens we need to restart the server, because the application cannot be restored from those errors.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (WFLY-3764) Problem with Infinispan and transactions
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3764?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3764:
------------------------------
Component/s: Clustering
> Problem with Infinispan and transactions
> -----------------------------------------
>
> Key: WFLY-3764
> URL: https://issues.jboss.org/browse/WFLY-3764
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Web (Undertow)
> Affects Versions: 8.0.0.Final, 8.1.0.Final
> Environment: Operating System: Redhat 6
> jdk1.7.0_51
> x86_64
> Reporter: Joel Sebastian
> Assignee: Mircea Markus
> Labels: domain, httpsession, infinispan, transactions, web
>
> We are using Jasing CAS 3.5.2 for Single Sign On purposes deployed on a server in a Wildfly 8.0.0 Final domain (yesterday we upgraded to 8.1.0 Final).
> The application is working just fine, but in sometimes we detect this error:
> 2014-08-22 00:30:50,365 ERROR [io.undertow.request] (default task-85) UT005023: Exception handling request to /SSO/login: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: Cookie name "comment" is a reserved token
> After this error the applications starts to fail with this error:
> 2014-08-22 00:31:24,387 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [15 seconds] on key [Urkr0TVHiwJ95KJnuhz9IB9n] for requestor [GlobalTransaction:<master:sso-server-1/web>:308:local]! Lock held by [GlobalTransaction:<master:sso-server-1/web>:296:local]
> 2014-08-22 00:31:24,407 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=308}, status=1} is not in a valid state to be invoking cache operations on.
> After this happens we need to restart the server, because the application cannot be restored from those errors.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months