WLS Architecture
Can anyone tell me what the best system architecture for WebLogic
Servers are?
I've heard a lot of different things. One is that if you have a Solaris
box with two processors, you should run with two instances on the same
machine. That would be alright, but we plan on implementing a clustered
environment in the future.
Another is that we should have one WebLogic Server on our Solaris box.
When we are doing load testing we are unable to saturate the CPU.
When we run the load test our execution queue rapidly increases to 50 or
60 and the response time gradually increases. Everything works fairly
well when we test with 10 to 20 users. Any more than that our
application becomes useless. Everything slows to almost a halt. If
someone could tell me what an optimal setup would be for WLS in a single
server environment is, that would be great. I've done everything by the
book. I just want to hear it from someone with more experience. I'm
hoping it's not the application that is doing this.
thanks
Chris
First, I would suggest try to find the bottleneck - It can be client machine,
the network, Database or maybe WLS. To detect it, some suggestions/pointers:
0. Monotor the resource utilization on the client machine - CPU, memory,
network etc.
1. During your test, use the WLS console to monitor the # of requests in the
input queue. On average, how many requests are there in the queue and how long
does it takes to drain them off. If there a large number of request in the
queue, it suggests that the requests are indeed arriving in the WLS otherwise
the issue may be with your client machine or your network, TCP etc.
2. Check the memory utilization. Is the system running out of memory. If so,
increase the heap size.
3. Use a profiler to detect where the bottleneck is - Database access,
interface with other resources, contention for some resources etc. (You can
monitor JDBC interaction with jdbc.log.)
4. Set the ThreadCount and Connection pool in conjunction.
Designing an optimal layout is an application specific issue.
Cheers
Venkatesh Iyer
Robert Patrick schrieb:
There are a lot of factors that go into tuning and load-testing your WLS
application. First of all, we have found that it takes somewhere between 2
and 5 times as much client hardware to drive the server to saturation. As
Srikant mentioned, the TCP device driver parameters can play a significant
role in throttling the client requests into the server(s). You might want
to get someone from BEA involved in your testing to help you work through
these issues.
Robert
Chris wrote:
Can anyone tell me what the best system architecture for WebLogic
Servers are?
I've heard a lot of different things. One is that if you have a Solaris
box with two processors, you should run with two instances on the same
machine. That would be alright, but we plan on implementing a clustered
environment in the future.
Another is that we should have one WebLogic Server on our Solaris box.
When we are doing load testing we are unable to saturate the CPU.
When we run the load test our execution queue rapidly increases to 50 or
60 and the response time gradually increases. Everything works fairly
well when we test with 10 to 20 users. Any more than that our
application becomes useless. Everything slows to almost a halt. If
someone could tell me what an optimal setup would be for WLS in a single
server environment is, that would be great. I've done everything by the
book. I just want to hear it from someone with more experience. I'm
hoping it's not the application that is doing this.
thanks
Similar Messages
-
Architectural Choice for accessing Coherence Cache Server
I am a newbie and have a coherence use-case question.
When accessing an independent coherence cache server from application code such as an EJB deployed in WLS, architecturally does one write up an entity which is then used as a sole point of
access to the resource (coherence cache server) for querying, adding, modifying entries or are the accesses to the coherence cache server split and spread among the application code.
For example,
1. I write an EJB (EJB 1) which recieves the request from other EJB's (EJB 2, EJB 3), EJB 1 runs requests from EJB2 and EJB 3 on the Coherence Cache Server and acts as the sole point of
contact to the resource.
2. EJB 2 and EJB 3 both run requests against the coherence cache server. No fixed entity in architecture repsonsible for interaction with Coherence Cache Server.
Which is more common ?stevephe wrote:
Yes you could treat Coherence as a "pluggable" resource, just like a database. But that, just like in the case of a database, wouldn't boil it down to a single entity/interface. You'd treat Coherence as a "integration tier" resource that you'd "plumb in" just like you would a database, thus shielding your application's "domain" objects from integration-level concerns. That's how I've tiered our application, although we aren't inside a container like Weblogic/WebSphere/etc. The domain objects specify their persistence requirements via a multiplicity of interfaces; those interfaces have a number of implementations in the integration tier, one set of which just happens to be a Coherence set. You can use a "registry" approach to pick up the appropriate implementations (we use Spring injection.) Have a look at the Coherence book from Apress for more details.Apress? You mean Packt, don't you?
Best regards,
Robert -
Front-end/back-end cluster question
[att1.html]
Patrick Power wrote:
> Thanx for your reply Prasad. I was surprised none of the Bea engineers
> wished to touch this one. What do you suppose is up with that? Either
> they are too busy, or possibly my question is too dumb.
>
I am from BEA so its not that we are not responding ;).
>
> Back to the issue: Yes, we will NES bridge/proxy into servlet front-end
> cluster, potentially with Directors on the very front of the topology for
> balancing. Your diagram as such:
>
> <Netscape/IIS/Apache/WLS FRONT END> ----- <CLUSTER OF WEBLOGIC SERVER
> > SERVING SERVLETS> --- <CLUSTER OF WEBLOGIC SERVERS SERVING EJB>
>
> 1) Does <Netscape/IIS/Apache/WLS FRONT END> mean NES with proxy shared lib,
> with a WLS service definition into cluster in obj.conf? I assume yes.
Yes.
>
> 2) I would assume that <CLUSTER OF WEBLOGIC SERVERS SERVING SERVLETS> would
> need the WLS HttpClusterServlet to the <CLUSTER OF WEBLOGIC SERVERS SERVING
> EJB> all the way in the back.
No. I was splitting presentation logic (namely servlets and jsp) and business
logic (ejb) into two layers. Again you don't have to split it into two. You can
colocate them both together. You could use NES or IIS or Apache or WLS. You
don't need HttpClusterServlet.
Lets get this straight.
1. You need our proxy plugin for failover and to load balance the request that
are going to presentation logic.
2. From presentation logic layer, when you talk to backend business logic
providers (like ejb cluster), if you use stateless session beans we provide
failover and load balancing. In future we will support clustered stateful
session beans as well. Therefore you don't need load balancer here.
3. HttpClusterServlet should run only in front of presentation logic cluster and
also it supports http only.
Hope this helps.
- Prasad
> The NES proxy would only proxy into the f/e
> cluster, right? You're not suggesting an external proxy of some type, are
> you? The HttpClusterServlet is for WLS cluster-to-cluster proxies.
> 3) A load balancer between the wls f/e and wls b/e clusters? That doesn't
> seem applicable here. Once again, it should be HttpClusterServlet for WLS
> cluster-to-cluster proxies.
> 4) "use two or three proxy servers to avoid single point of failure."
> Hmmm, once again - are we talking the WLS HttpClusterServlet proxy? Well,
> that's the inital question: Can I have more than one HttpClusterServlet
> proxy in the front-end cluster, proxying to the back-end cluster?
> Otherwise, internally from this WLS architecture perspective, it is a single
> point of failure.
>
> An example: 10 instances in f/e cluster. can more than one of these
> instances have the WLS HttpClusterServlet proxy to the b/e cluster? Or, are
> there instances of WLS HttpClusterServlet proxy in all 10 f/e cluster
> instances?
>
> Cheers, Pat
>
> Prasad Peddada <[email protected]> wrote in message
> news:[email protected]...
> >
> >
> > Patrick Power wrote:
> >
> > > I know that this topic was addressed to some degree here in an earlier
> > > posting, but I still have a question regarding the architecture
> > > design:
> > >
> > > If configuring a front-end cluster for servlets/sessions and a
> > > back-end cluster for remote services -- you route requests to the
> > > back-end using the WLS proxy servlet. ok, got that part.
> >
> > Not quite. The typical scenario is
> >
> > <Netscape/IIS/Apache/WLS FRONT END> ----- <CLUSTER OF WEBLOGIC SERVER
> > SERVING SERVLETS> --- <CLUSTER OF WEBLOGIC SERVERS SERVING EJB>
> >
> > You don't proxy and serve servlets from the same server.
> >
> > >
> > > The question: Is there a single instance of the wls proxy servlet in
> > > the front-end cluster? Or, is it on every instance in the front-end
> > > cluster? What is the failover mechanism, in the case of a single
> > > instance of proxy servlet in the f-e cluster failing?
> >
> > To prevent that you need to use some kind of h/w or software load
> > balancer and then use two or three proxy servers to avoid single point
> > of failure.
> >
> > > Is it a single point of failure between the 2 clusters?
> > >
> > > Thanx in advance for your help.
> > >
> > > BTW, I think Wei, Kumar and the other Bea folks cruising this group
> > > have been doing a bang-up job of providing badly-needed detail on this
> > > subject area - material this largely absent from the documentation.
> > > Good job.
> > >
> > >
> >
> > --
> > Cheers
> >
> > - Prasad
> >
> >
-
JCOM bridge and user context {principle}
I am using VB as a client, JCOM/JIntegra bridge and WLS 6.1 server. JCOM bridge
installed on the WLS maschine. I use late binding.
I have EJB component which returns to the client something based on the caller
principle. So, when I call InitialContext()from the Java/JSP client I put caller
identity object on the TLS. This caller identity object is passed to WLS and it
allows to know caller principle. This means that if I have multithreaded client
I have to call InitialContext in every thread. Well...
How can I get the same behaviour in the VB-JCOM-WLS architecture?
It seems that every call from VB JCOM execute in the different thread without
calling InitialCotext(). Thefore different VB clients get not correct data (based
on the wrong principle)
How can I overcome it ? Please helpI am using VB as a client, JCOM/JIntegra bridge and WLS 6.1 server. JCOM bridge
installed on the WLS maschine. I use late binding.
I have EJB component which returns to the client something based on the caller
principle. So, when I call InitialContext()from the Java/JSP client I put caller
identity object on the TLS. This caller identity object is passed to WLS and it
allows to know caller principle. This means that if I have multithreaded client
I have to call InitialContext in every thread. Well...
How can I get the same behaviour in the VB-JCOM-WLS architecture?
It seems that every call from VB JCOM execute in the different thread without
calling InitialCotext(). Thefore different VB clients get not correct data (based
on the wrong principle)
How can I overcome it ? Please help -
Choose a specific target managed server on OEPE
I have a domain with three weblogic managed server.
I use OEPE with WLS 10.3.6 and I want to choose a specific managed server as a target for a specific eclipse web project.
Is that possible?
Today OEPE can add (deploy) my project package (WAR or EAR) to all managed servers. Even when I delete or change the package target from a managed server, when I do a republish operation on WL Server (via OEPE) the package is redeployed to all managed server.
Thanks.
Edited by: Tuelho on Jul 30, 2012 5:04 PMHello,
Have you tried to delete the application, select the managed server and then publish it again? In order to test in my environment I'd need to create a managed server within my domain as I currently have just one where I deploy.
Not being an expert on WLS architecture, what's the benefit of having various managed servers within a domain? Is it parallelism?
Thanks
Juan Camilo -
The web docs talk about modifying RMI/IIOP applications to use WTC.
Just need a confirmation that RMI/IIOP calls to EJBs in WLS will not be
transactional. That XA transactions will require the ATMI interface to
Tuxedo EJBs. (Beta in WLS 6.1)Carl,
I for one would be interested to hear how you are using the Tuxedo/WTC (I
assume you mean Java ATMI) in your application. We need some feedback here
in development land so that we can see which things you like about jATMI and
which things you like less...
Of course, anyone using jATMI can reply as well...
John Wells (Aziz)
[email protected]
[email protected]
"Carl Lawstuen" <[email protected]> wrote in message
news:3bba357d$[email protected]..
Thanks for the clarification. While we will need to support CORBA style
access at some time, the Tuxedo/WTC interface fits nicely in our current
legacy to WLS architecture.
"Andy Piper" <[email protected]> wrote in message
news:[email protected]..
"Carl Lawstuen" <[email protected]> writes:
Yes, the ATMI interface to WTC should be transactional.
But I would assume that RMI/IIOP applications that uses WTC for access
to
WLS naming service would not be transactional due to limitations in
the
RMI/IIOP specification regarding transactions.
Just looking for confirmation that BEA has not done anything to make
RMI/IIOP calls into WLS transactional.RMI-IIOP calls over wtc (i.e. RMI-TGIOP) are transactional and
secure. RMI-IIOP calls over vanilla IIOP are not transactional, but
can be secure. OTS support is coming in Acadia.
RMI-IIOP over wtc totally leverages the ATMI support so you get all
the same features + CORBA-style access. The RMI-IIOP spec is fairly
irrelevant in this instance since we do not have to to support
interoperable transactions to support transaction propagation from Tux
over WTC. That's kind of the whole point - the specs have their rough
edges when it comes to defining transactions and security over IIOP
but we give you exactly what you want (transactions and security)
using the internal tux domains protocol.
andy -
WLS 7.0 - util jars being accessed from the war file
Some of classes in the warfile (servlets) need access to some of the util jars in my ear file. I really don't want to put them in the war file/WEB-INF/lib directory and in the ear file. Is there any way to do this without putting them in the classpath.
Any info would be appreciated.
Thanks,
IanIan,
Examine the following link on packaging utility classes and the Weblogic classloader
architecture
This link should provide (hopefully :-) ) the answer to your question
http://e-docs.bea.com/wls/docs70/programming/classloading.html
Chuck Nelson
DRE
BEA Technical Support -
WLS 8.1SP2 and AIX 5.1.0.0
After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
I am still unable to bring up my server. The following error occurs:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
<This server is being started as the administration server.>
<May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
domainconfiguration from configuration repository at
/users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
<May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
serverlog file
/users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
opened. All server side log events will be written to this file.>
<May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
initializing using security realm myrealm.>
<May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
t
JVMDG215: Dump Handler has Processed Exception Signal 11.
System Information for dixie
MODEL Bull ESCALA T (e8ED)
CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
MEM 2304 MB real memory
FIRM 03.03.09
OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
KERN System currently booted on 32 bits kernel
Attached is the Java core file
Any ideas?
Eric
[javacore37624.1083785465.txt]BEA currently supports AIX 5.1 ML-4. Your configuration is ML-5.
Eric Hardesty wrote:
After installing WLS 8.1 and the AIX supplement patch plus fixes to java1.4
I am still unable to bring up my server. The following error occurs:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<May 5, 2004 1:29:26 PM MDT> <Info> <WebLogicServer> <BEA-000377> <Starting
WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<May 5, 2004 1:29:28 PM MDT> <Info> <Configuration Management> <BEA-150016>
<This server is being started as the administration server.>
<May 5, 2004 1:29:28 PM MDT> <Info> <Management> <BEA-141107> <Version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284WebLogic XMLX
Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<May 5, 2004 1:29:30 PM MDT> <Notice> <Management> <BEA-140005> <Loading
domainconfiguration from configuration repository at
/users/interop8/bea/user_projects/domain/hooxsgb/./config.xml.>
<May 5, 2004 1:29:49 PM MDT> <Notice> <Log Management> <BEA-170019> <The
serverlog file
/users/interop8/bea/user_projects/domain/hooxsgb/myserver/myserver.logis
opened. All server side log events will be written to this file.>
<May 5, 2004 1:30:08 PM MDT> <Notice> <Security> <BEA-090082> <Security
initializing using security realm myrealm.>
<May 5, 2004 1:30:09 PM MDT> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "hooxsgb">
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to
/users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.tx
t
JVMDG215: Dump Handler has Processed Exception Signal 11.
System Information for dixie
MODEL Bull ESCALA T (e8ED)
CPU 4 x K45, 32 bits (360.0 MH) ** 4 enabled **
MEM 2304 MB real memory
FIRM 03.03.09
OS AIX 5.1.0.0 [Fix level 58] [Maintenance level 05]
KERN System currently booted on 32 bits kernel
Attached is the Java core file
Any ideas?
Eric
NULL ------------------------------------------------------------------------
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO signal 11 received
1TIDATETIME Date: 2004/05/05 at 12:31:05
1TIFILENAME Javacore filename: /users/interop8/bea/user_projects/domain/hooxsgb/javacore37624.1083785465.txt
NULL ------------------------------------------------------------------------
0SECTION XHPI subcomponent dump routine
NULL ==============================
1XHTIME Wed May 5 12:31:05 2004
1XHSIGRECV SIGSEGV received at 0xd3a96f54 in /usr/java14/jre/bin/classic/libjvm.a. Processing terminated.
1XHFULLVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
NULL
1XHCURRENTTHD Current Thread Details
NULL ----------------------
2XHCURRSYSTHD "ListenThread.Default" sys_thread_t:0x41C0F228
3XHNATIVESTACK Native Stack
NULL ------------
3XHSTACKLINE at 0xD46194CC in Java_weblogic_socket_PosixSocketMuxer_initNative
3XHSTACKLINE at 0xD3A96F54 in mmipInvoke_V_V
3XHSTACKLINE at 0xD3A909B0 in mmipInvokeLazyJniMethod
3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
3XHSTACKLINE at 0xD3A54BBC in xeRunJvmMethod
3XHSTACKLINE at 0xD3A47628 in JVM_NewInstanceFromConstructor
3XHSTACKLINE at 0xD3C5658C in Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0
3XHSTACKLINE at 0xD3A9641C in mmipInvoke_OO_O
3XHSTACKLINE at 0xD3A5CBD8 in mmipExecuteJava
3XHSTACKLINE at 0xD3BBCDF8 in mmijExecuteJavaFromJIT
3XHSTACKLINE at 0xD3C8AC90 in jit_init_memory_locks_md
NULL
1XHOPENV Operating Environment
NULL ---------------------
2XHHOSTNAME Host : dixie.gpv.az05.bull.com:141.112.17.150
2XHOSLEVEL OS Level : AIX 5.1.0.0
2XHCPUS Processors -
3XHCPUARCH Architecture : POWER_PC (impl: POWER_604, ver: PV_604)
3XHNUMCPUS How Many : 4
3XHCPUSENABLED Enabled : 4
NULL
1XHUSERLIMITS User Limits (in bytes except for NOFILE and NPROC) -
NULL -----------
2XHUSERLIMIT RLIMIT_FSIZE : infinity
2XHUSERLIMIT RLIMIT_DATA : 2147483645
2XHUSERLIMIT RLIMIT_STACK : 33554432
2XHUSERLIMIT RLIMIT_CORE : 1073741312
2XHUSERLIMIT RLIMIT_NOFILE : infinity
2XHLIMIT NPROC(max) : 4000
NULL
1XHPAGESPACES Page Space (in blocks) -
NULL ----------
2XHPAGESPACE /dev/hd6: size=200704, free=199709
2XHPAGESPACE /dev/paging00: size=196608, free=196495
2XHPAGESPACE /dev/paging01: size=196608, free=196495
NULL
1XHSIGHANDLERS JVM Signal Handlers
NULL -------------------
2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGPIPE : ignored
2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
NULL
1XHSIGHANDLERS Chained Signal Handlers
NULL -----------------------
2XHSIGHANDLER SIGHUP : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGINT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGQUIT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGILL : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGTRAP : JITSigTrapHandler (libjitc.a)
2XHSIGHANDLER SIGABRT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGEMT : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGFPE : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGBUS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSEGV : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGSYS : intrDispatchMD (libhpi.a)
2XHSIGHANDLER SIGPIPE : ignored
2XHSIGHANDLER SIGTERM : intrDispatchMD (libhpi.a)
NULL
1XHENVVARS Environment Variables
NULL ---------------------
2XHENVVAR _=/usr/java14/bin/java
2XHENVVAR JAVA_VENDOR=IBM
2XHENVVAR LANG=en_US
2XHENVVAR TMOUT2=43200
2XHENVVAR PRODUCTION_MODE=
2XHENVVAR LOGIN=interop8
2XHENVVAR CLASSPATHSEP=:
2XHENVVAR PAGER=more
2XHENVVAR POINTBASE_HOME=/users/interop8/bea/weblogic81/common/eval/pointbase
2XHENVVAR PATH=/users/interop8/bea/weblogic81/server/bin:/usr/java14/jre/bin:/usr/java14/bin:/users/interop8/GCOSInterop/dsad/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin::/app/oracle/product/8.1.7/bin:/usr/local/bin:/usr/lbin:/users/interop8/jte/bin
2XHENVVAR RES_RETRY=1
2XHENVVAR JTE_BASE=/users/interop8/jte
2XHENVVAR JAVA_VM=
2XHENVVAR LC__FASTMSG=true
2XHENVVAR POINTBASE_CLASSPATH=:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar
2XHENVVAR CGI_DIRECTORY=/var/docsearch/cgi-bin
2XHENVVAR EDITOR=vi
2XHENVVAR EXINIT=set tabstop=4
2XHENVVAR HISTFILE=/users/interop8/.sh_history
2XHENVVAR CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
2XHENVVAR LOGNAME=interop8
2XHENVVAR RES_TIMEOUT=2
2XHENVVAR MAIL=/usr/spool/mail/interop8
2XHENVVAR ETC_PROFILE=1
2XHENVVAR POINTBASE_TOOLS=/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbtools44.jar
2XHENVVAR LOCPATH=/usr/lib/nls/loc
2XHENVVAR ORACLE_SID=demo
2XHENVVAR PS1=[dixie] (interop8).${PWD#${HOME}}>
2XHENVVAR PATHSEP=:
2XHENVVAR USER=interop8
2XHENVVAR DOCUMENT_SERVER_MACHINE_NAME=localhost
2XHENVVAR AUTHSTATE=compat
2XHENVVAR BEA_HOME=/users/interop8/bea
2XHENVVAR DEFAULT_BROWSER=netscape
2XHENVVAR DISPLAY=harp.gpv.az05.bull.com:0
2XHENVVAR SHELL=/bin/ksh
2XHENVVAR ODMDIR=/etc/objrepos
2XHENVVAR JAVA_HOME=/usr/java14
2XHENVVAR DOCUMENT_SERVER_PORT=49213
2XHENVVAR TMOUT=43200
2XHENVVAR HOME=/users/interop8
2XHENVVAR MEM_ARGS=-Xms32m -Xmx200m
2XHENVVAR WEBLOGIC_CLASSPATH=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar
2XHENVVAR TERM=vt220
2XHENVVAR MAILMSG=[YOU HAVE NEW MAIL]
2XHENVVAR ORACLE_HOME=/app/oracle/product/8.1.7
2XHENVVAR ITECONFIGSRV=/etc/IMNSearch
2XHENVVAR PWD=/users/interop8/bea/user_projects/domain/hooxsgb
2XHENVVAR DOCUMENT_DIRECTORY=/usr/docsearch/html
2XHENVVAR TZ=MST7
2XHENVVAR ITECONFIGCL=/etc/IMNSearch/clients
2XHENVVAR WL_HOME=/users/interop8/bea/weblogic81
2XHENVVAR ITE_DOC_SEARCH_INSTANCE=search
2XHENVVAR A__z=! TMOUT2=! LOGNAME=! ETC_PROFILE="*TMOUT
2XHENVVAR _IBM_JAVA_PIPE_37624=
2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_OLD_VALUE=
2XHENVVAR IBM_JVM_AIXTHREAD_SCOPE_NEW_VALUE=S
2XHENVVAR AIXTHREAD_SCOPE=S
2XHENVVAR IBM_JVM_CHANGED_ENVVARS_37624=AIXTHREAD_SCOPE,LDR_CNTRL
2XHENVVAR IBM_JVM_LDR_CNTRL_OLD_VALUE=
2XHENVVAR IBM_JVM_LDR_CNTRL_NEW_VALUE=MAXDATA=0x80000000
2XHENVVAR LDR_CNTRL=MAXDATA=0x80000000
2XHENVVAR LIBPATH=/usr/java14/jre/bin:/usr/java14/jre/bin/classic:/usr/java14/jre/bin:/app/oracle/product/8.1.7}/lib:/users/interop8/bea/weblogic81/server/lib/aix
2XHENVVAR NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/opt/Xprint/MSG/%l/%N:/opt/Xprint/mercator/MSG/%l/%N:/var/spool/Xprint/config/MSG/%l/%N:/var/spool/Xprint/config/mercator/MSG/%l/%N
2XHENVVAR _IBM_ENV_INITIAL_37624=807444056
2XHENVVAR IBM_JAVA_COMMAND_LINE=/usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava..security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
NULL
1XHLOADEDLIBS Loaded Libraries (sizes in bytes)
NULL ---------------------------------
2XHLIBNAME /users/interop8/bea/weblogic81/server/lib/aix/libmuxer.so
3XHLIBSIZE filesize : 20757
3XHLIBSTART text start : 0xD4618000
3XHLIBLDSIZE text size : 0x282E
3XHLIBLDORG data start : 0x41E97CF4
3XHLIBLDDATASZ data size : 0x2AC
2XHLIBNAME /usr/java14/jre/bin/libnio.a
3XHLIBSIZE filesize : 61140
3XHLIBSTART text start : 0xD460F000
3XHLIBLDSIZE text size : 0x8925
3XHLIBLDORG data start : 0x408A5598
3XHLIBLDDATASZ data size : 0x50C
2XHLIBNAME /usr/java14/jre/bin/libnet.a
3XHLIBSIZE filesize : 122155
3XHLIBSTART text start : 0xD45F9000
3XHLIBLDSIZE text size : 0x1437A
3XHLIBLDORG data start : 0x3F592990
3XHLIBLDDATASZ data size : 0x820
2XHLIBNAME /usr/java14/jre/bin/libjitc.a
3XHLIBSIZE filesize : 2760315
3XHLIBSTART text start : 0xD3C7D000
3XHLIBLDSIZE text size : 0x2330F6
3XHLIBLDORG data start : 0x3E055F40
3XHLIBLDDATASZ data size : 0x1A8A4
2XHLIBNAME /usr/lib/libi18n.a
3XHLIBSIZE filesize : 148825
3XHLIBSTART text start : 0xD007A100
3XHLIBLDSIZE text size : 0xA1AE
3XHLIBLDORG data start : 0x3DFF2A18
3XHLIBLDDATASZ data size : 0x1290
2XHLIBNAME /usr/lib/nls/loc/en_US
3XHLIBSIZE filesize : 14342
3XHLIBSTART text start : 0xD0074000
3XHLIBLDSIZE text size : 0x2D71
3XHLIBLDORG data start : 0xD0077130
3XHLIBLDDATASZ data size : 0x2324
2XHLIBNAME /usr/java14/jre/bin/libzip.a
3XHLIBSIZE filesize : 109272
3XHLIBSTART text start : 0xD3C69000
3XHLIBLDSIZE text size : 0x1349A
3XHLIBLDORG data start : 0x3D80F398
3XHLIBLDDATASZ data size : 0x1908
2XHLIBNAME /usr/java14/jre/bin/classic/libcore.a
3XHLIBSIZE filesize : 172361
3XHLIBSTART text start : 0xD3C4E000
3XHLIBLDSIZE text size : 0x1AE66
3XHLIBLDORG data start : 0x3D801610
3XHLIBLDDATASZ data size : 0xD934
2XHLIBNAME /usr/java14/jre/bin/libhpi.a
3XHLIBSIZE filesize : 159668
3XHLIBSTART text start : 0xD3C36000
3XHLIBLDSIZE text size : 0x17708
3XHLIBLDORG data start : 0x3025DCC8
3XHLIBLDDATASZ data size : 0x1420
2XHLIBNAME /usr/java14/jre/bin/libxhpi.a
3XHLIBSIZE filesize : 44366
3XHLIBSTART text start : 0xD3C2F000
3XHLIBLDSIZE text size : 0x6578
3XHLIBLDORG data start : 0x3024E058
3XHLIBLDDATASZ data size : 0xE51C
2XHLIBNAME /usr/lib/libdl.a
3XHLIBSIZE filesize : 5248
3XHLIBSTART text start : 0xD070D0F8
3XHLIBLDSIZE text size : 0x1E0
3XHLIBLDORG data start : 0x3024D0F8
3XHLIBLDDATASZ data size : 0x0
2XHLIBNAME /usr/java14/jre/bin/libjsig.a
3XHLIBSIZE filesize : 13751
3XHLIBSTART text start : 0xD3C2D000
3XHLIBLDSIZE text size : 0x1B6E
3XHLIBLDORG data start : 0x3024C2F8
3XHLIBLDDATASZ data size : 0x1D0
2XHLIBNAME /usr/java14/jre/bin/libjava.a
3XHLIBSIZE filesize : 197639
3XHLIBSTART text start : 0xD3C10000
3XHLIBLDSIZE text size : 0x1CE78
3XHLIBLDORG data start : 0x30239690
3XHLIBLDDATASZ data size : 0x132C
2XHLIBNAME /usr/java14/jre/bin/classic/libjvm.a
3XHLIBSIZE filesize : 2698157
3XHLIBSTART text start : 0xD3A28000
3XHLIBLDSIZE text size : 0x1E71F8
3XHLIBLDORG data start : 0x302111E0
3XHLIBLDDATASZ data size : 0x27BE4
2XHLIBNAME /usr/lib/libiconv.a
3XHLIBSIZE filesize : 377974
3XHLIBSTART text start : 0xD0085100
3XHLIBLDSIZE text size : 0x1403A
3XHLIBLDORG data start : 0xF0317ED0
3XHLIBLDDATASZ data size : 0xA544
2XHLIBNAME /usr/lib/libbsd.a
3XHLIBSIZE filesize : 63178
3XHLIBSTART text start : 0xD01504C0
3XHLIBLDSIZE text size : 0x8183
3XHLIBLDORG data start : 0xF0169FB0
3XHLIBLDDATASZ data size : 0x1350
2XHLIBNAME /usr/lib/libpthreads.a
3XHLIBSIZE filesize : 912571
3XHLIBSTART text start : 0xD0047000
3XHLIBLDSIZE text size : 0x2B5BD
3XHLIBLDORG data start : 0xF0139000
3XHLIBLDDATASZ data size : 0x5020
2XHLIBNAME /usr/lib/libpthreads.a
3XHLIBSIZE filesize : 912571
3XHLIBSTART text start : 0xD0043000
3XHLIBLDSIZE text size : 0x38B1
3XHLIBLDORG data start : 0xF00D6000
3XHLIBLDDATASZ data size : 0x62318
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD0521560
3XHLIBLDSIZE text size : 0x1F983
3XHLIBLDORG data start : 0xF01E9560
3XHLIBLDDATASZ data size : 0x6578
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD0507E20
3XHLIBLDSIZE text size : 0x1846B
3XHLIBLDORG data start : 0xF01DFE20
3XHLIBLDDATASZ data size : 0x8511
2XHLIBNAME /usr/lib/libC.a
3XHLIBSIZE filesize : 6961880
3XHLIBSTART text start : 0xD04E7100
3XHLIBLDSIZE text size : 0x1F75A
3XHLIBLDORG data start : 0xF01DB700
3XHLIBLDDATASZ data size : 0x3019
2XHLIBNAME /usr/lib/libcrypt.a
3XHLIBSIZE filesize : 11059
3XHLIBSTART text start : 0xD00730F8
3XHLIBLDSIZE text size : 0x86E
3XHLIBLDORG data start : 0xF00D5530
3XHLIBLDDATASZ data size : 0x128
2XHLIBNAME /usr/lib/libc.a
3XHLIBSIZE filesize : 6806102
3XHLIBSTART text start : 0xD01D5640
3XHLIBLDSIZE text size : 0x1FDB9F
3XHLIBLDORG data start : 0xF0042520
3XHLIBLDDATASZ data size : 0x91B58
NULL
NULL ------------------------------------------------------------------------
0SECTION CI subcomponent dump routine
NULL ============================
1CIJAVAVERSION J2RE 1.4.1 IBM AIX build ca1411-20030930
1CIRUNNINGAS Running as a standalone JVM
1CICMDLINE /usr/java14/bin/java -Xms32m -Xmx200m -Dweblogic.Name=myserver -Dweblogic.ProductionModeEnabled= -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
1CIJAVAHOMEDIR Java Home Dir: /usr/java14/jre
1CIJAVADLLDIR Java DLL Dir: /usr/java14/jre/bin
1CISYSCP Sys Classpath: /usr/java14/jre/lib/core.jar:/usr/java14/jre/lib/graphics.jar:/usr/java14/jre/lib/security.jar:/usr/java14/jre/lib/server.jar:/usr/java14/jre/lib/xml.jar:/usr/java14/jre/lib/charsets.jar:/usr/java14/jre/classes
1CIUSERARGS UserArgs:
2CIUSERARG vfprintf 0x30000B94
2CIUSERARG -Xms32m
2CIUSERARG -Xmx200m
2CIUSERARG -Dweblogic.Name=myserver
2CIUSERARG -Dweblogic.ProductionModeEnabled=
2CIUSERARG -Djava.security.policy=/users/interop8/bea/weblogic81/server/lib/weblogic.policy
2CIUSERARG -Dinvokedviajava
2CIUSERARG -Djava.class.path=/usr/java14/lib/tools.jar:/users/interop8/bea/weblogic81/server/lib/weblogic_sp.jar:/users/interop8/bea/weblogic81/server/lib/weblogic.jar:/users/interop8/bea/weblogic81/server/lib/ojdbc14.jar::/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/users/interop8/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/usr/java14/jre/lib/rt.jar:/users/interop8/bea/weblogic81/server/lib/webservices.jar:
2CIUSERARG vfprintf
NULL
1CIJVMMI JVM Monitoring Interface (JVMMI)
NULL ------------------------
2CIJVMMIOFF No events are enabled.
NULL
NULL ------------------------------------------------------------------------
0SECTION DC subcomponent dump routine
NULL ============================
1DCHEADEREYE Header eye catcher DCST
1DCHEADERLEN Header length 24
1DCHEADERVER Header version 1
1DCHEADERMOD Header modification 0
1DCINTERFACE DC Interface at 0x3022270C with 15 entries
2DCINTERFACE 1 - dcCString2JavaString 0x3021EA7C
2DCINTERFACE 2 - dcInt642CString 0x3021EA88
2DCINTERFACE 3 - dcJavaString2NewCString 0x3021EA94
2DCINTERFACE 4 - dcJavaString2CString 0x3021EAA0
2DCINTERFACE 5 - dcJavaString2NewPlatformString 0x3021EAAC
2DCINTERFACE 6 - dcJavaString2UTF 0x3021EAB8
2DCINTERFACE 7 - dcPlatformString2JavaString 0x3021EAD0
2DCINTERFACE 8 - dcUnicode2UTF 0x3021EADC
2DCINTERFACE 9 - dcUnicode2UTFLength 0x3021EAE8
2DCINTERFACE 10 - dcUTF2JavaString 0x3021EAF4
2DCINTERFACE 11 - dcUTFClassName2JavaString 0x3021EB00
2DCINTERFACE 12 - dcJavaString2ClassName 0x3021EAC4
2DCINTERFACE 13 - dcUTF2UnicodeNext 0x3021EB0C
2DCINTERFACE 14 - dcVerifyUTF8 0x3021EB18
2DCINTERFACE 15 - dcDumpRoutine 0x3021EB24
1DCARRAYINFO Array info at 0x302131B8 with 16 entries
2DCARRAYINFO 1 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 2 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 3 - index 2 signature L name class[] factor 4
2DCARRAYINFO 4 - index 0 signature 0 name N/A factor 0
2DCARRAYINFO 5 - index 4 signature Z name bool[] factor 1
2DCARRAYINFO 6 - index 5 signature C name char[] factor 2
2DCARRAYINFO 7 - index 6 signature F name float[] factor 4
2DCARRAYINFO 8 - index 7 signature D name double[] factor 8
2DCARRAYINFO 9 - index 8 signature B name byte[] factor 1
2DCARRAYINFO 10 - index 9 signature S name short[] factor 2
2DCARRAYINFO 11 - index 10 signature I name int[] factor 4
2DCARRAYINFO 12 - index 11 signature J name long[] factor 8
2DCARRAYINFO 13 - index 0 signature 0 name uint[] factor 0
2DCARRAYINFO 14 - index 0 signature 0 name uint1[] factor 0
2DCARRAYINFO 15 - index 0 signature 0 name uint2[] factor 0
2DCARRAYINFO 16 - index 0 signature 0 name uint3[] factor 0
NULL ------------------------------------------------------------------------
0SECTION DG subcomponent dump routine
NULL ============================
1DGTRCENABLED Trace enabled: No
1DGJDUMPBUFF Javadump buffer size (allocated): 2621440
NULL ------------------------------------------------------------------------
0SECTION ST subcomponent dump routine
NULL ============================
1STGCMODES Resettable GC: No
1STGCMODES Concurrent GC: No
1STCURHBASE Current Heap Base: 302801fc
1STCURHLIM Current Heap Limit: 3281fbfc
1STMWHBASE Middleware Heap Base: 302801fc
1STMWHLIM Middleware Heap Limit: 3281fbfc
1STGCHELPERS Number of GC Helper Threads: 3
1STJVMOPTS -Xconcurrentlevel: 0
1STJVMOPTS -Xconcurrentbackground: 0
1STGCCTR GC Counter: 7
1STAFCTR AF Counter: 7
1STHEAPFREE Bytes of Heap Space Free: 80db00
1STHEAPALLOC Bytes of Heap Space Allocated: 259fa00
1STSMBASE SM Base: 0
1STSMEND SM End: 0
1STPAMSTART PAM Start: 0
1STPAMEND PAM End: 0
1STCOMACTION Compact Action: 0
NULL ------------------------------------------------------------------------
0SECTION XE subcomponent dump routine
NULL ============================
1XETHRESHOLD MMI threshold for java methods is set to 1250
1XEJITINIT JIT is initialized
1XEJVMPIOFF JVMPI is not activated
1XEJNITHRESH MMI threshold for JNI methods is set to 0
1XETRCHIS Trace history length is set to 4
1XEJITDUMP JIT dump routine is not yet implemented.
NULL ------------------------------------------------------------------------
0SECTION LK subcomponent dump routine
NULL ============================
NULL
1LKPOOLINFO Monitor pool info:
2LKPOOLINIT Initial monitor count: 32
2LKPOOLEXPNUM Minimum number of free monitors before expansion: 5
2LKPOOLEXPBY Pool will next be expanded by: 24
2LKPOOLTOTAL Current total number of monitors: 48
2LKPOOLFREE Current number of free monitors: 9
NULL
1LKMONPOOLDUMP Monitor Pool Dump (flat & inflated object-monitors):
2LKMONINUSE sys_mon_t:0x3020EE28 infl_mon_t: 0x3020E918:
3LKMONOBJECT java.lang.ref.Reference$Lock@303017F0/303017F8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "Reference Handler" (0x3D9C6A28)
2LKMONINUSE sys_mon_t:0x3020EED8 infl_mon_t: 0x3020E940:
3LKMONOBJECT java.lang.ref.ReferenceQueue$Lock@30301528/30301530: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "Finalizer" (0x3DA50CA8)
2LKMONINUSE sys_mon_t:0x3020EF88 infl_mon_t: 0x3020E968:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9830/302E9838: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" (0x3EDB86A8)
2LKMONINUSE sys_mon_t:0x3020F038 infl_mon_t: 0x3020E990:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9798/302E97A0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" (0x3EDB8D28)
2LKMONINUSE sys_mon_t:0x3020F0E8 infl_mon_t: 0x3020E9B8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9700/302E9708: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.Default'" (0x3EDC2528)
2LKMONINUSE sys_mon_t:0x3020F198 infl_mon_t: 0x3020E9E0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9668/302E9670: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" (0x3EDD1EA8)
2LKMONINUSE sys_mon_t:0x3020F248 infl_mon_t: 0x3020EA08:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E95D0/302E95D8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '4' for queue: 'weblogic.kernel.Default'" (0x3EDD4528)
2LKMONINUSE sys_mon_t:0x3020F2F8 infl_mon_t: 0x3020EA30:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9538/302E9540: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '5' for queue: 'weblogic.kernel.Default'" (0x3EDD98A8)
2LKMONINUSE sys_mon_t:0x3020F3A8 infl_mon_t: 0x3020EA58:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E94A0/302E94A8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" (0x3EDDCF28)
2LKMONINUSE sys_mon_t:0x3020F458 infl_mon_t: 0x3020EA80:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9408/302E9410: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '7' for queue: 'weblogic.kernel.Default'" (0x3EDE0528)
2LKMONINUSE sys_mon_t:0x3020F508 infl_mon_t: 0x3020EAA8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9370/302E9378: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '8' for queue: 'weblogic.kernel.Default'" (0x3EDE2BA8)
2LKMONINUSE sys_mon_t:0x3020F5B8 infl_mon_t: 0x3020EAD0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E92D8/302E92E0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" (0x3EDE8428)
2LKMONINUSE sys_mon_t:0x3020F668 infl_mon_t: 0x3020EAF8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9240/302E9248: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" (0x3EDE8A28)
2LKMONINUSE sys_mon_t:0x3020F718 infl_mon_t: 0x3020EB20:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E91A8/302E91B0: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" (0x3EDF5E28)
2LKMONINUSE sys_mon_t:0x3020F7C8 infl_mon_t: 0x3020EB48:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9110/302E9118: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '12' for queue: 'weblogic.kernel.Default'" (0x3EDF94A8)
2LKMONINUSE sys_mon_t:0x3020F878 infl_mon_t: 0x3020EB70:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E9078/302E9080: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '13' for queue: 'weblogic.kernel.Default'" (0x3EDFCAA8)
2LKMONINUSE sys_mon_t:0x3020F928 infl_mon_t: 0x3020EB98:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8FE0/302E8FE8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" (0x3EE000A8)
2LKMONINUSE sys_mon_t:0x3020F9D8 infl_mon_t: 0x3020EBC0:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8F48/302E8F50: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '0' for queue: 'weblogic.kernel.System'" (0x3EE03728)
2LKMONINUSE sys_mon_t:0x3020FA88 infl_mon_t: 0x3020EBE8:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8EB0/302E8EB8: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '1' for queue: 'weblogic.kernel.System'" (0x3EE06D28)
2LKMONINUSE sys_mon_t:0x3020FB38 infl_mon_t: 0x3020EC10:
3LKMONOBJECT weblogic.kernel.ExecuteThread@302E8E18/302E8E20: <unowned>
3LKNOTIFYQ Waiting to be notified:
3LKWAITNOTIFY "ExecuteThread: '2' for queue: 'weblogic.kernel.System'" (0x3EE0A328)
2LKMONINUSE sys_mon_t:0x3020FBE8 infl_mon_t: 0x3020EC38:
3LKMON -
Is WLS 12.1.2 or 12.1.3 supported on RH Linux 5.9 64bit
Hi,
We are planning to upgrade WLS 11g to WLS 12.1.2 or .3. The linux server we have is 5.9 64bit. Is this a supported configuration?
Thanks
RizHi Riz,
according to
http://www.oracle.com/technetwork/middleware/fusion-middleware/documentation/fmw-1213certmatrix-2226694.xls
WLS 12.1.3 is certified with RHEL 5 update 6+ in 64-bit architecture.
Cheers,
A. -
SOA 10.1.3.5.1 certified with WLS 10.3.2
You can download and run WLS 10.3.2 but only deploy SOA SUITE 10.1.3.5.1 to WLS 10.3.1.
Why can't Oracle synchronize the release of their products. I am not sure what path to pursue ! We are already using WLS 10.3.2 from other reasons and would rather not downgrade.
If you take a look at the "Oracle Fusion Middleware 10g Release 3 (10.1.3.5.1) Certification matrix, it is saying that you can only run 10.1.3.5.1 on WLS 10.3.1 and it should be Intel EM64T.
Does that mean I can not install it on Unbreakable linux 5 update 4 on a 32 bit i386 architecture.It is actually the case that you can not install soa suite 10.1.3.5.1 on WLS 10.3.2, and it is impossible to find out whether this is a part of Oracle's development plans, unfortunately.
I suppose that we still are many out there that actually are forced to work with the old versions for a while.
/jan -
WebCenter Content Architecture
Hello everyone,
I just need an advice on how to solve a particular client's document management requirement. Need help on a good (if not best) architecture for their case.
In a nutshell, they have satellite/offsite branches that can receive documents from their customers. They want to get those documents digitized and kept in a doc. mgmt. solution. I've looked into some implementation examples from this site: http://docs.oracle.com/cd/E10316_01/cs/cs_doc_10/implementation/wwhelp/wwhimpl/js/html/wwhelp.htm
but there's no WCC configuration where a content contributor is outside the client's intranet (or extranet). Is it ok to just have one Content Server in the head office/data center, and the branches can connect to WCC (client-server mode) from a different geographical location? Or should there be a branch content server where scanning is available?
Hope you can throw in some ideas.
Thanks,
JasonThank you for the explanation! I've commented inline on some of the items.
Well, I don't know. This very much depends on what requirements
> get those documents digitized and kept in a doc. mgmt. solution
and
> a content contributor is outside the client's intranet
really mean.
The process basically is that customers go to either the head office or satellite branches to file an application. In order for the application to be processed, supporting documents must be presented. Currently, the client is photocopying these documents and filing away manually in cabinets. If an application needs to be reviewed again later, they need to sift through their storage.
Since they can accept applications from different locations, scanning and indexing (or in WCC, uploading/checking-in) of documents will be outside the data center where WCC will reside.
a) It is certainly true that WebCenter Content is a centralized, not distributed system.
OK, noted!
b) There are few exceptions (that might be irrelevant to your use case)
Desktop Integration Suite supports also offline mode (for reading, but even updates of documents)
Some news from PM suggest that the new 11.1.1.8 release will support mobile solutions, where content can be ingested even in offline mode (where a mobile device has no signal)
The mobile support will definitely be great as some branches have limited physical space. Although, I might put this in the backburner for now.
However, those scenarios are usually only for exceptions - you cannot expect that a remote site would work with a single DIS client and/or mobile device.c) ODDC is also a centralized solution, but you could have one ODDC server per branch, if necessary, supplemented by ODC. However, ODC/ODDC can be used only for content ingestion (scanning/importing documents, initial metadata). Once a document is committed to a content repository, it is (usually) no longer available. Besides, there is no support for scenarios like searching, revisions, content retrieval, etc.d) Even though, WCC is a centralized system, it does not mean that you could not try to implement a distributed scenario using content migration/replication (Archiver utility). There are, however, two main reasons against it:
Costs - CPU/NUP license model is very effective for a centralized solution, because you can benefit from synergy effects of clustering. I remember a project where we had 80+ branches, altogether with 4K+ users that could run on something like 4 CPUs (eq. to 200 NUPs), if centralized
Manageability - everyone in OCS (Oracle Consulting Services) strongly discouraged us from any distributed design. Imagine a star architecture, where you have one central node containing everything, and a number of smaller branch systems containing items "belonging" to the branch. Unless the product supports a distributed locking (check-out) you can easily end up with inconsistent data. Again, there can be exceptions - in our case, we had just one revision, data were synchronized overnight and it could never happen that data was updated by anyone, but the branch that "owned" them.
In our case, the issue was the internet connectivity, and fortunately, we were finally able to convince the customer to solve the root cause, rather than go with an overkill architecture.
I think the architecture can survive with just one ODDC server where branches (not that many) can connect and send scanned documents to. There are no hard requirements on revisions yet. I also need an application to actually encode the customer's application, and is thinking of a custom-made ADF application, deployed on the WLS where WCC will run on. Or can I just create pages on WCC and expose that?
IMHO,
> a content contributor is outside the client's intranet (or extranet)
is not an argument for a distributed architecture.
OK, understood.
If your concern is security, you may install web server to DMZ. One remaining challenge might be managing user identities, but even for that there are solutions available.
OK, I'll look into this.
Thanks for all the inputs! -
WLS 10.3.x for RHEL 5.4
Hi
I'm trying to download WLS 10.3.x for a RHEL 5.4, and I don't see any link from the download page for this kind of architecture (64bits for RH).
Can someone tell from where I can get it (if there is a version)?
Thanks in advance,
AndresHi
I'm trying to download WLS 10.3.x for a RHEL 5.4, and I don't see any link from the download page for this kind of architecture (64bits for RH).
Can someone tell from where I can get it (if there is a version)?
Thanks in advance,
Andres -
Java.lang.thread exception while using Xalan 2.0 in WLS 6.0
Hi, I'm trying to use Xalan 2.0 in a servlet hosted by WLS. Ive
modified Xalan's SimpleTransform sample to be a servlet. I
create a Transformer with the .xsl, then call tranform() to
print the tranformed xml to the response stream. The xml is
tranformed correctly, but it throws a java.lang.thread
exception. The standalone Xalan sample doesn't do this. Anyone
else seen this problem?
Here's the code of interestest, I apologize if its not formatted very well:
public void doGet(HttpServletRequest req, HttpServletResponse res) throws IOException
PrintWriter out = res.getWriter();
res.setContentType("text/html");
out.println("<html><head><title>XalanTest<title></head>");
out.println("<body><h1>XalanTest</h1>");
try{
TransformerFactory tFactory = TransformerFactory.newInstance();
StreamSource ss = new StreamSource("file:\\\\My-path\\birds.xsl");
Transformer transformer = tFactory.newTransformer(ss);
StreamResult SR = new StreamResult(out);
transformer.transform(new StreamSource("file:\\\\My-path\\birds.xml"), SR );
catch(Exception e){
out.println("<p>" + e.toString() + "</p>");
e.printStackTrace(out);
out.println("<p>Exception</p>");
out.println("</body></html>");It also looks like the workaround suggested does not work.
I put the following code as workaround:
response.setContentType("text/html");
response.setHeader ("Pragma", "no-cache");
Transformer transformer;
TransformerFactory factory = TransformerFactory.newInstance();
String stylesheet = "config\\closs\\applications\\webroot\\jsp\\example\\Load2.xsl";
String sourceId = "config\\closs\\applications\\webroot\\jsp\\example\\Load2.xml";
String outputFile = "config\\closs\\applications\\webroot\\jsp\\example\\Load2.html";
String outputDirectFile = "config\\closs\\applications\\webroot\\jsp\\example\\Load2_Direct.html";
try
PrintWriter fout = new PrintWriter (new FileOutputStream (outputFile));
OutputStream os = new ByteArrayOutputStream();
transformer = factory.newTransformer(new StreamSource(stylesheet));
transformer.transform(new StreamSource(sourceId), new StreamResult(outputDirectFile));
transformer.transform(new StreamSource(sourceId), new StreamResult(os));
os.flush ();
os.close();
out.print(os.toString());
fout.print (os.toString ());
fout.flush ();
fout.close ();
catch (Exception e)
// Error Handler
e.printStackTrace();
The two .html files produced look exactly the same, which is good.
However, the screen output to my html browser (Internet Explorer 5.50 sp1) produces
different output.
That is strange, but that shows that this bug does not have a known workaround
"Rabinowitz" <[email protected]> wrote:
>
I have the same problem with java sun xml parser (jaxp 1-1)
It is interesting to know that all this perfectly works under weblogic
5.1, so
I cannot migrate my application to 6.0
So, the functionality of weblogic 6.0 degraded since 5.1.
I cannot buy the explanation that that is not bea's fault, because it
perfectly
worked with the same version of xml parser.
Now, their customer support is saying they have not decided whether this
is a
bug or a feature.
Interesting to know that degradation of functionality could be a feature!
It is now June 21, 3 months since this bug was reported, sp2 was shipped
since
that time, and this bug is still there.
"Chuck H. Zhao" <[email protected]> wrote:
I am having the exact same problem you are having. If we analyze the
stack
trace:
javax.xml.transform.TransformerException: java.lang.Thread
at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:1212)
at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894)
at java.lang.Thread.run(Thread.java:484)
java.lang.ClassCastException: java.lang.Thread
at
weblogic.servlet.internal.ResponseHeaders.setDateHeader(ResponseHeaders.java
:273)
at
weblogic.servlet.internal.ServletResponseImpl.setDateHeader(ServletResponseI
mpl.java:449)
at
weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseIm
pl.java:637)
at
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
mpl.java:124)
at
weblogic.servlet.internal.WLOutputStreamWriter.flush(WLOutputStreamWriter.ja
va:124)
at java.io.PrintWriter.flush(PrintWriter.java:120)
at
org.apache.xalan.serialize.SerializerToXML.flushWriter(SerializerToXML.java:
1431)
at
org.apache.xalan.serialize.SerializerToXML.endDocument(SerializerToXML.java:
629)
at
org.apache.xalan.transformer.ResultTreeHandler.endDocument(ResultTreeHandler
..java:180)
at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:1194)
at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894)
at java.lang.Thread.run(Thread.java:484)
What happened is: to support incremental output, Xalan-Java performs
the
transformation in a second thread while building the source tree inthe
main
thread. So Transformer.transform() creates a new thread to run the
transformer.run() method, which will write to weblogic's internal
ServletOutputStreamImpl, and in the end calls flush() on it.
ServletOutputStreamImpl determines that the headers haven't been written
yet, and the headers need to be written before any servlet output, so
it
calls ServletResponseImpl.writeHeaders(), which eventually calls
ResponseHeaders.setDateHeader(). The last method assumes the thread
is
weblogic's internal ExecuteThread and tries to cast the thread as such,
maybe to get the date from it. But the thread is a plain java.lang.Thread
created by xalan, thus we get the java.lang.ClassCastException:
java.lang.Thread
This suggests a second workaround: call ServletResponse.flushBuffer()
before any xalan stuff, which will force the headers to be written in
weblogic's ExecuteThread. The shortcoming of this is that this will
cause
the response to be commited, and if the xalan stuff throws exception
you can
not forward to another page.
Another thing is that xalan should not directly call flush() on
ServletOutputStreamImpl at all. I will report it to xalan and see if
they
consider that a bug. If they fix that then we have a third workaround:
set
the buffer size of ServletResponse big enough to accomodate everything
including the xslt outputs, so the ServletOutput does not need to be
flushed
during xalan code.
I do not consider this problem a weblogic bug, since the servlet container
has to right to expect any thread inside it to be its own. Serlvet2.2
spec
says:
1.2 What is a Servlet Container?
A Servlet Container may place security restrictions on the environment
that
a servlet executes in. In
a Java 2 Platform Standard Edition 1.2 (J2SE) or Java 2 Platform Enterprise
Edition 1.2 (J2EE)
environment, these restrictions should be placed using the permission
architecture defined by Java 2
Platform. For example, high end application servers may limit certain
action, such as the creation of
a Thread object, to insure that other components of the container are
not
negatively impacted.
Weblogic should explicitly warn the developers that creating threads
inside
the servlet container may have adverse effects, the same kind of problem
we
are having. (or maybe they already did somewhere in their documentation?)
On the xalan side, I would suggest them to either give the option to
switch
the two threads, or to give the option to buffer the output and write
it out
in the main thread, which is exactly what you did in your first workaround.
Any comments or thoughts on the subject are welcome.
-- Chuck Zhao
"MK Parini" <[email protected]> wrote in message
news:[email protected]...
I found, what I think to be a bug, and a work-around for it.
When doing an XSLT Transformation, you must specify a StreamResult
to which to write the output. I was doing my transformation in
a
servlet so I was writing my output to the HttpResponse
(The variable res is a javax.servlet.http.HttpServletResponse
object)
StreamResult htmlTarget = new StreamResult(res.getWriter());
If I use this, when I perform the transformation using the TRAX
APIs,
InputStream xslFile = context.getResourceAsStream(fileName);
TransformerFactory tFactory = TransformerFactory.newInstance();
Templates xslTemplates = tFactory.newTemplates(new StreamSource(xslFile));
transformer = xslTemplates.newTransformer();
transformer.transform(xmlSource, htmlTarget);
I receive the ClassCastException from the class
weblogic.servlet.internal.ResponseHeaders.setDateHeader(ResponseHeaders.java
:273),
as seen in my previous posting.
I discovered, if I write my output to a StringBuffer, and then
I write
the StringBuffer to the HttpResponse, I do not get the ClassCastException.
For example,
StringWriter myWriter = new StringWriter(2400);
StreamResult htmlTarget = new StreamResult(myWriter);
<Same transformation code as above>
myWriter.close();
PrintWriter out = res.getWriter();
out.print(myWriter.toString());
Is this a bug in the weblogic internal servlet class or am I just
missing something?
Also, one concern that I have with the workaround is that it might
hurt performance.
Any comments or thoughts on the subject are welcome. -
JAVA client JNDI lookup for EJB session in cluster in WLS 5.1
The documentation says :
to obtain a Context for JNDI lookup do the following :
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
try {
Context ctx = new InitialContext(ht);
// Do the client's work
catch (NamingException ne) {
// A failure occurred
finally {
try {ctx.close();}
catch (Exception e) {
// a failure occurred
where "mycluster" is the DNS name of my cluster. My DNS server (Windows 200
DNS server) use round robin
to call alernatively all the wls server node in "mycluster" and it's OK. The
two servers of my cluster
are called alternatively for my EJB session stateless.
Now I unplug one of the two nodes of my cluster and the remaining server is
called only 2 times
and not after.
Questions :
-is the load balancing between the nodes of mycluster only rely on DNS or
is there an internal
mecanism in EJB sub to try one server then an other ?
- do I need to obtain a new reference on JNDI Context for each call ?
Thank's a lot.
Farid Bellameche.
I too have the same problem. My scenario is :
I have the web tier architecture away from cluster. All ejbs are in cluster
running in two seperate machines. We have a factory class running in
webtier(we use servlet in this tier) which obtains home interface only once
and stores it for future reference. When ever we need the remoteobject stub,
we ask the factory class and which in turn uses the stored home interface to
get the same.
In the webtier, I list all the servers in the cluster as a part of url as
mentioned by you.
I started the web tier as well as Object tier cluster. I could see the
request coming in both the machines in the cluster for the ejb. But When I
bring one the server in the cluster,
1. Web tier throws an exception saying that it could not connect
to server using t3.
2. The other machine which is running the server, also says
'failed to create socket to : -32323234324 sever name
using protocol t3.
It looks like I am able to get load balance. But I am not able to get the
fail over to be working.
In the weblogic-ejb-jar.xml, I added the following.
<clustering-descriptor>
<home-is-clusterable>true</home-is-clusterable>
<home-load-algorithm>round-robin</home-load-algorithm>
</clustering-descriptor>
I compiled and added the .jar file. So the jar file now has replica aware
stubs.
Could any one of you help me for why the fail over is not working?
Suersh
"Giri Alwar" <[email protected]> wrote in message
news:[email protected]...
> Farid,
> (1) Yes, the stub has the logic to perform load-balancing and
fail-over.
> (2) In almost all cases, no. You can get the context once, store it
and
> use it thereafter. Please refer to
> http://www.weblogic.com/docs51/cluster/concepts.html#1025061 for more
info.
>
> A couple of notes on your situation. From what you are describing, your
> Windows DNS server is setup to serve only one IP from the cluster (using
> round-robin) as opposed to a list of all IP's in the cluster. Hence, the
> initial context you obtain is tied to a single server in the cluster (the
> one returned by the DNS). The weblogic implementation on the client side
has
> no idea of the existence of the other servers in the cluster. This is not
a
> cluster aware context. To obtain a cluster aware context, either list all
> the IP's in the URL like t3://server1,server2,server3:7001 or have
> "mycluster" return a list of all servers in the cluster.
>
> Giri
>
>
> "Farid Bellameche" <[email protected]> wrote in message
> news:[email protected]...
> > The documentation says :
> >
> > to obtain a Context for JNDI lookup do the following :
> > Hashtable ht = new Hashtable();
> > ht.put(Context.INITIAL_CONTEXT_FACTORY,
> > "weblogic.jndi.WLInitialContextFactory");
> > ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
> > try {
> > Context ctx = new InitialContext(ht);
> > // Do the client's work
> > }
> > catch (NamingException ne) {
> > // A failure occurred
> > }
> > finally {
> > try {ctx.close();}
> > catch (Exception e) {
> > // a failure occurred
> > }
> > }
> >
> > where "mycluster" is the DNS name of my cluster. My DNS server (Windows
> 200
> > DNS server) use round robin
> > to call alernatively all the wls server node in "mycluster" and it's OK.
> The
> > two servers of my cluster
> > are called alternatively for my EJB session stateless.
> > Now I unplug one of the two nodes of my cluster and the remaining server
> is
> > called only 2 times
> > and not after.
> >
> > Questions :
> > -is the load balancing between the nodes of mycluster only rely on DNS
> or
> > is there an internal
> > mecanism in EJB sub to try one server then an other ?
> >
> > - do I need to obtain a new reference on JNDI Context for each call ?
> >
> >
> > Thank's a lot.
> >
> > Farid Bellameche.
> >
> >
> >
> >
>
>
-
WLS 6.1 SP2 Cluster fails
Hi All.
we have migrated to WLS 6.1 SP2, now we have a serious problem with the cluster
wihch die after several minutes. Our architecture is several front-ends servers
(concretely servelts, without cluster) make request to back-end (starteles EJB,
DB access). This back-end is compuond by four WLS instances running into 2 Sun
Solaris Machines. The system reports the nexts messages in the weblogic.log.
* backendPlatformA instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformA|129.1027407260379', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
<platformA> <ExecuteThread: '117' for queue: 'default'> <system> <>
<000000> <Tried to renew lease on lost reference: '257'>
* backendPlatformB instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformB|118.1027407423933', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
<platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
<Removing "ClientContext - id: '#|platformB|119.1027407423933', bound:
'false', dead: 'false'" because of soft disconnect timeout.>
* ioboxPlatfromC instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformC|139.1027407286958', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
<platformC> <ExecuteThread: '119' for queue: 'default'> <system> <>
<000000> <Tried to renew lease on lost reference: '257'>
* Instancia ioboxPlatfromD
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
<platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
<Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
'false', dead: 'false'" because of soft disconnect timeout.>
####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
<ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
platformA
jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
from cluster view due to PeerGone>
####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
<ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
to the cluster>
####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
<platformD> <ExecuteThread: '102' fo
r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
anaydidos>
####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
<platformD> <ExecuteThread: '119' for queue: 'default'> <system> <>
<000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because of:
'Server received a message over an uninitialized connection: 'JVMMessage
from: 'null' to:
'1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
Any idea?
Thanks for all
Hi,
We are using Weblogic 6.1 SP2, NT 4.0 and java 1.3.1. We have also encountered
the same error message. We have 1 admin and 2 managed servers. We have tried connecting
in using weblogic.admin to check the idle thread and we are able to connect. However,
when we connect from IIS to Weblogic, the application failed to response. We have
tried connect direct to weblogic but it does not response as well. We have seen
that the idle thread left has been reduced but there is no activites from the
weblogic console. The thread is used but not releasing and the console is not
moving. When we shutdown one of the managed server, the application is able to
process as seen from the console.
We have turned off native io and this behavior is not seen. When we turn on native
io, it appear. So we can conclude that it is related to native io.
Is there any solution or intermediate patch without upgrading to the later SP
Thanks
Rajesh Mirchandani <[email protected]> wrote:
>We are shipping the Jdriver for oracle 816 with SP3. Use the driver
>from .\bin\oci816_8
>
>Manuel wrote:
>
>> Thanks Rajesh,
>>
>> we have another problem since our database is Oracle 8.1.6 and SP3
>jDriver doesn´t
>> support this version.
>>
>> Best Regards
>>
>> Rajesh Mirchandani <[email protected]> wrote:
>> >Upgrade to SP3, if possible.
>> >
>> >Manuel wrote:
>> >
>> >> Hi All.
>> >>
>> >> we have migrated to WLS 6.1 SP2, now we have a serious problem with
>> >the cluster
>> >> wihch die after several minutes. Our architecture is several front-ends
>> >servers
>> >> (concretely servelts, without cluster) make request to back-end
>(starteles
>> >EJB,
>> >> DB access). This back-end is compuond by four WLS instances running
>> >into 2 Sun
>> >> Solaris Machines. The system reports the nexts messages in the weblogic.log.
>> >>
>> >> * backendPlatformA instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformA|129.1027407260379', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
>> >> <platformA> <ExecuteThread: '117' for queue: 'default'> <system>
><>
>> >> <000000> <Tried to renew lease on lost reference: '257'>
>> >>
>> >> * backendPlatformB instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformB|118.1027407423933', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
>> >> <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
>> >> <Removing "ClientContext - id: '#|platformB|119.1027407423933',
>bound:
>> >> 'false', dead: 'false'" because of soft disconnect timeout.>
>> >>
>> >> * ioboxPlatfromC instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformC|139.1027407286958', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
>> >> <platformC> <ExecuteThread: '119' for queue: 'default'> <system>
><>
>> >> <000000> <Tried to renew lease on lost reference: '257'>
>> >>
>> >> * Instancia ioboxPlatfromD
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
>> >> <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
>> >> <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
>> >> 'false', dead: 'false'" because of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
>> >> <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
>> >> platformA
>> >> jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
>> >> from cluster view due to PeerGone>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
>> >> <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
>> >> 7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
>> >> to the cluster>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
>> >> <platformD> <ExecuteThread: '102' fo
>> >> r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
>> >> anaydidos>
>> >> ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
>> >> <platformD> <ExecuteThread: '119' for queue: 'default'> <system>
><>
>> >> <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because
>> >of:
>> >> 'Server received a message over an uninitialized connection: 'JVMMessage
>> >> Wrom: HJEXXIMQZU
>> >> '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
>> >> cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
>> >> flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
>> >>
>> >> Any idea?
>> >>
>> >> Thanks for all
>> >
>> >--
>> >Rajesh Mirchandani
>> >Developer Relations Engineer
>> >BEA Support
>> >
>> >
>
>--
>Rajesh Mirchandani
>Developer Relations Engineer
>BEA Support
>
>
Maybe you are looking for
-
Why can't i see my thumbnails in iPhoto?
I have hundreds of photos but all the thumbnails are blank. My photos are still there because i can see them once i open the thumbnails but i can't tell what photo i'm about to look at before i open it.
-
WiFi While Traveling in an RV or staying in a Hotel
Hi, I just purchased an Apple TV 2. I hooked it up to my home network and from what I've done with it so far I love it. Although the Netflix movie I wanted to stream last night took about 5 tries before it would bypass the try again later screen, do
-
few days ago I noticed that certain apps are displaying raw HTML instead of formatted content. Specifically, Skype during a chat session I cannot read what the messages I'm receiving are. I see lots of div tags and other stuff. also another app, MacG
-
Replacing the same value in a string with varying values
If I have a string: "%s is the %s I am referring to" and - I want to replace the %s occurrences with DIFFERENT values... what's the best way to do this. I was thinking parsing it into seperate strings using substr and instr but, I'm not sure if that'
-
ITunes in Time Capsule.
Is it possible to store all my music in time capsule and use the itunes in TC to create playlists that i can later sync with all my devices? I dont want to store music files in my MB Air, i just want to sync playlists which I created in TC to my MB A