Using WLS 6.1 and WLCS 3.5

We are looking to migrate a WLS 5.1 Sp8 and WLCS 3.2 environment to a later
release.
We are only using the Personalization components of WLCS. Has anyone used
the combination of WLS6.1 and WLCS 3.5, yet? What sort of problems are you
seeing? What sort of personalization problems are you seeing?
I know that WLCS 3.5 is only certified for WLS 6.0 sp2. My reason for
pushing WLS 6.1..
We have built an application that uses a lot of XML including XALAN-j 2.1.0,
(xalan.jar, xalanj1compat.jar, xerces.jar, xml.jar, xmlservlet.jar and
xsltc.jar). To get this working on WLS 5.1 SP8 with WLCS 3.2 was quite a lot
of work. In fact it only works if the WebLogic classpath is in a very
particular order. My initial read of WLS 6.1 would suggest that it includes
the XALAN features that we use. My concern with WLS 6.0 is that I may be
unable to get XALAN 2.1.0 working with it.
Let me know your experience,
Thanks
David Marshall

Similar Messages

Using RSA RADIUS Server and WLC 7.4 to dynamically asssign users to VLAN

Hello,
What we are trying to do:
John logs on to wifi using RSA fob for password. RSA sends back auth request with attibutes to WLC 7.4 that magically knows how to interpret the attributes and puts John on vlan 10. Mary logs on with her fob and gets put on VLAN 20.
We dont have ISE. We dont have ACS. We have RSA Authentication Manager 7.0
We have looked high and low for documentation for this kind of setup and we find stuff that is close to a match but not quite.
Here is what we are seeing
1. dynamic vlan assignment is not working -- radius server is set with the attributes
2. RSA authentication works
3. John and Mary are always put into the VLAN where the MGMT interface is
4. I can see that attributes are making it back to the WLC by sniffing
We are stuck at this point. Any help would be much appreciated,
P.

Here is a little more background:
We have created a dynamic interface in VLAN 157
Wireless LAN has been assigned to MGMT interface which is on VLAN 35
This is a VWLC ver 7.4.100
AP is attached to VWLC (only FlexConnect mode is supported)
RADIUS Server has been configured
Users are getting assigned to VLAN 35
Also I have attached some screenshots and two packet captures so you can see what the RSA is sending back with your own eyes
I dont see any atttributes in the capture when RSA sends to the VWLC
I see attributes in the capture when RSA send to my local RADIUS Client (My PC)
And to answer your question we have sending a VLAN ID (157)

Apache 1.3.27 with plugin WL7 and concurrent use of WLS5.1 and WLS7.0 SP1 cluster server

We plan to use WLS 5.1 and WLS 7.0 for different applications (and
clusters), but with the same Apache Webservers.
The installation of the Apache HTTP Server Plug-In is documented in
http://e-docs.bea.com/wls/docs70/plugins/apache.html, but I could not
find information about downward compatibility from the mod_wl.so. Can we
upgrade the Plugin to 7.0 to serve both, the WLS 5.1 and WLS 7.0 ?

You are in unchartered territory. But check the common "gotcha" and
make sure that all the Oracle environment variables are set in the
shell that starts Apache. Load the script <?php phpinfo(); ?> in a
browser and see that whatever variables you need are set in the
Environment section. See the section "Oracle Environment Variables
for Connections" in Underground PHP and Oracle Manual
I suspect it would be beneficial to migrate the PHP code to oci8.
Check table 16-1 in Underground PHP and Oracle Manual for the mapping
between 'oracle' and 'oci8' functions.
-- cj

WLS 6.1 and Struts Applications

I've been able to deploy a Struts 1.1b2 application on WLS 6.1...but only by
altering the startweblogic.cmd file (Adding all required jar files to the
classpath for the server - not an optimal solution by any means.)
I have not been able to get the application working by simply dumping struts
jar files in the application's WEB-INF\lib directory (as should be the
case).
So, is there any secret to making struts work under WLS 6.1 without
resorting to editing the startweblogic.cmd file?
Thanks.

