January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2166) Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea

by Ondrej Zizka (Created) (JIRA)

Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea ---------------------------------------------------------------------------- Key: AS7-2166 URL: https://issues.jboss.org/browse/AS7-2166 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka James Perkins: {quote} At one point there was a JIRA for OpenJDK 6, in fact I think a couple. The issue with OpenJDK 6 is in the build we use some JavaScript and OpenJDK 6 doesn't come with a JavaScript engine. I tried a couple things to get Rhino working with it as that's what the Sun JDK uses, but I think it needs to implement an SPI to get it to work. I didn't look into it much beyond that. JDK 7 is a different issue. It's a bug in the annotation processing API which the JBoss Logging Tooling uses. I just refreshed my OpenJDK 7 update source and it looks like the bug is fixed in there. It's fixed in IcedTea as well. There could be the JavaScript issue here as well I can't actually remember, but I thought I had some successful builds with custom JDK's I compiled. I did just try with IcedTea 7 and got some other errors. I'm building the latest upstream of OpenJDK 7 now and we'll see if it works. I'll let you know either way. Let me know if you have any more questions on this. I did dig into a while ago a little. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
8
0 / 0

[JBoss JIRA] Created: (JBAS-9121) CLONE - Cannot build JBoss AS 7 using OpenJDK

by Shelly McGowan (JIRA)

CLONE - Cannot build JBoss AS 7 using OpenJDK --------------------------------------------- Key: JBAS-9121 URL: https://issues.jboss.org/browse/JBAS-9121 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 7.0.0.Beta1 Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 7.0.0.Beta2 Compilation fails with: ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project jboss-as-arquillian-common: Compilation failure [ERROR] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-7.0.x-testSuite-openjdk/arquillian/common/src/main/java/org/jboss/as/arquillian/container/JBossASDeploymentPackager.java:[59,16] inconvertible types [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#470 of ?> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive I've confirmed this is the latest version of OpenJDK: java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
10
0 / 0

[JBoss JIRA] (AS7-2999) Integrate Remoting / SASL based authentication with EJB3

by Darran Lofthouse (Created) (JIRA)

Integrate Remoting / SASL based authentication with EJB3 -------------------------------------------------------- Key: AS7-2999 URL: https://issues.jboss.org/browse/AS7-2999 Project: Application Server 7 Issue Type: Bug Components: EJB, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker We need two approaches: - 1 - Support for the PLAIN SASL mechanism to pass the username and password straight to JAAS. 2 - Full SASL support with the JAAS security domain trusting the SASL Principal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
12
0 / 0

[JBoss JIRA] Created: (AS7-1625) Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies

by Ondrej Zizka (JIRA)

Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies ----------------------------------------------------------------------- Key: AS7-1625 URL: https://issues.jboss.org/browse/AS7-1625 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.1.Final Environment: standalone Reporter: Ondrej Zizka Assignee: Remy Maucherat I have a cookie in browser which was set for redhat.com, so my AS 7 on ozizka.brq.redhat.com is receiving it to. Now that "version 0" cookie contains characters illegal acc. to RFC-2109 and RFC-2068: {code} Cookie: s_vi=[CS]v1|261............[CE]; ... {code} AS 7 logs: {code} 22:18:13,365 INFO [org.apache.tomcat.util.http.Cookies] (http--0.0.0.0-8080-2) Cookies: Invalid cookie. Value not a token or quoted value {code} I haven't checked whether only the single value is discarded or all cookies. Possibly related: JBPAPP-5813 Some related links: Discussion http://old.nabble.com/DO-NOT-REPLY--Bug-49525--New%3A-IE8%3A-Unabled-to-s... and bug https://issues.apache.org/bugzilla/show_bug.cgi?id=49525 about Tomcat 7's bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (AS7-1735) Console: failure when creating new JMS should provide more information

by Radoslav Husar (JIRA)

