Jspc-error in WLS 6.1, SP 5

          We encountered the following error in jspc after installing SP 5 for Weblogic Server
          6.1 over SP 4.
          The following line was given in the jsp-page (the page was developed with the
          Struts-Bean-Taglib):
          <bean:define id="titel" name="lltreeForm" property="name" />
          With SP 4, the following Java-Code was generated by jspc:
          /*** sync AT_BEGIN TagExtra Vars here ***/ //[ /jsp/ll/main.jsp; Line: 116]
          /*** declare & sync AT_END TagExtra Vars here ***/ //[ /jsp/ll/main.jsp;
          Line: 116]
          java.lang.Object titel = null; //[ /jsp/ll/main.jsp; Line:
          116]
          titel = (java.lang.Object)pageContext.findAttribute("titel");
          //[ /jsp/ll/main.jsp; Line: 116]
          out.print("\r\n ");
          And with SP5, the following Code was generated, without the declaration of the
          variable titel:
          /*** sync AT_BEGIN TagExtra Vars here ***/ //[ /jsp/ll/main.jsp; Line: 116]
          out.print("\r\n ");
          Does anybody know a solution for this problem?
          

This is probably caused by the fix CR094190. Try using a begin and end tag
          until it's fixed by bea...
          <bean:define id="titel" name="lltreeForm" property="name" ></bean:define>
          MattM
          "Frank Eichfelder" <[email protected]> wrote in message
          news:[email protected]...
          >
          > We encountered the following error in jspc after installing SP 5 for
          Weblogic Server
          > 6.1 over SP 4.
          > The following line was given in the jsp-page (the page was developed with
          the
          > Struts-Bean-Taglib):
          >
          > <bean:define id="titel" name="lltreeForm" property="name" />
          >
          > With SP 4, the following Java-Code was generated by jspc:
          >
          > /*** sync AT_BEGIN TagExtra Vars here ***/ //[ /jsp/ll/main.jsp; Line:
          116]
          > /*** declare & sync AT_END TagExtra Vars here ***/
          //[ /jsp/ll/main.jsp;
          > Line: 116]
          > java.lang.Object titel = null; //[ /jsp/ll/main.jsp;
          Line:
          > 116]
          > titel =
          (java.lang.Object)pageContext.findAttribute("titel");
          > //[ /jsp/ll/main.jsp; Line: 116]
          > out.print("\r\n ");
          >
          > And with SP5, the following Code was generated, without the declaration of
          the
          > variable titel:
          >
          > /*** sync AT_BEGIN TagExtra Vars here ***/ //[ /jsp/ll/main.jsp; Line:
          116]
          > out.print("\r\n ");
          >
          > Does anybody know a solution for this problem?
          

