[JBoss JIRA] (WFCORE-1261) Changing the max-history attribute value for configuration-changes fails
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-1261:
-----------------------------------------
Summary: Changing the max-history attribute value for configuration-changes fails
Key: WFCORE-1261
URL: https://issues.jboss.org/browse/WFCORE-1261
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.5.Final
Reporter: ehsavoie Hugonnet
Assignee: Brian Stansberry
[standalone@localhost:9990 /] /core-service=management/service=configuration-changes:write-attribute(name=max-history,value=20)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0188: Stage MODEL is already complete",
"rolled-back" => true
}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFCORE-1261) Changing the max-history attribute value for configuration-changes fails
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1261?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-1261:
-----------------------------------------
Assignee: ehsavoie Hugonnet (was: Brian Stansberry)
> Changing the max-history attribute value for configuration-changes fails
> ------------------------------------------------------------------------
>
> Key: WFCORE-1261
> URL: https://issues.jboss.org/browse/WFCORE-1261
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.5.Final
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
>
> [standalone@localhost:9990 /] /core-service=management/service=configuration-changes:write-attribute(name=max-history,value=20)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0188: Stage MODEL is already complete",
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFCORE-1260) Capability resolution complaints on admin-only slave HCs not connected to the master
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1260:
----------------------------------------
Summary: Capability resolution complaints on admin-only slave HCs not connected to the master
Key: WFCORE-1260
URL: https://issues.jboss.org/browse/WFCORE-1260
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.5.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
If you start a slave HC in admin-only with no master to connect to, boot is fine but then any modifications made to the config result in capabiloty resolution ERROR messages in the host-controller.log
Starting a slave HC in admin-only with no master to connect to is meant to work, allowing you to use CLI to manipulate the slave's host config:
{code}
bin/domain.sh --host-config=host-slave.xml --admin-only -Djboss.domain.master.address=127.0.0.1
{code}
The boot is fine:
{code}
[Host Controller] 11:06:10,639 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final-SNAPSHOT (WildFly Core 2.0.5.Final) (Host Controller) started in 1152ms - Started 41 of 42 services (12 services are lazy, passive or on-demand)
{code}
However, subsequent changes made via management tools (e.g. CLI) succeed result in ERROR logging by the HC:
{code}
[domain@127.0.0.1:9999 /] /host=localhost/system-property=foo:add(value=bar)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
The HC's log:
{code}
[Host Controller] 11:07:37,744 ERROR [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0369: Required capabilities are not available:
[Host Controller] org.wildfly.domain.server-group.other-server-group in context 'server-config'; There are no known registration points which can provide this capability.
[Host Controller] org.wildfly.domain.server-group.main-server-group in context 'server-config'; There are no known registration points which can provide this capability.
{code}
The boot works without logging because of the enhancement Stuart added such that capability references failures won't fail an admin-only boot, thus letting the user use admin-only to fix the changes. But then with subsequent changes, the user gets ERRORs notifying them of the unfixed references.
But in this case, the references will never be available, so long as there is no connection to a master to provide the domain-wide config.
This is a general case that needs to be accounted for in the capability resolution logic.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-5914) JNDI view ClassNotFoundException with remote entry
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-5914?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFLY-5914:
-----------------------------------
I could not reproduce your issue on the latest WildFly checkout using your domain.xml. On both servers, the :jodi-view operation succeeds and display the JMS topic as expected:
{noformat}
"java:jboss/exported" => {"jms" => {
"class-name" => "javax.naming.Context",
"children" => {
"RemoteConnectionFactory" => {
"class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
"value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=8230&host=localhost], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
},
"topic" => {
"class-name" => "javax.naming.Context",
"children" => {"prueba" => {
"class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQTopic",
"value" => "ActiveMQTopic[PruebaTopic]"
}}
},
"queue" => {
"class-name" => "javax.naming.Context",
"children" => {"prueba" => {
"class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQQueue",
"value" => "ActiveMQQueue[PruebaQueue]"
}}
}
}
}},
{noformat}
> JNDI view ClassNotFoundException with remote entry
> --------------------------------------------------
>
> Key: WFLY-5914
> URL: https://issues.jboss.org/browse/WFLY-5914
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Naming
> Affects Versions: 10.0.0.CR5
> Reporter: Guillermo González de Agüero
> Assignee: Jeff Mesnil
> Attachments: domain.xml
>
>
> When a binding to a remote Artemis Topic/ConnectionFactory is created, JNDI view fails with a ClassNotFoundException. Both servers are running the "full" profile.
> I attach my domain.xml for reference porpuses. No application needs to be deployed.
> Full operation result:
> [domain@localhost:9990 /] /host=master/server=app-ins01/subsystem=naming:jndi-view()
> {
> "outcome" => "failed",
> "result" => {"java: contexts" => {
> "java:" => {
> "ConnectionFactory" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
> "value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=in-vm, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
> },
> "JmsXA" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "TransactionManager" => {
> "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate",
> "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@27b3c7"
> },
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {"queue" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "DLQ" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQQueue",
> "value" => "ActiveMQQueue[DLQ]"
> },
> "ExpiryQueue" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQQueue",
> "value" => "ActiveMQQueue[ExpiryQueue]"
> }
> }
> }}
> },
> "jboss" => {
> "class-name" => "javax.naming.Context",
> "value" => "org.jboss.as.naming.WritableServiceBasedNamingStore@d2c52f"
> },
> "global" => {
> "class-name" => "javax.naming.Context",
> "value" => "org.jboss.as.naming.WritableServiceBasedNamingStore@932e80"
> },
> "ejb" => {
> "class-name" => "javax.naming.Context",
> "children" => {"mgmt" => {
> "class-name" => "javax.naming.Context",
> "children" => {"MEJB" => {
> "class-name" => "javax.management.j2ee.ManagementHome",
> "value" => "Proxy for remote EJB EJBHomeLocator for \"jsr-77/jsr-77/EJB\", view is interface javax.management.j2ee.ManagementHome, affinity is None"
> }}
> }}
> }
> },
> "java:jboss" => {
> "ORB" => {
> "class-name" => "com.sun.corba.se.impl.orb.ORBImpl",
> "value" => "com.sun.corba.se.impl.orb.ORBImpl@1306d15"
> },
> "TransactionManager" => {
> "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate",
> "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@27b3c7"
> },
> "TransactionSynchronizationRegistry" => {
> "class-name" => "org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper",
> "value" => "org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper@206b4c"
> },
> "UserTransaction" => {
> "class-name" => "javax.transaction.UserTransaction",
> "value" => "UserTransaction"
> },
> "corbanaming" => {
> "class-name" => "org.omg.CosNaming._NamingContextExtStub",
> "value" => "IOR:000000000000002b49444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e300000000000010000000000000110000102000000000a3132372e302e302e31000e3600000039afabcb00000000220000000100000001000000000000000200000008526f6f74504f4100000000074e616d696e67000000000004726f6f741400000000000005000000010000002000000000000100010000000205010001000100200001010900000001000101000000002600000002000200000000000300000014000000000000000a3132372e302e302e31000e3700000014000000080000001a00000e370000002100000050000000000000000100000000000000220000000000400000000000080606678102010101000000170401000806066781020101010000000744656661756c740000000000000000000000000000000000"
> },
> "irpoa" => {
> "class-name" => "com.sun.corba.se.impl.oa.poa.POAImpl",
> "value" => "POA[ObjectAdapterID[RootPOA/IRPOA], uniquePOAId=2, state=RUN, invocationCount=0]"
> },
> "jaas" => {
> "class-name" => "com.sun.proxy.$Proxy58",
> "value" => "java:jboss/jaas/ Context proxy"
> },
> "poa" => {
> "class-name" => "com.sun.corba.se.impl.oa.poa.POAImpl",
> "value" => "POA[ObjectAdapterID[RootPOA], uniquePOAId=0, state=RUN, invocationCount=0]"
> },
> "ee" => {
> "class-name" => "javax.naming.Context",
> "children" => {"concurrency" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "scheduler" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "factory" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "executor" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> },
> "context" => {
> "class-name" => "javax.naming.Context",
> "children" => {"default" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }}
> }
> }
> }}
> },
> "infinispan" => {
> "class-name" => "javax.naming.Context",
> "children" => {"container" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "ejb" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "ejb"
> },
> "hibernate" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "hibernate"
> },
> "server" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "server"
> },
> "web" => {
> "class-name" => "org.jboss.as.clustering.infinispan.DefaultCacheContainer",
> "value" => "web"
> }
> }
> }}
> },
> "datasources" => {
> "class-name" => "javax.naming.Context",
> "children" => {"ExampleDS" => {
> "class-name" => "org.jboss.as.connector.subsystems.datasources.WildFlyDataSource",
> "value" => "org.jboss.as.connector.subsystems.datasources.WildFlyDataSource@c79ae8"
> }}
> },
> "mail" => {
> "class-name" => "javax.naming.Context",
> "children" => {"Default" => {
> "class-name" => "javax.mail.Session",
> "value" => "javax.mail.Session@1e9f277"
> }}
> },
> "clustering" => {
> "class-name" => "javax.naming.Context",
> "children" => {"registry" => {
> "class-name" => "javax.naming.Context",
> "children" => {"ejb" => {
> "class-name" => "javax.naming.Context",
> "children" => {"client-mappings" => {
> "class-name" => "org.wildfly.clustering.server.registry.CacheRegistryFactory",
> "value" => "org.wildfly.clustering.server.registry.CacheRegistryFactory@12ac291"
> }}
> }}
> }}
> }
> },
> "java:jboss/exported" => {"jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {"RemoteConnectionFactory" => {
> "class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
> "value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=8190&host=127-0-0-1], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
> }}
> }},
> "java:global" => undefined
> }},
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.RuntimeException: org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory from [Module \"org.jboss.as.naming:main\" from local module loader @130015a (finder: local module finder @9f0666 (roots: c:\\wildfly-10.0.0.CR5\\modules,c:\\wildfly-10.0.0.CR5\\modules\\system\\layers\\base))]]",
> "rolled-back" => true
> }
> Injection of the resources via @Resource in an application works as expected. I found this same problem where manually doing the remote lookup from application code, which I resolved adding a dependency to Artemis module in META-INF.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFCORE-1259) Embedded HC started with host-slave.xml does not allow changes as master connection service is not available
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1259?page=com.atlassian.jira.plugi... ]
Ken Wills updated WFCORE-1259:
------------------------------
Issue Type: Bug (was: Enhancement)
> Embedded HC started with host-slave.xml does not allow changes as master connection service is not available
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1259
> URL: https://issues.jboss.org/browse/WFCORE-1259
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ken Wills
> Assignee: Ken Wills
>
> # update host-slave.xml - simplify the example
> -<host xmlns="urn:jboss:domain:4.0">
> +<host name="slave" xmlns="urn:jboss:domain:4.0">
> $ ./jboss-cli.sh -Djboss.domain.master.address=127.0.0.1
> [disconnected /] embed-host-controller --host-config=host-slave.xml --std-out=echo
> [domain@embedded /] /host=slave/server-config=server-one:write-attribute(name=socket-binding-port-offset, value=1)
> 2:22:06,003 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 2) WFLYCTL0013: Operation
> +("write-attribute") failed - address: ([
> ("host" => "slave"),
> ("server-config" => "server-one")
> ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.domain.controller.connection not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationCo
> +ntextImpl.java:2208)
> at org.jboss.as.domain.controller.operations.SyncModelOperationHandlerWrapper.execute(SyncModelOperationHandle
> +rWrapper.java:131)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1341)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerCli
> +ent.java:63)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.j
> +ava:59)
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:84)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:753)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:799)
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:412)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> 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)
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"slave" => "WFLYCTL0158: Operation handler failed: org.j
> +boss.msc.service.ServiceNotFoundException: Service service jboss.domain.controller.connection not found"}},
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFCORE-951) LDAP context resource leaks in Picketbox
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-951?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFCORE-951.
-------------------------------------
Release Notes Text: I'm going to resolve this against 2.0.5 although it may have been an early 2.0.x release. The related JBEAP issue is verified and the code for this is in sync between the branches so for the JBEAP to be fixed this one must be as well.
Fix Version/s: 2.0.5.Final
Resolution: Done
> LDAP context resource leaks in Picketbox
> ----------------------------------------
>
> Key: WFCORE-951
> URL: https://issues.jboss.org/browse/WFCORE-951
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 2.0.0.Beta5
> Reporter: Josef Cacek
> Assignee: Peter Skopek
> Priority: Blocker
> Fix For: 2.0.5.Final
>
>
> There are several {{InitialLdapContext}} resource leaks in LDAP related code in PicketBox.
> The most critical is IMO leak in `LdapLoginModule.createLdapInitContext()` method. LDAP connections will stay open for customers who use administrators bind (i.e. {{java.naming.security.principal}} login module option for the Ldap login module).
> The problematic code seems like:
> {code:java}
> InitialLdapContext ctx = null;
> try
> {
> //...
> ctx = new InitialLdapContext(env, null);
> if (PicketBoxLogger.LOGGER.isTraceEnabled())
> {
> PicketBoxLogger.LOGGER.traceSuccessfulLogInToLDAP(ctx.toString());
> }
> if (bindDN != null)
> {
> // Rebind the ctx to the bind dn/credentials for the roles searches
> PicketBoxLogger.LOGGER.traceRebindWithConfiguredPrincipal(bindDN);
> env.setProperty(Context.SECURITY_PRINCIPAL, bindDN);
> env.put(Context.SECURITY_CREDENTIALS, bindCredential);
> ctx = new InitialLdapContext(env, null);
> }
> // ...
> }
> finally
> {
> // Close the context to release the connection
> if (ctx != null)
> ctx.close();
> // ...
> }
> {code}
> The first constructed {{InitialLdapContext}} is not closed before creating the "admin context".
> The other PicketBox classes which have weak handling of the {{InitialLdapContext}} are:
> * {{LdapContextHandler}}
> * {{LdapAttributeMappingProvider}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-5918) ServletContext.getResourceAsStream fails in latest CR5 version
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5918?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-5918:
------------------------------
Description:
Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
problem only occurs when server is started from path that is not case equal to real path on file system.
was:
Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
> ServletContext.getResourceAsStream fails in latest CR5 version
> --------------------------------------------------------------
>
> Key: WFLY-5918
> URL: https://issues.jboss.org/browse/WFLY-5918
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Environment: Wildfly 10.0.0 CR5
> Windows 7
> JDK 1.8_66 64Bit
> Reporter: Alban Chadenas
> Assignee: Stuart Douglas
>
> Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
> Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
> problem only occurs when server is started from path that is not case equal to real path on file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-5918) ServletContext.getResourceAsStream fails on windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5918?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-5918:
------------------------------
Summary: ServletContext.getResourceAsStream fails on windows (was: ServletContext.getResourceAsStream fails in latest CR5 version)
> ServletContext.getResourceAsStream fails on windows
> ---------------------------------------------------
>
> Key: WFLY-5918
> URL: https://issues.jboss.org/browse/WFLY-5918
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Environment: Wildfly 10.0.0 CR5
> Windows 7
> JDK 1.8_66 64Bit
> Reporter: Alban Chadenas
> Assignee: Stuart Douglas
>
> Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
> Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
> problem only occurs when server is started from path that is not case equal to real path on file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-5918) ServletContext.getResourceAsStream fails on windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5918?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-5918:
------------------------------
Description:
Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
*problem only occurs when server is started from path that is not case equal to real path on file system.*
was:
Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
problem only occurs when server is started from path that is not case equal to real path on file system.
> ServletContext.getResourceAsStream fails on windows
> ---------------------------------------------------
>
> Key: WFLY-5918
> URL: https://issues.jboss.org/browse/WFLY-5918
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Environment: Wildfly 10.0.0 CR5
> Windows 7
> JDK 1.8_66 64Bit
> Reporter: Alban Chadenas
> Assignee: Stuart Douglas
>
> Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
> Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
> *problem only occurs when server is started from path that is not case equal to real path on file system.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months