Error in WebLogic Logs

Hi all,
We have been seeing lot of error in the Web Logic Logs and we aren't able to figure out what exactly causing these errors..
I set the java Heap Size to 512 and also the file descriptor value to 4096. Even after this we are still getting these errors.
We are on PT 8.49 and HRMS 9.0 installed on LINUX machine with web logic 9.2
####<Jul 14, 2009 9:23:21 AM EDT> <Info> <ServletContext-> <xXXXXX> <PIA> <Thread-10> <<anonymous>> <> <> <1247577801110> <000000>
<26628797235202:
59 items transmitted at1247577801017 time:93> ####<Jul 14, 2009 9:23:22 AM EDT> <Error> <WebLogicServer> <xXXXXXX> <PIA> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1247577802724> <BEA-000337> <[STUCK]
ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'
has
been busy for "642" seconds working on the request "Http Request:
/psp/HRQA90/EMPLOYEE/HRMS/c/PERFORMANCE_MONITOR.PSPMAPPDOM.GBL", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
Stack
trace:
Thread-165 "[STUCK] ExecuteThread: '7' for queue:
'weblogic.kernel.Default
(self-tuning)'" <alive, in native, suspended, blocked, priority=1,
DAEMON>
-- Blocked trying to get lock: java.lang.String@1343da8[fat lock]
psft.pt8.psc.onActionDirect(psc.java:1187)
psft.pt8.portal.PIADirectConnection.connect(Unknown Source)
psft.pt8.portal.ContentGetter.getPIADirectContent(Unknown Source)
psft.pt8.portal.ContentGetter.getPIADirectContent(Unknown Source)
psft.pt8.portal.ContentGetter.getPIADirectContent(Unknown Source)
psft.pt8.portal.ContentGetter.getContent(Unknown Source)
psft.pt8.portal.ContentGetter.getContent(Unknown Source)
psft.pt8.portal.ContentGetter.getContent(Unknown Source)
psft.pt8.psp.getTemplateDoc(Unknown Source)
psft.pt8.psp.onAction(Unknown Source)
psft.pt8.psp.service(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet.java:851)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
psft.pt8.psfilter.doFilter(psfilter.java:45)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:684)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:117)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1946)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1868)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1331)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:206)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
And also we are using DEV Web Profile in our Production Environment, does it make any difference?
And what is the DIfference between DEV and PROD Web Profiles??
Thanks,
CKD

I don't know why you get this error, but you could read some docs about this parameter :
http://e-docs.bea.com/wls/docs91/wlsmbeanref/core/index.html
Maybe due to some specific install and env, do you have Performance monitoring ?
What's the consequence for the frontend user ?
Is it also in dev environment ? Did you try to apply latest patch of WL9.2 ?
If you have no clue, then you may want to open a SR to the support.
Lastly, for DEV and PROD webprofile, that should not make any difference for your error, please see the link below for a short description :
http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tprt/book.htm?File=tprt/htm/tprt18.htm#d0e31171
Nicolas.