Similar Messages

  • Unable to find information on WS data binding error on WLS 9.2.03 startup

    Frustratingly, when I Google for "WS data binding error" I get 'old' links to BEA forum issues which may help but these are nowhere to be seen on the read-only copies now on Oracle forums here :- http://forums.oracle.com/forums/category.jspa?categoryID=202.
    The link I'm looking for is:-
    forums.bea.com/thread.jspa?threadID=600017135
    Is there anywhere I can get access to this information or should I just post new items on the new WLS forum?
    Many thanks.
    p.s. the errors I am trying to research are as follows:-
    <WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
    <WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.

    Check this..
    http://docs.oracle.com/cd/E10291_01/doc.1013/e10538/weblogic.htm
    you can ignore those warnings
    The following data type binding warnings and errors are displayed during deployment and start of Decision Service (Business Rules) Applications. These errors and warnings can be ignored.
    <WS data binding error>could not find schema type '{http://www.w3.org/2001/XMLSchema}NCName
    <WS data binding error>could not find schema type
    '{http://websphere.ibm.com/webservices/}SOAPElement
    java.lang.IllegalStateException
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.
    getSchemaProperty(AnonymousTypeFinder.java:253)

  • Error in WLS 7.0

    I have in my WLS 7.0 cluster enviroment error like this:
              java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext Start server side stack trace: java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext at weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:359) at weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(ReplicatedSessionData.java:180) at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34) at weblogic.cluster.replication.ReplicationManager$wroManager.create(ReplicationManager.java:339) at weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.java:1059) at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:346) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:300) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:295) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133) End server side stack trace
              

    Have you defined a defaultwebapp for your WLS cluster ?
              Kumar Allamraju wrote:
              > Pls provide more details.
              > when does it happen? Can you consistently reproduce this stacktrace?
              >
              > thx
              > Kumar
              >
              > Marek wrote:
              >
              > > I have in my WLS 7.0 cluster enviroment error like this:
              > >
              > > java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext Start server side stack trace: java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext at weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:359) at weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(ReplicatedSessionData.java:180) at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34) at weblogic.cluster.replication.ReplicationManager$wroManager.create(ReplicationManager.java:339) at weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.java:1059) at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:346) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:300) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762) at weblogic.rmi.internal.Bas
              > icServerRef.handleRequest(BasicServerRef.java:295) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133) End server side stack trace
              > >
              Rajesh Mirchandani
              Developer Relations Engineer
              BEA Support
              

  • Compatibility error with WLS 10.3.5 and OSB 11.1.1.4.0

    As per out project requirement I am using WLS 10.3.5, OSB 11.1.1.4.0, and OEPE 11.1.1.6.1, but this oepe does not support these two WLS and OSB.
    when I am trying to create a new Oracle Service Bus Configuration Project, i am getting a error:
    Plug-in "com.bea.alsb.ui" was unable to instantiate class "com.bea.alsb.ui.wizards.NewALSBContainerWizard".
    com/bea/alsb/core/containers/exceptions/ContainerException
    Can anyone please suggest the correct version of OEPE if any.
    Thanks in advance,
    Jai

    Thanks Rene, but as I said we are not using the same version of WLS and OSB so in that case is there any option that which version of OEPE i should download which support these two versions of WLS 10.3.5 and OSB 11.1.1.4.0.

  • Error in WLS console

    Hi,
    Am getting the below error in my wls console .
    please help how to resolve this.
    <Mar 20, 2012 2:44:38 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "WebCenter-CustomPortalDS": IO Error: The Network Adapter could not establish the connection>
    <Mar 20, 2012 2:44:38 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Activities-CustomPortalDS": IO Error: The Network Adapter could not establish the connection>
    <Mar 20, 2012 2:44:39 AM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "WebCenter-CustomPortalDS": IO Error:

    Check if you are able to login with the users for all the schema's for the data-sources.
    If you get account locked exception then unlock it.
    http://ramannanda.blogspot.in/2012/02/oracle-database-account-unlocker.html
    Else check the connection properties in your application.

  • JSPC Error "Unrecognized option: -v0."

    Hii All
    I get this Error (shown below) when i try to compile my Jsp using ANT builder.What can be the reason behind this error.
    Thankx in advance
    Vikash
    /////////////////////// Error is shown below ////////////////////////////////.
    Buildfile: build.xml
    jspc:
    compile:
    [jspc] Compiling 79 source filesC:\ant\${webapp.path}\dest
    [jasperc] error:org.apache.jasper.JasperException: Unrecognized option: -v0.
    Use -help for help.
    [jasperc] at org.apache.jasper.JspC.setArgs(JspC.java:306)
    [jasperc] at org.apache.jasper.JspC.main(JspC.java:230)
    all:
    BUILD SUCCESSFUL
    Total time: 13 seconds
    //////////////////////////Build.xml is shown below ////////////////////
    <project name="Webapp Precompilation" default="all" basedir=".">
    <target name="jspc">
    <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
    <classpath id="jspc.classpath">
    <pathelement location="C:\Program Files\Apache Software Foundation\Tomcat 5.0/../lib/tools.jar"/>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/bin">
    <include name="*.jar"/>
    </fileset>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/server/lib">
    <include name="*.jar"/>
    </fileset>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/common/lib">
    <include name="*.jar"/>
    </fileset>
    </classpath>
    </taskdef>
    <jasper2
    validateXml="false"
    uriroot="${webapp.path}"
    webXmlFragment="${webapp.path}/WEB-INF/generated_web.xml"
    outputDir="${webapp.path}/WEB-INF/src" />
    </target>
    <target name="compile">
    <mkdir dir="${webapp.path}/WEB-INF/classes"/>
    <mkdir dir="${webapp.path}/WEB-INF/lib"/>
    <jspc destdir="${webapp.path}/dest"
    srcdir="${webapp.path}/WEB-INF/src"
    excludes="**/*.smap">
    <classpath>
    <pathelement location="${webapp.path}/WEB-INF/classes"/>
    <fileset dir="${webapp.path}/WEB-INF/lib">
    <include name="*.jar"/>
    </fileset>
    <pathelement location="C:\Program Files\Apache Software Foundation\Tomcat 5.0/common/classes"/>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/common/lib">
    <include name="*.jar"/>
    </fileset>
    <pathelement location="C:\Program Files\Apache Software Foundation\Tomcat 5.0/shared/classes"/>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/shared/lib">
    <include name="*.jar"/>
    </fileset>
    <fileset dir="C:\Program Files\Apache Software Foundation\Tomcat 5.0/bin">
    <include name="*.jar"/>
    </fileset>
    </classpath>
    <include name="**" />
    <exclude name="tags/**" />
    </jspc>
    </target>
    <target name="all" depends="jspc,compile">
    </target>
    </project>

    Hi,
    I've had this problem too. The -v options is meant to set the verbosity of the compilation but it doesn't seem to like it. I tried to see which versions of jasper/ ant were at fault (because an old script of mine broke) but couldn't find it quickly so I simply did a little hack in the ant 1.6.1 source to the file
    \apache-ant-1.6.1\src\main\org\apache\tools\ant\taskdefs\optional\jsp\compilers\JasperC.java
    where I commented out the line in setupJasperCommand()
    private CommandlineJava setupJasperCommand() {
    addArg(cmd, "-p", jspc.getPackage());
    // addArg(cmd, "-v" + jspc.getVerbose());
    addArg(cmd, "-uriroot", jspc.getUriroot());
    then rebuilt ant and the problem went away.
    Cheers
    Evan

  • Error connecting WLS 10.3.1 JMS & MDBs with Oracle Advanced Queuing

    I followed the guide at http://blogs.oracle.com/imc/2010/12/how_to_use_oracle_aq_with_message-driven_beans_in_weblogic.html. Since the AQ queues were already set up by SAs and had been working with stateless session beans, I assume they're OK for use with MDBs. Names had to be changed in the WLS foreign server definition, destinations & connection factories to match.
    My MDB is:
    package xxxx;
    import javax.ejb.MessageDriven;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    @MessageDriven(name = "TestQueueListenerEJB")
    public class TestQueueListener implements MessageListener
    public void onMessage(Message message)
    if ( message instanceof TextMessage )
    try
    System.out.println("AQMDBTest: text message " + ((TextMessage)message).getText() + " processed");
    catch (JMSException e)
    e.printStackTrace();
    else
    System.out.println("AQMDBTest: generic message " + message.toString() +
    " of type " + message.getClass().getName() + " processed");
    And the relevant portion of the weblogic-ejb-jar.xml is:
    <weblogic-enterprise-bean>
    <ejb-name>TestQueueListenerEJB</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>1</max-beans-in-free-pool>
    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>TestQueue</destination-jndi-name>
    <connection-factory-jndi-name>TestQueueConnectionFactory</connection-factory-jndi-name>
    </message-driven-descriptor>
    </weblogic-enterprise-bean>
    So when I deploy this to my test domain I get an error:
    <Feb 23, 2011 3:11:28 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TestQueueListenerEJB is unable to connect to the
    JMS destination: TestQueue. The Error was:
    Can not get destination information. The destination JNDI name is TestQueue, the provider URL is null>
    The test connection of the datasource is successful.
    What else could I have wrong? This is my first post to this topic. Please let me know what additional information I need to provide about this. Or if I've provided too much.
    Thanks very much,
    Jim Greetham

    OK. So I got my DBAs to create a new user with the necessary privs. Created a new queue, table, etc. I have been able to receive messages from it. So I have some looking to do in my production database queue definitions.
    Jim

  • CMD_IDENTIFY_REQUEST error on WLS 10.0 MP1

    Hello,
    We just started running a WLS 10.0 MP1 cluster (IBM JVM/AIX). We see this error getting logged in the WLS log file every few minutes. I found some old CR (WLS 7.0) which talks about this and this has been supposedly fixed. Any pointers?
    <Oct 16, 2008 10:29:46 AM PDT> <Error> <RJVM> <BEA-000506> <Closing: weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@36813681 because of Server expected to route a message received over an uninitialized connection: 'JVMMessage from: '4317822236859844709S:esbprod02:[7010,7010,-1,-1,-1,-1,-1]:esbprod01:7010,esbprod02:7010:prod_domain:esbprod02' to: '817180548870097230C:10.192.32.117R:-8825084390572923574S:esbprod01:[7010,7010,-1,-1,-1,-1,-1]:prod_domain:esbprod01' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x1', abbrev offset: '180''>
    <Oct 16, 2008 10:31:46 AM PDT> <Error> <RJVM> <BEA-000506> <Closing: weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@4020402 because of Server expected to route a message received over an uninitialized connection: 'JVMMessage from: '4317822236859844709S:esbprod02:[7010,7010,-1,-1,-1,-1,-1]:esbprod01:7010,esbprod02:7010:prod_domain:esbprod02' to: '8431435963259375603C:10.192.32.134R:-8825084390572923574S:esbprod01:[7010,7010,-1,-1,-1,-1,-1]:prod_domain:esbprod01' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x1', abbrev offset: '180''>
    Thanks
    Santosh

    I struggled with the same problem for weeks and found that a very likely solution was running <wlst> from within ant.
    We got this problem when our deploy scripts changed from shell scripts (windows cmd files) into a single ant script where wlst was called repeatedly using the <wlst>supplied target.
    Our scripts are used to create the domain and all resources from scratch and invokes wlst several times during the process.
    When the ant script was changed into <exec> .. where wlst was invoked in a forked process, the problem disappeared.
    I would think that the problem is wlst ant target not performing a proper cleanup.
    Or, if you have another external jvm that opens an rjvm connection to the server, you might want to turn this program off during domain creation and configuration.
    Hope this helps
    Niels Gylling, IT Practice

  • Muxer error on WLS shutdown on Solaris 8

    Hi,
    We're running WLS 5.1.0 (sp9) on Solaris 8 with JDK 1.2.2_07. When we shut WLS
    down we get the following muxer ThreadDeath errors at the end of the shutdown:
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <WebLogicServer> Waiting: '20' seconds
    for threads to complete shutdown
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <ListenThread> Shutting down Thread[ListenThread,5,]
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: Before free/total=62504072/67108864
    (93%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: After free/total=64015832/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: Before free/total=64004336/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: After free/total=64020208/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Shutting down execute
    threads
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Shutdown completed
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    WLS doesn't then actually shut down so we have to kill the process to get rid
    of it. When we try to restart WLS we get the following error (note that I've inserted
    asterisks where our IP address was displayed):
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** Unable to create server
    socket for: ********, port: '7001'. Perhaps the address is incorrect or another
    process is using the port.
    java.net.BindException: Address already in use
         at java.net.PlainSocketImpl.socketBind(Native Method)
         at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
         at java.net.ServerSocket.<init>(ServerSocket.java:173)
         at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:215)
         at weblogic.t3.srvr.ListenThread.run(Compiled Code)
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** The WebLogic Server
    is no longer listening for connections.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** You should probably
    restart it.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** Unable to create
    server socket for: ********, port: '7002'. Perhaps the address is incorrect or
    another process is using the port.
    java.net.BindException: Address already in use
         at java.net.PlainSocketImpl.socketBind(Native Method)
         at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
         at java.net.ServerSocket.<init>(ServerSocket.java:173)
         at weblogic.security.SSL.SSLServerSocket.<init>(SSLServerSocket.java:67)
         at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:473)
         at weblogic.t3.srvr.ListenThread.run(Compiled Code)
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** The WebLogic Server
    is no longer listening for connections.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** You should probably
    restart it.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown by system
    Tue Oct 30 19:47:43 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown by system
    Tue Oct 30 19:48:44 GMT+00:00 2001:<I> <WebLogicServer> WebLogic Server started
    Tue Oct 30 19:48:44 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown commencing
    NOW
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <HTTP> Destroying servlets in default servlet
    context.
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <WebLogicServer> Requesting thread shutdown
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <WebLogicServer> Waiting: '20' seconds
    for threads to complete shutdown
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <ListenThread> Shutting down Thread[ListenThread,5,]
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: Before free/total=64963208/67108864
    (96%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: After free/total=65159344/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: Before free/total=65147696/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: After free/total=65159944/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Shutting down execute
    threads
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Shutdown completed
    WLS is the onle process using these ports so it shouldn't hit this problem. Our
    only recourse is then to reboot the server itself after which WLS starts okay.
    Obviously we don't want to have to reboot the server everytime we shut down WLS.
    Has anyone else encountered this problem? Any help greatly appreciated.
    Thanks,
    Garry

    Hi.
    Please open a case with support for this issue.
    Thanks,
    Michael
    Garry Baird wrote:
    Hi,
    We're running WLS 5.1.0 (sp9) on Solaris 8 with JDK 1.2.2_07. When we shut WLS
    down we get the following muxer ThreadDeath errors at the end of the shutdown:
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <WebLogicServer> Waiting: '20' seconds
    for threads to complete shutdown
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
    Tue Oct 30 20:16:08 GMT+01:00 2001:<I> <ListenThread> Shutting down Thread[ListenThread,5,]
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: Before free/total=62504072/67108864
    (93%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: After free/total=64015832/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: Before free/total=64004336/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <GC> GC: After free/total=64020208/67108864
    (95%)
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Shutting down execute
    threads
    Tue Oct 30 20:16:28 GMT+01:00 2001:<I> <WebLogicServer> Shutdown completed
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    Tue Oct 30 20:16:28 GMT+01:00 2001:<E> <Performance Pack> Muxer got error: null
    java.lang.ThreadDeath
    WLS doesn't then actually shut down so we have to kill the process to get rid
    of it. When we try to restart WLS we get the following error (note that I've inserted
    asterisks where our IP address was displayed):
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** Unable to create server
    socket for: ********, port: '7001'. Perhaps the address is incorrect or another
    process is using the port.
    java.net.BindException: Address already in use
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
    at java.net.ServerSocket.<init>(ServerSocket.java:173)
    at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:215)
    at weblogic.t3.srvr.ListenThread.run(Compiled Code)
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** The WebLogic Server
    is no longer listening for connections.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <ListenThread> **** You should probably
    restart it.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** Unable to create
    server socket for: ********, port: '7002'. Perhaps the address is incorrect or
    another process is using the port.
    java.net.BindException: Address already in use
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
    at java.net.ServerSocket.<init>(ServerSocket.java:173)
    at weblogic.security.SSL.SSLServerSocket.<init>(SSLServerSocket.java:67)
    at weblogic.t3.srvr.SSLListenThread.newServerSocket(SSLListenThread.java:473)
    at weblogic.t3.srvr.ListenThread.run(Compiled Code)
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** The WebLogic Server
    is no longer listening for connections.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<!> <SSLListenThread> **** You should probably
    restart it.
    Tue Oct 30 19:47:43 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown by system
    Tue Oct 30 19:47:43 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown by system
    Tue Oct 30 19:48:44 GMT+00:00 2001:<I> <WebLogicServer> WebLogic Server started
    Tue Oct 30 19:48:44 GMT+00:00 2001:<I> <WebLogicServer> Server shutdown commencing
    NOW
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <HTTP> Destroying servlets in default servlet
    context.
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <WebLogicServer> Requesting thread shutdown
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <WebLogicServer> Waiting: '20' seconds
    for threads to complete shutdown
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <SSLListenThread> Shutting down Thread[SSLListenThread,5,]
    Tue Oct 30 19:48:45 GMT+00:00 2001:<I> <ListenThread> Shutting down Thread[ListenThread,5,]
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: Before free/total=64963208/67108864
    (96%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: After free/total=65159344/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Invoking garbage collection
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: Before free/total=65147696/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <GC> GC: After free/total=65159944/67108864
    (97%)
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Shutting down execute
    threads
    Tue Oct 30 19:49:05 GMT+00:00 2001:<I> <WebLogicServer> Shutdown completed
    WLS is the onle process using these ports so it shouldn't hit this problem. Our
    only recourse is then to reboot the server itself after which WLS starts okay.
    Obviously we don't want to have to reboot the server everytime we shut down WLS.
    Has anyone else encountered this problem? Any help greatly appreciated.
    Thanks,
    Garry--
    Developer Relations Engineer
    BEA Support

  • URGENT:: errors with WLS Portal GA

    Hi,
    I just installed the GA version of WebLogic Platform and tried to create a Portal
    using WorkShop.
    I selected a "Portal Application" and then a "Portal Web Project". The WebLogic
    console (stdout) shows many errors. It is not able to find some skins, portlets
    etc. The files seems to be there in the Web Project.
    When i create a Portal and try to run it, it comes up with a error (/framework/skeletons/default/desktop.jsp)
    not found. Even this file is present.
    These were working in the beta version.
    Anybody got the same errors. Any solutions??
    Attached is the error file.
    Raghu
    [Portal_Errors.txt]

    hi Raghu
    this happens if you have the WLS running while working with the workshop.
    The "update" - feature of WLW is not realy reliable and can cause errors.
    if you will be shure all updates commit with WLS .. restart the server through
    WLW.
    Greetings
    fear
    "Raghu Subramaniam" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I just installed the GA version of WebLogic Platform and tried to create
    a Portal
    using WorkShop.
    I selected a "Portal Application" and then a "Portal Web Project". The
    WebLogic
    console (stdout) shows many errors. It is not able to find some skins,
    portlets
    etc. The files seems to be there in the Web Project.
    When i create a Portal and try to run it, it comes up with a error (/framework/skeletons/default/desktop.jsp)
    not found. Even this file is present.
    These were working in the beta version.
    Anybody got the same errors. Any solutions??
    Attached is the error file.
    Raghu

  • 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.

  • Weblogic 9.1 jspc error

    I'm running this command:
              java weblogic.jspc -verboseJspc -d src/webapp/WEB-INF/classes -k -g -compileAll -webapp src/webapp
              and I get this error:
              Exception in thread "main" java.lang.AssertionError: java.io.IOException
              at weblogic.descriptor.DescriptorManager$DefaultMarshallerFactorySingleton.<clinit>(DescriptorManager.java:40)
              at weblogic.descriptor.DescriptorManager.getDefaultMF(DescriptorManager.java:110)
              at weblogic.descriptor.DescriptorManager.getMarshallerFactory(DescriptorManager.java:119)
              at weblogic.descriptor.DescriptorManager.getDescriptorFactory(DescriptorManager.java:147)
              at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:268)
              at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:240)
              at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:300)
              at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:379)
              at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:659)
              at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
              at weblogic.servlet.jsp.jspc20.initDescriptors(jspc20.java:470)
              at weblogic.servlet.jsp.jspc20.runBody(jspc20.java:228)
              at weblogic.utils.compiler.Tool.run(Tool.java:158)
              at weblogic.utils.compiler.Tool.run(Tool.java:115)
              at weblogic.jspc.main(jspc.java:22)
              Caused by: java.io.IOException
              at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:52)
              at weblogic.descriptor.DescriptorManager$DefaultMarshallerFactorySingleton.<clinit>(DescriptorManager.java:38)
              ... 14 more
              Caused by: com.bea.xml.XmlException: unable to load type library from classloader sun.misc.Launcher$AppClassLoader@133056f
              at com.bea.staxb.runtime.internal.BindingContextFactoryImpl.createBindingContext(BindingContextFactoryImpl.java:50)
              at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:50)
              ... 15 more
              anyone seen that before? I can't find any info on the web about it.
              CLASSPATH=/home/me/.maven/repository/weblogic/jars/weblogic-9.1.0.jar:/home/me/.maven/repository/weblogic/jars/wlxbean-9.1.0.jar:/home/me/.maven/repository/weblogic/jars/wlwebservices-9.1.0.jar
              I'm running this on redhat enterprise 4 and using sun's jdk 1.5.0_05

    I just ran into a similar problem while upgrading to WebLogic 9.1 from WebLogic 8.1sp5. Running the EJBGen task with the 9.1 WL jars produced this error:
              com.bea.xml.XmlException: unable to load type library from classloader java.net.URLClassLoader@1bd2664
              Adding weblogic-container-binding.jar to the classpath of the EJBGen task fixed this problem for me. Hope this helps anyone else struggling with the same issue.
              --Steven                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Cannot determine cause of Transaction Error in WLS 5.1 sp10

    Upgrading to sp10 for WebLogic, an ejbCreate() via CMP throws an
              javax.transaction.TransactionRolledbackException if an error occurs
              without any stack trace or details!!! Why or when does this happen?
              Is this specific to sp10? Current environment is Sun Solaris 7, Oracle
              8.1.6, thin driver
              

    WLS 6.0 is the first WebLogic Server version which supports XA/2PC. If you need to enlist
              multiple resources in a single transaction, you will need WLS 6.x. (I would recommend
              6.1)
              You should get your JDBC connections from TxDataSources.
              -- Rob
              Brendan wrote:
              > Hi,
              >
              > I'm looking for some definitive information on the support for distributed transactions
              > in wls 5.1 sp10.
              >
              > We are currently experiencing problems since we try to get connections from multiple
              > connectionPools in the one transaction, which seems to be disallowed.
              >
              > I have seen various posts commenting on the lack of support for 2pc/ distributed
              > transactions in wls 5.1 etc, but have not seen any definitive bea documentation
              > describing what is and is not supported.
              >
              > Before we decide to jump to 6.0 or 6.1 we'd like to ensure that 1) we need to,
              > and 2) it will support getting connections from multiple pools in the one transaction.
              >
              > Any pointers greatly appreciated.
              >
              > Brendan
              AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
              by Michael Girdley, Rob Woollen, and Sandra Emerson
              http://learnWebLogic.com
              [att1.html]
              

  • Sporadic errors in wls 61

    I just rolled out wls 6.1 two days ago and sporadically users are reporting "403
    forbidden" errors. Can someone shed the lights and point me to the dirction for
    fixes ? It's less than 10% of users experiencing the problems.
    Thanks,
    Jessie

    Thanks. Mike.
    Could it be something else since I've run into the same problem in development
    about a month ago and permenant key with ANY is used for production.
    Jessie
    "Michael Reiche" <[email protected]> wrote:
    >
    The demo license only allows browsers from 3 unique IP address to access
    it.
    If it is accessed by a fourth, it gives a 403 error.
    Mike
    "Jessie yau" <[email protected]> wrote in message
    news:3c113fe2$[email protected]..
    I just rolled out wls 6.1 two days ago and sporadically users arereporting "403
    forbidden" errors. Can someone shed the lights and point me to thedirction for
    fixes ? It's less than 10% of users experiencing the problems.
    Thanks,
    Jessie

  • Native Library(terminalio) Error in WLS 9.2

    Hello
    While starting up a WLS 9.2 domain in production mode, i get the following error "Native Library(terminalio) to read the password securely from commandline is not found".
    This is running on Red Hat Linux AS 4.0.
    I had the BEA files under /usr/local/bea installed by tar'ing up all the files from another installation running also on a RHEL box but created the domain on the new box.
    Since entering passwords was not a problem on the older RHEL box, could this be because of some missing libraries when i moved the BEA installation across?
    Thanks
    Ramdas

    I figured out the problem was the version of the OS on the newer system. Though it was running RHEL AS 4.0 on a 32 bit Xeon processor, it was derived from a 64 bit Red Hat channel. As a result, the hardware architecture as recognized by the commEnv.sh WLS script returned x86_64 which was not available in the list of native linux libraries under <WL_HOME>/server/native/linux. By forcing (-Djava.library.path) the WL server to include the i686 native libraries in its path helped get around this issue.
    Thanks
    Ramdas

Maybe you are looking for

  • Lightroom5 to Photoshop Elements

    A while ago I downloaded Lightoom 5 and Photoshop 6 as a trial. As I decided not to have monthly financial commitments and chose to opt out of the cloud. Instead I purchased Lightroom 5 and Photoshop Elements. Unfortunately when I want to open my ima

  • Why is South African Educator Discount almost non-existent?

    Hi I want to upgrade to Adobe Creative Cloud from the Photoshop subscription of $9.99 p.m.  However, since I am in South Africa, paying $49.99 p.m. (excluding 14% value added tax) is not affordable. Since I work at a university, I hoped to make use o

  • System switching on with lid closed?

    Hi there just wondering if anyone has come across this? I've noticed this twice now, when I shut down my machine I always make sure its fully powered down, I then close the lid, now normally I let the macbook charge overnight, but the system on both

  • Multiple address for one vendor

    Hi all, I have various partner function for my vendor. I assigned various partner function . I need to know where we have to assign the address to these partner functions like OA, PI and GS.So that in PO i will get correct ordering address . Or wheth

  • The iMessage button will not slide on in the settings. What is going on?

    The iMessage button will not slide on/green in the settings. Whay is going on?