December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1916) Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness

by Darran Lofthouse (JIRA)

Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness --------------------------------------------------------------------------------------------------------- Key: AS7-1916 URL: https://issues.jboss.org/browse/AS7-1916 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Can we generate a name of first boot? Possibly even separate the internal name use to link from the realm to the name presented to the end users? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[JBoss JIRA] (SECURITY-638) The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or

by Tom Fonteyne (Created) (JIRA)

The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-638 URL: https://issues.jboss.org/browse/SECURITY-638 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.4.SP9 Reporter: Tom Fonteyne Assignee: Anil Saldhana Priority: Minor Fix For: JBossSecurity_2.0.4.SP9 porting https://issues.jboss.org/browse/JBPAPP-7794 to PicketBox -- 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

13 years, 1 month

7
8
0 / 0

[JBoss JIRA] (AS7-2177) TS: Check logging

by Ondrej Zizka (Created) (JIRA)

TS: Check logging ----------------- Key: AS7-2177 URL: https://issues.jboss.org/browse/AS7-2177 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Some tests print to System.out, and also ex.printStackTrace(). Turn it to proper logging. Also check logging config. -- 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

13 years, 1 month

3
3
0 / 0

[JBoss JIRA] (AS7-2228) TS: Check IPv6

by Ondrej Zizka (Created) (JIRA)

TS: Check IPv6 -------------- Key: AS7-2228 URL: https://issues.jboss.org/browse/AS7-2228 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka This includes: * Check AS management support for IPv6 * Check Arquillian's support * Config param to scripts / maven property passed to arquillian * Replacing "http://localhost:..." in tests with a configurable value. -- 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

13 years, 1 month

7
16
0 / 0

[JBoss JIRA] (JBRULES-3279) Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package

by Geoffrey De Smet (Created) (JIRA)

Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package ----------------------------------------------------------------------------------------------------------- Key: JBRULES-3279 URL: https://issues.jboss.org/browse/JBRULES-3279 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Final Reporter: Geoffrey De Smet Assignee: Edson Tirelli I am trying to parse this rule: {code} rule "machineUsage" when $machineCapacity : MrMachineCapacity($machine : machine, $resource : resource) $usageTotal : Number() from accumulate( MrProcessRequirement(resource == $resource, $process : process, $usage : usage) MrProcessAssignment(machine == $machine, process == $process), sum($usage) ) then ... end {code} And I get this error message: {code} Exception in thread "main" java.lang.IllegalStateException: There are errors in the scoreDrl's:[47,77]: [ERR 102] Line 47:77 mismatched input ',' in rule "machineUsage" [0,0]: Parser returned a null Package {code} For this line: {code} MrProcessAssignment(machine == $machine, process == $process), {code} It clear that it's because I can't use 2 patterns inside a single accumulate, but the error message seems wrong? When I try this instead: {code} rule "machineUsage" when $machineCapacity : MrMachineCapacity($machine : machine, $resource : resource) $usageTotal : Number() from accumulate( (MrProcessRequirement(resource == $resource, $process : process, $usage : usage) and MrProcessAssignment(machine == $machine, process == $process)), sum($usage) ) then ... end {code} I get: {code} Exception in thread "main" org.drools.RuntimeDroolsException: BUG: Can't build a rete network with an inner OR group element {code} Don't really see the OR in there. -- 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

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3027) Guvnor repository connection does not support https connections

by Cristiano Nicolai (JIRA)

Guvnor repository connection does not support https connections --------------------------------------------------------------- Key: JBRULES-3027 URL: https://issues.jboss.org/browse/JBRULES-3027 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.2.0.M2 Environment: Jboss EAP 5.1 Guvnor 5.2.0-M2 Eclipse Helios Service Release 2 Reporter: Cristiano Nicolai Assignee: Mark Proctor When trying to access a Guvnor instance over https eclipse always throw an "Unexpected end of stream." exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
15
0 / 0

[JBoss JIRA] Created: (JBAS-8635) MailResourceAdapter mail check triggered only once

by Martin Clauss (JIRA)

