[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:
------------------------------
Environment: Windows 8, JDK8
> 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 resolved WFLY-4325.
-------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Rejected
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
> 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 commented on WFLY-4325:
-----------------------------------
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
> 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, 7 months
[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-707:
------------------------------------------------
jvahala(a)redhat.com changed the Status of [bug 1192054|https://bugzilla.redhat.com/show_bug.cgi?id=1192054] from ON_QA to VERIFIED
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
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 commented on WFLY-4325:
-----------------------------------
The case with Paths.get(getClass().getResource()) looks more interesting, can you reproduce this? that could be issue with VFS
> 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, 7 months
[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink commented on WFLY-2422:
----------------------------------------
Start a discussion on wildfly-dev list
http://lists.jboss.org/pipermail/wildfly-dev/2015-March/003674.html
> Simplify the remote-outbound connections
> ----------------------------------------
>
> Key: WFLY-2422
> URL: https://issues.jboss.org/browse/WFLY-2422
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Tomasz Adamski
> Fix For: 9.0.0.Beta1
>
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.
--
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 commented on WFLY-4325:
-----------------------------------
this looks to me as bug in brit reporting.
this is the offending code http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.birt.runtime/...
> 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, 7 months
[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-587?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated WFCORE-587:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1198186
> Wildfly does not log stack trace of an exception
> ------------------------------------------------
>
> Key: WFCORE-587
> URL: https://issues.jboss.org/browse/WFCORE-587
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 1.0.0.Alpha19
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Copied from BZ 1198186:
> AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE.
> https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29...
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
> 2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default"),
> ("connector" => "tp4")
> ] failed handling operation rollback -- java.lang.NullPointerException
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFCORE-587?page=com.atlassian.jira.plugin... ]
Tomas Hofman commented on WFCORE-587:
-------------------------------------
BZ Issue: https://bugzilla.redhat.com/show_bug.cgi?id=1198186
> Wildfly does not log stack trace of an exception
> ------------------------------------------------
>
> Key: WFCORE-587
> URL: https://issues.jboss.org/browse/WFCORE-587
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 1.0.0.Alpha19
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Copied from BZ 1198186:
> AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE.
> https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29...
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
> 2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default"),
> ("connector" => "tp4")
> ] failed handling operation rollback -- java.lang.NullPointerException
> 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months
[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception
by Tomas Hofman (JIRA)
Tomas Hofman created WFCORE-587:
-----------------------------------
Summary: Wildfly does not log stack trace of an exception
Key: WFCORE-587
URL: https://issues.jboss.org/browse/WFCORE-587
Project: WildFly Core
Issue Type: Bug
Components: Logging
Affects Versions: 1.0.0.Alpha19
Reporter: Tomas Hofman
Assignee: Tomas Hofman
Copied from BZ 1198186:
AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE.
https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29...
2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("connector" => "tp4")
] failed handling operation rollback -- java.lang.NullPointerException
2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 7 months