August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-639) XSD: background-validation-minutes

by Jesper Pedersen (JIRA)

XSD: background-validation-minutes ---------------------------------- Key: JBJCA-639 URL: https://issues.jboss.org/browse/JBJCA-639 Project: IronJacamar Issue Type: Bug Components: Common Affects Versions: 1.0.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.2.Final, 1.1.0.Alpha1 The XSDs refer to background-validation-minutes. It should be background-validation-millis -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-605) SecureIdentityLoginModule doesn't work on AS7

by Marcus Moyses (JIRA)

SecureIdentityLoginModule doesn't work on AS7 --------------------------------------------- Key: SECURITY-605 URL: https://issues.jboss.org/browse/SECURITY-605 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Reporter: Marcus Moyses Assignee: Marcus Moyses An issue with the new module classloader is preventing the SecureIdentityLoginModule class to be correctly loaded when used from the SubjectFactory. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-50) Documentation

by Dan Allen (JIRA)

Documentation ------------- Key: JBLOGGING-50 URL: https://jira.jboss.org/browse/JBLOGGING-50 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dan Allen Assignee: David Lloyd We desperately need some documentation for this project. Obviously documentation is a component in itself. I consider this issue resolved when there is at least some information about the project available and how to use it. That could be a web site, a reference guide a wiki page...anything. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-49) Relocate @Messages and @MessageBundle to i18n package

by Dan Allen (JIRA)

Relocate @Messages and @MessageBundle to i18n package ----------------------------------------------------- Key: JBLOGGING-49 URL: https://jira.jboss.org/browse/JBLOGGING-49 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd The message bundle facility in JBoss Logging is generally useful. In fact, we are planning on using it as a foundation for comprehensive i18n support in Seam 3. However, developers are going to be very standoff-ish if they have to import the @Messages and @MessageBundle annotations from a logging package (org.jboss.logging). I suggest moving them to the org.jboss.i18n package, though keeping it part of the JBoss Logging project since that will remain a foundation library and to stick to 1 JAR. Actual: org.jboss.logging.Messages org.jboss.logging.MessageBundle Proposed: org.jboss.i18n.Messages org.jboss.i18n.MessageBundle Relocate any other types as necessary. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Shelly McGowan commented on JBAS-8297: -------------------------------------- The JBoss Web update was committed: http://source.jboss.org/changelog/JBossAS6/?cs=111881 > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://issues.jboss.org/browse/JBAS-8297 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Assignee: Remy Maucherat > Fix For: 6.1.0 > > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1430) Creation of server-groups with invalid parameters succeeds

by Heiko Rupp (JIRA)

Creation of server-groups with invalid parameters succeeds ---------------------------------------------------------- Key: AS7-1430 URL: https://issues.jboss.org/browse/AS7-1430 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=infinispan] /server-group=bla:add(profile="asdfjasdklfjasklfj",socket-binding-group=asfasdfjaslfhjk) { "outcome" => "success", "result" => { "domain-results" => {"step-1" => undefined}, "server-operations" => undefined } } Clearly the profile and socket-binding-group are invalid - the operation still succeeds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-47) Support EAP 5.1 in JBoss Logging 3

by Pete Muir (JIRA)

Support EAP 5.1 in JBoss Logging 3 ---------------------------------- Key: JBLOGGING-47 URL: https://jira.jboss.org/browse/JBLOGGING-47 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Pete Muir Assignee: David Lloyd If you try to use JBoss Logging 3 in EAP 5.1 you get Caused by: java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object; at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47) at org.jboss.logging.Logger.getLogger(Logger.java:2164) at org.jboss.logging.Logger.getLogger(Logger.java:2189) As the LogManager is too old. We should add a provider for older versions of LogManager -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1072) Cannot use an encrypted database password

by Juergen Zimmermann (JIRA)

Cannot use an encrypted database password ----------------------------------------- Key: AS7-1072 URL: https://issues.jboss.org/browse/AS7-1072 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.0.0.Beta3 Reporter: Juergen Zimmermann I'm using Jenkins build 1241. When I declare datasources in standalone.xml with <user-name> and <password>, there is no problem. However, when I declare a security domain (java:/swe1DS is the datasource's jndi name): <security-domain name="verschluesseltesDbPassword" cache-type="default"> <authentication> <login-module code="SecureIdentity" flag="required"> <module-option name="username" value="swe2"/> <module-option name="password" value="..."/> <module-option name="managedConnectionFactoryName" value="jboss.jca:name=swe2DS,service=LocalTxCM"/> </login-module> </authentication> </security-domain> and changed the <security> section inside the datasource definition to <security-domain>verschluesseltesDbPassword</security-domain> then I get this stacktrace, when JBoss 7 is launched: 17:11:33,816 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-1) Exception during createSubject()Unauthenticated caller:null: java.lang.SecurityException: Unauthenticated caller:null at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83) at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:979) at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:959) at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26] at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:958) at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:507) at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:246) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:241) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:105) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-1348) Getting exception- at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: No such device