MailResourceAdapter mail check triggered only once -------------------------------------------------- Key: JBAS-8635 URL: https://jira.jboss.org/browse/JBAS-8635 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: 6.0.0.M5 Environment: Win7, JBoss 6.0.0.M5, Java 1.6.0_21 Ubuntu lucid, JBoss 6.0.0.M5, Java 1.6.0_18 Reporter: Martin Clauss Assignee: Jesper Pedersen Mail check is performed correctly only once (after first timeout of pollingInterval) and then never again... 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss.ejb:service=EJBTimerService; Required: Described 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and supplies: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jndi:null 18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Class:org.jboss.resource.adapter.mail.inflow.MailListener 18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3) to KernelDeployment of: CTAEJB3.jar 18:43:13,741 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: com.contactulater.ba.MailBean ejbName: MailBean ****snip**** 18:44:13,749 INFO [STDOUT] DEBUG: JavaMail version 1.4.2 18:44:13,760 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.providers 18:44:13,761 INFO [STDOUT] DEBUG: Tables of loaded providers 18:44:13,761 INFO [STDOUT] DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider ***snip*** 18:44:13,763 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map 18:44:13,771 INFO [STDOUT] DEBUG: setDebug: JavaMail version 1.4.2 18:44:13,771 INFO [STDOUT] DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc] 18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.fetchsize: 16384 18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.statuscachetimeout: 1000 18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.appendbuffersize: -1 18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.minidletime: 10 18:44:13,774 INFO [STDOUT] DEBUG: trying to connect to host "127.0.0.1", port 143, isSSL false 18:44:13,799 INFO [STDOUT] * OK **** Cyrus IMAP4 v2.2.13-Debian-2.2.13-19 server ready 18:44:13,800 INFO [STDOUT] A0 CAPABILITY 18:44:13,820 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS 18:44:13,821 INFO [STDOUT] A0 OK Completed 18:44:13,821 INFO [STDOUT] DEBUG: protocolConnect login, host=127.0.0.1, user=jbossra, password=<non-null> 18:44:13,844 INFO [STDOUT] A1 OK User logged in 18:44:13,845 INFO [STDOUT] A2 CAPABILITY 18:44:13,868 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE LOGINDISABLED 18:44:13,869 INFO [STDOUT] A2 OK Completed 18:44:13,870 INFO [STDOUT] A3 LIST "" INBOX 18:44:13,889 INFO [STDOUT] * LIST (\HasChildren) "." "INBOX" 18:44:13,890 INFO [STDOUT] A3 OK Completed (0.000 secs 4 calls) 18:44:13,891 INFO [STDOUT] DEBUG: connection available -- size: 1 18:44:13,891 INFO [STDOUT] A4 SELECT INBOX 18:44:13,973 INFO [STDOUT] * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) 18:44:13,973 INFO [STDOUT] * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] 18:44:13,973 INFO [STDOUT] * 2 EXISTS 18:44:13,974 INFO [STDOUT] * 0 RECENT 18:44:13,974 INFO [STDOUT] * OK [UIDVALIDITY 1288029487] 18:44:13,974 INFO [STDOUT] * OK [UIDNEXT 4] 18:44:13,974 INFO [STDOUT] A4 OK [READ-WRITE] Completed 18:44:13,974 INFO [STDOUT] A5 SEARCH UNSEEN ALL 18:44:13,993 INFO [STDOUT] * SEARCH 18:44:13,993 INFO [STDOUT] A5 OK Completed (0 msgs in 0.000 secs) 18:44:13,993 INFO [STDOUT] A6 CLOSE 18:44:14,138 INFO [STDOUT] A6 OK Completed 18:44:14,138 INFO [STDOUT] DEBUG: added an Authenticated connection -- size: 1 18:44:14,138 INFO [STDOUT] IMAP DEBUG: IMAPProtocol noop 18:44:14,138 INFO [STDOUT] A7 NOOP 18:44:14,156 INFO [STDOUT] A7 OK Completed 18:44:14,156 INFO [STDOUT] A8 LOGOUT 18:44:14,175 INFO [STDOUT] * BYE LOGOUT received 18:44:14,175 INFO [STDOUT] A8 OK Completed 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore connection dead 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup, force false 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup done MDB implementation: @MessageDriven(activationConfig={ @ActivationConfigProperty(propertyName="mailServer", propertyValue="127.0.0.1"), @ActivationConfigProperty(propertyName="mailFolder", propertyValue="INBOX"), @ActivationConfigProperty(propertyName="storeProtocol", propertyValue="imap"), @ActivationConfigProperty(propertyName="userName", propertyValue="jbossra"), @ActivationConfigProperty(propertyName="password", propertyValue="****"), @ActivationConfigProperty(propertyName="debug", propertyValue="true"), @ActivationConfigProperty(propertyName="starttls", propertyValue="false"), @ActivationConfigProperty(propertyName="pollingInterval", propertyValue="60000") }) @ResourceAdapter("mail-ra.rar") public class MailBean implements MailListener { public void onMessage(Message message) { // Process the message try { System.out.println("Message received:"+message.getSubject()); } catch (MessagingException e) { e.printStackTrace(); } } } -- 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, 1 month

6
12
0 / 0

[JBoss JIRA] Created: (JBAS-9084) Per-deployment logging configuration

by David Lloyd (JIRA)

Per-deployment logging configuration ------------------------------------ Key: JBAS-9084 URL: https://issues.jboss.org/browse/JBAS-9084 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 7.0.0.Beta4 Add a deployment descriptor for per-deployment logging. Should also support user-defined handler (JUL) and appender (log4j) configurations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

11
14
0 / 0

[JBoss JIRA] (AS7-2792) CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping

by Rostislav Svoboda (Created) (JIRA)

CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping ----------------------------------------------------------------------------------------------------------- Key: AS7-2792 URL: https://issues.jboss.org/browse/AS7-2792 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Rostislav Svoboda Assignee: Alexey Loubyansky Fix For: 7.1.0.CR1 Hi Alexey. CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping. I would expect to see 'resolved-multicast-address' or something similar to 'resolved-address' for interface definition. I hope management model can provide such information. If not please reassign to Brian. {code} $ bin/standalone.sh -c standalone-ha.xml -u 224.34.3.154 $ bin/jboss-admin.sh -c [standalone@localhost:9999 /] cd /socket-binding-group=standard-sockets/socket-binding=jgroups-udp [standalone@localhost:9999 socket-binding=jgroups-udp] :read-resource(include-runtime=true) { "outcome" => "success", "result" => { "bound" => false, "bound-address" => undefined, "bound-port" => undefined, "fixed-port" => false, "interface" => undefined, "multicast-address" => expression "${jboss.default.multicast.address:230.0.0.4}", "multicast-port" => 45688, "name" => "jgroups-udp", "port" => 55200 } } {code} -- 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

13 years, 1 month

6
8
0 / 0

[JBoss JIRA] Created: (AS7-1264) Add schema references to standalone.xml, domain.xml, host.xml

by Gerry Matte (JIRA)

Add schema references to standalone.xml, domain.xml, host.xml ------------------------------------------------------------- Key: AS7-1264 URL: https://issues.jboss.org/browse/AS7-1264 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Gerry Matte Assignee: Brian Stansberry It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features. It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues. I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on. Personally I favor having a switch that turns off validation - to be used on production servers only. If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attemted to use an out-of-date version when upgrading to a new version of Jboss 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

7
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011