You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Dave Rushall (JIRA)" <ji...@apache.org> on 2008/10/07 18:10:46 UTC
[jira] Created: (GERONIMO-4341) javax.mail.NoSuchProviderException:
Unable to locate provider for protocol: pop3
javax.mail.NoSuchProviderException: Unable to locate provider for protocol: pop3
--------------------------------------------------------------------------------
Key: GERONIMO-4341
URL: https://issues.apache.org/jira/browse/GERONIMO-4341
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Environment:
« Hide
geronimo-javamail_1.4_mail-1.4.jar
IBM JRE 6 SR 1
Windows XP
Reporter: Dave Rushall
Priority: Minor
There seems to be a race condition in session.getStore(protocol). I have multiple threads attempting to call this method on different session objects simultaneously and some of them get thrown the following exception:
javax.mail.NoSuchProviderException: Unable to locate provider for protocol:
pop3
at javax.mail.Session.getProvider(Session.java:229)
at javax.mail.Session.getStore(Session.java:270)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4341)
javax.mail.NoSuchProviderException: Unable to locate provider for protocol:
pop3
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire resolved GERONIMO-4341.
------------------------------------
Resolution: Fixed
Committed revision 702537. Specs
Committed revision 702543. Javamail providers.
> javax.mail.NoSuchProviderException: Unable to locate provider for protocol: pop3
> --------------------------------------------------------------------------------
>
> Key: GERONIMO-4341
> URL: https://issues.apache.org/jira/browse/GERONIMO-4341
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
> Environment:
> « Hide
> geronimo-javamail_1.4_mail-1.4.jar
> IBM JRE 6 SR 1
> Windows XP
> Reporter: Dave Rushall
> Assignee: Rick McGuire
> Priority: Minor
>
> There seems to be a race condition in session.getStore(protocol). I have multiple threads attempting to call this method on different session objects simultaneously and some of them get thrown the following exception:
> javax.mail.NoSuchProviderException: Unable to locate provider for protocol:
> pop3
> at javax.mail.Session.getProvider(Session.java:229)
> at javax.mail.Session.getStore(Session.java:270)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4341)
javax.mail.NoSuchProviderException: Unable to locate provider for protocol:
pop3
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire reassigned GERONIMO-4341:
--------------------------------------
Assignee: Rick McGuire
> javax.mail.NoSuchProviderException: Unable to locate provider for protocol: pop3
> --------------------------------------------------------------------------------
>
> Key: GERONIMO-4341
> URL: https://issues.apache.org/jira/browse/GERONIMO-4341
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
> Environment:
> « Hide
> geronimo-javamail_1.4_mail-1.4.jar
> IBM JRE 6 SR 1
> Windows XP
> Reporter: Dave Rushall
> Assignee: Rick McGuire
> Priority: Minor
>
> There seems to be a race condition in session.getStore(protocol). I have multiple threads attempting to call this method on different session objects simultaneously and some of them get thrown the following exception:
> javax.mail.NoSuchProviderException: Unable to locate provider for protocol:
> pop3
> at javax.mail.Session.getProvider(Session.java:229)
> at javax.mail.Session.getStore(Session.java:270)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.