Cannot forward messages

I have four email accounts in Thunderbird. When I try to forward message with imbedded attachment I get a message that "Sending of message failed" "The message could not be sent....... SMTP server plus was lost in the middle of the transaction."
If I switch to another account to send, it works fine. I checked the setting and they are all the same.
Win7 x64
Thanks, Stewart

McAfee, but I've disabled it no change. And the problem is intermittent. Good thought though, Thanks

Similar Messages

  • Cannot forward messages to SAP

    Hello,
    Not all message processors are able to forward message to SAP. Actually, only one user can do it which the user configured in table AISUSER whose S-user is the same as the one in DSWP --> Global Settings and SAP-OSS RFC destination.
    I tried to add another user in the AISUSER table and assigned the same S-user but got the error Error when Error when opening an RFC connection. Then, I assigned a different s-user but got the same error.
    I also tried to assign the working S-user for parameter SAPNETUSID in the user master record but always got the following error: The system could not find your SAP customer notification system user
    Message no. DNO150
    Can somebody help me how to address this issue? My solution manager is 4.0.
    Thanks,
    Regina

    This is already working. The user should both be in V_AISUSER table and have the SAPNETUSID parameter set.

  • JMS SAF client cannot forward messages - Caused by: javax.crypto.BadPadding

    Hi,
    I seem to be struggling with a problem that I'm not sure if I can ever find a solution.
    I have a configured a local JMS client to forward my messages to a remote WLSB 9.2.
    The local client is running JDK 1_0_14 on a windows platform.
    The remote server is on IBM JRE on linux. Now I'm getting problems when the messages are forwarded by the local SAF client. The client does not seem to be able to decrypt the password I have in my SAFClient.xml. I have pretty much followed every line in the documentation of SAF client and has already revisited it a few times.
    It seems to be something to do with the ClientSAFEncrypt utility that I was advised to get the encrypted password which I have put in the XML File. Here is the exception. Any help will be greatly appreciated.
    All I know is it is something to do with encoding of the password, but I cannot get a clue what else.
    <Mar 25, 2008 12:28:40 PM PDT> <Info> <Store> <BEA-280050> <Persistent store "SAFSTORE0V" opened: directory="C:\depot\javaSrc\logging\stores\default" writePolicy="Direct-Write" blockSize=512 directIO=false driver="NIO">
    javax.naming.NamingException: Invalid password key to unlock the passwords in the configuration file [Root exception is weblogic.jms.common.JMSException: Invalid password key to unlock the passwords in the configuration file]
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getNamingException(InitialContextFactoryImpl.java:31)
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:162)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at com.netflix.messaging.ESBFactory.<init>(ESBFactory.java:103)
         at com.netflix.messaging.ESBFactory.getFactory(ESBFactory.java:45)
         at com.netflix.messaging.NFMessagingManager.getProducerHandle(NFMessagingManager.java:218)
         at com.netflix.messaging.NFMessagingManager.initProducers(NFMessagingManager.java:730)
         at com.netflix.messaging.NFMessagingManager.init(NFMessagingManager.java:863)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1461)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1628)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.startMessagingManager(MessageDestinationDispatcher.java:164)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.<init>(MessageDestinationDispatcher.java:25)
         at com.netflix.logging.NFMessageAppender.append(NFMessageAppender.java:72)
         at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
         at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
         at org.apache.log4j.Category.callAppenders(Category.java:206)
         at org.apache.log4j.Category.forcedLog(Category.java:391)
         at org.apache.log4j.Category.log(Category.java:838)
         at com.netflix.logging.log4jAdapter.Log4jLoggingAdapter.log(Log4jLoggingAdapter.java:64)
         at com.netflix.logging.NFLogger.log(NFLogger.java:125)
         at com.netflix.logging.LogManager.info(LogManager.java:152)
         at com.netflix.logging.aggregator.Bucketer.init(Bucketer.java:92)
         at com.netflix.logging.aggregator.Bucketer.<init>(Bucketer.java:80)
         at com.netflix.logging.aggregator.TracerAggregator.<init>(TracerAggregator.java:29)
         at com.netflix.logging.aggregator.TracerAggregator.<clinit>(TracerAggregator.java:20)
         at com.netflix.logging.NFLogger.start(NFLogger.java:105)
         at com.netflix.logging.LogManager.registerLogger(LogManager.java:67)
         at com.netflix.logging.test.LoggingTest.sendDefault(LoggingTest.java:32)
         at com.netflix.logging.test.LoggingTest.main(LoggingTest.java:19)
    Caused by: weblogic.jms.common.JMSException: Invalid password key to unlock the passwords in the configuration file
         at weblogic.jms.safclient.admin.ConfigurationUtils.doRemoteContexts(ConfigurationUtils.java:475)
         at weblogic.jms.safclient.agent.AgentManager.<init>(AgentManager.java:54)
         at weblogic.jms.safclient.ClientSAFDelegate.open(ClientSAFDelegate.java:65)
         at weblogic.jms.safclient.ClientSAFImpl.open(ClientSAFImpl.java:62)
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:160)
         ... 30 more
    Caused by: javax.crypto.BadPaddingException: Given final block not properly padded
         at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
         at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
         at com.sun.crypto.provider.SunJCE_af.b(DashoA12275)
         at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(DashoA12275)
         at javax.crypto.Cipher.doFinal(DashoA12275)
         at weblogic.jms.common.SecHelper.decryptString(SecHelper.java:140)
         at weblogic.jms.safclient.admin.ConfigurationUtils.doRemoteContexts(ConfigurationUtils.java:473)
         ... 34 more
    java.lang.IllegalStateException: Cannot create context: Invalid password key to unlock the passwords in the configuration file
         at com.netflix.messaging.ESBFactory.<init>(ESBFactory.java:106)
         at com.netflix.messaging.ESBFactory.getFactory(ESBFactory.java:45)
         at com.netflix.messaging.NFMessagingManager.getProducerHandle(NFMessagingManager.java:218)
         at com.netflix.messaging.NFMessagingManager.initProducers(NFMessagingManager.java:730)
         at com.netflix.messaging.NFMessagingManager.init(NFMessagingManager.java:863)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1461)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1628)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.startMessagingManager(MessageDestinationDispatcher.java:164)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.<init>(MessageDestinationDispatcher.java:25)
         at com.netflix.logging.NFMessageAppender.append(NFMessageAppender.java:72)
         at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
         at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
         at org.apache.log4j.Category.callAppenders(Category.java:206)
         at org.apache.log4j.Category.forcedLog(Category.java:391)
         at org.apache.log4j.Category.log(Category.java:838)
         at com.netflix.logging.log4jAdapter.Log4jLoggingAdapter.log(Log4jLoggingAdapter.java:64)
         at com.netflix.logging.NFLogger.log(NFLogger.java:125)
         at com.netflix.logging.LogManager.info(LogManager.java:152)
         at com.netflix.logging.aggregator.Bucketer.init(Bucketer.java:92)
         at com.netflix.logging.aggregator.Bucketer.<init>(Bucketer.java:80)
         at com.netflix.logging.aggregator.TracerAggregator.<init>(TracerAggregator.java:29)
         at com.netflix.logging.aggregator.TracerAggregator.<clinit>(TracerAggregator.java:20)
         at com.netflix.logging.NFLogger.start(NFLogger.java:105)
         at com.netflix.logging.LogManager.registerLogger(LogManager.java:67)
         at com.netflix.logging.test.LoggingTest.sendDefault(LoggingTest.java:32)

    Hi,
    I seem to be struggling with a problem that I'm not sure if I can ever find a solution.
    I have a configured a local JMS client to forward my messages to a remote WLSB 9.2.
    The local client is running JDK 1_0_14 on a windows platform.
    The remote server is on IBM JRE on linux. Now I'm getting problems when the messages are forwarded by the local SAF client. The client does not seem to be able to decrypt the password I have in my SAFClient.xml. I have pretty much followed every line in the documentation of SAF client and has already revisited it a few times.
    It seems to be something to do with the ClientSAFEncrypt utility that I was advised to get the encrypted password which I have put in the XML File. Here is the exception. Any help will be greatly appreciated.
    All I know is it is something to do with encoding of the password, but I cannot get a clue what else.
    <Mar 25, 2008 12:28:40 PM PDT> <Info> <Store> <BEA-280050> <Persistent store "SAFSTORE0V" opened: directory="C:\depot\javaSrc\logging\stores\default" writePolicy="Direct-Write" blockSize=512 directIO=false driver="NIO">
    javax.naming.NamingException: Invalid password key to unlock the passwords in the configuration file [Root exception is weblogic.jms.common.JMSException: Invalid password key to unlock the passwords in the configuration file]
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getNamingException(InitialContextFactoryImpl.java:31)
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:162)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at com.netflix.messaging.ESBFactory.<init>(ESBFactory.java:103)
         at com.netflix.messaging.ESBFactory.getFactory(ESBFactory.java:45)
         at com.netflix.messaging.NFMessagingManager.getProducerHandle(NFMessagingManager.java:218)
         at com.netflix.messaging.NFMessagingManager.initProducers(NFMessagingManager.java:730)
         at com.netflix.messaging.NFMessagingManager.init(NFMessagingManager.java:863)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1461)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1628)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.startMessagingManager(MessageDestinationDispatcher.java:164)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.<init>(MessageDestinationDispatcher.java:25)
         at com.netflix.logging.NFMessageAppender.append(NFMessageAppender.java:72)
         at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
         at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
         at org.apache.log4j.Category.callAppenders(Category.java:206)
         at org.apache.log4j.Category.forcedLog(Category.java:391)
         at org.apache.log4j.Category.log(Category.java:838)
         at com.netflix.logging.log4jAdapter.Log4jLoggingAdapter.log(Log4jLoggingAdapter.java:64)
         at com.netflix.logging.NFLogger.log(NFLogger.java:125)
         at com.netflix.logging.LogManager.info(LogManager.java:152)
         at com.netflix.logging.aggregator.Bucketer.init(Bucketer.java:92)
         at com.netflix.logging.aggregator.Bucketer.<init>(Bucketer.java:80)
         at com.netflix.logging.aggregator.TracerAggregator.<init>(TracerAggregator.java:29)
         at com.netflix.logging.aggregator.TracerAggregator.<clinit>(TracerAggregator.java:20)
         at com.netflix.logging.NFLogger.start(NFLogger.java:105)
         at com.netflix.logging.LogManager.registerLogger(LogManager.java:67)
         at com.netflix.logging.test.LoggingTest.sendDefault(LoggingTest.java:32)
         at com.netflix.logging.test.LoggingTest.main(LoggingTest.java:19)
    Caused by: weblogic.jms.common.JMSException: Invalid password key to unlock the passwords in the configuration file
         at weblogic.jms.safclient.admin.ConfigurationUtils.doRemoteContexts(ConfigurationUtils.java:475)
         at weblogic.jms.safclient.agent.AgentManager.<init>(AgentManager.java:54)
         at weblogic.jms.safclient.ClientSAFDelegate.open(ClientSAFDelegate.java:65)
         at weblogic.jms.safclient.ClientSAFImpl.open(ClientSAFImpl.java:62)
         at weblogic.jms.safclient.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:160)
         ... 30 more
    Caused by: javax.crypto.BadPaddingException: Given final block not properly padded
         at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
         at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
         at com.sun.crypto.provider.SunJCE_af.b(DashoA12275)
         at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(DashoA12275)
         at javax.crypto.Cipher.doFinal(DashoA12275)
         at weblogic.jms.common.SecHelper.decryptString(SecHelper.java:140)
         at weblogic.jms.safclient.admin.ConfigurationUtils.doRemoteContexts(ConfigurationUtils.java:473)
         ... 34 more
    java.lang.IllegalStateException: Cannot create context: Invalid password key to unlock the passwords in the configuration file
         at com.netflix.messaging.ESBFactory.<init>(ESBFactory.java:106)
         at com.netflix.messaging.ESBFactory.getFactory(ESBFactory.java:45)
         at com.netflix.messaging.NFMessagingManager.getProducerHandle(NFMessagingManager.java:218)
         at com.netflix.messaging.NFMessagingManager.initProducers(NFMessagingManager.java:730)
         at com.netflix.messaging.NFMessagingManager.init(NFMessagingManager.java:863)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1461)
         at com.netflix.messaging.NFMessagingManager.start(NFMessagingManager.java:1628)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.startMessagingManager(MessageDestinationDispatcher.java:164)
         at com.netflix.logging.messaging.MessageDestinationDispatcher.<init>(MessageDestinationDispatcher.java:25)
         at com.netflix.logging.NFMessageAppender.append(NFMessageAppender.java:72)
         at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
         at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
         at org.apache.log4j.Category.callAppenders(Category.java:206)
         at org.apache.log4j.Category.forcedLog(Category.java:391)
         at org.apache.log4j.Category.log(Category.java:838)
         at com.netflix.logging.log4jAdapter.Log4jLoggingAdapter.log(Log4jLoggingAdapter.java:64)
         at com.netflix.logging.NFLogger.log(NFLogger.java:125)
         at com.netflix.logging.LogManager.info(LogManager.java:152)
         at com.netflix.logging.aggregator.Bucketer.init(Bucketer.java:92)
         at com.netflix.logging.aggregator.Bucketer.<init>(Bucketer.java:80)
         at com.netflix.logging.aggregator.TracerAggregator.<init>(TracerAggregator.java:29)
         at com.netflix.logging.aggregator.TracerAggregator.<clinit>(TracerAggregator.java:20)
         at com.netflix.logging.NFLogger.start(NFLogger.java:105)
         at com.netflix.logging.LogManager.registerLogger(LogManager.java:67)
         at com.netflix.logging.test.LoggingTest.sendDefault(LoggingTest.java:32)

  • I cannot forward messages from my Juno e-mail account.

    Firefox prevent messages in Juno e-mail from being forwarded. The background screen simply becomes darker with each failed attempt.

    Perform the suggestions mentioned in the following articles:
    * [https://support.mozilla.com/en-US/kb/Template:clearCookiesCache Clear Cookies & Cache]
    * [[How to clear the cache#w_clear-the-cache|Clear the Network Cache]]
    Start Firefox in -> [[Safe Mode]] to check if your add-ons/extension are causing the problem.
    * Also see this article -> [[Troubleshooting extensions and themes]]
    Check and tell if its working.

  • Cannot forward emails with pictures- it says missing plug ins

    I cannot forward messages with pictures. It says "missing plug-ins" I tried saving the pictures but when I put them as attachments it says the same.

    Are you sure your download of the images are complete?  Are these IMAP e-mails (iCloud uses iMac), POP e-mails, or Exchange?    Are you using Mac OS X Mail, or some other application for mail?

  • Cannot forward email message. Contact list does not appear to select. Can reply to sender only

    When trying to forward an email message, the contact list does not appear. It can
    only be forwarded by entering addresses manually. I can return an email by replying
    but I cannot forward under the Mozilla Fox server.
    When I am in Internet Explorer I can utilize the email forward without a problem.
    Contacted AT & T to see if it was their problem, since I use att.net.
    The technician stated it was a problem with Mozilla because it was not compatible
    with the AT & T net work. It could possibly be in recent updates, since I just
    discovered the problem within the last week.
    Would prefer to enter my email through Mozilla Fox. So can you solve this problem
    for me.

    Hello,
    Many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache.
    Note: ''This will temporarily log you out of all sites you're logged in to.''
    To clear cache and cookies do the following:
    #Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
    #Under "Time range to clear", select "Everything".
    #Now, click the arrow next to Details to toggle the Details list active.
    #From the details list, check ''Cache'' and ''Cookies'' and uncheck everything else.
    #Now click the ''Clear now'' button.
    Further information can be found in the [[Clear your cache, history and other personal information in Firefox]] article.
    Did this fix your problems? Please report back to us!
    Thank you.

  • I am trying to send SMS text via iPad Air and cannot. I have gone into my iPhone and "forward message to iPad". However I am prompted to enter "code shown on iPad"... What code and where do I find that on iPad??

    I am trying to send SMS text via iPad Air and cannot. I have gone into my iPhone and "forward message to iPad". However I am prompted to enter "code shown on iPad"... What code and where do I find that on iPad??

    The home screen is the screen that shows all of your app icons. You can have one home screen or up to 11 home screens depending on how many apps you have. The home screen on an iPad is the equivalent of the desktop screen on a computer. If you are using an app, just tap the home button once to return to a home screen.
    This is is a (my) home screen.
    You you might want to double check the instructions here.
    Connect your iPhone, iPad, iPod touch, and Mac using Continuity - Apple Support
    Make make sure that you are signed into your iCloud account in Settings>iCloud and make sure that you have selected your Apple ID email address as well in Settings>Messages>Send & Receive at>You can be reached by iMessages at.

  • TS3276 I have AOL on my Mac pro.I can receive Mail but cannot forward/send if I hit send the message goes to my outbox hit send it goes to

    have AOL on my Mac pro.I can receive Mail but cannot forward/send if I hit send, the message goes to my outbox

    Sorry Mate, I tried your suggestion ,but no joy.I now have 3 messages in my outbox,that will not send.
                                            Thank you for trying to help.
                                                                                   Ken.

  • Io7: cannot forward pictures sent through messaging.

    I recently updated to the ios7, but I cannot forward a picture that was sent to me to another person via message.  The picture doesn't send.  I have to save the pic to my camera roll, open up the conversation or create a new message for the person I wish to send it to, and then add/attach the photo like that. Anyone else getting this glitch?

    So I see what you mean by the arrow pointed up--so does that mean that I don't have the ability to share the picture?  Seems silly since I can just copy it or save it to my camera roll and then send it out to whomever I want...
    I don't understand JazzyTech LOL

  • Cannot forward a response that is already committed  exeption after Log out

    Hello,
    I am using Jdeveloper 11.1.1.3.0, ADF DC, ADF Faces, ADF security.
    I have a logout button in my template, and I want the user to go back to login page (login.html; which was generated automaticlly when you use ADF security) after successful Log out.
    here is my logout method
        public String doLogOut() throws IOException {
            // Add event code here...
            ExternalContext ectx =
                FacesContext.getCurrentInstance().getExternalContext();
            HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
            HttpSession session = (HttpSession)ectx.getSession(false);
            session.invalidate();
            response.sendRedirect("login.html");
            return null;      
        }when I click the log out button, every thing seems ok, and the user redirected to login.html page. However, I see the following Exception in Jdeveloper Log window.
    <Jan 4, 2012 12:16:31 PM EET> <Error> <HTTP> <BEA-101020> <[ServletContext@19059163[app:CTP-New module:CTP-New-ViewController-context-root path:/CTP-New-ViewController-context-root spec-version:2.5 version:V2.0]] Servlet failed with Exception
    java.lang.IllegalStateException: Cannot forward a response that is already committed
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         Truncated. see log file for complete stacktrace
    >
    <Jan 4, 2012 12:16:31 PM EET> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'DefaultServer' has triggered at Jan 4, 2012 12:16:31 PM EET. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    WatchData: DATE = Jan 4, 2012 12:16:31 PM EET SERVER = DefaultServer MESSAGE = [ServletContext@19059163[app:CTP-New module:CTP-New-ViewController-context-root path:/CTP-New-ViewController-context-root spec-version:2.5 version:V2.0]] Servlet failed with Exception
    java.lang.IllegalStateException: Cannot forward a response that is already committed
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)
         at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:473)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:141)
         at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
         at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:710)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:273)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:205)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101020 MACHINE = Mjabr-PC TXID =  CONTEXTID = 4b079561b4c220a0:10458ad0:134a7995c3f:-8000-0000000000000241 TIMESTAMP = 1325672191307 
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 30000
    >Further more when I try to login again, I get this message in the browser
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.Any help is highly appreciated.

    Thank you ADF7,
    I used this method
        public String doLogOut() throws IOException {
            // Add event code here...
            FacesContext ctx = FacesContext.getCurrentInstance();
            HttpServletRequest request =
                (HttpServletRequest)ctx.getExternalContext().getRequest();
            ExternalContext ectx =
                FacesContext.getCurrentInstance().getExternalContext();
            try {
                ectx.redirect(request.getContextPath() +
                              "/login.html");
            } catch (Exception exp) {
                exp.printStackTrace();
            return null;
        }but when I re login again I get the same error in the browser
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

  • NLS:4: Cannot open message catalog TMADMIN_CAT,  Solaris Container

    Hello,
    Can someone please help me ?
    I have used Tuxedo 8 for many years on Solaris 8 servers, however we have now ported our installation to a Solaris 8 container on a Solaris 10 server. The server was ported using a flar image from the source server onto the new zone (or container). Tuxedo works absolutely fine in the container and the application appears to run as expected until I try using tmadmin or qmadmin on the command line and run a command in the shell and the following message appears for tmadmin, qmadmin message is similar.
    NLS:4: Cannot open message catalog TMADMIN_CAT, set 1, num 111; check TUXDIR=/opt/apps/tuxedo/8.0, LANG=C
    tmadmin/qmadmin performs the function but appears to be unable to open it's message catalog in $TUXDIR/locale/C
    The mesasage catalog exists in $TUXDIR/locale/C and chksum's identical to source server.
    I have manually re-installed the Tuxedo software in the container with no effect
    I have tried installing Tuxedo in a different directory
    I have tried setting NLSPATH=$TUXDIR/locale/C in the environent with no effect
    The tuxedo application works fine with no similar messages in the ULOG from the running application, it is just tmadmin and qmadmin on the command line, using the same user as runs the application
    localel settings are identical to original source server and :
    localeLANG=
    LC_CTYPE="C"
    LC_NUMERIC="C"
    LC_TIME="C"
    LC_COLLATE="C"
    LC_MONETARY="C"
    LC_MESSAGES="C"
    LC_ALL=
    If i set $LANG = C and run tmadmin and run a command I get the following message instead
    NLS:6: Message not found, catalog TMADMIN_CAT, set 1, num 1136
    Which implies it can see the catalog but cannot open it
    Tuxedo version is 8.0 Rolling patch 222
    Can anyone help? i would be very grateful
    Thanks
    Adam

    I have now worked arround this by re-generating the message catalogs from the catalog text files
    cd $TUXDIR/locale/C
    gencat TMADMIN_CAT TMADMIN.text
    gencat Q_CAT Q.text
    tmadmin and qmadmin now display the output ok, It kind of makes sense since the catalogs are generated in the new environment, but a full install still did not work.
    The new catalogs are identical to the old catalogs and cksum identically, but they work. Still scratching my head over this one, but at least we can move forward now.

  • Cannot find message resources under key org.apache.struts.action.MESSAGE ?

    Hi All,
    I am getting the following error.. while running a simple application in struts.
    Cannot find message resources under key org.apache.struts.action.MESSAGE ?
    As I have searched in google but could not find the concreate example so please help and give me a proper answer..
    my struts-config.xml file is as .....
    <code>
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <!DOCTYPE struts-config PUBLIC
    "-//Apache Software Foundation//DTD Struts Configuration 1.0//EN"
    "http://jakarta.apache.org/struts/dtds/struts-config_1_0.dtd">
    <struts-config>
    <!-- ========== Form Bean Definitions ============ -->
    <form-beans>
         <form-bean name="login" type="test.struts.LoginForm" />
    </form-beans>
    <!-- ========== Global Forward Definitions ========= -->
    <global-forwards>
    </global-forwards>
    <!-- ========== Action Mapping Definitions ======== -->
    <action-mappings>
    <action
         path="/login"
         type="test.struts.LoginAction"
         name="login"
         input="/jsp/LoginView.jsp"
         validate="true">
         <forward name="valid" path="/jsp/MainMenu.jsp" />
         <forward name="invalid" path="/jsp/LoginView.jsp" />
         </action>
    </action-mappings>
    <message-resources null="false" parameter="test.struts.MessageResources"/>
    </struts-config>
    </code>
    And my LoginView.jsp file is as:
    <code>
    <!-- LoginView.jsp -->
    <%@ taglib uri="/struts/WEB-INF/struts-html.tld" prefix="html" %>
    <%@ taglib uri="/struts/WEB-INF/struts-bean.tld" prefix="bean" %>
    <%@ taglib uri="/struts/WEB-INF/struts-logic.tld" prefix="struts" %>
    <HTML>
    <HEAD><TITLE><bean:message key="title.login" /></TITLE></HEAD>
    <BODY>
    <bean:message key="heading.login" />
    <html:errors />
    <html:form action="/login">
         <p>
         <bean:message key="label.userId" />:
         <html:text property="userId" size="10" />
         <br>
         <bean:message key="label.passWord" />:
         <html:password property="passWord" size="10" />
         <br><br>
         <html:submit>
              <bean:message key="button.submit" />
         </html:submit>
    </html:form>
    </BODY>
    </HTML>
    </code>
    MessageResources.properties is as :
    <code>
    button.submit=Send for Verification
    error.no.userId=<li>User ID is a required field</li>
    error.no.passWord=<li>Password is a required field</li>
    error.invalid.login=<li>The User ID and/or Password are invalid. Please try again.</li>
    errors.footer=</ul><hr>
    errors.header=<h3><font color="red">Validation Error</font></h3>You must correct the following error(s) before proceeding:<ul>
    label.userId=User ID
    label.passWord=Password
    heading.login=<H2>Enter your user information</H2>
    title.login=Login Screen
    title.mainmenu=Welcome
    heading.mainmenu=<H1>Welcome!</H1>
    label.userType=<H2>You are authorized to use this system as a</H2>
    </code>
    Please reply soon.
    Thanks in advance
    Amitindia

    Hi All,
    I am getting the following error.. while running a simple application in struts.
    Cannot find message resources under key org.apache.struts.action.MESSAGE ?
    As I have searched in google but could not find the concreate example so please help and give me a proper answer.. my struts-config.xml file is as .....
    <?xml version="1.0" encoding="ISO-8859-1" ?> <!DOCTYPE struts- 
      config PUBLIC "-//Apache Software Foundation//DTD Struts
    Configuration 1.0//EN" "http://jakarta.apache.org/struts/dtds/struts-
    config_1_0.dtd"> <struts-config> <!-- ========== Form Bean
    Definitions ============ --> <form-beans> <form-bean name="login"
    type="test.struts.LoginForm" /> </form-beans> <!-- ========== Global Forward Definitions ========= --> <global-forwards> </global-
    forwards> <!-- ========== Action Mapping Definitions ======== --> <action-mappings> <action path="/login" type="test.struts.LoginAction" name="login" input="/jsp/LoginView.jsp" validate="true"> <forward name="valid" path="/jsp/MainMenu.jsp" /> <forward name="invalid" path="/jsp/LoginView.jsp" /> </action> </action-mappings> <message-resources null="false" parameter="test.struts.MessageResources"/> </struts-config>
    And my LoginView.jsp file is as:
    <!-- LoginView.jsp --> <%@ taglib uri="/struts/WEB-INF/struts-html.tld" prefix="html" %> <%@ taglib uri="/struts/WEB-INF/struts-bean.tld" prefix="bean" %> <%@ taglib uri="/struts/WEB-INF/struts-logic.tld" prefix="struts" %> <HTML> <HEAD><TITLE><bean:message key="title.login" /></TITLE></HEAD> <BODY> <bean:message key="heading.login" /> <html:errors /> <html:form action="/login">
    <bean:message key="label.userId" />: <html:text property="userId" size="10" /> <br> <bean:message key="label.passWord" />: <html:password property="passWord" size="10" /> <br><br> <html:submit> <bean:message key="button.submit" /> </html:submit> </html:form> </BODY> </HTML>
    MessageResources.properties is as :
    button.submit=Send for Verification error.no.userId=<li>User ID is a required field</li> error.no.passWord=<li>Password is a required field</li> error.invalid.login=<li>The User ID and/or Password are invalid. Please try again.</li> errors.footer=</ul><hr> errors.header=<h3><font color="red">Validation Error</font></h3>You must correct the following error(s) before proceeding:<ul> label.userId=User ID label.passWord=Password heading.login=<H2>Enter your user information</H2> title.login=Login Screen title.mainmenu=Welcome heading.mainmenu=<H1>Welcome!</H1> label.userType=<H2>You are authorized to use this system as a</H2>
    Please reply soon. Thanks in advance Amitindia                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • [ME21] error message : cannot find message associated with key

    Dear all,
    I try to develop an Mobile application using smartSync,
    but when the application running (on client) got an error message :
    Error: 500
    Location: /UPLOAD_TEST/upload_testapp/Menu.do
    Internal Servlet Error:
    javax.servlet.ServletException: cannot find message associated with key : dispatcher.forwardException
    at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDispatcherImpl.java:238)
    at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:162)
    at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:423)
    at 0002findex0002ejspindex_jsp_0._jspService(_0002findex_0002ejspindex_jsp_0.java:62)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java)
    note:
    when create this application, I'm using tcode : merep_sbuilder
    Sync type : U01 - Upload using SMAPIs
    Bapi wrapper : MEREP_CONTACT_CREATE
    SAP Mobile Engine 2.1
    and generate .war file using MDK tool
    any one know about this ??
    thanks & regards,

    Hi,
    this error comes up when the destination serlvet throws an exception other than ServletException!
    Its a standard tomcat bug!
    Rgds Thomas
    -->
    http://issues.apache.org/bugzilla/show_bug.cgi?id=19114
    -->From apache.org:
    When a forwarded servlet throws an exception other than ServletException or
    IOException, the thrown exception is lost. This is due to the line:
    throw new ServletException(sm.getString("dispatcher.forwardException", t));
    (found in org/apache/tomcat/facade/RequestDispatcherImpl.java:210)
    the earlier catched t is here not passed into the constructor of
    ServletException but into getString.
    To reproduce construct a servlet that throws an Exception (other than
    ServletException and IOException) and another servlet that forwards to it. You
    will get just a forwardException (if you have the proper locale strings
    installed!) but the originally thrown exception will get lost forever.

  • SyncBo Example - cannot find message associated with key

    Hi,
    I followed the tuturial to create a SmartSync Project.
    And when I run the project I've got a Servlet Exception:
    javax.servlet.ServletException: cannot find message appropriated with key: dispatcher.forwardException.
    What I need to change?
    Thanks a lot,
    Rachid

    Hi,
    this error comes up when the destination serlvet throws an exception other than ServletException!
    Its a standard tomcat bug!
    Rgds Thomas
    -->
    http://issues.apache.org/bugzilla/show_bug.cgi?id=19114
    -->From apache.org:
    When a forwarded servlet throws an exception other than ServletException or
    IOException, the thrown exception is lost. This is due to the line:
    throw new ServletException(sm.getString("dispatcher.forwardException", t));
    (found in org/apache/tomcat/facade/RequestDispatcherImpl.java:210)
    the earlier catched t is here not passed into the constructor of
    ServletException but into getString.
    To reproduce construct a servlet that throws an Exception (other than
    ServletException and IOException) and another servlet that forwards to it. You
    will get just a forwardException (if you have the proper locale strings
    installed!) but the originally thrown exception will get lost forever.

  • Help trouble with forwarded message

    Hello,
    I realized that many people have this issues as I had recently, but I still need some help about this.
    I found that original sender was actually receiving my forwarded message to other people.  I had an important correspondence to make with my Attorney since February, I forwarded several messages from my opponent to my attorney.  We have been resolving issues very well, but one day, the opponents suddenly changed their attitude and giving me a hard time.  I was checking my older correspondence with the person who was actually mediating the situation and found out that my conversation with my attorney was leaked to the opponents because I hit "forward" to including the original message from the sender(opponent).  The mediator actually saw what I was talking with my attorney.  it was bad enough, the mediator was not telling me she was recovering my e-mail to my attorney.  Now I have a trust issue to my mediator.  It is not professional that mediator leaked my conversation with my attorney to the opponents, but Apple mail set up caused this situation.  Am I wrong?  I want to know if I could avoid this by myself, if it was my problem, I want Apple to teach me how to use e-mail setting correctly ASAP.  In my understanding, it should be my choice if I including the original sender or not when I forward the message to others, correct? 
    Why Apple automatically include the original sender when I forward my comments to others???
    is anyone know to fix this problem?  We act civil to each other and the mediator was taking her position fairly, but once they knew my attorney has more to say to opponents, the mediator revealed her position toward executives in the company (opponent)  My legal issue to justify my position should not be jeopardized by something like this that I cannot control.  Bad thing is I didn't know the opponent are reading my conversation to my attorney until now.  I didn't say anything wrong on the e-mail to my attorney to offend the opponent, but the opponent has been over reacting to the issue with me.  Original issue was mediated by the mediator, but now I need my attorney longer to resolve the issue.  Because of the forwarding message setting with Apple, I had extra problem.  I recently send a message to the mediator and asked if she received any e-mail that should be going only to my attorney, she has no answer.  I don't like any e-mail setting I cannot fix causes this trouble in the future.  I will never forward the message to my attorney and ask a question again, but I want Apple to make better setting to avoid this kind of situation. 

    seems like you tried to invoke the method parseXml of the class com.bt.ma.utils.xmlPolicyReader but used a wrong (illegal & incompatible) parameter attribute...

Maybe you are looking for