[JBoss JIRA] (WFLY-9577) Application Error when stopping Windows service
by Markus Stier (JIRA)
[ https://issues.jboss.org/browse/WFLY-9577?page=com.atlassian.jira.plugin.... ]
Markus Stier updated WFLY-9577:
-------------------------------
Affects Version/s: 10.1.0.Final
> Application Error when stopping Windows service
> -----------------------------------------------
>
> Key: WFLY-9577
> URL: https://issues.jboss.org/browse/WFLY-9577
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Environment: Windows 10, Windows Server 2012 R2
> Reporter: Markus Stier
> Assignee: Tomaz Cerar
>
> I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with
> {code}
> net stop <servicename>
> {code}
> the service terminates with an application error 1000.
> {code}
> Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d
> Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db
> Ausnahmecode: 0xc0000005
> Fehleroffset: 0x00000000000356a0
> ID des fehlerhaften Prozesses: 0x608
> Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8
> Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe
> Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
> Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a
> {code}
> This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336
> The bug is fixed in version 1.1.x. Please update the Daemon Service to this version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-9577) Application Error when stopping Windows service
by Markus Stier (JIRA)
Markus Stier created WFLY-9577:
----------------------------------
Summary: Application Error when stopping Windows service
Key: WFLY-9577
URL: https://issues.jboss.org/browse/WFLY-9577
Project: WildFly
Issue Type: Bug
Components: Scripts
Affects Versions: 11.0.0.Final
Environment: Windows 10, Windows Server 2012 R2
Reporter: Markus Stier
Assignee: Tomaz Cerar
I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with
{code}
net stop <servicename>
{code}
the service terminates with an application error 1000.
This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336
The bug is fixed in version 1.1.x. Please update the Daemon Service to this version.
{code}
Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000356a0
ID des fehlerhaften Prozesses: 0x608
Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8
Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-9577) Application Error when stopping Windows service
by Markus Stier (JIRA)
[ https://issues.jboss.org/browse/WFLY-9577?page=com.atlassian.jira.plugin.... ]
Markus Stier updated WFLY-9577:
-------------------------------
Description:
I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with
{code}
net stop <servicename>
{code}
the service terminates with an application error 1000.
{code}
Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000356a0
ID des fehlerhaften Prozesses: 0x608
Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8
Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a
{code}
This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336
The bug is fixed in version 1.1.x. Please update the Daemon Service to this version.
was:
I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with
{code}
net stop <servicename>
{code}
the service terminates with an application error 1000.
This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336
The bug is fixed in version 1.1.x. Please update the Daemon Service to this version.
{code}
Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000356a0
ID des fehlerhaften Prozesses: 0x608
Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8
Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a
{code}
> Application Error when stopping Windows service
> -----------------------------------------------
>
> Key: WFLY-9577
> URL: https://issues.jboss.org/browse/WFLY-9577
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Environment: Windows 10, Windows Server 2012 R2
> Reporter: Markus Stier
> Assignee: Tomaz Cerar
>
> I've installed Wildflay as a Windows Service using the provided scripts in <Root>\docs\contrib\scripts\service. When stopping the windows service with
> {code}
> net stop <servicename>
> {code}
> the service terminates with an application error 1000.
> {code}
> Name der fehlerhaften Anwendung: wildfly-service.exe, Version: 1.0.15.0, Zeitstempel: 0x51543b9d
> Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.18821, Zeitstempel: 0x59ba86db
> Ausnahmecode: 0xc0000005
> Fehleroffset: 0x00000000000356a0
> ID des fehlerhaften Prozesses: 0x608
> Startzeit der fehlerhaften Anwendung: 0x01d3637dd37fa9c8
> Pfad der fehlerhaften Anwendung: ....\wildfly-service.exe
> Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
> Berichtskennung: ee6df2e2-d0eb-11e7-80e2-00505698739a
> {code}
> This is a known bug in the Apache Commons Daemon Service Runner version which is used in the wildfly distribution. See https://issues.apache.org/jira/browse/DAEMON-336
> The bug is fixed in version 1.1.x. Please update the Daemon Service to this version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-9576) Dependencies with module-info.class cause warnings on application start
by Yannick Majoros (JIRA)
Yannick Majoros created WFLY-9576:
-------------------------------------
Summary: Dependencies with module-info.class cause warnings on application start
Key: WFLY-9576
URL: https://issues.jboss.org/browse/WFLY-9576
Project: WildFly
Issue Type: Bug
Reporter: Yannick Majoros
Assignee: Jason Greene
We have an issue when deploying any application that has dependencies that have a module-info.class. We had a similar problem in Wildfly-swarm.
Here is the stack:
{code}
11:10:36,986 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0003: Could not index class module-info.class at /content/file-hosting-application-1.0-SNAPSHOT.ear/file-hosting-web-1.0-SNAPSHOT.war/WEB-INF/lib/javax.json-api-1.1.jar: java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 18
at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:1417)
at org.jboss.jandex.Indexer.index(Indexer.java:1451)
at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99)
at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
I submitted a patch for wildfly-swarm (https://issues.jboss.org/browse/SWARM-1500), but the real solution would be to upgrade Jandex to 2.0.2. Is this planned?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2000:
-------------------------------------
I am sorry, but there is currently no workaround for the issue. I could try to have a look deeper in next sprints.
> Test Scenario: Not possible to use a global
> -------------------------------------------
>
> Key: DROOLS-2000
> URL: https://issues.jboss.org/browse/DROOLS-2000
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Reporter: Toni Rikkola
> Assignee: Jozef Marko
> Priority: Blocker
>
> Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s).
> Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3429) DuplicateServiceException when artifact name equals to alias
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3429?page=com.atlassian.jira.plugi... ]
jaikiran pai commented on WFCORE-3429:
--------------------------------------
The exception looks correct to me. In your jboss-deployment-structure.xml you are giving a (new) alias for the deployment module and happen to use the same name as the default module name (deployment.moduleA.ear in this case) for the deployment. Which effectively means that you are using a duplicate name for the module.
> DuplicateServiceException when artifact name equals to alias
> ------------------------------------------------------------
>
> Key: WFCORE-3429
> URL: https://issues.jboss.org/browse/WFCORE-3429
> Project: WildFly Core
> Issue Type: Task
> Components: Server
> Affects Versions: 2.2.0.Final
> Reporter: Сергей Машкевич
> Assignee: Jason Greene
> Priority: Minor
> Labels: support
>
> Suppose that there is an artifact «moduleA.ear» with the following deployment descriptor:
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <deployment>
> <module-alias name="deployment.moduleA.ear"/>
> </deployment>
> </jboss-deployment-structure>
> {code}
> When I try to deploy this module on *WildFly 10.1.0*, I get the DuplicateServiceException:
> {code:java}
> jboss.deployment.unit."moduleA.ear".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."moduleA.ear".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "moduleA.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.moduleA.ear".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.server.deployment.module.ModuleSpecProcessor.createModuleService(ModuleSpecProcessor.java:263)
> at org.jboss.as.server.deployment.module.ModuleSpecProcessor.deployModuleSpec(ModuleSpecProcessor.java:124)
> at org.jboss.as.server.deployment.module.ModuleSpecProcessor.deploy(ModuleSpecProcessor.java:87)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {code}
> I think this exception should not be thrown in this case. Could you fix it?
> Thanks,
> Sergey Mashkevich
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months