Oyvind,
I believe using LDAPv2 with that release of Commerce Server is not supported.
If you would like more information please contact BEA Support.
Regards,
Richard Wallace
Senior Developer Relations Engineer
BEA Support.
"Oyvind" <[email protected]> wrote:
>
Hi,
We have a problem with WLS 6.1 and LDAPRealm v2. Our application was
working with
WLS 6.0 and the LDAPRealm v2 patch. It is also working with 6.1 and LDAPRealm
v1.
When upgrading to WLS 6.1 we experience problems looking up user properties
from
LDAP. I put the same properties in the <CustomRealm> properties in config.xml
as we had in the old ldaprealm.properties file.
We are using WLCS 3.5 SP2, and we are looking up the user properties
using the
<um:getProperty> tag but it always returns null.
Any idea what's wrong? This could be both a WLCS or a realm problem I
guess?
Below is the realm declaration in config.xml
<CustomRealm
ConfigurationData="user.dn=ou=People, o=my.com;server.principal=cn=Directory
Manager;server.credential=adminadmin;user.filter=(&(cn=%u)(objectclass=person));group.dn=ou=Groups,
o=my.com;group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=aaa.my.com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames))"
Name="LDAPRealmV2" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
Any input is appreciated,
Oyvind

WLS 6.1 and WLS 6.1 Service Pack1 install clears out registry.xml

Hi,
Just thought I'd post this problem and solution in case others came across it.
I installed WLS 6.1 and then the Service Pack 1 separately. The Service Pack
1 install clears out registry.xml.
I then tried to install WLI V2.1 and it would not let me install as it could not
find WLS 6.1 SP1 the definition of which it gets from registry.xml. The error
was WLS 6.1 SP1 not detected.
To get around this I got sent a registry.xml and edited it to be my home machine.
(Not the safest thing to do but it worked!).
I think if you download WLS 6.1 and SP1 and install as one rather than separately
this does not happen.
Regards,
Kathryn

Oyvind,
I believe using LDAPv2 with that release of Commerce Server is not supported.
If you would like more information please contact BEA Support.
Regards,
Richard Wallace
Senior Developer Relations Engineer
BEA Support.
"Oyvind" <[email protected]> wrote:
>
Hi,
We have a problem with WLS 6.1 and LDAPRealm v2. Our application was
working with
WLS 6.0 and the LDAPRealm v2 patch. It is also working with 6.1 and LDAPRealm
v1.
When upgrading to WLS 6.1 we experience problems looking up user properties
from
LDAP. I put the same properties in the <CustomRealm> properties in config.xml
as we had in the old ldaprealm.properties file.
We are using WLCS 3.5 SP2, and we are looking up the user properties
using the
<um:getProperty> tag but it always returns null.
Any idea what's wrong? This could be both a WLCS or a realm problem I
guess?
Below is the realm declaration in config.xml
<CustomRealm
ConfigurationData="user.dn=ou=People, o=my.com;server.principal=cn=Directory
Manager;server.credential=adminadmin;user.filter=(&(cn=%u)(objectclass=person));group.dn=ou=Groups,
o=my.com;group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=aaa.my.com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames))"
Name="LDAPRealmV2" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
Any input is appreciated,
Oyvind

Acs 5.3 and wlc 2504 config with restricted network access

Hello,
i submit you the following issue that i'm actually facing:
i must configure a secured wireless network with access restriction based on SSID. the equipements are : cisco wlc 2504 (soft 7.3) cisco secure acs aplliance 1121 (soft 5.4) .
the users that will connect to the network are regrouped by identity groups, each identity group having it's own SSID. Clearly each group of users must access only one SSID.
i followed the procedure below to configure it:
-- creating user identity groups;
-- creating users and assigning them to the groups;
--- creating authorization profiles for each SSID under policy element/ authorization and permission/network access/authorization profiles and putting the Airespace-Wlan-Id(the SSID number) in the radius tab.
--- assigning the authorization profiles to the identity groups under access policies.
after all these config the users can access the network using there userid/password configured. But the problem is Every user can access every SSID, seems like the restriction is so not very well configured.
i found some documentation on this kind of config but the version of ACS used seems older than the one that i use, so menu are very different.
Please can someone provide with the right steps to follow to achieve this kind of config.
tkx in advance

