Bea WL 6.3 SP3 on W2K

Hello!
I try to install WL 6.1 Sp3 on W2K and the install programm always stops during
extraction and wants to have a new loaction for its temporary files. Have I made
so changes on my machine to start the installatio?
Thank
Mike

I think the problem is that Solaris comes with JDK 1.2 and that is not good enough.
What does "java -version" show you?
Try it without specifying the LAX_VM so that the jdk within weblogic is used.
Better yet, if you have a previous version of wls installed, use the jdk that came with
it by putting it in your PATH in the FRONT.
export PATH=<whatever>/bea/jdk131_03/bin:$PATH
sh weblogic610sp3_sol.bin install -i console
Wayne Scott
Fion Tam wrote:
Yes, I have Java bin in my path.
When I run installation with the command you've mentioned in the previous reply,
the process still hangs on the create password step.
Fion
"Wayne W. Scott" <[email protected]> wrote:
Try inserting the word "install" before the '-i'
sh weblogic610sp3_sol.bin LAX_VM $JAVA_HOME/bin/java install -i console
Do you have the JAVA bin in your PATH?
Wayne Scott
Fion Tam wrote:
Dear all,
When I try to run the installation toolkit weblogic610sp3_sol.bin onSolaris 7
Intel, the following error occurs: "Error: can't find libjava.so."
Then, I try to run the toolkit with the following command:
sh weblogic610sp3_sol.bin LAX_VM $JAVA_HOME/bin/java -i console
but it hangs on the create password step.
I wonder if the installation toolkit supports Solaris 7 Intel.
Any answer would be appreciated.
Regards,
Fion

