October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-669) Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-669?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-669: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-669 > URL: https://issues.jboss.org/browse/WFLY-669 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > The ServerDeploymentManager and DomainDeploymentManager interfaces allow users to pass in a File. Currently we immediate convert that File to a FileInputStream and use that IS in the resulting operation. That will force an in-memory copy. Instead, use the OperationBuilder.addFileAsAttachment method introduced in the parent task. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-543) Provide an operation to request service status report after server has been started

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-543?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-543: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Provide an operation to request service status report after server has been started > ------------------------------------------------------------------------------------- > > Key: WFLY-543 > URL: https://issues.jboss.org/browse/WFLY-543 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Labels: console_prio > Fix For: 8.0.0.CR1 > > > For proper healthcare it would beneficial if I could verify the server status after it has been started. I.e. to catch these, which currently only appear in the server log: > [Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report > [Server:server-three] New missing/unsatisfied dependencies: > [Server:server-three] service jboss.binding.http2 (missing) > [Server:server-three] > [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1309) CLI: creating a server on a domain slave followed by setting a system property fails when done in batch mode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1309?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1309: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > CLI: creating a server on a domain slave followed by setting a system property fails when done in batch mode > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-1309 > URL: https://issues.jboss.org/browse/WFLY-1309 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Alpha1 > Environment: wildfly build from a git clone on 2013-05-02 > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > Attachments: host-domain-controller.xml, host-slave.xml > > > Setup two boxes: > - on one, run domain mode (full-ha) -> domain controller > - on the other, configure host.xml to point to the DC, and run the host controller > Now in CLI: > # add the group: > /server-group=slaves:add(profile=full-ha,socket-binding-group=full-ha-sockets) > # create server and set a prop > batch > /host=slave1/server-config=i1:add(group=slaves,auto-start=false) > /host=slave1/server-config=i1/system-property=env:add(value=dev) > run-batch > results in: > JBAS010839: Operation failed or was rolled back on all servers. > Debugging (on EAP 6.0.1) showed the real reason: > activeStep.response = (org.jboss.dmr.ModelNode) { > "outcome" => "failed", > "failure-description" => "JBAS010850: No handler for operation > composite at address [ > (\"host\" => \"slave1\"), > (\"server\" => \"i1\") > ]", > "rolled-back" => true > } > More debugging led to : > org.jboss.as.controller.AbstractOperationContext > seems to be where the rollback is set. When debugging, I found that the constructor always sets > ModelController.OperationTransactionControl transactionControl > but at line 332 (eap 6.0.1) / line 372 (wildfly), the end of doCompleteStep() : > // Allow any containing TransactionControl to vote > final AtomicReference<ResultAction> ref = new AtomicReference<ResultAction>(transactionControl == null ? ResultAction.KEEP : ResultAction.ROLLBACK); > and ref becomes a rollback. > I "walked" pretty much of all the code going on in between. The bit where the config is getting persisted is successful. > But I'm afraid I'm out of my depth as there is *a lot* going on to execute such a composite command :) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1014) Enable CORS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1014?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1014: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Enable CORS > ----------- > > Key: WFLY-1014 > URL: https://issues.jboss.org/browse/WFLY-1014 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 8.0.0.CR1 > > > We've been prototyping an alternative distribution channel for the console and have setup a demo that leverages the mozilla app store to deliver the AS7 web console to users: > https://marketplace.firefox.com/app/kea/?src=mkt-search > For this to work the AS needs to fully support CORS [1]. The general idea is that you can retrieve the console through a marketplace like the mozilla one (chrome would be another alternative) and connect to any domain controller, wether it runs locally or remotely. > If want to give it shot, point four firefox browser to the marketplace URL, launch the app and connect to our CORS demo instance that runs on EC2: > http://as7-preview.dyndns.org:9990 > user: admin > pass: webstore123! > [1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-943: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ----------------------------------------------------------------------------------- > > Key: WFLY-943 > URL: https://issues.jboss.org/browse/WFLY-943 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 8.0.0.Alpha3 > Reporter: Elias Ross > Fix For: 8.0.0.CR1 > > Attachments: jboss-deployment-structure.xml > > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-768) Caused by: javax.sound.sampled.UnsupportedAudioFileException: could not get audio input stream from input stream

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-768?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-768: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Caused by: javax.sound.sampled.UnsupportedAudioFileException: could not get audio input stream from input stream > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-768 > URL: https://issues.jboss.org/browse/WFLY-768 > Project: WildFly > Issue Type: Bug > Components: Server > Environment: windows 7 jdk1.6,eclipse juno, > Reporter: raky k > Assignee: Jason Greene > Labels: UnsupportedAudioFileException > Fix For: 8.0.0.CR1 > > > The application is working fine in the tomcat when deployed in the Jboss server it does not recognizes wav format and throws error Caused by: javax.sound.sampled.UnsupportedAudioFileException: could not get audio input stream from input stream > The application is open source and can be found > http://sourceforge.net/projects/simplecaptcha/files/simplecaptcha-1.2-j2e... > i have done below changes but still no luck. ( as advised on https://community.jboss.org/thread/197517 ) > " > Darran is right, it requires to edit the modules/sun/jdk/main/modules.xml and add an entry for com.sun.media. > > Moreover, copy the following files to modules/sun/jdk/main/service-loader-resources/META-INF/services/ > javax.sound.sampled.spi.AudioFileReader > javax.sound.sampled.spi.AudioFileWriter > javax.sound.sampled.spi.FormatConversionProvider > javax.sound.sampled.spi.MixerProvider > These files can be found inside /jre/lib/resources.jar of JDK, under /META-INF/services/ " -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1428) Extra resource root added to WARs

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1428?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1428: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Extra resource root added to WARs > --------------------------------- > > Key: WFLY-1428 > URL: https://issues.jboss.org/browse/WFLY-1428 > Project: WildFly > Issue Type: Bug > Components: Web (JBoss Web), Web (Undertow) > Reporter: David Lloyd > Assignee: Remy Maucherat > Fix For: 8.0.0.CR1 > > > When the class path for WAR deployments is being assembled, it appears that the WAR's root is being added as a resource root. This seems to be counter to spec; by default this should not be done. Now that we have the ability to iterate class loader resources, this causes unusual things to be listed. > Some users may desire this non-standard behavior though. So, we should have a way (preferably simpler than {{jboss-deployment-structure.xml}}) to enable it; however in this case, the following paths *must* be excluded: > * {{WEB-INF/lib}} > * {{WEB-INF/classes}} > * Any additional configured library or class directories > * Any other nested, mounted JAR files -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1388) Cannot load module alias defined for root deployment

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1388?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1388: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Cannot load module alias defined for root deployment > ---------------------------------------------------- > > Key: WFLY-1388 > URL: https://issues.jboss.org/browse/WFLY-1388 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.CR1 > > > A module defined like this cannot get loaded by its module-alias > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <resources> > <resource-root path="wrapped-resource.jar" use-physical-code-source="true"/> > </resources> > <dependencies> > <module name="javax.api"/> > <module name="javax.jms.api"/> > <module name="org.apache.camel.core"/> > <module name="org.springframework.beans"/> > <module name="org.springframework.context"/> > <module name="org.springframework.core"/> > <module name="org.springframework.jms"/> > <module name="org.springframework.transaction"/> > <module name="org.slf4j"/> > </dependencies> > <module-alias name="org.apache.camel.component.jms"/> > </deployment> > </jboss-deployment-structure> > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1315) Evaluate making operation "composite" EntryType.PUBLIC

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1315?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1315: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Evaluate making operation "composite" EntryType.PUBLIC > ------------------------------------------------------ > > Key: WFLY-1315 > URL: https://issues.jboss.org/browse/WFLY-1315 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > When the composite operation handler is registered, it's marked as EntryType.PRIVATE. This operation really isn't private; any reasonable management client will need to invoke it. > Changing it may have some implications though; we need to evaluate those. The biggest is the operation metadata cannot be complete, because the step parameter elements cannot be fully described. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1312) Restore EJB3 tests that deploy duplicate test deployment

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1312?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1312: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Restore EJB3 tests that deploy duplicate test deployment > -------------------------------------------------------- > > Key: WFLY-1312 > URL: https://issues.jboss.org/browse/WFLY-1312 > Project: WildFly > Issue Type: Task > Components: EJB > Reporter: Thomas Diesler > Assignee: jaikiran pai > Fix For: 8.0.0.CR1 > > > There are a number of EJB3 tests that [have been disabled|https://github.com/wildfly/wildfly/commit/a22ea284c7a7761e4626e1...] because they deploy a duplicate test deployment -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013