Java Mail/EJB/WebLogic/weblogicSP6 "No Such Provider Exception"

Hi,
My application that is coded to send e-mail is not performing at all.
Application architecture is as follows:
1)JSP-EJB on Web Logic App server and
2)SMTP Host is IIS server and its SMTP service.
3)Using Java Mail API and installed Service Pack 6 of WebLogic that supports Java Mail API
4)EJB Programs coded as per the Sun JavaMail API documentation.
5)Send Mail occuring in the EJB.
Runtime Error: "No such provider exception"
Could u help me by instructing me about:
1)weblogic service pack installation.
2)sample ejb
PS:Same code on a simple java class fired on command line is executing without any exception. Wheras in an EJB on Weblogic is throwing the exception.

That error you are seeing typically comes from JavaMail being unable to
contact the SMTP host. Are you sure that you are a valid user/permitted to
access the mailer?
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Omm" <[email protected]> wrote in message
news:3a3cd390$[email protected]..
>
Hi,
My application that is coded to send e-mail is not performing at all.
Application architecture is as follows:
1)JSP-EJB on Web Logic App server and
2)SMTP Host is IIS server and its SMTP service.
3)Using Java Mail API and installed Service Pack 6 of WebLogic thatsupports Java Mail API
4)EJB Programs coded as per the Sun JavaMail API documentation.
5)Send Mail occuring in the EJB.
Runtime Error: "No such provider exception"
Could u help me by instructing me about:
1)weblogic service pack installation.
2)sample ejb
PS:Same code on a simple java class fired on command line is executingwithout any exception. Wheras in an EJB on Weblogic is throwing the
exception.
>
>