Similar Messages

  • Error in weblogic.log using weblogic 6.1

    I have this error in my weblogic.log file. I do not know the reason for the
    error. What is the error about?
    ####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
    <myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
    <system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
    mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
    ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
    escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
    Method: null>
    javax.management.AttributeNotFoundException: EJBName.MethodName
    at
    weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
    Impl.java:1643)
    at
    weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
    java:502)
    at
    weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
    java:477)
    at
    com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
    3)
    at
    com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
    3)
    at
    weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
    at $Proxy77.getAttribute(Unknown Source)
    at
    weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
    at
    weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
    r.java:83)
    at java.util.Arrays.mergeSort(Arrays.java:1176)
    at java.util.Arrays.sort(Arrays.java:1123)
    at java.util.Collections.sort(Collections.java:116)
    at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
    at
    weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
    Tag.java:96)
    at
    weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
    4606)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
    l.java:482)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
    l.java:308)
    at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
    at
    weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:242)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at
    weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
    :35)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:171)
    at
    weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
    et.java:91)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2546)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2260)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Ronak Parekh

    It looks like an error/bug in the deployment descriptor editor in the
    console.
    -- Rob
    Ronak Parekh wrote:
    I have this error in my weblogic.log file. I do not know the reason for the
    error. What is the error about?
    ####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
    <myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
    <system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
    mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
    ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
    escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
    Method: null>
    javax.management.AttributeNotFoundException: EJBName.MethodName
    at
    weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
    Impl.java:1643)
    at
    weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
    java:502)
    at
    weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
    java:477)
    at
    com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
    3)
    at
    com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
    3)
    at
    weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
    at $Proxy77.getAttribute(Unknown Source)
    at
    weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
    at
    weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
    r.java:83)
    at java.util.Arrays.mergeSort(Arrays.java:1176)
    at java.util.Arrays.sort(Arrays.java:1123)
    at java.util.Collections.sort(Collections.java:116)
    at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
    at
    weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
    Tag.java:96)
    at
    weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
    4606)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
    l.java:482)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
    l.java:308)
    at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
    at
    weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:242)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at
    weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
    :35)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:171)
    at
    weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
    et.java:91)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2546)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2260)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Ronak Parekh

  • Socket Read Timeout error in weblogic logs happening every 30 min

    One of my customer is getting Socket Read Time out error, when creating connection pool.
    java.sql.SQLException: Socket read timed out
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:203)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:489)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:439)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:640)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:205)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:554)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:327)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:227)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
         at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2451)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: oracle.net.ns.NetException: Socket read timed out
         at oracle.net.ns.Packet.receive(Packet.java:333)
         at oracle.net.ns.DataPacket.receive(DataPacket.java:94)
         at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:176)
         at oracle.net.ns.NetInputStream.read(NetInputStream.java:121)
         at oracle.net.ns.NetInputStream.read(NetInputStream.java:96)
         at oracle.net.ns.Packet.extractData(Packet.java:443)
         at oracle.net.ns.AcceptPacket.<init>(AcceptPacket.java:108)
         at oracle.net.ns.NSProtocol.setNetStreams(NSProtocol.java:697)
         at oracle.net.ns.NSProtocol.connect(NSProtocol.java:386)
         at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1088)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:305)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:642)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:205)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:554)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:227)
         at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2451)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Any suggestions?

    Could be a firewall rule terminating an idle connection?

  • Weblogic.log error levels

    I am trying to find some more information on the different error levels that are logged to weblogic.log. Does anyone know if the levels are described anywhere?

    Or see weblogic.logging.Severities @
    http://e-docs/wls/docs60/javadocs/index.html
    Brad Stone <[email protected]> wrote in message
    news:[email protected]...
    WebLogic uses the following severities, in order of criticality:
    Emergency The server is in an unusable state. This should only be used to
    designate severe system failures or panics.
    Alert A particular service is in an unusable state. Other parts of the
    system continue to function. Automatic recovery is not possible and the
    immediate attention of the administrator is required to resolve theproblem.
    >
    Critical A system/service level error has occurred. The system is ableto
    recover, perhaps with a momentary loss or permanent degradation ofservice.
    >
    Notice A particularly important warning or informational message.
    Messages, such as notification of successful recovery from a failure,which
    is of particular importance to an administrator monitoring the server.
    Error A user level error has occurred. The system is able to handle the
    error with no interruption and limited degradation in service. Make this
    severity less 'severe' than NOTICE.
    Warning A warning message. A suspicious operation or configuration which
    doesn't affect the normal operation of the server.
    Informational An informational message. Used for the logging of normal
    operations for later examination.
    Debug A debug message. Should be output only when the server isconfigured
    in a debug mode. May contain detailed information about operations or the
    state of the server.
    "Beth" <[email protected]> wrote in message
    news:[email protected]...
    I never found anything in the documentation. But if you are using
    LogOutputStream, there is the following:
    - emergency
    - alert
    - critical
    - error
    - notice
    - warning
    - info
    - debug
    All take parameters of either just a String or a String and Throwable.
    I don't know of a way to tell Weblogic just to log certain levels andignore
    others so when you are done debugging you don't log any of the debug
    messages to the log file.
    This can be found by doing a
    javap weblogic.logging.LogOutputStream
    Hope this is what you are looking for.
    "Jennifer Edwards" <[email protected]> wrote in message
    news:[email protected]...
    I am trying to find some more information on the different error
    levels
    that are logged to weblogic.log. Does anyone know if the levels are
    described anywhere?

  • Dont have "javax.servlet.jsp.JspException errors" in my logs (WebLogic 9.2)

    Hi,
              I have 2 servers.
              One with WebLogic6.1 & one with WebLogic9.2
              With WL6.1, i have errors like :
              <i>
              <2 août 2006 13:00:20 IRST> <Error> <HTTP> <[WebAppServletContext(10414345,imargo,/imargo)] Root cause of ServletException
              javax.servlet.jsp.JspException: Missing message for key MG01.loc.index
              at org.apache.struts.taglib.bean.MessageTag.doStartTag(MessageTag.java:297)
              at jsp_servlet._jsp.__im_in_tec_MGN01_MGN001._jspService(__im_in_tec_MGN01_MGN001.java:1711)
              </i>
              With WL9.2, i don't have those errors in my logs...
              I have no errors o_o
              Help me plz
              Many thanks

    I never used DynaActionForm, what I have noticed here is, don't you need to declare the form bean? I may be wrong.
    <form-beans>
    <form-bean name="newProdForm" type="com.package.form.NewProdForm"></form-bean>
    </form-beans>

  • How to write  to weblogic.log from JSP ?

    It is possible to write some messages to weblogic.log from JSP?
              

    Use weblogic.logging.LogOutputStream class to log messages into
              weblogic.log file.
              javap on weblogic.logging.LogOutputStream
              for e.g
              <%@ page import="weblogic.logging.*" %>
              <%
              LogOutputStream los = new LogOutputStream("TEST");
              los.error("Writing into Log file");
              %>
              Hope this helps.
              --kumar allamraju
              Mikhail Ershov wrote:
              > It is possible to write some messages to weblogic.log from JSP?
              

  • How to use weblogic.logging classes in 6.0

    Hi,
    We developed a number of logging classes under 5.1. One used
    weblogic.logging.LogOutputStream to write messages out to the log. This
    code no longer works under WLS 6.0. Everything compiles and runs but I
    don't see any of our messages in any of the log files. Judging from the 6.0
    JavaDoc, it looks like LogOutputStream is no longer supported. So I
    switched over to using NonCatalogLogger. Same results - no output in the
    logs.
    What am I missing?
    Thanks.
    -brian

    My coding error. weblogic.logging.* classes work just fine in 6.0 (he said
    sheepishly)!
    -b
    "Brian J. Levine" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    We developed a number of logging classes under 5.1. One used
    weblogic.logging.LogOutputStream to write messages out to the log. This
    code no longer works under WLS 6.0. Everything compiles and runs but I
    don't see any of our messages in any of the log files. Judging from the6.0
    JavaDoc, it looks like LogOutputStream is no longer supported. So I
    switched over to using NonCatalogLogger. Same results - no output in the
    logs.
    What am I missing?
    Thanks.
    -brian

  • Patch error in Weblogic server9.1 & 9.2

    :Ohi,
    i am using weblogic 9.1 and 9.2 on windows xp.
    when i click smart update to get patches i am getting an error:
    "an unknown error occured upgrading the patch client ",
    when i have a BEA support id and password , i am unable to see error in log file of BEA home directory.
    can u plz give me the solution as i need to apply public patches .
    thanks in advance,
    sweta

    Upgrade to sp3.
    "Sreekanth" <[email protected]> wrote:
    >
    I am getting the following error in weblogic server. I am unable to understand
    the situation when this occurs. can anybody help. Sometimes i get the
    mentioned
    class as "weblogic.rmi.internal.MethodDescriptor"/ "weblogic.rjvm.ClassTableEntry"
    <Aug 7, 2003 2:48:31 AM IST> <Error> <ConnectionManager> <
    java.rmi.UnmarshalException: Incoming message header or abbreviation
    processing
    failed ; nested exception is:
    java.lang.ClassCastException: weblogic.rjvm.ClassTableEntry
    Start server side stack trace:
    java.rmi.UnmarshalException: Incoming message header or abbreviation
    processing
    failed ; nested exception is:
    java.lang.ClassCastException: weblogic.rjvm.ClassTableEntry
    java.lang.ClassCastException: weblogic.rjvm.ClassTableEntry
    at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:182)
    at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ; nested exception is:
    java.lang.ClassCastException: weblogic.rjvm.ClassTableEntry

  • FrontEndHost Error with Weblogic Integration Domain

    We have created a WLI Domain with an Admin server and two managed servers in a cluster. We have deployed lot of applications on this. We had a release of these applications which was workin on Production mode. The release name was R500. After that when we did R600, it did not work on Prodcution but worked on Development mode with the following error.
    java.lang.RuntimeException: frontEndHost is not configured for the cluster and hostname is not set in wlw-config or wlw-runtime-config
            at com.bea.wlw.runtime.core.util.Util.getCallbackHttpUrl(Util.java:845)
            at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.getCallbackURL(ServiceHandleImpl.java:379)
            at com.bea.wlw.runtime.jws.dispatcher.JwsDispClass.<init>(JwsDispClass.java:170)
            at com.bea.wli.bpm.runtime.JpdDispClass.<init>(JpdDispClass.java:41)
            at com.bea.wli.bpm.runtime.JpdDispFile.createPrimaryDispClass(JpdDispFile.java:367)
            at com.bea.wlw.runtime.core.dispatcher.DispFile.<init>(DispFile.java:154)
            at com.bea.wlw.runtime.jws.dispatcher.JwsDispFile.<init>(JwsDispFile.java:44)
            at com.bea.wli.bpm.runtime.JpdDispFile.<init>(JpdDispFile.java:103)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
            at com.bea.wlw.runtime.core.dispatcher.DispUnit.loadDispFile(DispUnit.java:219)
            at com.bea.wlw.runtime.core.dispatcher.DispUnit.<init>(DispUnit.java:153)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:578)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:967)
            at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:889)
            at com.bea.wli.broker.JWSSubscriber.getDispClass(JWSSubscriber.java:229)
            at com.bea.wli.broker.JWSSubscriber.getRequest(JWSSubscriber.java:188)
            at com.bea.wli.broker.JWSSubscriber.doDispatch(JWSSubscriber.java:356)
            at com.bea.wli.broker.JWSSubscriber.doDispatch(JWSSubscriber.java:346)
            at com.bea.wli.broker.SubscriptionDispatcher.doDispatch(SubscriptionDispatcher.java:87)
            at com.bea.wli.broker.MessageBroker$PrivilegedSubscriptionDispatcher.run(MessageBroker.java:167)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at com.bea.wli.security.authentication.AuthenticationService.runAs(AuthenticationService.java:109)
            at com.bea.wli.broker.MsgBrokerSecurityHelper.doDispatch(MsgBrokerSecurityHelper.java:232)
            at com.bea.wli.broker.MessageBroker$PrivilegedSubscriptionDispatcher.doDispatch(MessageBroker.java:153)
            at com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:966)
            at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.java:334)
            at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:466)
            at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
            at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)After this when we did R700 release, both the managed servers are continuously failing and the above error has been logged very frequently on both managed1 and managed 2 logs.
    Can anyone help me resolve this error or anyone who has faced this problem earlier, please reply.
    As per this error, we do not have wlw-runtime-config.xml file anywhere so we are unable to determine whether the problem is with host name of the proxy server in wlw-runtime-config.xml file.
    Brijesh Shah

    Your server is started in RUNNING mode :
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[8
    ]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[9
    ]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp,
    http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <Server> <BEA-002613> <Channel "Default[3
    ]" is now listening on fe80:0:0:0:0:5efe:a22:516c:7001 for protocols iiop, t3, l
    dap, snmp, http.>
    <Dec 27, 2012 3:21:01 PM EST> <Notice> <WebLogicServer> <BEA-000331> <Started We
    bLogic Admin Server "AdminServer" for domain "base_domain" running in Developmen
    t Mode>
    <Dec 27, 2012 3:21:11 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to RUNNING>
    <Dec 27, 2012 3:21:11 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
    rted in RUNNING mode>
    Why are you saying that you are unable to start it? Make sure you are hitting http://<IP>:7001/console to view the Admin console.

  • Error installin Weblogic Server 7.0 in silent mode

    Hi, I'm trying to install Weblogic Server 7.0 using to silent.xml file. All my
    configuration looks fine and work well on Windows NT 4.0. But when I try to install
    it on Windows 2000 or Windows XP I get the following error in my log file:
    2002-09-05 10:23:24,722 INFO [dwsilent] com.bea.wizard.domain.tasks.silent.DWSilentTask
    - fullSilentTemplateFileName = c:\silent.xml
    2002-09-05 10:23:24,782 INFO [dwsilent] com.bea.wizard.domain.DWParseXML - Parsing
    template.xml/String subs is OK !
    2002-09-05 10:23:24,782 INFO [dwsilent] com.bea.wizard.domain.DWParseXML - Parsing
    template.xml is OK !
    2002-09-05 10:23:24,782 FATAL [dwsilent] com.bea.wizard.domain.tasks.silent.DWSilentTask
    Domain Wizard Installation Failed: The system cannot find the path specified
    2002-09-05 10:23:24,782 INFO [BEAInstallController] com.bea.installer.BEAInstallController
    - Terminating.
    I thought it's was the long filename for the TEMP directory that is located under
    "C:\Documents and Settings..." but I got the same error after modifying environment
    variable TEMP and TMP to c:\TEMP.
    Someone has a clue ?
    Thank You
    Jean-Sebastien Frerot
    Software Integrator
    Meloche Monnex Inc.
    [erreur.txt]

    Hi..
    They changed a few things in 10.3.. see http://edocs.bea.com/common/docs103/install/silent.html#wp1044118
    looks like the Server sub category has changed to Core Application Server..
    If you checkout the log.txt file in the logs directory of the root where you've installed a copy using the gui, it generally lists all the installation options available.
    ..Mark.

  • Unwanted stack trace in weblogic.log for thrown JSP Exceptions

    We are throwing a JSP exception within a custom tag when data validation
              errors occur; the errorPage for the JSP page is then invoked to show the
              appropriate errors. However, in the weblogic.log, a stack trace is shown
              indicating the exception (example below). We do not want this stack track
              shown unless there is a real "error" in our system vs. invoking the
              errorPage to show "application" errors. Is there any way to supress this,
              as we are not explicitly causing this to happen. It appears to be a
              weblogic feature. This causes us problems in finding true system errors
              that might be occurring due to these non-problems showing up in the
              weblogic.log.
              Thanks for the help.
              John Bauer
              Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception raised
              on '/test/test.jsp'
              javax.servlet.ServletException: runtime failure in custom tag 'testtag'
              at jsp_servlet._test._test._jspService(_test.java:89)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :124)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:
              60)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:
              07)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager
              java:251)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              

    The design of the data entry pages is such that the error page is the same
              page as the data entry page, and a validation JSP tag validates the data and
              if it finds a problem, it will set some variables and throw a JSP exception
              to redisplay the page. Unfortunately, we are forced to live with this
              design. Are you aware of any mechanism to suppress the automatic logging of
              thrown JSP exceptions in the weblogic log?
              Thanks,
              JDB
              Cameron Purdy <[email protected]> wrote in message
              news:[email protected]...
              > Exception handling for custom tags is very poorly handled right now. For
              > one thing, WL hides the actual exception.
              >
              > However, the way that you are doing this seems very odd. The error page
              is
              > for server errors, not user typos.
              >
              > Peace,
              >
              > --
              > Cameron Purdy
              > Tangosol, Inc.
              > http://www.tangosol.com
              > +1.617.623.5782
              > WebLogic Consulting Available
              >
              >
              > "John Bauer" <[email protected]> wrote in message
              > news:[email protected]...
              > > We are throwing a JSP exception within a custom tag when data validation
              > > errors occur; the errorPage for the JSP page is then invoked to show the
              > > appropriate errors. However, in the weblogic.log, a stack trace is
              shown
              > > indicating the exception (example below). We do not want this stack
              track
              > > shown unless there is a real "error" in our system vs. invoking the
              > > errorPage to show "application" errors. Is there any way to supress
              this,
              > > as we are not explicitly causing this to happen. It appears to be a
              > > weblogic feature. This causes us problems in finding true system errors
              > > that might be occurring due to these non-problems showing up in the
              > > weblogic.log.
              > >
              > > Thanks for the help.
              > > John Bauer
              > >
              > > Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception
              raised
              > > on '/test/test.jsp'
              > > javax.servlet.ServletException: runtime failure in custom tag 'testtag'
              > > at jsp_servlet._test._test._jspService(_test.java:89)
              > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > > :124)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > > l.java:
              > > 60)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > > l.java:
              > > 07)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              > > Manager
              > > java:251)
              > > at
              > >
              >
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              > > at
              > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
              Compiled
              > > Code)
              > >
              > >
              >
              >
              

  • Weblogic.log formatting

    I have 2 weblogic servers running.
    one on my W2K laptop and an AS400
    When a nosuchmethod error is logged on my W2K webserver
    I get the method name.
    When the same error is generated on my AS400 webserver it does not.
    Is there a way to get it to show up in the AS400 weblogic.log
    thanks in advance
    Mickey

    "Beth" <[email protected]> wrote:
    Hi,
    I'm trying to find out some more info on the weblogic.log:
    1) I see that there is a weblogic.system.maxLogFileSize property
    in the weblogic.properties file which will rotate the log based on size.
    Are we limited to size only? Is there any way to rotate the log file
    based on a new day?This is available for access log...(for HTTP)
    not sure for weblogic.log
    >
    2) Is there any way to specify exactly how many rotations you want?
    For example if I only want to keep the last three weblogic.log files-
    if there are already three on the system, overwrite the oldest one.
    3) I am looking for more information on LogOutputStream, but haven't
    been able to locate the doc on the web site. Any idea where I might find
    it?
    4) I assume by using LogOutputStream and log() that the server is taking
    care of synchronizing multiple calls to the log file?I dont think logging is synchronised.
    for me it makes sense.
    >
    5) During development I will be using calls such as log.debug() but when
    I'm
    ready for production I don't want those log messages in the log file. Is
    there
    any kind of switch to tell the logging mechanism to ignore certains types of
    log
    messages? Or does one have to do something specific to the code to ignore
    those messages when the time comes?check out weblogic.system.discardOutAndErr=true
    but i am not sure this will help..
    >
    Thanks in advance,
    Beth

  • Socket error in weblogic 7 when switching app to ssl

    I am supporting an app that is running on weblogic 7.0.2.0. Because of security requirements I have been asked to enable SSL access and turn off the non-SSL listen port. I can enable the SSL port without issue but when I attempt to close the non-ssl port (so that users can only access via SSL) I get the following error in the log on startup.
    ####<Dec 7, 2009 12:34:21 AM GMT> <Error> <socket> <ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000405> <Uncaught Throwable in p
    rocessSockets
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Old socket closed and released FD before FDRecord still exists, resulting in two sockets for same FD, old socket:weblogic.socket.SSLFilter@25143a
    , new socket:weblogic.ldap.MuxableSocketLDAP@6c9f34 ]>
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Old socket closed and released FD before FDRecord still exists, resulting in two sockets for same FD, old socket:weblogic.socket.SSLFilter@25143a,
    new socket:weblogic.ldap.MuxableSocketLDAP@6c9f34 ]
    Start server side stack trace:
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Old socket closed and released FD before FDRecord still exists, resulting in two sockets for same FD, old socket:weblogic.socket.SSLFilter@25143a,
    new socket:weblogic.ldap.MuxableSocketLDAP@6c9f34 ]
    at weblogic.socket.PosixSocketMuxer.read(PosixSocketMuxer.java:567)
    at weblogic.ldap.MuxableSocketLDAP.dispatch(MuxableSocketLDAP.java:148)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:279)
    at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:277)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:279)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:770)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:694)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    End server side stack trace
    <<no stack trace available>>
    Initially I didn't see this problem in validation, but now that I have restarted the admin server and managed servers in validation I see the same error in both environments.
    Does anyone have an idea of what might cause this error?
    Thanks,
    -Mike
    Edited by: user3862080 on Dec 8, 2009 9:07 AM

    We faced with the similar issue in WLS 7.X after below Assertion error after restoring services we were able to resolve this issue for time being as per the weblogic there is a patch provided by BEA and this sort of issue is resolved.
    This issue has been identified and updated under cars CR103525
    Regards,
    CSR
    BEA Analyst

  • Receiving "Error truncating change log: null" after redeploying application

    Hi,
    I am running Weblogic 8.1 SP5 on Windows 2003. We are running into a problem where we redeploy an EAR on the server and it's causing an error "Error truncating change log: null" in the admin server. Here are the basic steps:
    1) We have an application from a third-party that is deployed to the managed nodes in a cluster.
    2) We Stop the application.
    3) We redeploy the application. The application redeploys ok.
    4) We stop the application for a 2nd time.
    5) We redeploy the application. This time, the server reports that it's in progress forever. This is when we start to see the errors in the log.
    6) To get the server back, we need to shut down the managed and admin servers.
    7) We have to kill the java.exe process on each node.
    8) We have to delete the ldap directory on the admin node.
    9) Once we restart the server, we are back again.
    So, after receiving hundreds (maybe a few thousand), we get the error:
    java.io.IOException: More than 2048 open files
    If anyone has any idea what's happening, it would be greatly appreciated.
    Thanks,
    Eric
    Here is the full stack trace:
    ####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <Error truncating change log: null>
    ####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.io.IOException: More than 2048 open files>
    ####<Sep 2, 2011 12:44:15 PM EDT> <Critical> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.io.IOException: More than 2048 open files
         at java.io.RandomAccessFile.open(Ljava.lang.String;I)V(Native Method)
         at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
         at java.io.RandomAccessFile.<init>(RandomAccessFile.java:94)
         at com.octetstring.vde.replication.BackendChangeLog.open(BackendChangeLog.java:192)
         at com.octetstring.vde.replication.BackendChangeLog.truncate(BackendChangeLog.java:183)
         at com.octetstring.vde.replication.BackendChangeLog.receiveEntryChanges(BackendChangeLog.java:540)
         at com.octetstring.vde.backend.BackendHandler.modify(BackendHandler.java:717)
         at com.octetstring.vde.operation.ModifyOperation.perform(ModifyOperation.java:144)
         at com.octetstring.vde.MessageHandler.doModify(MessageHandler.java:280)
         at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:73)
         at com.octetstring.vde.WorkThread.executeWorkQueueItem(WorkThread.java:83)
         at weblogic.ldap.LDAPExecuteRequest.execute(LDAPExecuteRequest.java:28)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    >
    ####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.lang.NullPointerException: null>

    Chris
    Could you please tell us what version of DVD SP your are using?
    If its 3.x or earlier, then A.Pack should be used.
    If it's 4.x, then you will need to use compressor's, Dolby 2.0 audio encoding, because A.Pack will have been removed by the DVD SP 4's installer.
    There are also adjustments you will need to make to the basic settings of the Dolby 2.0 settings that come with compressor or A.Pack, to get the best output.
    Here's a how to: http://www.kenstone.net/fcphomepage/a_packwarmouth.html

  • Logging to weblogic.log

     

    hi
    i need couple of clarifications with regard to implementation of logging with
    weblogic.
    a) Is logging implemented using JMS? ( Is logging asynchronous?)
    b) I am wondering if i can use logging api into some helper classes that wouldn't
    be run in weblogic server. If weblogic server is a pre-requisite, then i will
    not be able to use this logging api in these classes.
    Thanks
    Rob Woollen <[email protected]> wrote:
    From server-side code (ie servlets or EJB). do
    LogServiceDef log = T3Services.getT3Services().log();
    to get the log, and then you can use log.inform(), log.debug, or
    log.error as appropriate.
    See
    http://www.weblogic.com/docs45/classdocs/weblogic.common.LogServicesDef.html
    -- Rob
    Rob Woollen
    Software Engineer
    BEA WebLogic
    [email protected]
    Vinny Carpenter wrote:
    Hi there. I have a cluster of WebLogic 4.5.1 servers running under
    Solaris 2.6. My application consists of two EJB's and a couple of
    servlets as front end. As part of the application logging process,I
    output certain text using System.out.println and System.err.printlnthat
    are typically displayed on the console.
    How can I redirect those messages to the machine's weblogic.log file??
    Is there a logging mechanism that will allow me to do that?? thanks
    --Vinny

Maybe you are looking for