September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8407) JBoss AS 6 failes to start with IPv6

by Shelly McGowan (JIRA)

JBoss AS 6 failes to start with IPv6 ------------------------------------ Key: JBAS-8407 URL: https://jira.jboss.org/browse/JBAS-8407 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Reporter: Shelly McGowan Assignee: Scott Marlow Fix For: 6.0.0.CR1 due to MalformedURLException. I'll attach the full server.log for reference. Also note that the AS server start scripts, 14:15:33,367 INFO [SnmpAgentService] SNMP agent going active 14:15:33,383 ERROR [TrapEmitter] SNMP send error for localhost/127.0.0.1:1162: <java.security.InvalidParameterException: Buffer overflow error converting IP address> 14:15:33,640 WARN [InvokerLocator] Host resolves to null in socket://3ffe:ffff:100:f101::1:3873?timeout=300000. Perhaps the host contains an invalid character. See http://www.ietf.org/rfc/rfc2396.txt. 14:15:34,060 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 14:15:34,374 INFO [JMXConnector] starting JMXConnector on host 3ffe:ffff:100:f101::1:1090 14:15:34,393 ERROR [JMXConnector] Could not start JMXConnector: java.net.MalformedURLException: Bad port number: "": java.lang.NumberFormatException: For input string: "" at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:193) [:1.6.0_13] at org.jboss.system.server.jmx.JMXConnector.start(JMXConnector.java:143) [:6.0.0.20100721-M4 (Build SVNTag:JBoss_6.0.0.20100721-M4 date: 20100723)] Note that the start scripts set java.net.preferIPv4Stack=true: # Force IPv4 on Linux systems since IPv6 doesn't work correctly with jdk5 and lower if [ "$linux" = "true" ]; then JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" fi -- 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

13 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-8427) EJBContext.getCallerPrincipal() is not returning custom principal

by ANIL SALDHANA (JIRA)

EJBContext.getCallerPrincipal() is not returning custom principal ----------------------------------------------------------------- Key: JBAS-8427 URL: https://jira.jboss.org/browse/JBAS-8427 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA Reporter: ANIL SALDHANA Assignee: Marcus Moyses Fix For: 6.0.0.Final We will add a test case to AS test suite and see if we have an issue in the EJB3 security layer. More details in the forum thread. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8440) AS 7 failes to compile on a clean machine

by Carlo de Wolf (JIRA)

AS 7 failes to compile on a clean machine ----------------------------------------- Key: JBAS-8440 URL: https://jira.jboss.org/browse/JBAS-8440 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Blocker Fix For: 7.0.0.M1 carlo@dwarf:~/work/jboss-as$ ./build.sh clean install /home/carlo/work/jboss-as/tools/maven/bin/mvn -s tools/maven/conf/settings.xml clean install [INFO] Scanning for projects... [ERROR] The build could not read 2 projects -> [Help 1] [ERROR] The project org.jboss.as:jboss-as-testsuite-protocol-base:7.0.0.Beta1-SNAPSHOT (/home/carlo/work/jboss-as/testsuite/protocol/base/pom.xml) has 1 error [ERROR] Non-resolvable parent POM org.jboss.as:jboss-as-parent:7.0.0.Beta1-SNAPSHOT for org.jboss.as:jboss-as-testsuite-protocol-base:7.0.0.Beta1-SNAPSHOT: Failed to resolve POM for org.jboss.as:jboss-as-parent:7.0.0.Beta1-SNAPSHOT due to Missing: ---------- 1) org.jboss.as:jboss-as-parent:pom:7.0.0.Beta1-SNAPSHOT ---------- 1 required artifact is missing. for artifact: org.jboss.as:jboss-as-parent:pom:7.0.0.Beta1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2, releases=true, snapshots=false) -> [Help 2] [ERROR] The project org.jboss.as:jboss-as-testsuite-protocol-test:7.0.0.Beta1-SNAPSHOT (/home/carlo/work/jboss-as/testsuite/protocol/test/pom.xml) has 1 error [ERROR] Non-resolvable parent POM org.jboss.as:jboss-as-testsuite:7.0.0.Beta1-SNAPSHOT for org.jboss.as:jboss-as-testsuite-protocol-test:7.0.0.Beta1-SNAPSHOT: Failed to resolve POM for org.jboss.as:jboss-as-testsuite:7.0.0.Beta1-SNAPSHOT due to Missing: ---------- 1) org.jboss.as:jboss-as-testsuite:pom:7.0.0.Beta1-SNAPSHOT ---------- 1 required artifact is missing. for artifact: org.jboss.as:jboss-as-testsuite:pom:7.0.0.Beta1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2, releases=true, snapshots=false) -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- 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

13 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8445) Translator example fails to deploy due to ClassCast exception in WebCompJndiBinder

by Pete Muir (JIRA)

