[jboss-jira] [JBoss JIRA] Commented: (JBAS-6923) jboss provides wrong mailsession properties when multiple mailservices are deployed

Matthew Robinson (JIRA) jira-events at lists.jboss.org
Mon May 31 19:22:51 EDT 2010


    [ https://jira.jboss.org/browse/JBAS-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12533286#action_12533286 ] 

Matthew Robinson commented on JBAS-6923:
----------------------------------------

Please advise whether this issue is going to be actioned.  It has been open for more than a year and is very serious for those of us who need multiple mail sessions.  I am faced with having to hardcode the Session management into my application.  It is classed on your own system as Major.

> jboss provides wrong mailsession properties when multiple mailservices are deployed
> -----------------------------------------------------------------------------------
>
>                 Key: JBAS-6923
>                 URL: https://jira.jboss.org/browse/JBAS-6923
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.GA
>         Environment: linux
>            Reporter: Stefan Schueffler
>
> Having more than one MailService deployed (regardless if they are located each in its own xml-file, or if they are combined into one xml-file containing all the mail-related mbeans), jboss returns the wrong properties when retrieving a javax.mail.Session from jndi-context.
> After deployment of at least two or more MailService-mbeans, using the jmx-console or twiddle.sh reveals the correct values for the properties in the different MailServices. 
> But: a javax.mail.Session retrieved from jndi-context always is initialized with the properties of the last deployed MailService, regardless of which of the existing jndi-names is used to lookup this particular mailsession.
> Having multiple, different MailServices worked fine in jboss-4.2.x.
> This could somehow be related to JBAS-5896

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

        


More information about the jboss-jira mailing list