Error in javamail with weblogic 6.0

Hi,I am facing the following error while installing Javamail in weblogic 6.0.javax.activation.UnsupportedDataTypeException: no object DCH for MIME type text/plain; charset=us-ascii at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:851)Any help,regards,Biswajit

Hi,
Please check with the file SAPINST.exe in Windows Program files or System 32. It is the Log file and after that restart the server then you can install fresh.
And also check with JAVA_HOME environment Variable is now set to
"C:\j2sdk1.4.2_09" ( as your drive ) after that restart the server.
This should solve your problem please try it and Let me know.
Thomas
Edited by: thomas_raja on Jul 25, 2011 8:53 AM

Similar Messages

  • Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

    Hello everybody,
              I get the error given below when calling a JSP in a WebLogic
              application which seems to work fine in all other (non-JSP) parts:
              java.lang.NullPointerException:
                   at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
                   at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
                   at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
                   at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
                   at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
                   at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
                   at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
                   at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              I know that this error has been reported more than once in these
              discussion groups, and all people who solved it say
              - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
              1.2.2
              - that it may also be caused by bad jsp code
              But in my case, it has to be another reason, because
              - I am using jdk 1.2.2
              - the same JSP file is running withour errors on WebLogic 6
              I wonder if it could have something to do with the operating system:
              the parsing error is produced on a Windows version of WL 5.1, while my
              WL 6 which doesn't cause errors is running with Linux.
              Many thanks in advance for any help,
              Eckhard Beisswenger
              

    Once again me!
              After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
              http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
              The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.
              

  • Error while deploying application with WebLogic server

    Hi,
    I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
    "There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
    Plz help me.
    Thx

    I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
    Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
    Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
    Cheers!

  • Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

    Hi Sudhir,
    If you do not know if upgrade or not, have a look here :
    http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
    Note that at the end of June SP3 will be released...
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    >
    Hi Sergi,
    Thanks a lot for the class file, I figured out what the problem was. Actually
    the
    database version I was working with was 8.0.6.0. The Oracle driver doesn't
    work with
    this but the JDriver worked. This is the output of running CheckDriver..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
    Production
    With the Partitioning and Objects options
    PL/SQL Release 8.0.6.0.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.1.0
    Then I tried on using the Oracle Driver on another instance which has the
    version
    8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
    database.
    The output of CheckDriver for this Oracle instance is..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
    Production
    With the Partitioning option
    JServer Release 8.1.7.1.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.0.0
    By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
    I upgrade
    Thanks once again,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir ,
    JDriver works well, you can work with it.
    Just for curiosity, can you run the class I attached using the "exact"classpath
    of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
    is the
    output ?
    On which platform are you running your WLSP2 ?
    Thanks
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    I just checked the things you mentioned. The connection pool starts correctly
    without
    any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
    I do have the JAVA_XA package installed and it has EXECUTE permission
    to
    PUBLIC.
    I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
    and
    it works perfect without any issue. The only consideration is that itis
    a Type 2
    Driver and needs to have the Oracle Client installed. But right now Ido
    have it
    installed on the same machine.
    Do you know any known issues with Weblogic JDriver. Do you think it'sa
    good idea
    to go with it ?
    Thanks,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    does your connection pool start correctly ?
    Check the setup of your Oracle server too:
    1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
    2) package JAVA_XA installed (with grant execute to PUBLIC)
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
    and put
    it in classpath in front of weblogic.jar. I still get the same problem.
    Is there
    another location where we can download the Oracle driver with the bug
    fixed
    Regards, Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    I think you are using Oracle JDBC drivers 8.1.6.
    They have a bug, they do not accept a foreign XID.
    Use 8.1.7 or higher to solve this problem.
    Sergi
    Sudhir Babu <[email protected]> wrote:
    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver.
    These
    are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I amnot
    sure where the problem is as I have configured Connection Pool and
    TXDataSource
    as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured in the transaction branch start() failed on resource 'myXAPool'
    Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

  • Error in configuring apache plug in with weblogic 8.1.5

    I tried to configure Apache 2.2 plugin with weblogic 8.1 SP 5 in Linux ES 4.0 . I am getting the following error while loading weblogic_module in httpd.conf file in Apache server (restarting apache server after putting entries in httpd.conf).. The error is httpd: Syntax error on line 414 of /usr/local/apache2/conf/httpd.conf: API module structure `weblogic_module' in file /usr/local/apache2/modules/mod_wl_20.so is garbled - perhaps this is not an Apache module DSO?
    Did anyone got this error before?

    The solution is for BEA to provide the plug-in. Probably a few minutes of a work for BEA developer. Weblogic 9.0 has it.
    Edited by muralive at 09/17/2007 10:08 PM

  • Hyperion Shared Services Configuration Error with Weblogic 9.2

    Hi All,
    I have been trying to configure Hyperion Shared Services 9.3.1 with Weblogic Ver 9.2
    During configuration of the Database and the Application Server, I select Manual Configuration option on Weblogic 9
    However, it returns a configuration failure everytime of the Database.
    In my case, the DB used is SQL 2005.
    Can someone, please advise me.
    Thanks in advance
    Regards,
    Apo

    Hi Apo,
    Check the configtool.log in the logs/config folder and post the error message that is being returned.
    Thanks
    Nick

  • Stylesheet error with weblogic application server 9.1

    Hi ALL,
    I deployed my application on weblogic AS 9.1.
    i have created my own domain using sun JDK 1.5.
    i am able to log in into my application & able to do all the tasks.
    but when i click on a specific tab weblogic AS 9.1 waits for some time & give this error on its console :-
    <b>ERROR: 'Variable 'can-modify' is multiply defined in the same scope.'
    FATAL ERROR: 'Could not compile stylesheet'</b>
    i am not find any more details in the weblogic server error log.
    the same application works fine with weblogic 8.1 sp4 + jdk 1.4 & tomcat 5.0.27 + jdk 1.5( without any error)
    so i think the problem is not because of jdk, it something to do with weblogic!
    does anybody has info about this.
    it will be great help.
    regards
    Rahul

    I found that error is coming from this line.
    <b><xsl:variable name="can-modify" select="/dashboard/@can-save|/dashboard/@can-saveas" /></b>
    can somebody suggest why this happening, same code works is weblogic 8.1 & give error in 9.1.
    -Rahul

  • Weblogic.appc (weblogic 9.1) giving error while using with jdk 1.6

    hi,
    I am trying to build my ear using jdk1.6 with weblogic 9.1.
    I am getting this error while doing weblogic.appc using my ant scripts. Could some one pls let me know the solution for this problem.
    [java] Created working directory: c:\windows\TEMP\appcgen_gdoasis.jar
    [java] <02-Aug-2007 14:54:22 o'clock BST> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile yo
    ur application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
    [java] javax.xml.stream.FactoryConfigurationError: Provider javax.xml.stream.XMLInputFactory could not be
    instantiated: java.lang.InstantiationException
    [java] at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:158)
    [java] at weblogic.ejb.container.dd.xml.DDUtils.<clinit>(DDUtils.java:85)
    [java] at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1345)
    [java] at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:431)
    [java] at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:292)
    [java] at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:95)
    [java] at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:113)
    [java] at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
    [java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:55)
    [java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    [java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:24)
    [java] at weblogic.application.compiler.Appc.runBody(Appc.java:151)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [java] at weblogic.application.compiler.Appc.main(Appc.java:162)
    [java] at weblogic.appc.main(appc.java:14)
    [java] Provider javax.xml.stream.XMLInputFactory could not be instantiated: java.lang.InstantiationExcept
    ion
    Thanks

    hi,
    I am trying to build my ear using jdk1.6 with weblogic 9.1.
    I am getting this error while doing weblogic.appc using my ant scripts. Could some one pls let me know the solution for this problem.
    [java] Created working directory: c:\windows\TEMP\appcgen_gdoasis.jar
    [java] <02-Aug-2007 14:54:22 o'clock BST> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile yo
    ur application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
    [java] javax.xml.stream.FactoryConfigurationError: Provider javax.xml.stream.XMLInputFactory could not be
    instantiated: java.lang.InstantiationException
    [java] at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:158)
    [java] at weblogic.ejb.container.dd.xml.DDUtils.<clinit>(DDUtils.java:85)
    [java] at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1345)
    [java] at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:431)
    [java] at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:292)
    [java] at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:95)
    [java] at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:113)
    [java] at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
    [java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:55)
    [java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    [java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:24)
    [java] at weblogic.application.compiler.Appc.runBody(Appc.java:151)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [java] at weblogic.application.compiler.Appc.main(Appc.java:162)
    [java] at weblogic.appc.main(appc.java:14)
    [java] Provider javax.xml.stream.XMLInputFactory could not be instantiated: java.lang.InstantiationExcept
    ion
    Thanks

  • Pre_compiling jsp's with weblogic.jspc error

    Hi all,
    Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
    The jsp's do compile under OC4J's jsp compiler.
    Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
    I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
    This is on Windows XP SP4 box.
    So far I've tried:
    adding the -classpath option
    adding the -d option to specify a directory
    adding the -backwardcompatible option
    adding the -librarydir option
    here's my command line format:
    java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
    -backwardcompatible -d WEB-INF addNote.jsp
    heres a sample of output:
    jspc failed with errors :weblogic.servlet.jp.CompilationException:
    addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
    <template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
    addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
    <html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
    I couldn't add the jsp snippets becuase this input form is complaining about the tags.
    Any help would be greatly appreciated.

    Hi all,
    Im using weblogic 11g weblogic.jspc to try to pre-compile JSP's that were created with struts 1.2.x under OC4J 9.0.x.
    The jsp's do compile under OC4J's jsp compiler.
    Im getting many errors that seem to be related to the version difference between struts1.2.x used with OC4J and the struts bundled with weblogic.
    I'm trying to "force" the weblogic.jspc to use the older version of struts but have not been successful.
    This is on Windows XP SP4 box.
    So far I've tried:
    adding the -classpath option
    adding the -d option to specify a directory
    adding the -backwardcompatible option
    adding the -librarydir option
    here's my command line format:
    java weblogic.jspc -classpath .;c:\...\struts.jar;WEB-INF\struts-bean.tld;c:\...\struts-validator.jar;c:\...\struts-nested.jar;c:\...\strutstest2.0.0.jar...
    -backwardcompatible -d WEB-INF addNote.jsp
    heres a sample of output:
    jspc failed with errors :weblogic.servlet.jp.CompilationException:
    addNote.jsp:11:57 The method setContent(String) in the type PutTag is not applicable for the arguments (Object)
    <template:put name="title" direct="true" content="<%=request.getAttribute(Constants.TITLE)%>"/>
    addNote.jsp:15:31: Th method setAction(String) in the type FormTag is not applicable for the arguments (Object)
    <html:form action="<%=request.getAttribute(Constants.ACTION)%>" focus="notBean.subject">
    I couldn't add the jsp snippets becuase this input form is complaining about the tags.
    Any help would be greatly appreciated.

  • Error invoking WebService in Eclipse with WebLogic 12c plugin

    I am using Eclipse Indigo with WebLogic 12c plugin to create a standalone WebService Client which invokes a simple WebService. The WebService is protected by Security Policies Wssp1.2-2007-Wss1.0-X509-Basic256.xml and Wssp1.2-SignBody.xml.
    I get the following exception when I run the standalone client:
    h2. Exception in thread "main" java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider could not be instantiated: java.lang.ExceptionInInitializerError
    The same program works fine using JDeveloper 11g but not in Eclipse Indigo or in Juno. Has anyone faced this issue?
    Thanks,
    Madhav

    The stand-alone client JAR file does not, however, support invoking Web services that use the following advanced features:
    Web services reliable SOAP messaging
    Message-level security (WS-Security)
    http://docs.oracle.com/cd/E14571_01/web.1111/e13760/client.htm#i229632
    Can you try running by adding weblogic.jar. but if you run the client inside the wls Server it should work.
    Regards,
    Sunil P

  • Integration of ALBPM 5.7 with WebLogic 9.2 ::: Error

    Hi All,
    We are trying to configure ALBPM5.7 Enterprise Edition(with Weblogic) and WebLogic 9.2 Server. We have followed one particular document which states the use of Oracle as a Server.i.e ALBPM_5-7_WebLogic_9-2_Installation.pdf
    But we are using MS-SQL Server. We are also using Merlia.jar as a JDBC Driver.
    Now the issue is, we reach @ the end of the document by installing the jar file named "fuegoj2ee-lib-all.jar" through WebConsole. But we are getting stuck while installing the EAR file through Webconsole. Actually this file is neccessary to start the ALBPM 5.7 Engine to run.
    We get "Direcory Service could not be reached" on DOMAIN console.
    We are need and seeking a solution for the same.
    Thanks
    Shail

    Hi.
    We have tested the configuration of the engine. Its says "Directory Service has been found". So there is no issue of the directory service being null as such.
    This is the domain log ------->
    weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Too many connections :3
         at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:241)
         at weblogic.jdbc.jts.Driver.newConnection(Driver.java:918)
         at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:340)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:181)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:82)
         at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:59)
         at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:129)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:280)
         at fuego.connector.JDBCHelper.getConnection(JDBCHelper.java:43)
         at fuego.directory.provider.jdbc.j2ee.RemoteJDBCConnectionProvider.getEntry(RemoteJDBCConnectionProvider.java:60)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:552)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:120)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:163)
         at fuego.directory.provider.Factory.startSession(Factory.java:488)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:167)
         at fuego.directory.Directory.startSession(Directory.java:674)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:335)
         at fuego.ejbengine.Engine.start(Engine.java:120)
         at fuego.ejbengine.servlet.SchedulerServlet.init(SchedulerServlet.java:107)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:278)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1715)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1692)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1612)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    We have large of active connections available on the MS SQL Server.
    Awaiting Reply.
    Thanks
    Shail.

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Error while running in weblogic

    I get an error when i use weblogic to run a simple hello servlet
    deployment of my.war is successful
    import java.io.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    public class HelloServlet extends HttpServlet {
        public void service(HttpServletRequest request,
                          HttpServletResponse response)
            throws IOException, ServletException
              response.setContentType("text/html");
              PrintWriter out = response.getWriter();
             out.println("<html>");
             out.println("<head>");
             out.println("Hello Servlet");
             out.println("</body>");
             out.println("</html>");
    web.xml is
    <web-app>
    <servlet>
    <servlet-name>my</servlet-name>
    <servlet-class>HelloServlet</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>my</servlet-name>
    <url-pattern>run</url-pattern>
    </servlet-mapping>
    </web-app>error on testing the application in weblogic console:(i m using domain poojasdomain)
    <Oct 5, 2006 10:15:40 PM IST> <Warning> <HTTP> <BEA-101248> <[Application: 'C:\b
    ea\user_projects\domains\poojasdomain\myserver\upload', Module: 'my']: Deploymen
    t descriptor "web.xml" is malformed. Check against the DTD: org.xml.sax.SAXParse
    Exception: cvc-elt.1: Cannot find the declaration of element 'web-app'. (line 1,
    column 10).>
    i think web.xml is correctly written,what can be the problem?

    finally the error is :....
    <Oct 6, 2006 7:15:29 PM IST> <Error> <HTTP> <BEA-101018> <[ServletContext(id=407
    8341,name=my,context-path=/my)] Servlet failed with ServletException
    javax.servlet.ServletException: [HTTP:101249][ServletContext(id=4078341,name=my,
    context-path=/my)]: Servlet class HelloServlet for servlet my could not be loade
    d because the requested class was not found in the classpath C:\bea\user_project
    s\domains\poojasdomain\myserver\.wlnotdelete\extract\myserver_my_my\my.war;C:\be
    a\user_projects\domains\poojasdomain\.\myserver\.wlnotdelete\extract\myserver_my
    my\jarfiles\wl_cls_gen.jar;C:\bea\user_projects\domains\poojasdomain\.\myserve
    r\.wlnotdelete\extract\myserver_my_my.
    java.lang.UnsupportedClassVersionError: HelloServlet (Unsupported major.minor ve
    rsion 49.0).

  • EJB 3.0 MDB deployment issue with weblogic 10.0

    Hi there,
    I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
    After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
    weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
    Unable to deploy EJB: MessageBean from Message.jar:
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
         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)
         Truncated. see log file for complete stacktrace
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
         at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
         Truncated. see log file for complete stacktrace
    >
    Any help really appreciated. It's too urgent.
    Thanks in advance,
    Piyush

    here is the code for my bean.
    package com.ups;
    import java.util.logging.Logger;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.EJBException;
    import javax.ejb.MessageDriven;
    import javax.ejb.MessageDrivenContext;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    * Message-Driven Bean implementation class for: MessageBean
    @MessageDriven(
              activationConfig = { @ActivationConfigProperty(
                        propertyName = "destinationType", propertyValue = "javax.jms.Queue"
    public class MessageBean implements MessageListener {
         private MessageDrivenContext mdc;
    * Default constructor.
    public MessageBean() {
    // TODO Auto-generated constructor stub
    * @see MessageListener#onMessage(Message)
    public void onMessage(Message message) {
         TextMessage tmsg = null;
    try {
    tmsg = (TextMessage) message;
    System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
    System.out.println ("The onMessage() is called");
    } catch (JMSException e) {
    e.printStackTrace( );
    mdc.setRollbackOnly( );
    catch (Throwable th) {
    th.printStackTrace();
    public void ejbRemove( )throws EJBException{
         System.out.println("ejbRemove() is executed >>>>>>>");
    I have configured my JMS Distributed queue in the Weblogic.
    If possible please provide more details so that I can get rid of this error as soon as possible.
    Thanks for reply.
    Piyush

  • Security violation exception with Weblogic cluster installation on OIm 9.1

    Hi,
    I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
    m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
    DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
    e, signature={}.
    at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
    riptor.java:486)
    at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
    :80)
    at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
    tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
    ... 126 more
    ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
    Interface encounter some problems: {1}
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.in
    Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
    Any suggestions would be useful...

    No Response???
    Where are the good guys??

Maybe you are looking for