Translator example fails to deploy due to ClassCast exception in WebCompJndiBinder ---------------------------------------------------------------------------------- Key: JBAS-8445 URL: https://jira.jboss.org/browse/JBAS-8445 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Reporter: Pete Muir Assignee: Marius Bogoevici Fix For: 6.0.0.CR1 -- 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

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2011) Create Session Manager for EJB3 Stateful Session Beans

by Andrew Lee Rubinger (JIRA)

Create Session Manager for EJB3 Stateful Session Beans ------------------------------------------------------ Key: EJBTHREE-2011 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2011 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger EJB 2.x has the notion of an EJB "Home", which can destroy bean instances (sessions) without invoking any business logic. CDI demands the same "backdoor" removal from EJB3, and we must provide a remotable, replicable mechanism. Additionally, SFSB injection is not a great idea. Sessions can time out or be removed by the container entirely, leading invocations upon the injected reference to throw NoSuchEJBException. Instead we can leverage a "SessionManager" to be injected, which may create/destroy bean instances as instructed by the bean provider. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2173) exclude hibernate-jmx and hibernate-annotations from jboss-ejb3-as6-depchain

by Scott Marlow (JIRA)

exclude hibernate-jmx and hibernate-annotations from jboss-ejb3-as6-depchain ---------------------------------------------------------------------------- Key: EJBTHREE-2173 URL: https://jira.jboss.org/browse/EJBTHREE-2173 Project: EJB 3.0 Issue Type: Task Reporter: Scott Marlow I'm trying to upgrade to a newer version of Hibernate that no longer includes hibernate-jmx & hibernate-annotations. I updated a local copy of the jboss-ejb3-as6-depchain to exclude the above two jars but that didn't seem to exclude them from the AS 6 build. -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2175) @Resource processing should not mandate lookup or mapped-name

by jaikiran pai (JIRA)

@Resource processing should not mandate lookup or mapped-name ------------------------------------------------------------- Key: EJBTHREE-2175 URL: https://jira.jboss.org/browse/EJBTHREE-2175 Project: EJB 3.0 Issue Type: Bug Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai As per section EE.5.18, a EJB can have an injection point with just @Resource annotation without any "lookup" or "mapped-name" attribute: <quote> Alternatively, the Resource annotation can be used to request the injection of a Managed Bean given either its type or its name. If a name is specified using the lookup element then the type of the resource can be any of the types that the Managed Bean class implements, including any of its interfaces. If no name is specified, the type must be the Managed Bean class itself. (Note that the name element of the Resource annotation serves an entirely different purpose than the lookup element, consistently with other uses of Resource in this specification.) The authenticationType and shareable elements of the Resource annotation must not be specified. For example, given a ShoppingCartBean bean named "cart" defined in the same module as the client code and implementing the ShoppingCart interface, a client may use any of the following methods to obtain an instance of the bean class: @Resource ShoppingCartBean cart; </quote> Currently while processing @Resource injections in an EJB, we mandate the mapped-name (for user specific types): Caused by: java.lang.RuntimeException: mapped-name is required for org.myapp.ejb.MyBean of deployment MyBean at org.jboss.injection.ResourceHandler.loadXmlResourceEnvRefs(ResourceHandler.java:247) [:1.5.2] at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:336) [:1.5.2] at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:678) [:1.5.2] -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8374) EL parsing fails for no-arg method call.

by Stan Silvert (JIRA)

EL parsing fails for no-arg method call. ---------------------------------------- Key: JBAS-8374 URL: https://jira.jboss.org/browse/JBAS-8374 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.M4 Reporter: Stan Silvert Assignee: Remy Maucherat EL expressions with params works fine. However, if you have a no-arg method and you try to call it using parens you will get a parsing error: This works: <h:outputText value="ServerInfo: #{application.serverInfo}"/> But this does not work: <h:outputText value="ServerInfo: #{application.serverInfo()}"/> I'm attaching a simple hello world JSF application to demonstrate the problem. Also see forum reference. -- 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

13 years, 9 months

2
13
0 / 0

[JBoss JIRA] Created: (JBLOGGING-46) Log facade does not calculate line numbers correctly

by David Lloyd (JIRA)

Log facade does not calculate line numbers correctly ---------------------------------------------------- Key: JBLOGGING-46 URL: https://jira.jboss.org/browse/JBLOGGING-46 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 2.1.1.GA-jboss-logging, 2.1.0.GA-jboss-logging Reporter: David Lloyd Assignee: David Lloyd Fix For: 2.1.2.GA-jboss-logging The wrong logger delegation method is used in 2.1.x. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-174) Publish source jars to maven repo

by Brian Stansberry (JIRA)

Publish source jars to maven repo --------------------------------- Key: JBWEB-174 URL: https://jira.jboss.org/browse/JBWEB-174 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Remy Maucherat Please update your maven deployment process to include source jars. It's frustrating having to check out the JBW project and add it to my IDE to see what's going on whenever a problem involves JBW classes. -- 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

13 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010