[JBoss JIRA] (WFLY-2319) LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2319?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2319:
-----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1061181|https://bugzilla.redhat.com/show_bug.cgi?id=1061181] from NEW to POST
> LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2319
> URL: https://issues.jboss.org/browse/WFLY-2319
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Naming
> Affects Versions: 8.0.0.Beta1
> Reporter: Darran Lofthouse
> Assignee: Eduardo Martins
> Fix For: 8.0.0.CR1
>
> Attachments: LdapSearching.tgz
>
>
> The following code: -
> {code}
> Hashtable env = new Hashtable();
> env.put("java.naming.factory.initial", "com.sun.jndi.ldap.LdapCtxFactory");
> env.put("java.naming.security.authentication", "simple");
> env.put("java.naming.provider.url", "ldap://localhost:10389");
> env.put(InitialDirContext.SECURITY_PRINCIPAL, "uid=admin,ou=system");
> env.put(InitialDirContext.SECURITY_CREDENTIALS, "secret");
> SearchControls ctl = null;
> String attrArr[] = new String[1];
> attrArr[0] = "sn";
> ctl = new SearchControls(2, 0L, 0, attrArr, false, false);
> String base = "ldap://localhost:10389/dc=simple,dc=wildfly,dc=org";
> String filter = "(uid=UserOne)";
> NamingEnumeration nenum = null;
> DirContext ictx = null;
> ictx = new InitialDirContext(env);
> nenum = ictx.search(base, filter, ctl);
> {code}
> Results in the following exception: -
> {noquote}
> 13:03:45,598 ERROR [stderr] (default task-1) javax.naming.InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given : ldap: (0x6C 0x64 0x61 0x70 0x3A ) is invalid]; remaining name 'ldap://localhost:10389/dc=simple,dc=wildfly,dc=org'
> 13:03:45,599 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3025)
> 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840)
> 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1034)
> {noquote}
> Switching to a base that does not begin with a URL and the search works, executing this code outside of WildFly also works.
> The underlying issue is that the default InitialContext implementation contains the following method: -
> {code}
> protected Context getURLOrDefaultInitCtx(String name)
> throws NamingException {
> if (NamingManager.hasInitialContextFactoryBuilder()) {
> return getDefaultInitCtx();
> }
> String scheme = getURLScheme(name);
> if (scheme != null) {
> Context ctx = NamingManager.getURLContext(scheme, myProps);
> if (ctx != null) {
> return ctx;
> }
> }
> return getDefaultInitCtx();
> }
> {code}
> As the naming subsystem has registered a InitialContextFactoryBuilder this code will never fall down to the scheme specific section.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2047) testConnection should account for deployment classloader
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2047?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2047:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1060997|https://bugzilla.redhat.com/show_bug.cgi?id=1060997] from POST to MODIFIED
> testConnection should account for deployment classloader
> --------------------------------------------------------
>
> Key: WFLY-2047
> URL: https://issues.jboss.org/browse/WFLY-2047
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Alpha4
> Environment: All
> Reporter: Jay Kumar SenSharma
> Assignee: Stefano Maestri
> Fix For: 9.0.0.CR1
>
>
> If a DataSource is created as following:
> ++++++++++++++++
> <datasource jndi-name="java:jboss/datasources/test_pool" pool-name="test_pool" enabled="true" use-java-context="true">
> <connection-url>jdbc:oracle:thin:@ldap://example.com:3060/test,cn=OracleA,dc=worldA</connection-url>
> <driver>oracle</driver>
> <pool>
> <min-pool-size>1</min-pool-size>
> <max-pool-size>15</max-pool-size>
> </pool>
> <security>
> <user-name>Test</user-name>
> <password>testPassword</password>
> </security>
> </datasource>
> <drivers>
> <driver name="oracle" module="com.oracle.jdbc6">
> <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
> </driver>
> <driver name="h2" module="com.h2database.h2">
> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
> </driver>
> </drivers>
> ++++++++++++++++
> Then while testing the DataSource the Wildfly throws the following Exception:
> +++++++++++++++++++++
> 16:47:10,498 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:282) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:240) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:781) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:344) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:627) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_21]
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.sql.SQLRecoverableException: Io exception: JNDI Package failurejavax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.as.connector:main" from local module loader @571a75a2 (finder: local module finder @a210b5b (roots: /home/jsensharma/NotBackedUp/SVN_16_Jan/EAP6_Main/build_wildfly/jboss-as-7.3.0.Final-redhat-X-SNAPSHOT/modules,/home/jsensharma/NotBackedUp/SVN_16_Jan/EAP6_Main/build_wildfly/jboss-as-7.3.0.Final-redhat-X-SNAPSHOT/modules/system/layers/base))
> at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
> at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:458)
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)
> at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:490)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202)
> at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:474)
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:254) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final]
> ++++++++++++++++++++++
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2872) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
Steve Storey created WFLY-2872:
----------------------------------
Summary: Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
Key: WFLY-2872
URL: https://issues.jboss.org/browse/WFLY-2872
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Server
Affects Versions: 8.0.0.Final
Environment: Fedora 20, i686, Java 8b128
Reporter: Steve Storey
Assignee: Jason Greene
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
2014-02-05 18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."two.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."two.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "two.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
... 5 more
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.vfs.VFS.mount(VFS.java:127)
at org.jboss.vfs.VFS.doMount(VFS.java:336)
at org.jboss.vfs.VFS.mountZip(VFS.java:360)
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
... 6 more
2014-02-05 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2871) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
[ https://issues.jboss.org/browse/WFLY-2871?page=com.atlassian.jira.plugin.... ]
Steve Storey closed WFLY-2871.
------------------------------
Resolution: Duplicate Issue
Raised WFLY-2872 instead
> Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
> -------------------------------------------------------------------
>
> Key: WFLY-2871
> URL: https://issues.jboss.org/browse/WFLY-2871
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.0.0.Final
> Environment: Fedora 20, i686, Java 8b128
> Reporter: Steve Storey
> Assignee: Jason Greene
>
> * Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
> * Start up in standalone mode
> * Have 2 WAR files, and copy each individually into .../standalone/deployments/
> * Observe that the 2nd one will always fail.
> Sample trace:
> {code}
> 2014-02-05 18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."two.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."two.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "two.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> ... 5 more
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.vfs.VFS.mount(VFS.java:127)
> at org.jboss.vfs.VFS.doMount(VFS.java:336)
> at org.jboss.vfs.VFS.mountZip(VFS.java:360)
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
> ... 6 more
> 2014-02-05 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
> {code}
> A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2871) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
[ https://issues.jboss.org/browse/WFLY-2871?page=com.atlassian.jira.plugin.... ]
Steve Storey commented on WFLY-2871:
------------------------------------
Ugh - this isn't a bug. I'll close and re-raise
> Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
> -------------------------------------------------------------------
>
> Key: WFLY-2871
> URL: https://issues.jboss.org/browse/WFLY-2871
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.0.0.Final
> Environment: Fedora 20, i686, Java 8b128
> Reporter: Steve Storey
> Assignee: Jason Greene
>
> * Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
> * Start up in standalone mode
> * Have 2 WAR files, and copy each individually into .../standalone/deployments/
> * Observe that the 2nd one will always fail.
> Sample trace:
> {code}
> 2014-02-05 18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."two.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."two.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "two.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> ... 5 more
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.vfs.VFS.mount(VFS.java:127)
> at org.jboss.vfs.VFS.doMount(VFS.java:336)
> at org.jboss.vfs.VFS.mountZip(VFS.java:360)
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
> ... 6 more
> 2014-02-05 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
> {code}
> A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2871) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
[ https://issues.jboss.org/browse/WFLY-2871?page=com.atlassian.jira.plugin.... ]
Steve Storey updated WFLY-2871:
-------------------------------
Description:
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
2014-02-05 18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."two.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."two.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "two.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
... 5 more
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.vfs.VFS.mount(VFS.java:127)
at org.jboss.vfs.VFS.doMount(VFS.java:336)
at org.jboss.vfs.VFS.mountZip(VFS.java:360)
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
... 6 more
2014-02-05 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
was:
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
> Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
> -------------------------------------------------------------------
>
> Key: WFLY-2871
> URL: https://issues.jboss.org/browse/WFLY-2871
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.0.0.Final
> Environment: Fedora 20, i686, Java 8b128
> Reporter: Steve Storey
> Assignee: Jason Greene
>
> * Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
> * Start up in standalone mode
> * Have 2 WAR files, and copy each individually into .../standalone/deployments/
> * Observe that the 2nd one will always fail.
> Sample trace:
> {code}
> 2014-02-05 18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."two.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."two.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "two.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
> ... 5 more
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
> at org.jboss.vfs.VFS.mount(VFS.java:127)
> at org.jboss.vfs.VFS.doMount(VFS.java:336)
> at org.jboss.vfs.VFS.mountZip(VFS.java:360)
> at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
> ... 6 more
> 2014-02-05 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
> {code}
> A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2871) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
[ https://issues.jboss.org/browse/WFLY-2871?page=com.atlassian.jira.plugin.... ]
Steve Storey updated WFLY-2871:
-------------------------------
Description:
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
was:
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."paris-admin-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."paris-admin-1.0.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "paris-admin-1.0.war"
SNAPSHOT]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
SNAPSHOT]
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
> Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
> -------------------------------------------------------------------
>
> Key: WFLY-2871
> URL: https://issues.jboss.org/browse/WFLY-2871
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.0.0.Final
> Environment: Fedora 20, i686, Java 8b128
> Reporter: Steve Storey
> Assignee: Jason Greene
>
> * Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
> * Start up in standalone mode
> * Have 2 WAR files, and copy each individually into .../standalone/deployments/
> * Observe that the 2nd one will always fail.
> Sample trace:
> {code}
> 18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
> Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
> {code}
> A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2871) Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
by Steve Storey (JIRA)
Steve Storey created WFLY-2871:
----------------------------------
Summary: Deploying a 2nd WAR file gives VFS000017 for resteasy-spring module
Key: WFLY-2871
URL: https://issues.jboss.org/browse/WFLY-2871
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Server
Affects Versions: 8.0.0.Final
Environment: Fedora 20, i686, Java 8b128
Reporter: Steve Storey
Assignee: Jason Greene
* Download the nightly from https://ci.jboss.org/hudson/job/WildFly-latest-master/934/
* Start up in standalone mode
* Have 2 WAR files, and copy each individually into .../standalone/deployments/
* Observe that the 2nd one will always fail.
Sample trace:
{code}
18:02:17,346 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."paris-admin-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."paris-admin-1.0.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "paris-admin-1.0.war"
SNAPSHOT]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
SNAPSHOT]
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
18:02:17,349 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "two.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"two.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"two.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"two.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\"
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point \"\"/opt/jboss/wildfly-8.0.0.Final-SNAPSHOT/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar\"\""}}
{code}
A stackoverflow poster appears to have the same problem: http://stackoverflow.com/questions/21565734/resteasy-spring-module-in-jbo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (WFLY-2870) Distinct HTTP and HTTPS listen addresses for management HTTP interface are not configurable
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-2870?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-2870:
----------------------------------------
This will make redirecting between the two difficult, also when both are defined the http interface is virtually redundant other than to respond with a redirect to push the traffic over https.
> Distinct HTTP and HTTPS listen addresses for management HTTP interface are not configurable
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-2870
> URL: https://issues.jboss.org/browse/WFLY-2870
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 9.0.0.CR1
>
>
> Add a single attribute to the existing http management interface resource, named "secure-interface". The current attributes are "interface", "http-port", "https-port", with the "interface" value being used for both ports. The new "secure-interface" attribute would specify the interface to use for the "https-port" socket. It, unlike "interface", will accept a null value, in which case the value for "interface" will be used for the "https-port" socket. This would be the standard config and preserves backward compatibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months