by namrata sarda (JIRA)

Getting exception- at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: No such device ---------------------------------------------------------------------------------------------------------- Key: JGRP-1348 URL: https://issues.jboss.org/browse/JGRP-1348 Project: JGroups Issue Type: Bug Environment: Java 1.5.0 Reporter: namrata sarda Assignee: Bela Ban We have faced this problem for 3 of our customer hosted by 3rd party vendor in just one week - Customer 1 Param : UDP = { discard_incompatible_packets = true; down_thread = false; enable_bundling = false; enable_diagnostics = false; ip_mcast = true; ip_ttl = 1; loopback = false; mcast_addr = 224.135.43.60; mcast_port = 6979; mcast_recv_buf_size = 1000000; mcast_send_buf_size = 640000; receive_on_all_interfaces = true; tos = 16; ucast_recv_buf_size = 1000000; ucast_send_buf_size = 640000; up_thread = false; use_incoming_packet_handler = true; use_outgoing_packet_handler = true; }; Mon Jul 11 04:26:14 PDT 2011 (T62) (org.jgroups.protocols.UDP:ERROR) : exception sending packet { ThreadName = "Thread[OutgoingPacketHandler,5,Pooled Threads]";} java.lang.Exception: dest=/224.135.43.60:6979 (58 bytes) at org.jgroups.protocols.UDP._send(UDP.java:356) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:300) at org.jgroups.protocols.TP.doSend(TP.java:952) at org.jgroups.protocols.TP.send(TP.java:941) at org.jgroups.protocols.TP.access$1600(TP.java:49) at org.jgroups.protocols.TP$OutgoingPacketHandler.handleMessage(TP.java:1305) at org.jgroups.protocols.TP$OutgoingPacketHandler.run(TP.java:1288) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: No such device at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:612) at org.jgroups.protocols.UDP._send(UDP.java:330) ... 7 more Customer 2 UDP = { discard_incompatible_packets = true; down_thread = false; enable_bundling = false; enable_diagnostics = false; ip_mcast = true; ip_ttl = 1; loopback = false; mcast_addr = 228.62.152.231; mcast_port = 6999; mcast_recv_buf_size = 1000000; mcast_send_buf_size = 640000; receive_on_all_interfaces = true; tos = 16; ucast_recv_buf_size = 1000000; ucast_send_buf_size = 640000; up_thread = false; use_incoming_packet_handler = true; use_outgoing_packet_handler = true; }; java.lang.Exception: dest=/228.62.152.231:6999 (58 bytes) at org.jgroups.protocols.UDP._send(UDP.java:356) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:300) at org.jgroups.protocols.TP.doSend(TP.java:952) at org.jgroups.protocols.TP.send(TP.java:941) at org.jgroups.protocols.TP.access$1600(TP.java:49) at org.jgroups.protocols.TP$OutgoingPacketHandler.handleMessage(TP.java:1305) at org.jgroups.protocols.TP$OutgoingPacketHandler.run(TP.java:1288) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: No such device at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:612) at org.jgroups.protocols.UDP._send(UDP.java:330) ... 7 more Customer 3 UDP = { discard_incompatible_packets = true; down_thread = false; enable_bundling = false; enable_diagnostics = false; ip_mcast = true; ip_ttl = 1; loopback = false; mcast_addr = 228.135.43.59; mcast_port = 6129; mcast_recv_buf_size = 1000000; mcast_send_buf_size = 640000; receive_on_all_interfaces = true; tos = 16; ucast_recv_buf_size = 1000000; ucast_send_buf_size = 640000; up_thread = false; use_incoming_packet_handler = true; use_outgoing_packet_handler = true; }; Thu Apr 14 19:17:43 EDT 2011 (T1165) (org.jgroups.protocols.UDP:ERROR) : exception sending packet { ThreadName = "Thread[OutgoingPacketHandler,5,Pooled Threads]";} java.lang.Exception: dest=/228.135.43.59:6129 (166 bytes) at org.jgroups.protocols.UDP._send(UDP.java:356) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:300) at org.jgroups.protocols.TP.doSend(TP.java:952) at org.jgroups.protocols.TP.send(TP.java:941) at org.jgroups.protocols.TP.access$1600(TP.java:49) at org.jgroups.protocols.TP$OutgoingPacketHandler.handleMessage(TP.java:1305) at org.jgroups.protocols.TP$OutgoingPacketHandler.run(TP.java:1288) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: No such device at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:612) at org.jgroups.protocols.UDP._send(UDP.java:330) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9150) JRuby war deployment error on JBoss AS

by Abin Shahab (JIRA)

JRuby war deployment error on JBoss AS -------------------------------------- Key: JBAS-9150 URL: https://issues.jboss.org/browse/JBAS-9150 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Abin Shahab -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
8
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 August 2011