Yes.. you only have to add the end filter like what I posted... as far as the calling station id in the WLC security tab, it doesn't matter because that is not used when using 802.1x. I would also try to not enable everything that you have just to start from the basic and make sure it works first. The WAP Authentication Method might or might not work for you. Uncheck that for now and when you have a successful authentication, look at the monitor log and see what radius attributes are being sent, because those attributes is what you can use to build your policies.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Ask the Expert: Cisco BYOD Wireless Solution: ISE and WLC Integration

With Jacob Ideji, Richard Hamby and Raphael Ohaemenyi
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the new Identity Solutions Engine (ISE) and Wireless LAN Controller (WLC) hardware/software, integration, features, specifications, client details, or just questions about Cisco's Bring-your-own device (BYOD) solution with cisco Experts Richard Hamby, Jacob Ideji, and Raphael Ohaemenyi. The interest in BYOD (Bring You Own Device) solutions in the enterprise has grown exponentially as guests and company users increasingly desire to use personal devices to access . Cisco BYOD enhances user experience and productivity while providing security, ease-of-administration, and performance. The heart of the Cisco wireless BYOD solution is Identity Solutions Engine (ISE) utilizing the Cisco Unified Wireless portfolio. Starting with ISE v1.1.1MR and WLC (Wireless LAN Controller) code v7.2.110.0 and higher, end-to-end wireless BYOD integration is reality.
Jacob Ideji is the technical team lead in the Cisco authentication, authorization and accounting (AAA) security team in Richardson, Texas. During his four years of experience at Cisco he has worked with Cisco VPN products, Cisco Network Admission Control (NAC) Appliance, Cisco Secure Access Control Server, and Dot1x technology as well as the current Cisco Identity Services Engine. He has a total of more than 12 years experience in the networking industry. Ideji holds CCNA, CCNP, CCSP, CCDA, CCDP, and CISM certifications from Cisco plus other industry certifications.
Richard Hamby works on the Cisco BYOD Plan, Design, Implement (PDI) Help Desk for Borderless Networks, where he is the subject matter expert on wireless, supporting partners in the deployment of Cisco Unified Wireless and Identity Services Engine solutions. Prior to his current position, Hamby was a customer support engineer with the Cisco Technical Assistance Center for 3 years on the authentication, authorization, accounting (AAA) and wireless technology teams.
Raphael Ohaemenyi Raphael Ohaemenyi is a customer support engineer with the authentication, authorization and accounting (AAA) team in the Technical Assistance Center in Richardson, Texas, where he supports Cisco customers in identity management technologies. His areas of expertise include Cisco Access Control Server, Cisco Network Admission Control (NAC) Appliance, Cisco Identity Services Engine, and IEEE 802.1X technologies. He has been at Cisco for more than 2 years and has worked in the networking industry for 8 years. He holds CCNP, CCDP, and CCSP certification.
Remember to use the rating system to let Jacob, Richard and Raphael know if you have received an adequate response.
Jacob, Richard and Raphael might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the wireless mobility sub community forum shortly after the event. This event lasts through Oct 5th, 2012. Visit this forum often to view responses to your questions and the questions of other community members.

OOPS !!
I will repost the whole messaqge with the correct external URL's:
In general, the Trustsec design and deployment guides address the specific support for the various features of the 'whole' Cisco TS (and other security) solution frameworks. And then a drill-down (usually the proper links are embedded) to the specifc feature, and then that feature on a given device. TS 2.1 defines the use of ISE or ACS5 as the policy server, and confiugration examples for the platforms will include and refer to them.
TrustSec Home Page
http://www.cisco.com/en/US/netsol/ns1051/index.html
http://www.cisco.com/en/US/solutions/collateral/ns170/ns896/ns1051/product_bulletin_c25-712066.html
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5712/ps11637/ps11195/at_a_glance_c45-654884.pdf
I find this page very helpful as a top-level start to what features and capabilities exist per device:
http://www.cisco.com/en/US/solutions/ns170/ns896/ns1051/trustsec_matrix.html
The TS 2.1 Design Guides
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns744/landing_DesignZone_TrustSec.html
DesignZone has some updated docs as well
http://www.cisco.com/en/US/netsol/ns982/networking_solutions_program_home.html#~bng
As the SGT functionality (at this point) is really more of a router/LAN/client solution, the most detailed information will be in the IOS TS guides like :
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/security/configuration/guide/b_Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_6.x.html
http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_cts/configuration/xe-3s/asr1000/sec-usr-cts-xe-3s-asr1000-book.html
http://www.cisco.com/en/US/docs/switches/lan/trustsec/configuration/guide/trustsec.html

