December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4155) WatchService error when deploying an app to a remote file system

by Martin Malina (JIRA)

Martin Malina created WFLY-4155: ----------------------------------- Summary: WatchService error when deploying an app to a remote file system Key: WFLY-4155 URL: https://issues.jboss.org/browse/WFLY-4155 Project: WildFly Issue Type: Bug Components: IO, Web (Undertow) Affects Versions: 8.1.0.Final Reporter: Martin Malina Assignee: Stuart Douglas I'm getting this output when I deploy a simple web project to WildFly 8.1: {code} 12:28:59,160 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy 12:28:59,211 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "dynproj.war" (runtime-name: "dynproj.war") 12:29:00,402 ERROR [io.undertow] (MSC service thread 1-1) UT005024: Could not register resource change listener for caching resource manager, automatic invalidation of cached resource will not work: java.lang.RuntimeException: java.io.IOException: Incorrect function. at org.xnio.nio.WatchServiceFileSystemWatcher.watchPath(WatchServiceFileSystemWatcher.java:179) at io.undertow.server.handlers.resource.FileResourceManager.registerResourceChangeListener(FileResourceManager.java:115) [undertow-core-1.0.15.Final.jar:1.0.15.Final] at org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:80) at io.undertow.server.handlers.resource.CachingResourceManager.<init>(CachingResourceManager.java:64) [undertow-core-1.0.15.Final.jar:1.0.15.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:505) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:245) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] Caused by: java.io.IOException: Incorrect function. at sun.nio.fs.WindowsWatchService$Poller.implRegister(WindowsWatchService.java:405) [rt.jar:1.7.0_51] at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260) [rt.jar:1.7.0_51] at sun.nio.fs.WindowsWatchService$Poller.run(WindowsWatchService.java:531) [rt.jar:1.7.0_51] ... 1 more 12:29:00,680 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /dynproj 12:29:00,750 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war" (runtime-name : "dynproj.war") 12:29:26,096 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /dynproj 12:29:26,157 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.1.0.Final 12:29:26,308 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment dynproj.war (runtime-name: dynproj.war) in 231ms 12:29:26,378 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dynproj.war" (runtime-name: "dynproj.war") 12:30:06,475 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy 12:30:06,496 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "dynproj.war" (runtime-name: "dynproj.war") 12:30:06,697 ERROR [io.undertow] (MSC service thread 1-2) UT005024: Could not register resource change listener for caching resource manager, automatic invalidation of cached resource will not work: java.lang.RuntimeException: java.io.IOException: Incorrect function. at org.xnio.nio.WatchServiceFileSystemWatcher.watchPath(WatchServiceFileSystemWatcher.java:179) at io.undertow.server.handlers.resource.FileResourceManager.registerResourceChangeListener(FileResourceManager.java:115) [undertow-core-1.0.15.Final.jar:1.0.15.Final] at org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:80) at io.undertow.server.handlers.resource.CachingResourceManager.<init>(CachingResourceManager.java:64) [undertow-core-1.0.15.Final.jar:1.0.15.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:505) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:245) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] Caused by: java.io.IOException: Incorrect function. at sun.nio.fs.WindowsWatchService$Poller.implRegister(WindowsWatchService.java:405) [rt.jar:1.7.0_51] at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260) [rt.jar:1.7.0_51] at sun.nio.fs.WindowsWatchService$Poller.run(WindowsWatchService.java:531) [rt.jar:1.7.0_51] ... 1 more 12:30:06,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /dynproj 12:30:06,767 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dynproj.war" (runtime-name : "dynproj.war") {code} My setup is this: OS X is my host OS, I'm running Windows 7 in virtualbox and have a shared folder from the host OS mounted in Windows. On this share, I have WildFly 8.1. I ran Eclipse Luna SR1 with JBoss Tools 4.2.1.CR1 installed, but it seems that this issue is not related to Eclipse. The main problem seems to be the remote FS. Dominik found this: https://docs.oracle.com/javase/7/docs/api/java/nio/file/WatchService.html {quote} If a watched file is not located on a local storage device then it is implementation specific if changes to the file can be detected. In particular, it is not required that changes to files carried out on remote systems be detected. {quote} So in fact this behavior may be kind of expected. But maybe instead of throwing errors, the server might want to have a more graceful behavior? Also, feel free to let me know if you need more details or if you want me to try different versions of WF or other server, but chances are this will happen in other versions as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-98) Compatility tests using Byteman hang

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-98?page=com.atlassian.jira.plugin.sys... ] Jan Kalina edited comment on ELY-98 at 12/4/14 6:15 AM: -------------------------------------------------------- Resolved replacing Byteman tests by JMockit compatibility tests. was (Author: honza889): Solved replacing Byteman tests by JMockit compatibility tests. > Compatility tests using Byteman hang > ------------------------------------ > > Key: ELY-98 > URL: https://issues.jboss.org/browse/ELY-98 > Project: WildFly Elytron > Issue Type: Task > Reporter: Peter Skopek > Assignee: Jan Kalina > > Tests were @Ignored. Check/fix the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-98) Compatility tests using Byteman hang

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-98?page=com.atlassian.jira.plugin.sys... ] Jan Kalina resolved ELY-98. --------------------------- Resolution: Done Solved replacing Byteman tests by JMockit compatibility tests. > Compatility tests using Byteman hang > ------------------------------------ > > Key: ELY-98 > URL: https://issues.jboss.org/browse/ELY-98 > Project: WildFly Elytron > Issue Type: Task > Reporter: Peter Skopek > Assignee: Jan Kalina > > Tests were @Ignored. Check/fix the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTEST-21) Intermittent fail of DataSourceOperationsUnitTestCase on IBM JDK 1.6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTEST-21?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTEST-21: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1100839|https://bugzilla.redhat.com/show_bug.cgi?id=1100839] from ASSIGNED to POST > Intermittent fail of DataSourceOperationsUnitTestCase on IBM JDK 1.6 > -------------------------------------------------------------------- > > Key: JBTEST-21 > URL: https://issues.jboss.org/browse/JBTEST-21 > Project: JBoss Test > Issue Type: Bug > Environment: IBM JDK > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > When test DataSourceOperationsUnitTestCase is build with IBM JDK 1.6 it fails with error : > Tests in error: > org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase: [SHRINKWRAP-93] Cannot use this JDK-based implementation to export as ZIP an archive with no content: 314225ff-6abf-4453-b69b-7dd12b707d65.jar: 0 assets > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4154) Provide an 'enable' parameter to the 'full-replace-deployment' operation

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4154?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4154: ------------------------------ Summary: Provide an 'enable' parameter to the 'full-replace-deployment' operation (was: Provide an 'enable' parameter to the 'full-replace-deoplyment' operation) > Provide an 'enable' parameter to the 'full-replace-deployment' operation > ------------------------------------------------------------------------ > > Key: WFLY-4154 > URL: https://issues.jboss.org/browse/WFLY-4154 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 9.0.0.Beta1 > > > Similar to the /deployment=*:add() operation the /:full-replace-deployment() operarion should provide an 'enable' parameter that defines wether or not the deplyment should be enabled after the reaplcement. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4154) Provide an 'enable' parameter to the 'full-replace-deoplyment' operation

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4154?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4154: ------------------------------ Fix Version/s: 9.0.0.Beta1 > Provide an 'enable' parameter to the 'full-replace-deoplyment' operation > ------------------------------------------------------------------------ > > Key: WFLY-4154 > URL: https://issues.jboss.org/browse/WFLY-4154 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Jason Greene > Fix For: 9.0.0.Beta1 > > > Similar to the /deployment=*:add() operation the /:full-replace-deployment() operarion should provide an 'enable' parameter that defines wether or not the deplyment should be enabled after the reaplcement. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4154) Provide an 'enable' parameter to the 'full-replace-deoplyment' operation

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4154?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4154: ------------------------------ Component/s: Domain Management > Provide an 'enable' parameter to the 'full-replace-deoplyment' operation > ------------------------------------------------------------------------ > > Key: WFLY-4154 > URL: https://issues.jboss.org/browse/WFLY-4154 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Jason Greene > Fix For: 9.0.0.Beta1 > > > Similar to the /deployment=*:add() operation the /:full-replace-deployment() operarion should provide an 'enable' parameter that defines wether or not the deplyment should be enabled after the reaplcement. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4154) Provide an 'enable' parameter to the 'full-replace-deoplyment' operation

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4154?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4154: ------------------------------ Assignee: Brian Stansberry (was: Jason Greene) > Provide an 'enable' parameter to the 'full-replace-deoplyment' operation > ------------------------------------------------------------------------ > > Key: WFLY-4154 > URL: https://issues.jboss.org/browse/WFLY-4154 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 9.0.0.Beta1 > > > Similar to the /deployment=*:add() operation the /:full-replace-deployment() operarion should provide an 'enable' parameter that defines wether or not the deplyment should be enabled after the reaplcement. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4153: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 900798|https://bugzilla.redhat.com/show_bug.cgi?id=900798] from NEW to POST > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4153: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900798 > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014