[JBoss JIRA] (WFLY-769) Align domain.sh and standalone.sh logic about adding -server
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-769?page=com.atlassian.jira.plugin.s... ]
Jason Greene moved AS7-5293 to WFLY-769:
----------------------------------------
Project: WildFly (was: Application Server 7)
Key: WFLY-769 (was: AS7-5293)
Component/s: Scripts
(was: Scripts)
Fix Version/s: Awaiting Volunteers
(was: Awaiting Volunteers)
> Align domain.sh and standalone.sh logic about adding -server
> ------------------------------------------------------------
>
> Key: WFLY-769
> URL: https://issues.jboss.org/browse/WFLY-769
> Project: WildFly
> Issue Type: Task
> Components: Scripts
> Reporter: Brian Stansberry
> Fix For: Awaiting Volunteers
>
>
> The domain.sh script has a number of JVM vendor checks it uses to decide whether to add -server to the jvm launch command. In standalone.sh it's simpler; it simply checks for OSX.
> I can't see any reason this logic should be significantly different between the two cases, either the JVM vendor checks are needed in both or they aren't needed in either.
--
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, 8 months
[JBoss JIRA] (AS7-5293) Align domain.sh and standalone.sh logic about adding -server
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-5293?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated AS7-5293:
------------------------------
Parent: (was: AS7-5283)
Issue Type: Task (was: Sub-task)
> Align domain.sh and standalone.sh logic about adding -server
> ------------------------------------------------------------
>
> Key: AS7-5293
> URL: https://issues.jboss.org/browse/AS7-5293
> Project: Application Server 7
> Issue Type: Task
> Components: Scripts
> Reporter: Brian Stansberry
> Fix For: Awaiting Volunteers
>
>
> The domain.sh script has a number of JVM vendor checks it uses to decide whether to add -server to the jvm launch command. In standalone.sh it's simpler; it simply checks for OSX.
> I can't see any reason this logic should be significantly different between the two cases, either the JVM vendor checks are needed in both or they aren't needed in either.
--
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, 8 months
[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 moved AS7-6491 to WFLY-768:
----------------------------------------
Project: WildFly (was: Application Server 7)
Key: WFLY-768 (was: AS7-6491)
Issue Type: Bug (was: Release)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: 7.1.1.Final)
Component/s: Server
(was: Server)
Fix Version/s: 8.0.0.Alpha2
(was: No Release)
> 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.Alpha2
>
>
> 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, 8 months
[JBoss JIRA] (AS7-6370) Failures in TransactionSubsystemTestCase on Jenkins
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-6370?page=com.atlassian.jira.plugin.s... ]
Jason Greene closed AS7-6370.
-----------------------------
Fix Version/s: No Release
Resolution: Out of Date
> Failures in TransactionSubsystemTestCase on Jenkins
> ---------------------------------------------------
>
> Key: AS7-6370
> URL: https://issues.jboss.org/browse/AS7-6370
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Transactions
> Reporter: Brian Stansberry
> Fix For: No Release, 7.1.4.Final (EAP)
>
>
> E.g. in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBoss-AS-7.1.x-testSu...
> Running org.jboss.as.txn.TransactionSubsystemTestCase
> Resolving artifact org.jboss.as:jboss-as-transactions:jar:7.1.2.Final
> Resolved artifact org.jboss.as:jboss-as-transactions:jar:7.1.2.Final from jboss-developer (http://repository.jboss.org/nexus/content/groups/developer/, releases+snapshots)
> /home/hudson/.m2/repository/org/jboss/as/jboss-as-transactions/7.1.2.Final/jboss-as-transactions-7.1.2.Final.jar
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.74 sec <<< FAILURE!
> Results :
> Tests in error:
> testTransformers(org.jboss.as.txn.TransactionSubsystemTestCase): java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT
> testSubsystem(org.jboss.as.txn.TransactionSubsystemTestCase): java.lang.NoClassDefFoundError: Could not initialize class org.jboss.as.txn.subsystem.TxStatsHandler
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
--
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, 8 months
[JBoss JIRA] (AS7-4126) double values cannot be read from dmr response
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-4126?page=com.atlassian.jira.plugin.s... ]
Jason Greene closed AS7-4126.
-----------------------------
Resolution: Done
Closing assuming it was fixed with a lack of response
> double values cannot be read from dmr response
> ----------------------------------------------
>
> Key: AS7-4126
> URL: https://issues.jboss.org/browse/AS7-4126
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.0.Final
> Reporter: Rob Cernich
> Assignee: Heiko Braun
> Fix For: 7.1.2.Final (EAP)
>
>
> This appears to be a bug in the GWT compiler. The compiler turns the following:
> {code:java|title=DataInput.readDouble()}
> return IEEE754.toDouble(bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++]);
> {code}
> into: (effectively; the GWT compiler is adding a set of parentheses around the parameters passed to the native function)
> {code:java|title=DataInput.readDouble() compiled}
> return IEEE754.toDouble(new byte[] {bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++]});
> {code}
> This results in all double values in the model being interpreted as NaN.
> I've patched the code I'm using in SwitchYard as follows:
> {code:java|title=DataInput.java}
> public double readDouble() throws IOException {
> byte doubleBytes[] = new byte[8];
> readFully(doubleBytes);
> return IEEE754.toDouble(doubleBytes);
> }
> {code}
> {code:java|title=IEEE754.java}
> public static native double toDouble(byte[] bytes) /*-{
> var ebits = 11;
> var fbits = 52;
> // Bytes to bits
> var bits = [];
> //snip...
> }
> {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, 8 months