Web Redirection Problem on Cisco ISE 1.2 and WLC 7.5

Hello,
We are at initial phase of deploying ISE 1.2 in our environment for Wireless Guest Users.
I have configured ISE and WLC to talk to each other which is working fine. An SSID with MAC-Filtering is also configured on WLC and ACL only allowing ISE and DNS traffice.
I have configured proper authentication and authorization policies on ISE. Now, when I try to connect my device (laptop and android mobile), I see my device gets associated with the SSID (Demo) and gets the right IP Address from DHCP and right VLAN from WLC. The log process on ISE is as follows.
11001
Received RADIUS Access-Request
11017
RADIUS created a new session
11027
Detected Host Lookup UseCase (Service-Type = Call Check (10))
15049
Evaluating Policy Group
15008
Evaluating Service Selection Policy
15048
Queried PIP
15048
Queried PIP
15004
Matched rule
15041
Evaluating Identity Policy
15006
Matched Default Rule
15013
Selected Identity Source - Internal Endpoints
24210
Looking up User in Internal Users IDStore - B8:B4:2E:A6:7D:75
24216
The user is not found in the internal users identity store
24209
Looking up Endpoint in Internal Endpoints IDStore - B8:B4:2E:A6:7D:75
24211
Found Endpoint in Internal Endpoints IDStore
22037
Authentication Passed
15036
Evaluating Authorization Policy
15048
Queried PIP
15048
Queried PIP
15048
Queried PIP
15004
Matched rule - Guest Redirection
15016
Selected Authorization Profile - Test_Profile
11002
Returned RADIUS Access-Accept
I also see a redirect url in the detailed authentication logs. But the problem is that when I open my browser on my device, it doesn't get redirected to the guest portal url. Now since I can't get there, I can't continue with the rest of the process of authentication, COA and final ACL for internet access.
Can some one please either guide me the correct steps that I need to follow, if I have mis configured something or advise if this is a bug.
Thanks in advance.
Jay

The ACL is definitely used to define what traffic is re-directed to ISE and what traffic is not redirected. Having the permit-all statement at the end will break redirection. If you are using flex-connect then you will need to use flex-connect ACLs and apply those to the flex-connect APs. The links below should give you an idea of what needs to be done:
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/113606-byod-flexconnect-dg-000.html
http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116087-configure-cwa-wlc-ise-00.html
Thank you for rating helpful posts!

Error message when access WLS: active sockets and socket readers configuration

Hi,
I got the following error when I tried to access the WLS using a program to get
the mbeans data.
This error happens when I have 3 or more servers running ( 1 admin server, 2 or
more managed servers). With cluster with more than 2 servers running, this error
also occurs.
<Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
sockets, but the maximum number of socket readers allowed by theconfiguration
is: '2', you may want alter your configuration.>
I creased the socket readers from 33% to 66%, but I still got the same error.
I'm using WLS version 6.0 sp2
My configuration is:
Execute Threads = 15,
Socket Readers = 33% or 66%
Does anyone know how to fix this ? I am really appreciate for any suggestions.
thanks,
Kieu

thank you, I just found out about setting those sockets using command line options
an hour ago. But thanks a lot.
-Kieu
Kaye Wilcox <[email protected]> wrote:
Kieu,
You could try increasing the number of execute threads, you can do this
via
the admin console on the <server> --> Tuning tab.
See http://edocs.bea.com/wls/docs60/perform/WLSTuning.html#1104317 for
guidelines on setting the thread pool size and the number of socket readers.
Here is a link that talks about socket communication in a cluster
http://edocs.bea.com/wls/docs60/cluster/features.html#1007001.

