geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-4290) pop3s: java.lang.IllegalArgumentException: hostname can't be null
Date Tue, 09 Sep 2008 17:59:44 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick McGuire resolved GERONIMO-4290.
------------------------------------

    Resolution: Fixed

Committed revision 693530.

> pop3s: java.lang.IllegalArgumentException: hostname can't be null
> -----------------------------------------------------------------
>
>                 Key: GERONIMO-4290
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4290
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>         Environment: geronimo-javamail_1.4_mail-1.4.jar
> IBM JRE 6 SR 1
> Windows XP
>            Reporter: Dave Rushall
>            Assignee: Rick McGuire
>            Priority: Minor
>
> When calling connect() for a "pop3s" store with mail.debug enabled, I see...
> DEBUG: getProvider() returning provider protocol=pop3s; type=javax.mail.Provider$Type@48864886;
class=org.apache.geronimo.javamail.store.pop3.POP3SSLStore; vendor=Apache Software Foundation;version=1.0
> pop3s DEBUG: Attempting SSL socket connection to server null:0
> pop3s DEBUG: Creating SSL socket using factory javax.net.ssl.SSLSocketFactory
> pop3s DEBUG: Received exception -> Failure creating SSL socket
> pop3s DEBUG: Exception message -> hostname can't be null
> java.lang.IllegalArgumentException: hostname can't be null
> 	at java.net.InetSocketAddress.<init>(InetSocketAddress.java:135)
> 	at com.ibm.jsse2.jc.<init>(jc.java:340)
> 	at com.ibm.jsse2.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:7)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:615)
> 	at org.apache.geronimo.javamail.util.MailConnection.getConnectedSSLSocket(MailConnection.java:432)
> 	at org.apache.geronimo.javamail.util.MailConnection.getConnection(MailConnection.java:249)
> 	at org.apache.geronimo.javamail.store.pop3.connection.POP3Connection.getConnection(POP3Connection.java:152)
> 	at org.apache.geronimo.javamail.store.pop3.connection.POP3Connection.protocolConnect(POP3Connection.java:121)
> 	at org.apache.geronimo.javamail.store.pop3.connection.POP3ConnectionPool.createPoolConnection(POP3ConnectionPool.java:155)
> 	at org.apache.geronimo.javamail.store.pop3.connection.POP3ConnectionPool.getConnection(POP3ConnectionPool.java:184)
> 	at org.apache.geronimo.javamail.store.pop3.POP3Store.getConnection(POP3Store.java:181)
> 	at org.apache.geronimo.javamail.store.pop3.POP3Store.isConnected(POP3Store.java:266)
> 	at javax.mail.Service.connect(Service.java:123)
>         ...
> However, the implementation does seem to recover from this as the debug trace continues
to show that the POP3 connection over SSL is established.
> I do not see this exception when using a plain "pop3" store.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message