Console: failure when creating new JMS should provide more information ---------------------------------------------------------------------- Key: AS7-1735 URL: https://issues.jboss.org/browse/AS7-1735 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.0.1.Final Reporter: Radoslav Husar Assignee: Heiko Braun Say I try to create a queue, but input incorrect values, the console provides the following which is not enough to know what was the root cause: {code} Tue Sep 06 12:52:33 GMT+200 2011 Failed to create queue Unexpected HTTP response: 500 Request { "operation" => "add", "address" => [ ("profile" => "default"), ("subsystem" => "messaging"), ("jms-queue" => "asdas") ], "entries" => ["dasdasd"], "durable" => false, "selector" => "*" } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => [("main-server-group" => {"master" => { "host" => "master", "response" => { "outcome" => "failed", "failure-description" => {"Failed services" => {"jboss.messaging.jms.queue.asdas" => "org.jboss.msc.service.StartException in service jboss.messaging.jms.queue.asdas: failed to create queue"}}, "rolled-back" => true } }})]}, "failure-description" => "Operation failed or was rolled back on all servers.", "rolled-back" => true } {code} while the server says: {code} [Server:server-one] 12:52:33,840 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.messaging.jms.queue.asdas: org.jboss.msc.service.StartException in service jboss.messaging.jms.queue.asdas: failed to create queue [Server:server-one] at org.jboss.as.messaging.jms.JMSQueueService.start(JMSQueueService.java:60) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] [Server:server-one] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] [Server:server-one] Caused by: HornetQException[errorCode=103 message=Invalid filter: * Encountered "*" at line 1, column 1. [Server:server-one] Was expecting one of: [Server:server-one] "TRUE" ... [Server:server-one] "FALSE" ... [Server:server-one] "NOT" ... [Server:server-one] "(" ... [Server:server-one] "-" ... [Server:server-one] "+" ... [Server:server-one] <INTEGER_LITERAL> ... [Server:server-one] <FLOATING_POINT_LITERAL> ... [Server:server-one] <SIMPLE_STRING> ... [Server:server-one] <IDENTIFIER> ... [Server:server-one] ] [Server:server-one] at org.hornetq.core.filter.impl.FilterImpl.<init>(FilterImpl.java:117) [Server:server-one] at org.hornetq.core.filter.impl.FilterImpl.createFilter(FilterImpl.java:97) [Server:server-one] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1694) [Server:server-one] at org.hornetq.core.server.impl.HornetQServerImpl.deployQueue(HornetQServerImpl.java:1060) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateQueue(JMSServerManagerImpl.java:1046) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.access$100(JMSServerManagerImpl.java:98) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl$1.runException(JMSServerManagerImpl.java:422) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1643) [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.createQueue(JMSServerManagerImpl.java:413) [Server:server-one] at org.jboss.as.messaging.jms.JMSQueueService.start(JMSQueueService.java:58) [Server:server-one] ... 5 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
12
0 / 0

[JBoss JIRA] (AS7-3195) Expansion of variables in persistence.xml

by Hasan Ceylan (Created) (JIRA)

Expansion of variables in persistence.xml ----------------------------------------- Key: AS7-3195 URL: https://issues.jboss.org/browse/AS7-3195 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final Reporter: Hasan Ceylan Hello, I am not sure if this is a bug or a feature request. IIR, expansion of variables in the form of ${foo.bar} was supported in persistence.xml (and may be other). In Jboss 7.X, I see this is not supported. Regards, Hasan Ceylan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

8
20
0 / 0

[JBoss JIRA] (AS7-2931) System property replacement doesn't work within the web.xml

by Mo Zo (Created) (JIRA)

System property replacement doesn't work within the web.xml ----------------------------------------------------------- Key: AS7-2931 URL: https://issues.jboss.org/browse/AS7-2931 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.Beta1, 7.0.2.Final Reporter: Mo Zo System property expressions won't be resolved within the web.xml Expressions like: ${my.system.property} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (JASSIST-127) interface proxy creation fails if there are methods with covariant return types

by Paul Pogonyshev (JIRA)

interface proxy creation fails if there are methods with covariant return types ------------------------------------------------------------------------------- Key: JASSIST-127 URL: https://jira.jboss.org/browse/JASSIST-127 Project: Javassist Issue Type: Bug Affects Versions: 3.12.0.GA Environment: Java 1.6. Reporter: Paul Pogonyshev Assignee: Shigeru Chiba Creation of proxy class for interface Bar fails: public interface Foo { Foo getSelf (); } public interface Bar extends Foo { Bar getSelf (); } This is because of covariant return types of method getSelf(). However, as this is permitted by the language (i.e. subtype can restrict the return type further), I consider this a bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBLOGGING-61) Support for log4j Logger.getLogger(String, LogFactory)

by Elias Ross (JIRA)

Support for log4j Logger.getLogger(String, LogFactory) ------------------------------------------------------ Key: JBLOGGING-61 URL: https://issues.jboss.org/browse/JBLOGGING-61 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Elias Ross Assignee: David Lloyd Attachments: 0001-Create-custom-appender-use-it-to-output-messages-if-.patch org.apache.log4j.Logger(String, LogFactory) does not function. This patch adds support using a custom Log4j appender that sends messages to JBoss's appender. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
13
0 / 0

[JBoss JIRA] (LOGTOOL-38) @MessageBundle with String return types and %n in the format return the %n.

by James Perkins (Created) (JIRA)

@MessageBundle with String return types and %n in the format return the %n. --------------------------------------------------------------------------- Key: LOGTOOL-38 URL: https://issues.jboss.org/browse/LOGTOOL-38 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.CR4 Need to either test for formats or just run everything through String.format(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
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 January 2012