Setting up the environment in WLS 7.0 and deplying?

Hi,
Previously I have used WLS 6.1.
I have set up the properties file and the required folders in the mydomain folder for the classes. It worked fine for me.
Now when I am using WLS 7.02.
This looks complicated. I have seen the documentation, it tells about different folders other than config like stage and server.
My question is can I use the same old environment setting as in 6.1 in 7.02 and deploy the applications as before.
If not, am I missing anything.
If anyone has worked on WLS 7.02, please let me know how you have set up the environment and deplyed the applications.
Thanks in Advance
Rama
[att1.html]

"rama" <[email protected]> wrote in message news:[email protected]..
Hi,
Previously I have used WLS 6.1.
I have set up the properties file and the required folders in the mydomain folder for the classes. It worked fine for me.
Now when I am using WLS 7.02.
This looks complicated. I have seen the documentation, it tells about different folders other than config like stage and server.
You dont have to setup anything extra for 7.x deployment. The server and stage directories will take suitable defaults.
See 'Using WebLogic Server 6.x Deployment Protocol' in http://e-docs/wls/docs70/programming/deploying.html
My question is can I use the same old environment setting as in 6.1 in 7.02 and deploy the applications as before.
If not, am I missing anything.
If anyone has worked on WLS 7.02, please let me know how you have set up the environment and deplyed the applications.
Thanks in Advance
Rama
[att1.html]

Using WLS as a web server

Hi,
we are currently using Netscape Enterprise Server 3.6 as our web
server and WLS 5.1 as web container, both running on AIX 4.3.3.
We want to get rid of the NES (it is buggy and unsupported) but we are
unsure if need to replace it with another web server (e.g. Apache or
iPlanet), or just use WLS 6.1 as both web server and web container.
So the question is: do you have any experience regarding the
performance of the WLS 6.1 web server compared to a standard web
server?
TIA
/\/\orten Hindsholm

The main reason that 5.1 is 25% slower than NES or Apache on serving static html
is that NES/Apache do a lot of native I/O and caching ( their code base is C/C++).
6.1 fixed that problem, BEA use native I/O to retrieve static html and img files,
and caching them in memory. Benchmark data shows that they are in par with NES/Apache's
performance. It's pretty safe for you to use 6.1 to host your static contents
and use it as web container at the same time.
My 2 cents.
Jim Zhou.
[email protected] (Morten Hindsholm) wrote:
Hi,
we are currently using Netscape Enterprise Server 3.6 as our web
server and WLS 5.1 as web container, both running on AIX 4.3.3.
We want to get rid of the NES (it is buggy and unsupported) but we are
unsure if need to replace it with another web server (e.g. Apache or
iPlanet), or just use WLS 6.1 as both web server and web container.
So the question is: do you have any experience regarding the
performance of the WLS 6.1 web server compared to a standard web
server?
TIA
/\/\orten Hindsholm

ConnectionPool problems with WLS 7.0 and Oracle 9.2

Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
     public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
     public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
     at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
     at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
     at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
     at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
     at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
     at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

ISE and WLC

Dear friends,
We are using ISE and WLC integrity in our network, we have Corporate and Guest SSID, we configured it but client cant connect to this ssid and cant be authenticated, please see attached files and tell me if i done something wrong in configuration of WLC
10.10.17.201 is ISE
Thank you for attention

Hi,
After viewing the Trap logs it seems you have checked on validate machine.
On the client side, make sure you don't check validate machine and then try.

ISE and WLC SRE module compatibilty matrix

Hi all,
We are running SRE module on router with code of 6.x release .Is there any compatibilty matrix available for ISE and WLC code to support CWA . because as of now , the wireless clients are not redirecting to the ISE login page.
Kindly suggest.
Thanks,
Regards,
Vijay

The doc is for wireless guest using CWA. For wired guest, I don't know since you can do wired guest from a WLC that supports it or from a switch.
Sent from Cisco Technical Support iPhone App

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

Using WLS 6.1 and WLCS 3.5

Similar Messages

Maybe you are looking for