[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered
by Robert Smith (JIRA)
[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ]
Robert Smith updated WFLY-4414:
-------------------------------
Description:
We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
We use a non-standard session id in a web application as follows:
...
<distributable />
<session-config>
<cookie-config>
<name>VSOPSESSIONID</name>
</cookie-config>
</session-config>
...
During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.
In our 1st request we do:
request.getSession().setAttribute(KEY, value)
In our 2nd request we do:
request.getSession.getAttribute(KEY)
The second request always returns null.
When we remove the custom session id, the session data is avaliable.
> Non Standard SESSIONID not clustered
> ------------------------------------
>
> Key: WFLY-4414
> URL: https://issues.jboss.org/browse/WFLY-4414
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Robert Smith
> Assignee: Jason Greene
>
> We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
> We use a non-standard session id in a web application as follows:
> ...
> <distributable />
> <session-config>
> <cookie-config>
> <name>VSOPSESSIONID</name>
> </cookie-config>
> </session-config>
> ...
> During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.
> In our 1st request we do:
> request.getSession().setAttribute(KEY, value)
> In our 2nd request we do:
> request.getSession.getAttribute(KEY)
> The second request always returns null.
> When we remove the custom session id, the session data is avaliable.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (JGRP-1919) SimpleChat example doesn't work
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1919?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1919:
--------------------------------
No, you need to pass the system prop to the java command, e.g.
{{java -Djava.net.preferIPv4Stack=true org.jgroups.demos.Draw}}
> SimpleChat example doesn't work
> -------------------------------
>
> Key: JGRP-1919
> URL: https://issues.jboss.org/browse/JGRP-1919
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.2
> Reporter: rama rama
> Assignee: Bela Ban
> Fix For: 3.4.8
>
>
> Hello,
> i have try to run SimpleChat.java class (provided on example) but it doesn't work... with version 3.6.2 i run two java but they doesn't 'connect' eachother..
> i got this error (if i use ipv4 the error persist, it change only the fact that is an ipv4 ip)
> ----
> WARNING: JGRP000034: iMac-di-Rama-78: failure sending message to /ff0e:0:0:0:0:8:8:8: java.io.IOException: No route to host
> ----
> version 3.4.8 isn't affected, and two process
> runned with this version connect and i can see the messages.
> Also, no error is displayed on 3.4.8
> just to avoid misunderstanding
> 1. i have read the other 'similar' message
> 2. i have try
> java org.jgroups.tests.McastReceiverTest +
> java org.jgroups.tests.McastSenderTest
> and work
> 3. i have try to use ipv4 and jgroups.bind_addr props
> what is strange is that with 3.4.8 the example work out of the box.
> os: osx
> java: 1.7.0_76
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (JGRP-1919) SimpleChat example doesn't work
by rama rama (JIRA)
[ https://issues.jboss.org/browse/JGRP-1919?page=com.atlassian.jira.plugin.... ]
rama rama commented on JGRP-1919:
---------------------------------
i use
public static void main(String[] args) throws Exception {
System.setProperty("java.net.preferIPv4Stack", "true"); -->
System.setProperty("jgroups.bind_addr","192.168.2.123"); -->
new SimpleChat().start();
}
shouldn't be the same?
> SimpleChat example doesn't work
> -------------------------------
>
> Key: JGRP-1919
> URL: https://issues.jboss.org/browse/JGRP-1919
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.2
> Reporter: rama rama
> Assignee: Bela Ban
> Fix For: 3.4.8
>
>
> Hello,
> i have try to run SimpleChat.java class (provided on example) but it doesn't work... with version 3.6.2 i run two java but they doesn't 'connect' eachother..
> i got this error (if i use ipv4 the error persist, it change only the fact that is an ipv4 ip)
> ----
> WARNING: JGRP000034: iMac-di-Rama-78: failure sending message to /ff0e:0:0:0:0:8:8:8: java.io.IOException: No route to host
> ----
> version 3.4.8 isn't affected, and two process
> runned with this version connect and i can see the messages.
> Also, no error is displayed on 3.4.8
> just to avoid misunderstanding
> 1. i have read the other 'similar' message
> 2. i have try
> java org.jgroups.tests.McastReceiverTest +
> java org.jgroups.tests.McastSenderTest
> and work
> 3. i have try to use ipv4 and jgroups.bind_addr props
> what is strange is that with 3.4.8 the example work out of the box.
> os: osx
> java: 1.7.0_76
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (JGRP-1919) SimpleChat example doesn't work
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1919?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1919:
--------------------------------
Use -Djava.net.preferIPv4Stack=true to start your instances
> SimpleChat example doesn't work
> -------------------------------
>
> Key: JGRP-1919
> URL: https://issues.jboss.org/browse/JGRP-1919
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.2
> Reporter: rama rama
> Assignee: Bela Ban
> Fix For: 3.4.8
>
>
> Hello,
> i have try to run SimpleChat.java class (provided on example) but it doesn't work... with version 3.6.2 i run two java but they doesn't 'connect' eachother..
> i got this error (if i use ipv4 the error persist, it change only the fact that is an ipv4 ip)
> ----
> WARNING: JGRP000034: iMac-di-Rama-78: failure sending message to /ff0e:0:0:0:0:8:8:8: java.io.IOException: No route to host
> ----
> version 3.4.8 isn't affected, and two process
> runned with this version connect and i can see the messages.
> Also, no error is displayed on 3.4.8
> just to avoid misunderstanding
> 1. i have read the other 'similar' message
> 2. i have try
> java org.jgroups.tests.McastReceiverTest +
> java org.jgroups.tests.McastSenderTest
> and work
> 3. i have try to use ipv4 and jgroups.bind_addr props
> what is strange is that with 3.4.8 the example work out of the box.
> os: osx
> java: 1.7.0_76
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-227) RejectedExecutionException when closing ModelControllerClient client
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-227?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-227:
------------------------------------------------
Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1193926|https://bugzilla.redhat.com/show_bug.cgi?id=1193926] from NEW to POST
> RejectedExecutionException when closing ModelControllerClient client
> --------------------------------------------------------------------
>
> Key: WFCORE-227
> URL: https://issues.jboss.org/browse/WFCORE-227
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Remoting
> Affects Versions: 1.0.0.Alpha11
> Reporter: Alessio Soldano
> Assignee: David Lloyd
> Fix For: 1.0.0.Alpha15
>
>
> After wildfly-core 1.0.0.Alpha11 has been included in WFLY master, I'm seeing hundreds of the following exceptions in the logs when running the JBossWS-CXF testsuite:
> {noformat}
> Exception in thread "Remoting "management-client" task-4" java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteConnectionChannel$3@5651c0c2 rejected from org.xnio.XnioWorker$TaskPool@11462cd4[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 4]
> at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048)
> at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372)
> at org.xnio.XnioWorker.execute(XnioWorker.java:741)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.receiveMessage(RemoteConnectionChannel.java:363)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:107)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:451)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception is logged just after the org.jboss.as.webservices.deployer.RemoteDeployer calls the RemotingModelControllerClient#close method.
> The issue seems to be related to some kind of race condition, as trying to reproduce it with an attached debugger is not possible.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 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 edited comment on WFLY-4325 at 3/9/15 11:59 AM:
------------------------------------------------------------
Closing as it is caused/exposed by change in JDK, not WildFly.
was (Author: ctomc):
Closing as it is caused by regression in JDK, not WildFly.
> 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
> Environment: Windows 8, JDK8
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> 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, 7 months
[JBoss JIRA] (JGRP-1919) SimpleChat example doesn't work
by rama rama (JIRA)
rama rama created JGRP-1919:
-------------------------------
Summary: SimpleChat example doesn't work
Key: JGRP-1919
URL: https://issues.jboss.org/browse/JGRP-1919
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.2
Reporter: rama rama
Assignee: Bela Ban
Fix For: 3.4.8
Hello,
i have try to run SimpleChat.java class (provided on example) but it doesn't work... with version 3.6.2 i run two java but they doesn't 'connect' eachother..
i got this error (if i use ipv4 the error persist, it change only the fact that is an ipv4 ip)
----
WARNING: JGRP000034: iMac-di-Rama-78: failure sending message to /ff0e:0:0:0:0:8:8:8: java.io.IOException: No route to host
----
version 3.4.8 isn't affected, and two process
runned with this version connect and i can see the messages.
Also, no error is displayed on 3.4.8
just to avoid misunderstanding
1. i have read the other 'similar' message
2. i have try
java org.jgroups.tests.McastReceiverTest +
java org.jgroups.tests.McastSenderTest
and work
3. i have try to use ipv4 and jgroups.bind_addr props
what is strange is that with 3.4.8 the example work out of the box.
os: osx
java: 1.7.0_76
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 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 edited comment on WFLY-4325 at 3/9/15 11:02 AM:
------------------------------------------------------------
Looking bit further, i think the regression is caused by upgrading JDK7 --> JDK8 and how java.util.logging.FileHandler.openFiles() is implemented.
On java7 is does:
{code:java}
FileChannel fc;
try {
lockStream = new FileOutputStream(lockFileName);
fc = lockStream.getChannel();
} catch (IOException ix) {
// We got an IOException while trying to open the file.
// Try the next file.
continue;
}
{code}
and in JDK8 it does
{code:java}
try {
lockFileChannel = FileChannel.open(Paths.get(lockFileName),
CREATE_NEW, WRITE);
} catch (FileAlreadyExistsException ix) {
// try the next lock file name in the sequence
continue;
}
{code}
and the difference is that it uses Paths.get()
so in both cases, brit returns the same, but if pass path with "/" Paths.get() it fails where File api is happy about it.
To be fair, Path api behaves correctly...
was (Author: ctomc):
Looking bit further, i think the regression is caused by upgrading JDK7 --> JDK8 and how java.util.logging.FileHandler.openFiles() is implemented.
On java7 is does:
{code:java}
FileChannel fc;
...
try {
lockStream = new FileOutputStream(lockFileName);
fc = lockStream.getChannel();
} catch (IOException ix) {
// We got an IOException while trying to open the file.
// Try the next file.
}
{code}
and in JDK8 it does
{code:java}
try {
lockFileChannel = FileChannel.open(Paths.get(lockFileName),
CREATE_NEW, WRITE);
} catch (FileAlreadyExistsException ix) {
// try the next lock file name in the sequence
continue;
}
{code}
and the difference is that it uses Paths.get()
so in both cases, brit returns the same, but if pass path with "/" Paths.get() it fails where File api is happy about it.
To be fair, Path api behaves correctly...
> 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
> Environment: Windows 8, JDK8
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> 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, 7 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 updated WFLY-4325:
------------------------------
Workaround Description: use absolute references or run on JDK7 not 8 (was: use absolute references)
> 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
> Fix For: 9.0.0.Beta1
>
>
> 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, 7 months