Similar Messages

  • Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

    Hi,
    Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
    The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
    I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
    Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
    PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
    * To start WebLogic Server, use a username and *
    === Debugging ===
    This window is necessary for debugging code using WebLogic Workshop
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Listening for transport dt_socket at address: 8453
    Starting WLS with line:
    C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    Listening for transport dt_socket at address: 8453
    <27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
    <27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
    <27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
    Stopping the Weblogic Workshop debugger...
    Debugger Stopped.
    Stopping Pointbase server...
    Pointbase server stopped.
    If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
    Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
    Regards.
    Full Exception
    EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
    at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
    at java.lang.String.valueOf(String.java:2131)
    at java.lang.StringBuffer.append(StringBuffer.java:370)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
    I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
    However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
    Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
    Regards.

  • Observed Memory Leak When Invoking Controls in Workshop 8.1 sp3

    Hello,
    We have developed a website using Bea Portal 8.1 sp3. In testing we have observed severe memory leaking problems which occur also in the production environment where WebLogic is not being run in debug mode. The troubleshooting was started by profiling the testing environment (running in debug mode) using JProfiler. The leak was isolated to occur especially in control method invocation via InvocationHandler call. The object being leaked was character array. After further study we noticed that the method call which this framework InvocationHandler was delegating had especially large return value. Namely a map consisting of ~5Mb of content. After reviewing our own code for possible leak source and coming up with nothing obviously wrong we started to suspect that something was leaking memory in the WebLogic framework code. As the leaked object was character array we suspected that the framework was calling toString() method of the return value and the string was never released. To prove this we constructed a small test program which just demonstrated passing large object as arguments and return values in invocations to WebLogic Workshop control from page flow. The memory consumption in WebLogic monitor and console output proved that indeed the toString() method was invoked 1 times in invocation per argument and 2 times per return value. Furthermore by returning empty string in one test and string of several megabytes in other from toString() one could observe exactly matching memory leaking. Manual running of the garbage collector did not release the memory.
    To resolve this problem we have tried to alter the Workshop logging configuration in WorkshopLogCfg.xml. Lowering the log level to debug in categories caused much more invocations to the toString() of the arguments. We did not monitor the memory leaking in this test. Raising all the category levels to fatal did not have effect compared to the original settings. Also removing all categories did not have effect on toString() calls.
    We have established quite reliably that this leak occurs with our configuration both in development environment (Windows XP) and testing environment (Redhat Linux) both running WebLogic in debug mode. Both of these environments have out of the box log configuration. We have also observed memory leaking in production environment but it has not yet been profiled to see whether the leak is 100% surely due to this same problem.
    We have not yet tested this in sp5 nor sp6. Switching service packs is not solution for as in the moment as we are not able to switch the service pack in production environment due to reasons which are out of our control.
    We would appreciate confirmation whether this issue is real and any solutions available like configuration modification, patching or switching service pack. Also links to existing articles about this issue would be nice to have.
    We can provide the testing code and some screenshots of memory usage via email. You can request it from tommi.laukkanen at xiiris.com.
    best regards,
    Tommi Laukkanen / WM-data Finland / Digital Media (tommi.laukkanen at wmdata.fi or tommi.laukkanen at xiiris.com)
    Artti Jaakkola / WM-data Finland / Digital Media (artti.jaakkola at wmdata.fi)
    PS. This is the console out from the test page flow invoking the control:
    We have manually thrown and catched exceptions in toString() method to get the stack trace printed to console out.
    java.lang.Exception
    at Test.ControlTest.TestControlImpl$TestContainer.toString(TestControlImpl.jcs:43)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logReturn(WlwThreadContext.java:430) <---------------------
    at com.bea.wlw.runtime.core.context.WlwThreadContext.endInvocation(WlwThreadContext.java:637)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:445)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:84)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315)
    at $Proxy19.testMethod(Unknown Source)
    at Test.ControlTest.ControlTestController.begin(ControlTestController.jpf:58)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1507)
    at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1433)
    at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:764)
    at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211)
    at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:594)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:650)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:316)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.superForward(PageFlowRequestProcessor.java:1301)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor$DefaultHttpRedirector.forward(PageFlowRequestProcessor.ja
    va:1317)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.doForward(PageFlowRequestProcessor.java:1199)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:637)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6458)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    java.lang.Exception
    at Test.ControlTest.TestControlImpl$TestContainer.toString(TestControlImpl.jcs:43)
    at com.bea.wlw.runtime.core.request.ExecResponse.toString(ExecResponse.java:53)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:269) <---------------------
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315)
    at $Proxy19.testMethod(Unknown Source)
    at Test.ControlTest.ControlTestController.begin(ControlTestController.jpf:58)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1507)
    at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1433)
    at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:764)
    at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211)
    at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:594)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:650)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:316)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.superForward(PageFlowRequestProcessor.java:1301)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor$DefaultHttpRedirector.forward(PageFlowRequestProcessor.ja
    va:1317)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.doForward(PageFlowRequestProcessor.java:1199)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:637)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6458)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    java.lang.Exception
    at Test.ControlTest.TestControlImpl$TestContainer.toString(TestControlImpl.jcs:43)
    at java.lang.String.valueOf(String.java:2131)
    at java.lang.StringBuffer.append(StringBuffer.java:370)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363) <---------------------
    at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:84)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:99)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326)
    at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315)
    at $Proxy19.testMethod2(Unknown Source)
    at Test.ControlTest.ControlTestController.begin(ControlTestController.jpf:59)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1507)
    at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1433)
    at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:764)
    at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211)
    at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:594)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:650)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:316)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.superForward(PageFlowRequestProcessor.java:1301)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor$DefaultHttpRedirector.forward(PageFlowRequestProcessor.ja
    va:1317)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.doForward(PageFlowRequestProcessor.java:1199)
    at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:637)
    at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
    at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:351)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6458)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Message was edited by:
    tlaukkan
    Message was edited by:
    tlaukkan
    Message was edited by:
    tlaukkan

    Hi
    I did not find any known issues on this. But since you can replicate the issue, could you please contact BEA Support and open a case and have this followed?
    Since we may have to do some testing/profiling etc with different service packs with your sample, it would be better to follow up via a support case.
    Thanks
    Vimala

  • What is the Best was to create a newsletter application using BEA / Documen

    Hi,
    I have some queries.
    What is the Best was to create a newsletter application using BEA / Documentum
    The newsletter will be republished and users will see new content every month. We plan to use BEA portal 8.1 sp3 with Documentum 5.3Sp1 / SCS.
    The content of newsletter may be coming from data sources, we will combine this content plus some static content, and publish to Documentum using BEA's CM SPI implementation for Documentum. To connect to different data sources we will use registered table feature of Documentum. Anybody can suggest the best to achieve this or any suggestion or any samples....
    How can we create our custom portlets which can use Documentum registered table feature to connect to data sources.
    Thanks for the help,
    Sudhir

    I assume that you are thinking about using the 'n" wireless version of the AirPort Express, or the "new" dual band AirPort Express.
    Simply connect each Express one at a time via Ethernet back to the Ethernet switch and use AirPort Setup to configure the device. Other than entering a device name for each Express, AirPort Setup will do everything else for you automatically. You will be amazed at how easy this will be.
    I do not want to use the "Extend Range" feature, as it trys to link the express back to the extreme via wireless.
    Sounds like you might be a bit confused here. When AirPort Setup recognizes that the Express is connected via Ethernet, it will configure the Express to "extend" using an Ethernet connection....not wireless.
    In other words, Apple devices can "extend" using wireless or Ethernet connections. AirPort Setup analyzes the connection and chooses the correct settings for you.
    If you later go back in and check the settings for the Express using AirPort Utility, you will see that it has actually been set up to "create" a wireless network using the same wireless network name, same security and same password as the main router. The Express will also be in Bridge Mode to work correctly on the network.

  • WebLogic6.1 SP3/Solaris5.7: "HotSpot Virtual Machine Error, Internal Error"

    Hello,
    I get the following error when I try to start up the
    BEA Weblogic (6.1+SP3) server, running the petstore demo...
    # HotSpot Virtual Machine Error, Internal Error
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Error ID: 53484152454432554E54494D450E43505000EA 01
    # Problematic Thread: prio=5 tid=0x283a8 nid=0x1 runnable
    Abort - core dumped
    I get this crash during the startup sequence,
    #> uname -a
    SunOS xxxxxx 5.7 Generic_106541-06 sun4u sparc SUNW,Ultra-250
    #> java -version
    java version "1.3.1_03"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
    Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)
    This machine has 2 CPUs.
    Any ideas or suggestions?
    thanks,
    Steve_O

    Update:
    I checked the OS patch level and then installed a set of recommended patches from:
    http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE
    This appears to have fixed the problem.
    /Steve

  • Best was to create a newsletter application using BEA / Documentum

    The newletter will be republished and users will see new content every month. We plan to use BEA portal 8.1 sp3 with Documentum 5.3Sp1.
    The content of newsletter may be coming from data sources, we will combine this content plus some static content, and publish to documentum using BEA's CM SPI implememation for documentum. To connect to different datasources we will use registered table feature of Documentum. Anybody can suggest the best to achive this or any suggestion or any samples....
    Thanks for the help,
    Sudhir

    Whilst code without any permissions (as supplied through the ProtectionDomain by the class' ClassLoader) cannot access network, file and system clipboard, this does not mean it is entirely isolated.
    Even modern cryptographic systems are surprisingly vulnerable to side-channel attacks.
    Where an untrusted agent has access to sensitive data, it isn't very feasible to stop any escape of that data. Sure, you can block off overt posting of the data, but you cannot reasonably block off all covert channels.
    Steganographic techniques are a particularly obvious way to covertly send sensitive data out amongst intended publications.

  • Invalid console application caused WLS to fail to start

    We are using WLS 6.1 SP3 on W2K. In our config.xml, there is no reference
    to
    a console app., after shutting down the WLS using weblogic.Admin, the
    config.xml
    has an entry like this:
    <Application Name="console-1"
    Path="d:\bea\wlserver6.1\config\agileDomain\applications">
    <WebAppComponent Name="console" URI="console.war"/>
    </Application>
    The name 'console-1' caused WLS to fail to start. Any hints. I don't
    believe we have this problem in
    WLS 6.1 SP2.
    Thanks in advance,
    Hien
    =================================================================
    <Aug 5, 2002 12:41:13 PM PDT> <Error> <Management>
    <InvocationTargetException setting attribute Deployed on MBean
    agileDomain:Location=himalayaServer,Name=console-1,Type=ApplicationConfig to
    value true. Method: public void
    weblogic.management.mbeans.custom.Application.setDeployed(boolean) throws
    weblogic.management.DeploymentException,weblogic.management.UndeploymentExce
    ption
    weblogic.j2ee.DeploymentException: Cannot deploy
    WebAppServletContext(1274224,console,/console) on himalayaServer because
    WebAppServletContext(6208755,console,/console) is already registered for
    path /console
    at
    weblogic.servlet.internal.ServletContextManager.registerContext(ServletConte
    xtManager.java:123)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:450)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:78)
    at weblogic.j2ee.Application.deploy(Application.java:271)

    If you send me your entire config.xml file and your application.xml,
    and application-config.xml (if you are using one) I can look at it for
    you.
    >
    =================================================================
    <Aug 5, 2002 12:41:13 PM PDT> <Error> <Management>
    <InvocationTargetException setting attribute Deployed on MBean
    agileDomain:Location=himalayaServer,Name=console-1,Type=ApplicationConfig to
    value true. Method: public void
    weblogic.management.mbeans.custom.Application.setDeployed(boolean) throws
    weblogic.management.DeploymentException,weblogic.management.UndeploymentExce
    ption
    weblogic.j2ee.DeploymentException: Cannot deploy
    WebAppServletContext(1274224,console,/console) on himalayaServer because
    WebAppServletContext(6208755,console,/console) is already registered for
    path /console
    at
    weblogic.servlet.internal.ServletContextManager.registerContext(ServletConte
    xtManager.java:123)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:450)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:78)
    at weblogic.j2ee.Application.deploy(Application.java:271)

  • 1.4.1 plugin not working?

    I have deployed Java applets on IE5/6 with plugin versions 1.3.x up until 1.4.0_01 without any problems. Recently I upgraded to 1.4.1 (what does FCS stand for?) and now applets deployed in a JAR file fail to load and start altogether.
    I use the plugin as the default Java content handler for IE6 and use a plain <applet> tag. With 1.4.0_01 this worked perfectly. Also some other applets which are deployed as class-files show strange behaviour also.
    The Java console shows no errors. What is wrong? 1.4.0rc had some plugin problems also, but these where gone in the release version.
    Any ideas?
    Regards,
    Silvio Bierman

    I also experienced problems with IE6 and this JDK/JRE.
    I'm using W2K SP3 and have and SP1 patch for IE.
    Upon chance I stumbles upon other reports on google (primarily derived from users in the Netherlands) who also experienced problems since they installed SP3 for W2K. The theory is that MS has incorporated some kind of security check. This is second hand info though and I know nothing about it, so I really can't say if the fault is SUN's or Microsoft's.
    What I can say though is that the problem manifested itself via the SUN JVM. My symptom was that both IE 6 and Mozilla 1.0 would just silently close all windows running under the process firing up the JRE. This information would have been impossible to get just by using IE or Mozilla, as no error messages were shown, nor core dumps or similar (does MS Windows have a dump concept? I'm no MS Windows expert).
    What I did though was install the Norwegian browser Opera and that crashed as well when starting certain applets. However, Opera died and triggered the MS VC6 debugger, so that I could get a "stack trace". The last 10 function calls were indeed from the JVM! The stack looked like this: 3 kernel calls (USER32), 16 Opera calls, 10 JVM calls and BOOM!
    Unfortunately I can't read assembler, so I couldn't backstep in order to find the core of the problem. However, when I uninstalled the SUN JRE and JDK the applets that previously would make all browsers crash now worked great.
    The reference page I've been using to reproduce the problem has been by accessing http://www.hushmail.com (will redirect to https) -> Sign up for FREE -> <entered a user id> -> Continue.
    Try if doing this will reproduce the problem for you.
    It would also be interesting to hear if someone at SUN can reproduce the problem, or if we have any assembler hackers / Microsoft specialists here on the forum who might have a clue as to what is causing the problem.

  • Call another WebLogic's EJBs from resource adapter?

              Is it possible to call another WebLogic's EJBs from a resource adapter?
              A call to the javax.naming.InitialContext(Hashtable environment) results in a
              VersioningError:
              weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
              (BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
              not compatible with
              (BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              at java.lang.Class.newInstance0(Native Method)
              at java.lang.Class.newInstance(Class.java:232)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at java.lang.reflect.Constructor.newInstance(Native Method)
              I'm not sure it will always be possible to match the version, although here upgrading
              the SP3 to SP4 will probably be done soon.
              Does anyone have experience with this?
              Or better: is there any documentation on this issue?
              

              Hi Hans,
              Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
              http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
              Hope this will help you.
              Let me know if u have any further problems.
              rgds
              KSK
              "Hans Bausewein" <[email protected]> wrote:
              >
              >
              >Is it possible to call another WebLogic's EJBs from a resource adapter?
              >
              >A call to the javax.naming.InitialContext(Hashtable environment) results
              >in a
              >VersioningError:
              >
              >weblogic.common.internal.VersioningError: Incompatible service packs
              >in CLASSPATH:
              >(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
              >6.1.4.0)
              >not compatible with
              >(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              > at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              > at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              > at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              > at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              > at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              > at java.lang.Class.newInstance0(Native Method)
              > at java.lang.Class.newInstance(Class.java:232)
              > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > at javax.naming.InitialContext.init(InitialContext.java:217)
              > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > at java.lang.reflect.Constructor.newInstance(Native Method)
              >
              >
              >
              >I'm not sure it will always be possible to match the version, although
              >here upgrading
              >the SP3 to SP4 will probably be done soon.
              >
              >Does anyone have experience with this?
              >
              >Or better: is there any documentation on this issue?
              >
              

  • 终于搞定Weblogic8.1sp3下奇怪的Oracle错误了!也算是新Bug喽!

    本来计划新服务器割接要在本月底完成,可是在部署完成以后在操作数据库的时候却出了岔子。怎么也不能用了,连接很正常,就是不能 select,update,insert等操作。最经常报的三个错误是:
    OALL8 is in an inconsistent state.
    Bigger type length than Maximum
    Protocol Violation
    三个错误随机出现,最常见的是前两个。
    因为现有的程序正在一台 Linux 服务器上正常运行,我只是把整套系统原模原样的重新部署到了一台 Sun V480 服务器上,操作系统是 Solaris 9,依然用的是 Weblogic。数据库依然同一台 DELL 服务器,不同的只是操作系统以及JDK,所以首先怀疑的是 Solaris 上的JDK是不是该打补丁了,去了Sun的网站也看到了for Solaris的补丁,但是好像没有关系。然后又重新下载了最新的JDK 1.4.6 beta ,问题依旧。然后又装了 JDK 1.5,这次连 weblogic 都运行不起来了。为了再次验证是不是JDK的问题,我在控制台下写了一个简单的Java程序来连接那台数据库服务器,惊讶的发现一切正常,说明跟JDK没关系了。
    莫非是驱动的问题?可是在linux服务器上用的就是这个驱动呀,都是ojdbc14,看了一下CLASSPATH,也有啊。DELL 服务器上的Oracle版本是8.0.5,要不换成它自带的ojdbc看看,更换以后问题依旧!
    于是又把怀疑的目光转向了 weblogic,觉得是不是因为字符集的问题?又按照bea提供的一份中文化文档一步一步操作了一遍,确保提交数据的编码、连接oracle的编码、页面输出编码都是GBK,问题依旧!
    然后又怀疑到了 Solaris 上,毫无有道理的怀疑是不是因为字符集的不同,导致连接Oracle时发生的错误?因为这台服务器的操作系统是数据分公司的工程师负责安装的,他在安装的时候没有安装中文语言包,所以我设置了 LANG=zh_CN.GBK 后,系统不停的提示 couldn't set locale correctly。于是我又去了IDC机房,找来 Solaris 9的语言包光盘,把中文语言包安装上去,再次测试,问题依旧!
    实在没辙了,决定装上Tomcat看看,去了apache的网站后,发现tomcat有了5.5的版本,也没仔细看发行说明就直接下载回来了,却发现不能用,提示只能运行在JDK1.5下。幸亏前面已经下回来JDK1.5了,重新设置了JAVA_HOME后,哈,成功了。于是又再次怀疑weblogic的问题。
    我静下来仔细想了一下两台服务器除了系统不同之外,还有哪里不同?Linux上weblogic没有配置cluster,新装的Sun V480上配置了Cluster,我的神经再次兴奋起来,我重新部署了一个新的配置,只写了一个简单的JSP页面,上面就是连接那台 Oracle 数据库,也没有用群集,问题依旧!
    看来与Cluster没有关系喽,问题会在哪里呢?于是又怀疑了我现在用的数据库连接池,这个连接池虽然简陋,但是已经用了很长时间,也从没见过这个问题的发生。于是在weblogic上配置了一个连接池,然后又写了一个页面,哈,问题依旧!可是先前我一直用的是我下载回来的那个ojdbc14啊。
    不会跟开发版的license有关吧,我又找来公司的一个有时间限制的license,明年1月15号就要到期了。不管他,先换了,可是问题依旧!
    于是又不停的在google上搜索,看来出现这种问题的几率实在小,就找到寥寥可数的几个页面,不过在oracle的官方论坛上看到了一个相关帖子,据说是oracle老驱动的问题,需要升级驱动,可是最新的驱动就是1.4,我现在用的就是啊,无果,继续找。
    实在找不到什么结果,看来问题十之八九就在 weblogic 自己身上,我又去bea网站上看有关 weblogic 8.1 sp3 的发行信息,主要看了有关Oracle的部分,上面写的是在 weblogic 8.1 sp3 上的Oracle数据库已经把ojdbc1.4默认安装上去,而且默认的驱动就是ojdbc1.4,可是在先前我没有用过weblogic自带的连接池,应该和这个没有什么关系吧,但是抱着死马当做活马医的心态看了一下weblogic里面的ojdbc,发现也有一个ojdbc14.jar,但是和我用的大小不一样。不过既然都是1.4的版本,那我就把我一直用的把Weblogic的覆盖了吧,然后又是重新启动服务,打开测试页面,哇呜呜,成功了!!!
    问题竟然就是 weblogic 下 ojdbc 的问题!!!可是我在系统的CLASSPATH中已经添加了我自己的ojdbc,但是可恶的weblogic却优先使用了自己带的ojdbc!版本分明都是一样的,weblogic下的却有问题。浪费了我好几天,正所谓家贼难防啊,呜呜呜呜……
    最后的总结:
    看来在weblogic上部署的web应用程序,在使用相同的类库的时候,weblogic自带的相同类库优先,其次是CLASSPATH里添加的,最后才是WEB-INF/lib里的。在前面的问题中,虽然我在CLASSPATH里添加了ojdbc14的驱动,但是weblogic里已经有了,所以当然是用的weblogic自带的那个驱动了,CLASSPATH是没有效果的了。
    至于为什么那台Linux服务器上很正常,是因为上面装的是Weblogic 8.1 sp2!!!
    本月的任务看来有望在明天完成了……
    Weblogic 里的 ojdbc 还是是个老版本的?该升级啦,这也算是Bug吧 :-(

    "看来在weblogic上部署的web应用程序,在使用相同的类库的时候,weblogic自带的相同类库优先,其次是CLASSPATH里添加的,最后才是WEB-INF/lib里的。"
    不是这样的吧? 这取决于在CLASSPATH里的先后顺序,你要想自己的覆盖weblogic自带的,就把你的path放在weblogic的path包前面。

  • Installing IAS on a P$

    I'm trying to IAS on a Pentium 4 with Windows 2000?.
    I know that iPlanet does not support W2K but we have it running on P3s
    now in W2K
    when we ignore the warning. The only difference is the chip. On the P4
    the server will not load and I get the following errors:
    - The application, httpd.exe generated and application error. The
    error occurred (date and time). The exception generated was c0000005 at
    address 500BF974.
    - httpd.exe has generated errors and will be close by windows
    - httpps4.0 failed. The error code is DWORD 0 of the record data.
    Thanks

    Hi Nick
    Your problem seems to be related to web server. Could you clarify which
    web server you are using.
    I think processer doesn't make any difference whether it is p3 or p4.
    One good news is that now iAS sp3 supports W2k also.
    Thanks
    Deepak
    Nick Cardella wrote:
    >
    I'm trying to IAS on a Pentium 4 with Windows 2000?.
    I know that iPlanet does not support W2K but we have it running on P3s
    now in W2K
    when we ignore the warning. The only difference is the chip. On the P4
    the server will not load and I get the following errors:
    - The application, httpd.exe generated and application error. The
    error occurred (date and time). The exception generated was c0000005 at
    address 500BF974.
    - httpd.exe has generated errors and will be close by windows
    - httpps4.0 failed. The error code is DWORD 0 of the record data.
    Thanks

  • Oracle Web Center on Weblogic ?

    Hello there,
    I don't know nothing about Oracle Web Center.
    Do you known if it's possible mount some version of Oracle Web Center into some version of Weblogic?
    Thanks in advance.

    In a nutshell, yes.
    Here is a link to the interoperability chart (login required): http://one.bea.com/portal/server.pt?open=512&objID=3422&&PageID=5325&mode=2&in_hi_userid=726696
    In case you don't have a login to that site, here is a copy of the WCI/WebLogic part:
    WCI - Application Server
    10.3.0 - BEA WebLogic 9.2 MP1, BEA WebLogic 10.0 MP1, MP2 and MP3, Oracle WebLogic 10.3.0
    6.5, 6.5 MP1 - BEA WebLogic 8.1 SP4^, BEA WebLogic 9.1^, BEA WebLogic 9.2^, WebLogic 10.0^
    6.1 MP1 - BEA WebLogic 8.1 SP4^, BEA WebLogic 9.1^, BEA WebLogic 9.2^, WebLogic 10.0^
    6.1 - BEA WebLogic 8.1 SP4^, BEA WebLogic 9.1, BEA WebLogic 9.2
    6.0 SP1 - BEA WebLogic 8.1 SP4^
    6 - BEA WebLogic 8.1 SP4^
    5.0.5 - BEA WebLogic 8.1 SP3^

  • Cursors non closed immediately

    hello to everybody....i don't understand a thing....
    i work on application under bea weblogic 8.1 sp3 on hp with oracle 10 db.I use the prepared statemtn to insert a certain number of record.....but also when tha application finish to insert....and I close de PreparedStatement and the Connection taken by the pool ( transactional driver XA oracle 10 and transactional Data Source )...i still see the opened cursors on oracle....and then after a while them come closed....
    Th question is...why when I close the prepared statement and the connection the oracle cursors don't close immediately?

    giorgio giustiniani wrote:
    hello to everybody....i don't understand a thing....
    i work on application under bea weblogic 8.1 sp3 on hp with oracle 10 db.I use the prepared statemtn to insert a certain number of record.....but also when tha application finish to insert....and I close de PreparedStatement and the Connection taken by the pool ( transactional driver XA oracle 10 and transactional Data Source )...i still see the opened cursors on oracle....and then after a while them come closed....
    Th question is...why when I close the prepared statement and the connection the oracle cursors don't close immediately?Prepared statements offer higher performance by being re-useable. WebLogic
    will cache prepared statements along with the pooled connection they came
    from. In the same way we do not really close a pooled connection when you
    call close(), it is the same for most prepared statements. Are you using
    our pools?
    Joe

  • Complication if Hostname Verification Ignored enabled?

    Currently we are testing our application. The application need to
    connect to a remote system through an SSL connection. However,
    without the 'Hostname Verification Ignored' enabled, the application
    always received a UnknownHostException just until we enable the option
    above, the application can connect succesfully.
    The cert on the remote system is not a real cert yet (it will be once
    we move to production). However, we already add the CA into our
    trusted list. We are using JVM bundled with BEA WLS 6.1 SP3.
    The concern that our customer has right now is how it will affect
    production system? With this option enabled, is that meant any cert
    from any server will be accepted by the JVM/WLS as trusted?
    Currently looking at the trusted CA in the key ring, there are only 2
    company supported by default (Verisign and Thawte), is there any
    specific documentation on how to include another CA into WLS trusted
    list?
    Thank you,
    Irawan.

    I did some more research for the issue mentioned which I yet to get rid of.
    1) I wrote a REST web service which makes a call to another REST service deployed on another weblogic using HTTPs (same code as mentioned above is used). I delpoyed the war and made a http call to the first webservice, the other REST service was invoked successfully using HTTPs. So this confirmed that there is no problem with the certificates or keystore or hostname verifictaion.
    2) My actual application still throws the handshake exception as below -
    <Warning> <Security> <BEA-090542> <Certificate chain received from xx.yy.zz.rrr - xx.yy.zz.rrr was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
    So I think the problem is something else but weblogic is priniting the exception message wrong.
    The process hierarchy ( in UNIX ) is as shown below -
    bea 31914 31913 0 14:29 ? 00:00:00 /bin/sh <DOMAIN HOME>//bin/startWebLogic.sh
    bea 31989 31914 0 14:29 ? 00:01:25 /opt/bea/jdk160_24/bin/java <The weblogic start server process> started by startWebLogic.sh
    bea 32107 31989 0 14:29 ? 00:00:09 /opt/bea/jdk160_24/bin/java <One of custom process>
    bea 2038 32107 0 18:38 ? 00:00:15 /opt/bea/jdk160_24/bin/java <Another custom process which contains my java classes containing the REST client>
    The problem is there in both Weblogic 11 and 10.3 version.
    I will be grateful if someone gives any clue about the problem.

  • Block lock

    Does anyone have any idea what is the function of the following statement?
    select o.owner#, u.name, o.name, o.namespace, o.obj#, d.d_timestamp, nvl(d.property,0)
    from dependency$ d, obj$ o, user$ u
    where d.p_obj#=:1 and (d.p_timestamp=:2 or d.property=2) and d.d_obj#=o.obj# and o.owner#=u.user# and decode(:3,0,0,o.type#)=:3
    We are running on BEA Weblogic 6.1 sp3 and using its connection pool to manage our connections. A common processing in our application is to lock a user record, process, and issue commit to release the lock. However it seems that the execution of this statement has (or indirectly) caused a block on our application. All connections (or the database itself) kind of pause, and our application could not commit or issue new locks. Upon killing this statement, then the block is gone and our application can continue running.
    As this statement is not issued by our application, we wonder who could be the party which issues it. Whether it is Oracle, a 3rd party monitoring tool, application server or Oracle issues this due to the locking sql statements issue by application. And what is the impact of the above statement on the database.
    Would appreciate if anyone can provide some information. Thank you!
    ES

    Does anyone have any idea what is the function of the following statement?
    select o.owner#, u.name, o.name, o.namespace, o.obj#, d.d_timestamp, nvl(d.property,0)
    from dependency$ d, obj$ o, user$ u
    where d.p_obj#=:1 and (d.p_timestamp=:2 or d.property=2) and d.d_obj#=o.obj# and o.owner#=u.user# and decode(:3,0,0,o.type#)=:3
    We are running on BEA Weblogic 6.1 sp3 and using its connection pool to manage our connections. A common processing in our application is to lock a user record, process, and issue commit to release the lock. However it seems that the execution of this statement has (or indirectly) caused a block on our application. All connections (or the database itself) kind of pause, and our application could not commit or issue new locks. Upon killing this statement, then the block is gone and our application can continue running.
    As this statement is not issued by our application, we wonder who could be the party which issues it. Whether it is Oracle, a 3rd party monitoring tool, application server or Oracle issues this due to the locking sql statements issue by application. And what is the impact of the above statement on the database.
    Would appreciate if anyone can provide some information. Thank you!
    ES

Maybe you are looking for