August 2012 - jboss-jira - Jboss List Archives

[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

11 years, 6 months

6
12
0 / 0

[JBoss JIRA] (AS7-5254) Upgrade to infinispan 5.2

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-5254: -------------------------------- Summary: Upgrade to infinispan 5.2 Key: AS7-5254 URL: https://issues.jboss.org/browse/AS7-5254 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Tomaz Cerar Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 Infinispan 5.2 has some fixes that are needed for CapeDwarf to work properly. -- 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

11 years, 6 months

4
4
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

11 years, 6 months

11
14
0 / 0

[JBoss JIRA] (AS7-5062) PersistenceUnitRootURL for JPA providers may not be spec compliant

by Craig Ringer (JIRA)

Craig Ringer created AS7-5062: --------------------------------- Summary: PersistenceUnitRootURL for JPA providers may not be spec compliant Key: AS7-5062 URL: https://issues.jboss.org/browse/AS7-5062 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.1.Final Environment: $ java -version java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) $ uname -a Linux ayaki.localdomain 3.4.2-4.fc17.x86_64 #1 SMP Thu Jun 14 22:22:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Reporter: Craig Ringer Assignee: Scott Marlow Discussion on the EclipseLink bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=383200 ("On JBoss AS 7, EclipseLink doesn't find entity classes unless they're explicitly listed in persistence.xml") suggests that JBoss AS 7 may not be providing a spec-compliant PersistenceUnitRootURL or contents. EclipseLink can't scan the contents of a deployment for @Entity annotated classes, so it doesn't find any entities unless they're explicitly named in persistence.xml . http://docs.oracle.com/javaee/6/api/javax/persistence/spi/PersistenceUnit... states: {quote} java.net.URL getPersistenceUnitRootUrl() Returns the URL for the jar file or directory that is the root of the persistence unit. (If the persistence unit is rooted in the WEB-INF/classes directory, this will be the URL of that directory.) The URL will either be a file: URL referring to a jar file or referring to a directory that contains an exploded jar file, or some other URL from which an InputStream in jar format can be obtained. *Returns*: a URL referring to a jar file or directory {quote} ... and that's what EclipseLink expects. However, for EclipseLink class scanning to function correctly an adapter class must be provided, such as the classes provided here: https://community.jboss.org/wiki/HowToUseEclipseLinkWithAS7 to integrate EclipseLink with JBoss's VFS. It may be worth investigating why this is necessary and whether the current behavior is standards compliant. -- 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

11 years, 6 months

3
20
0 / 0

[JBoss JIRA] (AS7-5474) Url returned by PersistenceUnitInfo#getPersistenceUnitRootUrl() point to an empty folder

by Adriano Verona (JIRA)

Adriano Verona created AS7-5474: ----------------------------------- Summary: Url returned by PersistenceUnitInfo#getPersistenceUnitRootUrl() point to an empty folder Key: AS7-5474 URL: https://issues.jboss.org/browse/AS7-5474 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.2.0.Alpha1 Environment: $ java -version java version "1.6.0_31" Java(TM) SE Runtime Environment (build 1.6.0_31-b05) Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing) Windows 7 x64 Reporter: Adriano Verona Assignee: Scott Marlow When setting "jboss.as.jpa.vfs" property to false in persistence.xml PersistenceUnitInfo#getPersistenceUnitRootUrl() returns an Url that points to an empty folder (named "Contents"). The parent of this folder does holds the application jar. file:/D:/Java/jboss-as-7.2.0.Alpha1/standalone/tmp/vfs/temp9c270668d311f0c4/vjpa_jboss_example.jar-7ef91a4c66eeff18/contents/ Observed this at PersistenceProvider#createContainerEntityManagerFactory() method call. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
7
0 / 0

[JBoss JIRA] (AS7-5281) JBoss loading wrong Hibernate version when using Persistence unit in WAR file

by Kuthair Habboush (JIRA)

Kuthair Habboush created AS7-5281: ------------------------------------- Summary: JBoss loading wrong Hibernate version when using Persistence unit in WAR file Key: AS7-5281 URL: https://issues.jboss.org/browse/AS7-5281 Project: Application Server 7 Issue Type: Feature Request Components: Class Loading, JPA / Hibernate Affects Versions: 7.1.1.Final Environment: JBoss 7.1.1.Final & Hibernate 4.1.5.SP1 on Mac OSX 10.7/10.8 SQL Server 2008 on Windows 7 virtual Reporter: Kuthair Habboush Assignee: David Lloyd Attachments: hibernate-test.zip JBoss is loading Hibernate 4.0.1.Final (ships with) instead of the version specified in my Maven POM file and embedded in WAR archive, version: 4.1.5.SP1. This ONLY occurs when I have a Persistence Unit setup in my WAR file in directory: resources/META-INF. If I rename persistence.xml to persistence.xml.old, JBoss loads the correct version: Hibernate 4.1.5.SP1. I have a sample project. -- 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

11 years, 6 months

3
24
0 / 0

[JBoss JIRA] (AS7-3298) Deployment of POJO web service faild, if virtual server by name "default-host" does not exist.

by Tomaz Zupan (JIRA)

Tomaz Zupan created AS7-3298: -------------------------------- Summary: Deployment of POJO web service faild, if virtual server by name "default-host" does not exist. Key: AS7-3298 URL: https://issues.jboss.org/browse/AS7-3298 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1b Environment: Windows 7, Oracle Java 1.7.02 Reporter: Tomaz Zupan Assignee: Alessio Soldano If you change the name of the virtual-sarver in web subsystem, then deployment of any POJO web service failed with the folowing message: {quote} 13:21:25,506 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report}} JBAS014775: New missing/unsatisfied dependencies: service jboss.web.host.default-host (missing) dependents: [service jboss.ws.port-component-link, service jboss.web.deployment.default-host./server] {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

11 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-5344) JPA deploymen should set the thread context classloader during PersistenceProvider.createContainerEntityManagerFactory()

by Scott Marlow (JIRA)

Scott Marlow created AS7-5344: --------------------------------- Summary: JPA deploymen should set the thread context classloader during PersistenceProvider.createContainerEntityManagerFactory() Key: AS7-5344 URL: https://issues.jboss.org/browse/AS7-5344 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 -- 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

11 years, 6 months

1
7
0 / 0

[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4065: --------------------------------- Summary: TS: Migrate from Surefire to Failsafe maven plugin. Key: AS7-4065 URL: https://issues.jboss.org/browse/AS7-4065 Project: Application Server 7 Issue Type: Enhancement Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.2.0.Alpha1 Surefire aims at unit testing. Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). -- 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

11 years, 6 months

2
5
0 / 0

[JBoss JIRA] (SECURITY-668) Checkstyle into Picketbox build

by Anil Saldhana (JIRA)

Anil Saldhana created SECURITY-668: -------------------------------------- Summary: Checkstyle into Picketbox build Key: SECURITY-668 URL: https://issues.jboss.org/browse/SECURITY-668 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: Picketbox_v5.0.0.Alpha Available in the JBoss AS7 workspace. -- 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

11 years, 6 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 August 2012