Similar Messages

  • No Such Provider Exception SunJSSE

    Hello,
    We are facing problem using SunJSSE with WebSphere4.0. We placed jsse jars in the jre/lib/ext directory and in our code we are trying to create SSLcontext as below
    context = SSLContext.getInstance("SSL","SunJSSE");
    tmFact=TrustManagerFactory.getInstance("SunX509","SunJSSE");
    kmfact = KeyManagerFactory.getInstance("SunX509","SunJSSE");
    And then intializing the context with trustmanager[], keymanager[] and secure random parameters.
    In our code we are dynamicaly setting the provider as
    java.security.Security.insertProviderAt(new com.sun.net.ssl.internal.ssl.Provider(),2);
    We also made the entry in the java.security file statically.
    However we are occasionally getting No such Provider Exception SunJSSE.
    Please note all this is running under websphere 4.0 and IBM has IbmjSSE jars in the jre/lib/ext as well.
    Any Ideas? thoughts? comments? help?
    Thanks

    Hi,
    I'm having a similar problem to this, what was wrong with this ? as it appears the provider should be available.
    Thanks

  • Error while sending mail when using Java Mail API

    Hi Experts,
    I am trying to execute a webdynpro application which uses the Java Mail API to send emails. The exception that I get on executing the application is :
    Sending failed;  nested exception is: javax.mail.SendFailedException: Invalid Addresses;  nested exception is: javax.mail.SendFailedException: 550 5.7.1 Unable to relay for [email protected]
    Can anybody please help me sort out the issue.
    Regards
    Abdullah

    Hi,
    Usually one get this error if the SMTP server is configured not to relay mails (a security measure) or the SMTP server need the mail to be sent from a trusted IP or with proper authentication. Some SMTP servers are configured to block junk mails.
    Pls check with your  mail server administrator.
    Regards

  • Weblogic Java Mail Session

    Cannot figure out what's the problem?
    I'm trying to send e-mail via Weblogic Mail Session EJB, the code seems pretty right to me, but it's always is throwing an exception.
    For SMTP I'm using personal computer SMTP service (Win XP), smtp.host=my IP address, user=domain name.
    --- begin ---
    javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.SendFailedException: Invalid Addresses; nested exception is: javax.mail.SendFailedException: 550 5.7.1 Unable to relay for [email protected] at javax.mail.Transport.send0(Transport.java:219)
    --- end ---
    Does anyone have an idea what's the glitch?

    This looks like a relay problem. Usually, ISPs have mail locked down so that you cannot send from their SMTP server without being logged in through them. They need to verify that you have an account with them and that you are logged on through that account ... usually done by checking to see if you have done a POP login in the last X number of minutes.
    Hope this helps.
    Paul

  • Java Generics in Ejbs WebLogic 9.2 MP1 WindowsXP Sun JDK

    Hi guys,
    I tried to deploy our application on Weblogic Server 9.2 MP1 (Windows, Sun JDK) and during deployment I have this error see bellow.
    Can somebody tell me what is the problem with generics and EJB compiler?
    Is necessary to add any path or change any server settings?
    Thanks for help
    Robert
    location: interface
    ...daoadapter_DaoAdapter_rge4uk_Intf
    public void batchPersist(java.util.List<T> arg0);
    ^
    ...daoadapter_DaoAdapter_rge4uk_Intf.java:20: cannot find symbol
    symbol : class T
    location: interface
    2 errors
    at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
    n.java:189)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:15
    7)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
    tReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
    erCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
    lbackDeliverer.java:45)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Thanks Matt for your answer.
    But I don't finish my testing :)
    I tried to deploy the same application on Weblogic 9.2 MP2 and then MP3 (sun jdk domain) and I didn't have problem with generics (application was correctly deployed and running).
    Then something was fixed in newer versions or may be bea guys support more then is in EJB 2.x specification.
    My next step, I'll try to deploy it on Jrockit domain and I give a note to conference what happen, may be it can help to somebody else.
    Thanks
    Robert

  • Java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl

    Hi All,
    I have recently encountered very very unusual problem which am not able to understand. If you could kindly shade some light on that it would be of great help. I have three environment where the application is being deployed. In the first two environment it works fine without any problem. But when I deployed in the third environment it behave very funny. The full stack trace of the error is bellow:
    Exception in EJBTestClient: java.rmi.RemoteException: ; nested exception is:
    weblogic.rmi.ServerError: A RemoteException occurred in the server metho
    d
    - with nested exception:
    [java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method findMeth
    The problem occurs when I try to call EJB from client. When I re-build the EJBS on the same environment it works fine. Am not able to understand this unusual behavior. If you could kindly help me understand the problem it would of great help. The environments are as follows.
    ENV-1
    OS - SunOS 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-Enterprise
    JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
    Weblogic - 5.1.0 Service Pack 8 12/20/2000 16:34:54 #95137
    Oracle � 8.1.6
    ENV-2
    OS - SunOS 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-Enterprise
    JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
    Weblogic - 5.1.0 Service Pack 9 04/06/2001 12:10:43 #105983
    Oracle � 8.1.6
    ENV-3
    OS - SunOS cfesit 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-Enterprise
    JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
    Weblogic - 5.1.0 Service Pack 9 04/05/2001 14:59:53 #105983
    Oracle � 8.1.6
    The problem occurs in the 3rd environment.
    Cheers,
    Tapas
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Hi..
    I guess itzz more of the service pack problems.
    Jars built on the later version won't work in the previous version (service packs) of weblogic.
    Try building a jar on the oldest version (service pack) u have and then try deploying it to the later version , i think it won't give u any problems.
    Try it out and let me know if u face any problems

  • Qustion about weblogic java mail

              hello
              i config a mail session in my weblogic8,when i run following code,the exception
              is thrown:
              Hashtable ht=new Hashtable();
              ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
              ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
              try {
              InitialContext ic = new InitialContext(ht);
              Session session = (Session) ic.lookup("MyMailSession");
              catch (Exception ex) {
              ex.printStackTrace();
              the exception is:
              javax.naming.ConfigurationException. Root exception is java.rmi.MarshalException:
              error marshalling return; nested exception is:
                   java.io.NotSerializableException: javax.mail.Session
                   at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
                   at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
                   at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
                   at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
                   at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
                   at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
                   at javax.naming.InitialContext.lookup(InitialContext.java:347)
                   at SendMail.main(SendMail.java:16)
              Caused by: java.io.NotSerializableException: javax.mail.Session
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                   at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:114)
                   at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:93)
                   at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
                   at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
                   at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              why?who can help me?
              thank you
              

    Hi,
              This a JMS forum, not a mail forum.
              They are very different animals.
              Try posting to "general", or perhaps "jndi".
              Tom
              zbcong wrote:
              > hello
              > i config a mail session in my weblogic8,when i run following code,the exception
              > is thrown:
              >
              >
              >
              > Hashtable ht=new Hashtable();
              > ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
              > ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
              > try {
              > InitialContext ic = new InitialContext(ht);
              > Session session = (Session) ic.lookup("MyMailSession");
              > }
              > catch (Exception ex) {
              > ex.printStackTrace();
              > }
              >
              >
              >
              >
              >
              > the exception is:
              >
              >
              > javax.naming.ConfigurationException. Root exception is java.rmi.MarshalException:
              > error marshalling return; nested exception is:
              >      java.io.NotSerializableException: javax.mail.Session
              >      at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
              >      at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
              >      at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
              >      at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
              >      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
              >      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
              >      at javax.naming.InitialContext.lookup(InitialContext.java:347)
              >      at SendMail.main(SendMail.java:16)
              > Caused by: java.io.NotSerializableException: javax.mail.Session
              >      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
              >      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
              >      at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:114)
              >      at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:93)
              >      at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
              >      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
              >      at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
              >      at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
              >      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
              >      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              >      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
              >      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              >      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              >
              >
              > why?who can help me?
              > thank you
              

  • Can't using J2EE java mail?

    hi all,
    Here is a problem that I have with my the usage of Java Mail Session
    that i set up in weblogic. I use weblogic 8.1
    When I do the JNDI lookup to the mail session (set up in the weblogic
    admin interface), it looks that the lookup itself is ok but when i do
    the casting, it doesn't work. Have a look at my code and the trace
    produced :
    writed an external client,follow:
    <myCode>
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory
    h.put(Context.PROVIDER_URL,"t3://localhost:7001"); // provider url is
    right
    h.put(Context.SECURITY_PRINCIPAL,"weblogic");
    h.put(Context.SECURITY_CREDENTIALS,"password");
    Context namingContext = new InitialContext(h);
    Session mailSession = (Session) namingContext.lookup("jndi/mail");
    </myCode>
    <trace>
    javax.naming.ConfigurationException. Root exception is
    java.rmi.MarshalExceptio
    n: error marshalling return; nested exception is:
    java.io.NotSerializableException: javax.mail.Session
    java.io.NotSerializableException: javax.mail.Session
    <<no stack trace available>>
    </trace>
    I can understand the exception as javax.mail.Session doesn't implement
    serializble. But How do I have to do to make it work, then? Because what
    I do is just how it's explained in the weblogic doc. Is there a mistake
    in the do? Do I have to cast to somethig else?
    Any help would be very appraciated.
    Thanks.

    Try this on the server side not from external client - that should work fine.
    If you need this from an external client, since the java.mail.Session object is not serializable - you can also implement an EJB and have your client lookup the session bean and send the data to the server and have the serverside session bean implementation create the mail session and interact.
    hth
    sree

  • Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/JoinPoint

    Hi,
    I have an application jar file which is run from a .sh file.
    The application uses ridc api to checkin a document on UCM.
    I have placed jars for supporting the application on the folder where we have kept the application jar
    also we have mentioned the supporting jar file names in the Manifest.mf file of the application jar.
    The necessary jar files which we have placed are:
    com.lnt.ucm.integrationutility.ucm.Client
    log4j-1.2.16.jar
    oracle.ucm.ridc-11.1.1.jar
    poi-2.5.1.jar
    commons-codec-1.2.jar
    commons-httpclient-3.1.jar
    commons-logging-1.0.4.jar
    mail.jar
    jxl-2.6.10.jar
    com.bea.core.antlr.runtime_2.7.7.jar
    com.oracle.toplink_1.0.0.0_11-1-1-5-0.jar
    jrf.jar
    org.eclipse.persistence_1.1.0.0_2-1.jar
    weblogic.jar
    wlfullclient.jar
    wseeclient.jar
    jaxws-rt-2.1.4.jar
    we are getting below exception when we run the jar from the .sh file.
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/JoinPoint
    at weblogic.wsee.jaxws.spi.WLSProvider.<clinit>(WLSProvider.java:90)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:31)
    at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:90)
    at javax.xml.ws.spi.Provider.provider(Provider.java:83)
    at javax.xml.ws.Service.<init>(Service.java:56)
    at com.abc.ucm.proxy.JDEUCMManagerService.<init>(JDEUCMManagerService.java:66)
    at com.abc.ucm.integrationutility.ucm.Client.executeUtilty(Client.java:50)
    at com.abc.ucm.integrationutility.ucm.Client.main(Client.java:540)
    I'm not able to find any jar for weblogic/diagnostics/instrumentation/JoinPoint can you please tell me which jar needs to be added.
    Regards,
    Tejaswini L

    914897 wrote:
    I encounter the similar error. Anyone knows how to fix it?By providing a configuration file which validates with the corresponding XSDs found in coherence.jar. Sorry, but can't point you to the specific issue without seeing the erroneous configuration file.
    Best regards,
    Robert

  • Problem using Java Mail API with WLS 7.0

    Hi All,
    I am trying to use the Java Mail API provided by WLS 7.0. I have made the
    settings metioned in the WLS 7.0 docs. However when I try to run the program I
    am getting the following error:
    javax.naming.NoInitialContextException: Need to specify class name in environment
    or system property, or as an applet parameter, or in an application resource file:
    java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    46)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
    a:283)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    The code that I have written is as follows
    import java.util.*;
    import javax.activation.*;
    import javax.mail.*;
    import javax.mail.internet.*;
    import javax.naming.*;
    import java.io.*;
    import java.net.InetAddress;
    import java.util.Properties;
    import java.util.Date;
    public class MailTo {
         public static void main(String args[])
              try
                   //Context ic = getInitialContext();
                   InitialContext ic = new InitialContext();
    /* My jndi name is "testSession" */
                   Session session = (Session) ic.lookup("testSession"); /* THE PROBLEM IS SHOWN
    IN THIS LINE */
                   Properties props = new Properties();
                   props.put("mail.transport.protocol", "smtp");
                   props.put("mail.smtp.host", "XX.XX.XX.XX");
    /* For security reasons I have written the ip add in this format */
                   props.put("mail.from", "[email protected]"); /* for security reasons i have
    changed the mail address */
                   Session session2 = session.getInstance(props);
                   Message msg = new MimeMessage(session2);
                   msg.setFrom();
                   msg.setRecipients(Message.RecipientType.TO, InternetAddress.parse("[email protected]",
    false));
                   msg.setSubject("Test Message");
                   msg.setSentDate(new Date());
                   MimeBodyPart mbp = new MimeBodyPart();
                   mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
                   Multipart mp = new MimeMultipart();
                   mp.addBodyPart(mbp);
                   msg.setContent(mp);
                   Transport.send(msg);
              catch(Exception e)
                   e.printStackTrace();
         }//end of main
    public static Context getInitialContext()
         throws NamingException
              Properties p = new Properties();
              p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
              p.put(Context.PROVIDER_URL, "t3://localhost:7501/testWebApp");
                   p.put(Context.SECURITY_PRINCIPAL, "weblogic");
                   p.put(Context.SECURITY_CREDENTIALS, "weblogic");
              return new InitialContext(p);
    }//end of class
    Can anyone please tell me what is the problem. I thought that we cannot directly
    do
    InitialContext ic = new InitialContext();
    So I had written a method getInitialContext() as shown in the above piece of code,
    but that too did not work.
    Eagerly awaiting a response.
    Jimmy Shah

    You can use InitialContext ic = new InitialContext() only if you are using a startup class, servlet or a JSP i.e
    server side code.
    If you are using a java client you need to use Context ic = getInitialContext();
    Try this code
    import java.util.*;
    import javax.activation.*;
    import javax.mail.*;
    import javax.mail.internet.*;
    import javax.naming.*;
    import java.io.*;
    import java.net.InetAddress;
    import java.util.Properties;
    import java.util.Date;
    public class MailTo {
    public static void main(String args[])
    try {
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, "t3://localhost:7001");
    Context ic = new InitialContext(h);
    Session session = (Session) ic.lookup("testSession");
    Properties props = new Properties();
    props.put("mail.transport.protocol", "smtp");
    props.put("mail.smtp.host", "XX.XX.XX.XX");
    props.put("mail.from", "[email protected]");
    Session session2 = session.getInstance(props);
    Message msg = new MimeMessage(session2);
    msg.setFrom();
    msg.setRecipients(Message.RecipientType.TO,InternetAddress.parse("[email protected]",false));
    msg.setSubject("Test Message");
    msg.setSentDate(new Date());
    MimeBodyPart mbp = new MimeBodyPart();
    mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
    Multipart mp = new MimeMultipart();
    mp.addBodyPart(mbp);
    msg.setContent(mp);
    Transport.send(msg);
    catch(Exception e)
    e.printStackTrace();
    }//end of main
    }//end of class
    We have shipped a javamail example in the samples\server\src\examples\javamail folder.
    Jimmy Shah wrote:
    Hi All,
    I am trying to use the Java Mail API provided by WLS 7.0. I have made the
    settings metioned in the WLS 7.0 docs. However when I try to run the program I
    am getting the following error:
    javax.naming.NoInitialContextException: Need to specify class name in environment
    or system property, or as an applet parameter, or in an application resource file:
    java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    46)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
    a:283)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    The code that I have written is as follows
    import java.util.*;
    import javax.activation.*;
    import javax.mail.*;
    import javax.mail.internet.*;
    import javax.naming.*;
    import java.io.*;
    import java.net.InetAddress;
    import java.util.Properties;
    import java.util.Date;
    public class MailTo {
    public static void main(String args[])
    try
    //Context ic = getInitialContext();
    InitialContext ic = new InitialContext();
    /* My jndi name is "testSession" */
    Session session = (Session) ic.lookup("testSession"); /* THE PROBLEM IS SHOWN
    IN THIS LINE */
    Properties props = new Properties();
    props.put("mail.transport.protocol", "smtp");
    props.put("mail.smtp.host", "XX.XX.XX.XX");
    /* For security reasons I have written the ip add in this format */
    props.put("mail.from", "[email protected]"); /* for security reasons i have
    changed the mail address */
    Session session2 = session.getInstance(props);
    Message msg = new MimeMessage(session2);
    msg.setFrom();
    msg.setRecipients(Message.RecipientType.TO, InternetAddress.parse("[email protected]",
    false));
    msg.setSubject("Test Message");
    msg.setSentDate(new Date());
    MimeBodyPart mbp = new MimeBodyPart();
    mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
    Multipart mp = new MimeMultipart();
    mp.addBodyPart(mbp);
    msg.setContent(mp);
    Transport.send(msg);
    catch(Exception e)
    e.printStackTrace();
    }//end of main
    public static Context getInitialContext()
    throws NamingException
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    p.put(Context.PROVIDER_URL, "t3://localhost:7501/testWebApp");
    p.put(Context.SECURITY_PRINCIPAL, "weblogic");
    p.put(Context.SECURITY_CREDENTIALS, "weblogic");
    return new InitialContext(p);
    }//end of class
    Can anyone please tell me what is the problem. I thought that we cannot directly
    do
    InitialContext ic = new InitialContext();
    So I had written a method getInitialContext() as shown in the above piece of code,
    but that too did not work.
    Eagerly awaiting a response.
    Jimmy Shah--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • Java.io.NotSerializableException: weblogic.ejb20.internal.EntityEJBContextImpl

    Hi,
    We are currently in the process of moving from Weblogic 6.1 SP5 and
    Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
    I have seen a "scaring" stack trace. It seems that, for some reason, a
    thing that "uses to work" failed with a very strange error. I tried to
    reproduce it but without any success. Besides asking if anybody knows
    what could have caused this error I would like to know what the "not
    serializable" object is. Is it the EntityEJBContext?
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    In case it could share some light in the case I will explain a bit what
    does the process intended to do:
    The general idea is that, given some data (managed with Toplink's 9.0.4
    CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
    has been working for ages without any problem) and "publish" it via JMS
    in order to perform asyncronous actions with it. I'm sure this is a,
    more than usual, scenario for a lot of folks.
    As it seems looking at the stack at some point during some internal
    object serialization it fails and rollbacks all the process. The object
    being serialized by our side only contains four attributes: a
    java.math.BigDecimal for it's primary key, a java.util.Date for
    timestamp locking and two simple java.lang.String's
    Although I'm pretty sure the problem should not be with the entity bean
    itself but with an internal Weblogic op (is it trying to serialize the
    EntityBeanContext as stated after the java.io.NotSerializableException
    message?
    Any help with this would be greatly appreciated as I have no clue how
    this happened and I'm also unable to reproduce it (I'm also sure if I
    managed to trigger it testing the application alone it will rise many
    more times that could be admited if we move to production).
    I would like to point also that currently until we have some more time
    to fix it we are using "remote" entity bean, I mean even if we are alway
    s calling them within the container they are not deployed with "local"
    interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
    being co-located with the session beans).
    Regards.
    Ignacio.
    P.S. here is the full stack dump
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at
    app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
    at
    app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
    at app.biz.common.Publisher.performPublication(Publisher.java:1644)
    at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
    at app.biz.module.ModuleDAO.update(ModuleDAO.java)
    at
    app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at app.core.util.Proxy.execute(Proxy.java:583)
    at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
    at
    app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
    at
    app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
    at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
    at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

    Ignacio,
    6.1 used pass-by-reference by default, so parameters to beans were
    passed by reference.
    It's very likely that you are getting this error because in 8.1 this default
    was turned off. This causes serialization of parameters by default and
    that's why your code that worked started failing - you just did not know
    that you were passing non-serializable objects around.
    To fix this you could either turn on the pass-by-reference explicitly and/or
    find out where your code is passing non-serializable objects. This is a useful
    exercise anyways.
    Hope this helps.
    Regards,
    Slava Imeshev
    "Ignacio G. Dupont" <[email protected]> wrote in message news:41b8c93f@mail...
    Hi,
    We are currently in the process of moving from Weblogic 6.1 SP5 and
    Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
    I have seen a "scaring" stack trace. It seems that, for some reason, a
    thing that "uses to work" failed with a very strange error. I tried to
    reproduce it but without any success. Besides asking if anybody knows
    what could have caused this error I would like to know what the "not
    serializable" object is. Is it the EntityEJBContext?
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    In case it could share some light in the case I will explain a bit what
    does the process intended to do:
    The general idea is that, given some data (managed with Toplink's 9.0.4
    CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
    has been working for ages without any problem) and "publish" it via JMS
    in order to perform asyncronous actions with it. I'm sure this is a,
    more than usual, scenario for a lot of folks.
    As it seems looking at the stack at some point during some internal
    object serialization it fails and rollbacks all the process. The object
    being serialized by our side only contains four attributes: a
    java.math.BigDecimal for it's primary key, a java.util.Date for
    timestamp locking and two simple java.lang.String's
    Although I'm pretty sure the problem should not be with the entity bean
    itself but with an internal Weblogic op (is it trying to serialize the
    EntityBeanContext as stated after the java.io.NotSerializableException
    message?
    Any help with this would be greatly appreciated as I have no clue how
    this happened and I'm also unable to reproduce it (I'm also sure if I
    managed to trigger it testing the application alone it will rise many
    more times that could be admited if we move to production).
    I would like to point also that currently until we have some more time
    to fix it we are using "remote" entity bean, I mean even if we are alway
    s calling them within the container they are not deployed with "local"
    interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
    being co-located with the session beans).
    Regards.
    Ignacio.
    P.S. here is the full stack dump
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at
    app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
    at
    app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
    at app.biz.common.Publisher.performPublication(Publisher.java:1644)
    at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
    at app.biz.module.ModuleDAO.update(ModuleDAO.java)
    at
    app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at app.core.util.Proxy.execute(Proxy.java:583)
    at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
    at
    app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
    at
    app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
    at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
    at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

  • Java Websphere and Weblogic

    Can any one explain or what type of applications are being developed by
    java websphere and weblogic ,also is there any sample project or source
    url please inform me?
    Thanks
    Arun

    websphere and weblogic are j2ee container implementations by IBM and BEA respectively. They are ment to host j2ee application complient to the j2ee spec. You can develop any kind of applications on these servers as long as they comply to j2ee spec. Both these servers provide various extensions to j2ee such as tools and APIs to make development for these server easier.

  • Java Mail error rfc822

              Hi,
              Getting following error message when the servlet try to send a
              mail.( Servlet uses Java Mail ApI).
              javax.mail.NoSuchProviderException: No provider for Address type:
              rfc822
              at java.lang.Throwable.fillInStackTrace(Native Method)
              at java.lang.Throwable.fillInStackTrace(Compiled Code)
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Exception.<init>(Compiled Code)
              at javax.mail.MessagingException.<init>(MessagingException.java:42)
              at javax.mail.NoSuchProviderException.<init>(NoSuchProviderException.java:34)
              at javax.mail.Session.getTransport(Session.java:475)
              at javax.mail.Transport.send0(Compiled Code)
              at javax.mail.Transport.send(Transport.java:80)
              at com.arsin.vcommerce.b2beprocurement.SendMail.sendMail(Compiled
              Code)
              at com.arsin.vcommerce.b2beprocurement.StatusServlet.doPost(StatusServlet.java:39)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              at weblogic.kernel.ExecuteThread.run(Compiled Code)
              Any help.
              Thanks
              Ram.
              

              If Weblogic 6, see if you can get help from
              http://edocs.bea.com/wls/docs60/programming/topics.html
              "ram chinnasamy" <[email protected]> wrote:
              >
              >Hi,
              > Getting following error message when the servlet try
              >to send a
              >mail.( Servlet uses Java Mail ApI).
              >
              >javax.mail.NoSuchProviderException: No provider for Address
              >type:
              >rfc822
              > at java.lang.Throwable.fillInStackTrace(Native
              >Method)
              > at java.lang.Throwable.fillInStackTrace(Compiled
              >Code)
              > at java.lang.Throwable.<init>(Compiled Code)
              > at java.lang.Exception.<init>(Compiled Code)
              > at javax.mail.MessagingException.<init>(MessagingException.java:42)
              > at javax.mail.NoSuchProviderException.<init>(NoSuchProviderException.java:34)
              > at javax.mail.Session.getTransport(Session.java:475)
              > at javax.mail.Transport.send0(Compiled Code)
              > at javax.mail.Transport.send(Transport.java:80)
              > at com.arsin.vcommerce.b2beprocurement.SendMail.sendMail(Compiled
              >Code)
              > at com.arsin.vcommerce.b2beprocurement.StatusServlet.doPost(StatusServlet.java:39)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
              > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
              > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
              > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
              > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              > at weblogic.kernel.ExecuteThread.run(Compiled
              >Code)
              >
              >
              >Any help.
              >Thanks
              >Ram.
              >
              >
              

  • Java mail with proxy server

    Hi I am a novice, working on a mail sender though proxy. I read Java mail FAQ in http://java.sun.com/products/javamail/FAQ.html#proxy.
    And also I found a snippet in below therad.
    http://forums.sun.com/thread.jspa?threadID=615715&start=0&tstart=0
    <QUOTE>here is the solution that you can send mail through a proxy server
    Properties p = System.getProperties();
             p.setProperty("proxySet","true");
             p.setProperty("socksProxyHost","192.168.155.1");
             p.setProperty("socksProxyPort","1080");</QUOTE>
    I installed CCProxy in my machine and gave my own IP address ( 1. LAN IP and 2. IP from whatismyip.com; both works ) and port number. It works. But I gave IP addrss of my friend ( 1. LAN IP and 2. IP from whatismyip.com; both NONE work ) who got CCProxy and in his machine. But doesnt work ( throws Below exception).
    Exception in thread "main" javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465;
      nested exception is:
            java.net.SocketException: Can't connect to SOCKS proxy:Connection timedout: connect
            at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1391)
            at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:412)
            at javax.mail.Service.connect(Service.java:310)
    His IP address is found with whatismyip.com. I guess its a problem with IP address. What am I doing wrong here ?? Could some one help me out please ?
    Edited by: baskark on Mar 8, 2009 6:26 PM
    Edited by: baskark on Mar 8, 2009 6:44 PM

    I believe we can give some other socks proxy ip address too, other than CCproxy machine ip address If I am correct. Is there any specific way to use the socks server ip address ( such as provided in many websites, used for open relay) ? I tried some of them, which I am able to ping. But still I get the same exception like connection request timed out.

  • Problems with a java bean in Weblogic 5.1

    Hello,
              I am having a problem deploying a java bean in Weblogic 5.1:
              I have been given a .class and a .jar file for a java bean (not an EJB). I
              placed the .class file into e:\temp\WEB-INF\classes and added the following
              line to my weblogic.properties file:
              weblogic.httpd.webApp.testApp=e:/temp/
              I have also updated the web.xml file in the WEB-INF directory as follows:
              <?xml version="1.0" encoding="UTF-8"?>
              <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
              Application 1.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
              <web-app>
              <servlet>
              <servlet-name>EdIface</servlet-name>
              <jsp-file>test.jsp</jsp-file>
              </servlet>
              <servlet-mapping>
              <servlet-name>EdIface</servlet-name>
              <url-pattern>EdIface</url-pattern>
              </servlet-mapping>
              </web-app>
              When I try to access my http:\\server:port\testApp\test I get an "Error
              500 - internal server error".
              Has anyone had experice with deploying a java bean with jsut the .class and
              .jar file? Where should I put the .jar file?
              I appreciate any advice!
              

    Bump

Maybe you are looking for

  • How to Create a Table with Merge and partitions in HANA

    Hi, What is the best way to create a Table with MERGE and PARTITION and UNLOAD PRIORITIES. Any body can you please give me some examples. Regards, Deva

  • ITunes recognizes new iPhone 5 as old iPhone 4s

    I had several problems 4 days into my life with my new iphone 5. Flashing screen, exiting out of apps, not downloading apps... and I was driving 1400 miles in a rental with no navigation. On top of that... my iTunes program was only recognizing it as

  • Smartform form for Payment remittance advice to Vendor

    Hi Friends, My requirement is i have a sapscript "F110_IN_AVIS" (Driver program:RFF0EDI1 This is a standard sap driver program)and it should be converted to Smartform with all the windows as it was present in sapscript. I have migrated the sapscript

  • Word Wrap on all-day events?

    When I create an all-day event, if the event name is too long to fit on one line, it does not wrap to the next line (like it does with a timed event) and the event is truncated. How can I see all of the event name with all-day events? The problem exi

  • Who knows oracle application's history

    Hi, I like to know the history of oracle application(s), does anyone know or have a link? Some employers are looking for application administrator with 10+ years experience, I just wonder whether the application itself has 10+ years history or not :-