September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service

by Nicklas Karlsson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ] Nicklas Karlsson commented on WFCORE-1719: ------------------------------------------ Confirmed in 10.1.0-Final Amusingly enough, the preceding line is a comment that no quotes should be used but they are still there... > Wildfly 10.1.0.CR1 does not start as a windows service > ------------------------------------------------------ > > Key: WFCORE-1719 > URL: https://issues.jboss.org/browse/WFCORE-1719 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.Final > Environment: Windows 8/Windows Server 2012 > Oracle Java 8 > Reporter: Anton Yudin > Assignee: Tomaz Cerar > Fix For: 3.0.0.Alpha6, 2.2.1.CR1 > > > Wildfly fails to start as a windows service. > Installation works fine: > {code} > .\service.bat install > Using the X86-64bit version of prunsrv > "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown" > Service Wildfly installed > {code} > Windows reports this error: > {quote} > Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1. > {quote} > {code} > Event log report: > The Wildfly service terminated with the following service-specific error: > Incorrect function. > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> > <System> > <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/> > <EventID Qualifiers="49152">7024</EventID> > <Version>0</Version> > <Level>2</Level> > <Task>0</Task> > <Opcode>0</Opcode> > <Keywords>0x8080000000000000</Keywords> > <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/> > <EventRecordID>196500</EventRecordID> > <Correlation/> > <Execution ProcessID="668" ThreadID="10184"/> > <Channel>System</Channel> > <Computer>ITPC7.intra.rfgh.net</Computer> > <Security/> > </System> > - > <EventData> > <Data Name="param1">Wildfly</Data> > <Data Name="param2">%%1</Data> > <Binary>570069006C00640066006C0079000000</Binary> > </EventData> > </Event> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-180) [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-180?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-180: -------------------------------------- Labels: 5.0 mm-integration-hawkular-qe (was: ) > [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support > --------------------------------------------------------------------------------- > > Key: HAWKULARQE-180 > URL: https://issues.jboss.org/browse/HAWKULARQE-180 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: 5.0, mm-integration-hawkular-qe > > See https://issues.jboss.org/browse/JMAN4-194 > Development is done MiQ Upstream: https://github.com/ManageIQ/manageiq-providers-hawkular/pull/30 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-180) [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support - Sprint 69

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-180?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-180: -------------------------------------- Summary: [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support - Sprint 69 (was: [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support) > [QE] - JMAN4-194 - (JDR Reports) Collection of configuration and logs for Support - Sprint 69 > --------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-180 > URL: https://issues.jboss.org/browse/HAWKULARQE-180 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: 5.0, mm-integration-hawkular-qe > > See https://issues.jboss.org/browse/JMAN4-194 > Development is done MiQ Upstream: https://github.com/ManageIQ/manageiq-providers-hawkular/pull/30 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9351) Upgrade JBoss EJB Client to 4.0.1.Final (Legacy to 3.0.1.Final)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9351?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9351: ------------------------------- Summary: Upgrade JBoss EJB Client to 4.0.1.Final (Legacy to 3.0.1.Final) (was: Upgrade JBoss EJB Client to 4.0.1.Final) > Upgrade JBoss EJB Client to 4.0.1.Final (Legacy to 3.0.1.Final) > --------------------------------------------------------------- > > Key: WFLY-9351 > URL: https://issues.jboss.org/browse/WFLY-9351 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9359) wildfly8.1 can't graceful shut down JNDI perfectly

by fantesy so (JIRA)

fantesy so created WFLY-9359: -------------------------------- Summary: wildfly8.1 can't graceful shut down JNDI perfectly Key: WFLY-9359 URL: https://issues.jboss.org/browse/WFLY-9359 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 8.x.x TBD Environment: wildfly8.1.0.Final servlet3.0 mysql5.x eclipse neon.3 jdk1.7 Reporter: fantesy so Fix For: 8.1.0.Final Attachments: DemoServlet.java, server.log I create a servlet to query some mysql data. And I use jboss JNDI which defined in standalone.xml。 I want this querying is needs to be done 1000 times。But when I shut down wildfly8.1.0 suddenly during the querying is running, the querying can't finished and will throw some exception is server.log。But I do this test case in apache-tomcat-8.0.36 and websphere7, the querying is finished before server is down。 So I this wildfly8.1.x cant shutdown graceful perfectly。 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9358) Remote EJB clustered node discovery is ignored

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9358?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9358: ------------------------------- Description: Due to issues with affinity processing, authentication stickiness, and user transaction stickiness, node topology information is effectively ignored, causing balancing and failover to not behave properly. (was: If a client use PROVIDER_URL as property for InitialContext it is expected that if one of the servers is available the invocation is successful. But if the first server is not available the invocation fail as the provided proxy has an URI affinity even if there are multiple servers listed Context.PROVIDER_URL == "http-remoting://localhost:8080,http-remoting://localhost:8180" The proxy looks like this: Proxy for remote EJB StatelessEJBLocator for "EAP71-PLAYGROUND-server/ejb/SimpleBean", view is interface org.jboss.wfink.eap71.playground.Simple, affinity is URI<http-remoting://localhost:8080>) > Remote EJB clustered node discovery is ignored > ---------------------------------------------- > > Key: WFLY-9358 > URL: https://issues.jboss.org/browse/WFLY-9358 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Priority: Blocker > > Due to issues with affinity processing, authentication stickiness, and user transaction stickiness, node topology information is effectively ignored, causing balancing and failover to not behave properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9358) Remote EJB clustered node discovery is ignored

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9358?page=com.atlassian.jira.plugin.... ] Jason Greene moved JBEAP-13186 to WFLY-9358: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9358 (was: JBEAP-13186) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB Naming Remoting (was: EJB) (was: Naming) (was: Remoting) Affects Version/s: (was: 7.1.0.CR1) > Remote EJB clustered node discovery is ignored > ---------------------------------------------- > > Key: WFLY-9358 > URL: https://issues.jboss.org/browse/WFLY-9358 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > > If a client use PROVIDER_URL as property for InitialContext it is expected that if one of the servers is available the invocation is successful. > But if the first server is not available the invocation fail as the provided proxy has an URI affinity even if there are multiple servers listed > Context.PROVIDER_URL == "http-remoting://localhost:8080,http-remoting://localhost:8180" > The proxy looks like this: > Proxy for remote EJB StatelessEJBLocator for "EAP71-PLAYGROUND-server/ejb/SimpleBean", view is interface org.jboss.wfink.eap71.playground.Simple, affinity is URI<http-remoting://localhost:8080> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9358) Remote EJB clustered node discovery is ignored

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9358?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-9358: ---------------------------------- Assignee: Jason Greene (was: David Lloyd) > Remote EJB clustered node discovery is ignored > ---------------------------------------------- > > Key: WFLY-9358 > URL: https://issues.jboss.org/browse/WFLY-9358 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Priority: Blocker > > If a client use PROVIDER_URL as property for InitialContext it is expected that if one of the servers is available the invocation is successful. > But if the first server is not available the invocation fail as the provided proxy has an URI affinity even if there are multiple servers listed > Context.PROVIDER_URL == "http-remoting://localhost:8080,http-remoting://localhost:8180" > The proxy looks like this: > Proxy for remote EJB StatelessEJBLocator for "EAP71-PLAYGROUND-server/ejb/SimpleBean", view is interface org.jboss.wfink.eap71.playground.Simple, affinity is URI<http-remoting://localhost:8080> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9357) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9357?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9357: ------------------------------- Summary: User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used (was: [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used) > User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used > ------------------------------------------------------------------------------------------------- > > Key: WFLY-9357 > URL: https://issues.jboss.org/browse/WFLY-9357 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Environment: WildFly 11 CR1 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > > It is expected that the user can be overridden witht he properties passed to InitialContext. > But the user logged at the server side is still the one from the wildfy-config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9357) [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9357?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9357: ------------------------------- Fix Version/s: 11.0.0.Final > [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9357 > URL: https://issues.jboss.org/browse/WFLY-9357 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Environment: WildFly 11 CR1 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > > It is expected that the user can be overridden witht he properties passed to InitialContext. > But the user logged at the server side is still the one from the wildfy-config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 September 2017