December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1848) Allow configuring TransactionAttribute type for Session Bean Lifecycle methods

by Stuart Douglas (JIRA)

Allow configuring TransactionAttribute type for Session Bean Lifecycle methods ------------------------------------------------------------------------------ Key: AS7-1848 URL: https://issues.jboss.org/browse/AS7-1848 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas We need to make sure that SLSB lifecycle methods never join an existing transaction. dmlloyd: @TA would be okay by me as long as we validate the argument [10:54pm] dmlloyd: restrict it to REQUIRES_NEW or NEVER or NOT_SUPPORTED I guess [10:54pm] dmlloyd: forbid MANDATORY, SUPPORTS, and REQUIRED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9092) Audit logging

by Brian Stansberry (JIRA)

Audit logging ------------- Key: JBAS-9092 URL: https://issues.jboss.org/browse/JBAS-9092 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta4 All modifications through the administrative infrastructure will be audited. The administrative audit log will be tamper proof. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
11
0 / 0

[JBoss JIRA] (AS7-2390) Warnings ARJUNA16037, ARJUNA16038 in log file

by Robert Petermeier (Created) (JIRA)

Warnings ARJUNA16037, ARJUNA16038 in log file --------------------------------------------- Key: AS7-2390 URL: https://issues.jboss.org/browse/AS7-2390 Project: Application Server 7 Issue Type: Bug Components: Transactions Affects Versions: 7.0.1.Final Environment: Windows 7, Windows Server 2008 Reporter: Robert Petermeier Assignee: Jonathan Halliday Priority: Minor We keep seeing the following warning messages in our log files every 2m, 10s: 12:05:29,290 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac146de0:3231b1f3:4ea67b21:4acc, node_name=1, branch_uid=0:ffffac146de0:3231b1f3:4ea67b21:4ad5, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@79453076 > On another system these are intermixed with 14:41:27,440 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86a7, node_name=1, branch_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86ab, eis_name=unknown eis name > We are using JBoss 7 in standalone mode, with three datasources. One of them is an XA datasource (a H2 database with class org.h2.jdbcx.JdbcDataSource on one system, oracle.jdbc.xa.client.OracleXADataSource on another). JDBC drivers for Oracle and H2 are deployed as jars in standalone/deployments along with our app. -- 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, 5 months

4
3
0 / 0

[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, 5 months

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, 5 months

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, 5 months

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, 5 months

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, 5 months

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, 5 months

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, 5 months

6
12
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 December 2011