Apach1 .1.3.22+ mod_ssl /Weblogic 5.1 Browser to Apache SSL does not work
We are using Weblogic 5.1 and apache 1.3.22+mod_ssl. HTTPS requests to the apache
server for jsp do not work. However if
a HTTP request for the same jsp is made, it works.
SSL requests only work if the ServerName directive for HTTP
server and the 443 Virtual Server are commented out in httpd.conf. Is this right?
Hi.
Firstly, this is not a supported configuration. The latest version of apache we
certify is 1.3.19. See the following link for supported platforms:
http://edocs.bea.com/wls/platforms/index.html#apach.
Without seeing your httpd.conf file this should work. You probably already know this,
but with WLS 5.1 https between the server and the plugin is not supported, so apache
needs to translate all http/https requests to http for WLS.
I recommend you try posting this question to the plugin newsgroup -
weblogic.developer.interest.plugin.
Thanks,
Michael
shakeel rao wrote:
We are using Weblogic 5.1 and apache 1.3.22+mod_ssl. HTTPS requests to the apache
server for jsp do not work. However if
a HTTP request for the same jsp is made, it works.
SSL requests only work if the ServerName directive for HTTP
server and the 443 Virtual Server are commented out in httpd.conf. Is this right?--
Michael Young
Developer Relations Engineer
BEA Support
Similar Messages
-
Weblogic server 5.1.0 with sp8 does not work with LDAP (Netscape Directory Server 4.12)
I have weblogic server 5.1.0 with the sp8 running on Windows NT server 4.0.
The weblogic server is configured to use LDAP realm (Netscape directory
server 4.12).
When I try to run weblogic server and I am getting the following errors:
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: java.lang.ExceptionInInitialize
or: weblogic.security.ldaprealm.LDAPRealmException: cannot connect to ldapse
without a principal to authenticate as
at weblogic.security.ldaprealm.LDAPDelegate.setupProperties(LDAPDele
.java, Compiled Code)
at weblogic.security.ldaprealm.LDAPDelegate.<clinit>(LDAPDelegate.ja
83)
at weblogic.security.ldaprealm.LDAPRealm.<init>(LDAPRealm.java:34)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:241)
at weblogic.security.acl.Realm.getRealm(Realm.java:78)
at weblogic.security.acl.Realm.getRealm(Realm.java:56)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1756)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
java.lang.ExceptionInInitializerError: weblogic.security.ldaprealm.LDAPRealm
ption: cannot connect to ldapserver without a principal to authenticate as
at weblogic.security.ldaprealm.LDAPDelegate.setupProperties(LDAPDele
.java, Compiled Code)
at weblogic.security.ldaprealm.LDAPDelegate.<clinit>(LDAPDelegate.ja
83)
at weblogic.security.ldaprealm.LDAPRealm.<init>(LDAPRealm.java:34)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:241)
at weblogic.security.acl.Realm.getRealm(Realm.java:78)
at weblogic.security.acl.Realm.getRealm(Realm.java:56)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1756)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
And here is the my ldaprealm.properties file
netscape.server.host=localhost
netscape.server.port=389
netscape.server.ssl=false
netscape.server.principal=uid=admin, ou=Administrators,
ou=TopologyManagement, o=NetscapeRoot
netscape.server.credential=password
netscape.user.dn=ou=People, o=towers.com
netscape.user.filter=(&(uid=%u)(objectclass=person))
netscape.group.dn=ou=Groups, o=towers.com
netscape.group.filter=(&(cn=%g)(objectclass=groupofuniquenames))
netscape.membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquename
s))
By looking at the error message, it seems like the "server.principal" and
"server.credential" info is not correct.
But I was able to use the same Netscape Directory server with Welogic 5.1.0
with sp4, although the ldaprealm.properties file has somewhat different
format.
Did anyone have similar problems with sp8?
Thanks in advance for any suggestions.BEA support just gave me the solution.
They told me to uncomment out the line
server.alias=netscape
in the ldaprealm.properties file
And I am able to start weblogic with my NIS
Thanks
"Enrique" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
Have you try to remove the "system" user on the LDAP server?
Regards.
"Honghai Zhang" <[email protected]> wrote:
I have weblogic server 5.1.0 with the sp8 running on Windows NT server
4.0.
The weblogic server is configured to use LDAP realm (Netscape directory
server 4.12).
When I try to run weblogic server and I am getting the following errors:***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException:
java.lang.ExceptionInInitialize
or: weblogic.security.ldaprealm.LDAPRealmException: cannot connect toldapse
without a principal to authenticate as
atweblogic.security.ldaprealm.LDAPDelegate.setupProperties(LDAPDele
..java, Compiled Code)
atweblogic.security.ldaprealm.LDAPDelegate.<clinit>(LDAPDelegate.ja
83)
atweblogic.security.ldaprealm.LDAPRealm.<init>(LDAPRealm.java:34)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:241)
at weblogic.security.acl.Realm.getRealm(Realm.java:78)
at weblogic.security.acl.Realm.getRealm(Realm.java:56)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1756)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
java.lang.ExceptionInInitializerError:weblogic.security.ldaprealm.LDAPRealm
ption: cannot connect to ldapserver without a principal to authenticate
as
atweblogic.security.ldaprealm.LDAPDelegate.setupProperties(LDAPDele
..java, Compiled Code)
atweblogic.security.ldaprealm.LDAPDelegate.<clinit>(LDAPDelegate.ja
83)
atweblogic.security.ldaprealm.LDAPRealm.<init>(LDAPRealm.java:34)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:241)
at weblogic.security.acl.Realm.getRealm(Realm.java:78)
at weblogic.security.acl.Realm.getRealm(Realm.java:56)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1756)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)***************************************************************************
And here is the my ldaprealm.properties file////////////////////////////////////////////////////////////////////////////
netscape.server.host=localhost
netscape.server.port=389
netscape.server.ssl=false
netscape.server.principal=uid=admin, ou=Administrators,
ou=TopologyManagement, o=NetscapeRoot
netscape.server.credential=password
netscape.user.dn=ou=People, o=towers.com
netscape.user.filter=(&(uid=%u)(objectclass=person))
netscape.group.dn=ou=Groups, o=towers.com
netscape.group.filter=(&(cn=%g)(objectclass=groupofuniquenames))
netscape.membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquename
s))////////////////////////////////////////////////////////////////////////////
By looking at the error message, it seems like the "server.principal" and
"server.credential" info is not correct.
But I was able to use the same Netscape Directory server with Welogic5.1.0
with sp4, although the ldaprealm.properties file has somewhat different
format.
Did anyone have similar problems with sp8?
Thanks in advance for any suggestions. -
WebLogic 7.0.1 and apache ssl plug-in
I am not seeing any forwarding of SSL requests from Apache to WebLogic once I upgraded
from 7.0.0.1 to 7.0.1 and used the new plug-in. I actually found the plug-in
size for solaris to be smaller then the 7.0.0.1 which I found to be a little strange.
The old plug-in does not work either.
I am not sure if this is a bug or what, just want to see if anyone has a similar
setup and seeing similar issues. We run OpenSSL on Apache 1.3.9 and this was
working fine in 7.0.0.1 and just stopped working for the SSL pages only, the regular
pages pass through no problem.I am not seeing any forwarding of SSL requests from Apache to WebLogic once I upgraded
from 7.0.0.1 to 7.0.1 and used the new plug-in. I actually found the plug-in
size for solaris to be smaller then the 7.0.0.1 which I found to be a little strange.
The old plug-in does not work either.
I am not sure if this is a bug or what, just want to see if anyone has a similar
setup and seeing similar issues. We run OpenSSL on Apache 1.3.9 and this was
working fine in 7.0.0.1 and just stopped working for the SSL pages only, the regular
pages pass through no problem. -
Apache-Weblogic Bridge does not work?
I've gone thru' the documentation regarding setting up of apache-weblogic bridge, but still it does not work. Does anyboday have any more details regarding this...EnvironmentOS - Solars 5.7Weblogic - 5.1 SP 8Apache 1.3.12
I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?! -
Weblogic 6.1 sp1 Application Server MDB does not consume messages
I have the following situation:
WebLogic Application Server 6.1 sp1. A deployed mdb does nothing - just sits idle
even when the JMS queue it points to has many messages waiting to be consumed.
When the application server is bounced (i.e., shutdown and restarted), the mdb
starts processing the messages. JMS server has a JDBC backing store.
Any ideas?
Thanks,
PrakashTobin is right, my apoplication is called "portal", I am not using WLPortal. Anyway,
I managed to resolve my problem,I had sax2 , xp and xt parsers placed in the WEB-INF\lib
directory of my application in addition to my own jar file. I removed the parsers
, and now my application is running fine.
It is strange though, since my application used to load and work flawlessly on
weblogic 6 as well as weblogic 6.1 sp1 with the parsers in the lib directory....
Anyhow, thanks a lot for the help.
Regards,
Lalitha
"Tobin Paterson" <[email protected]> wrote:
>
Having applied WLS 6.1 sp2 upgrade today I am seeing the same fault.
I am not using
WL Portal. Also I think the original poster's application just happens
to be called
"portal" and is not using WL Portal.
cheers,
Tobin.
"BEA Support" <[email protected]> wrote:
Hello,
Only WLCS and/or WLPS 3.5 sp 2 support WLS 6.1 sp 2
WL Portal 4.0 support only WLS 6.1 sp 1.
Regards,
Developer Relations Engineer
BEA Support
"Lalitha" <[email protected]> a écrit dans le message de news:
[email protected]..
Hi
For some reason, my application 'portal' does not run on weblogic
6.1
sp2,
It used to run fine on 6.1 sp1 .
I am attaching the weblogic.log file with this msg.
Thanks,
Regards,
Lalitha -
SSL between WebLogic 10.0 and IIS 6.0 does'nt work
Hi,
I don't understand why the SSL connection between WL10.0 and IIS 6.0 doesn't work. My ini file is below:
WebLogicHost=10.0.162.31
WebLogicPort=7002
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WlForwardPath=/weblogic
PathTrim=/weblogic
Debug=ON
SecureProxy=ON
TrustedCAFile=C:\trustedca.pem
EnforceBasicConstraints=off
RequireSSLHostMatch=false
where 'trustedca.pem' is the pem extracted (and converted) from wlsdemoca contained into DemoTrust.jks and '7002' is my ssl listen port.
I need to set any more parameter??
My wlpsoxy.log for one request is:
================New Request: [crl4/.wlforward] =================
Thu Apr 17 10:27:32 2008 <351612084388524> SSL is not being used
Thu Apr 17 10:27:32 2008 <351612084388524> resolveRequest: wlforward: /crl4/
Thu Apr 17 10:27:32 2008 <351612084388524> URI is /crl4/, len=6
Thu Apr 17 10:27:32 2008 <351612084388524> Request URI = [crl4/]
Thu Apr 17 10:27:32 2008 <351612084388524> attempt #0 out of a max of 10
Thu Apr 17 10:27:32 2008 <351612084388524> Trying a pooled connection for '10.0.162.31/7001/7001'
Thu Apr 17 10:27:32 2008 <351612084388524> getPooledConn: No more connections in the pool for Host[10.0.162.31] Port[7001] SecurePort[7001]
Thu Apr 17 10:27:32 2008 <351612084388524> general list: trying connect to '10.0.162.31'/7001/7001 at line 1239 for '/crl4/'
Thu Apr 17 10:27:32 2008 <351612084388524> INFO: New NON-SSL URL
Thu Apr 17 10:27:32 2008 <351612084388524> Connect returns -1, and error no set to 10035, msg 'Unknown error'
Thu Apr 17 10:27:32 2008 <351612084388524> EINPROGRESS in connect() - selecting
Thu Apr 17 10:27:32 2008 <351612084388524> Local Port of the socket is 1476
Thu Apr 17 10:27:32 2008 <351612084388524> Remote Host 10.0.162.31 Remote Port 7001
Thu Apr 17 10:27:32 2008 <351612084388524> general list: created a new connection to '10.0.162.31'/7001 for '/crl4/', Local port: 1476
Thu Apr 17 10:27:32 2008 <351612084388524> WLS info in sendRequest: 10.0.162.31:7001 recycled? 0
Thu Apr 17 10:27:32 2008 <351612084388524> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 17 10:27:32 2008 <351612084388524> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 17 10:27:32 2008 <351612084388524> parsed all headers OK
Thu Apr 17 10:27:32 2008 <351612084388524> sendResponse() : uref->getStatus() = '200'
Thu Apr 17 10:27:32 2008 <351612084388524> Going to send headers to the client. Status :200 OK
Thu Apr 17 10:27:32 2008 <351612084388524> Content Length = 264
Thu Apr 17 10:27:32 2008 <351612084388524> canRecycle: conn=1 status=200 isKA=1 clen=264 isCTE=0
Thu Apr 17 10:27:32 2008 <351612084388524> closeConn: pooling for '10.0.162.31/7001'
Thu Apr 17 10:27:32 2008 <351612084388524> request [crl4/] processed successfully ..................
Thu Apr 17 10:27:57 2008 <351612084387971> timed out 1 connections, idle for (at least) 25 secs
Any idea that help me?I had a look into the xlclient.cmd file and went to the JAVA directory which is being used. And did a search for the "cacerts" and found out that there is a file named cacerts in the JAVA_HOME/jre/lib/security folder over there.
But how does that relate to the problem of running the keytool command successfully at the right place (OIM_DC_HOME) ?
Any hints Kevin....
Thanks,
- oidm. -
Weblogic cluster OIM 10g - "Edit workflow" selection does not show anything
Hello,
My setup is OIM 10g (9102 BP15) in WLS cluster.
When i login as a administrator and click on "Resource Management" -> Manage -> chose a resource -> "Resource workflow" (from drop down) -> "Edit workflow" on approval/provisioning flows, a new window pops up. However, it doesn't open any workflow details in the GUI. When i click "Done" (IE Yellow Triangle) on the bottom left corner of the IE window and copy the error details, it is:
=============================================================================
Webpage error details:
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Timestamp: Mon, 6 Feb 2012 22:30:33 UTC
Message: 'Is' is undefined
Line: 207
Char: 5
Code: 0
URI: http://<hostname>/xlWebApp/richclientlauncher.jsp?app=xlWebApp/loadDesignWorkflow.do?method=LoadWorkflow&processName=<chosen+resource>
Message: Object expected
Line: 30
Char: 6
Code: 0
URI: http://<hostname>/xlWebApp/richclientlauncher.jsp?app=xlWebApp/loadDesignWorkflow.do?method=LoadWorkflow&processName=<chosen+resource>
=============================================================================
On the other hand, if i click on
"Resource Management" -> Manage -> chose a resource -> "Resource workflow" (from drop down) -> "Configure" (Form Data Flow/Reconciliation Data Flow). I see below errors in the log:
=====================================
<Feb 7, 2012 10:56:48 AM PST> <Error> <Cluster> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.
java.rmi.MarshalException: failed to marshal update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;Ljava.lang.Object;); nested exception is:
java.io.NotSerializableException: com.thortech.xl.webclient.workflowutil.ImageGenerator$Field
at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:92)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:221)
at weblogic.cluster.replication.ReplicationManager_1035_WLStub.update(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
Caused By: java.io.NotSerializableException: com.thortech.xl.webclient.workflowutil.ImageGenerator$Field
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at java.util.HashMap.writeObject(HashMap.java:1195)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Truncated. see log file for complete stacktrace
>
<Feb 7, 2012 10:56:48 AM PST> <Error> <Cluster> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.
java.rmi.MarshalException: failed to marshal update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;Ljava.lang.Object;); nested exception is:
java.io.NotSerializableException: com.thortech.xl.webclient.workflowutil.ImageGenerator$Field
at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:92)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:221)
at weblogic.cluster.replication.ReplicationManager_1035_WLStub.update(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
Caused By: java.io.NotSerializableException: com.thortech.xl.webclient.workflowutil.ImageGenerator$Field
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at java.util.HashMap.writeObject(HashMap.java:1195)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Truncated. see log file for complete stacktrace
>
ERROR,07 Feb 2012 10:56:51,516,[org.apache.struts.actions.DispatchAction],Request[resourceWorkflows] does not contain handler parameter named method
=============================
Anyone encountered this before in the clustered setup ?
Thanks,Hello,
But if you see the trace, it is coming from the OOTB library. Isn't it ? It doesn't indicate if there is any issue in any custom beans.
java.io.NotSerializableException: com.thortech.xl.webclient.workflowutil.ImageGenerator$FieldMoreover, i see this error in the log with case 2: ("configure" data flow). However, it is working and the the UI is showing me the data flow with this error in the log.
My major concern is case 1: ("edit" workflow) which is not showing me anything on the UI ?
Ideally, it should trigger Nexaweb client to populate the workflows in the UI.
*1 interesting observation:*
If i go to "Design console" -> process definition -> "Render workflow",
then it opens the workflow in the default explorer and the url which is opened in the browser is same as the previous case. It is working here as expected. Does this means the problem is with Nexaweb client load in the UI in case 1. How to fix this ?
Please suggest.
Thanks,
Edited by: oimuser007 on Feb 7, 2012 2:44 PM -
Weblogic 6.1 example/security/sslclient jsseWLS.bat does not work
I try to run the weblogic 6.1 example under the examples\security\sslclient.
I follow the instruction and setup the server.
wlsWLS.bat is working fine.
but jsseWLS.bat is not working
It gives back following error.
===== in jsseURLConnect =====
JDK Protocol Handlers and Security Providers:
java.protocol.handler.pkgs - com.sun.net.ssl.internal.www.protocol
provider[0] - SUN - SUN (DSA key/parameter generation; DSA signing; SHA-1,
MD
5 digests; SecureRandom; X.509 certificates; JKS keystore)
provider[1] - SunRsaSign - SUN's provider for RSA signatures
provider[2] - SunJSSE - Sun JSSE provider(implements RSA Signatures, PKCS12,
SunX509 key/trust factories, SSLv3, TLSv1)
provider[3] - SunJCE - SunJCE Provider (implements DES, Triple DES, Blowfish,
PBE, Diffie-Hellman, HMAC-MD5, HMAC-SHA1)
Trying a new HTTP connection using JDK client classes -
http://localhost:80/examplesWebApp/SnoopServlet.jsp
====Permission =(java.net.SocketPermission localhost:80 connect,resolve)
===== inside tryConnection
Connection refused: connectjava.net.ConnectException: Connection refused: connec
t
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:100)
at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:277)
at sun.net.www.http.HttpClient.New(HttpClient.java:289)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:408)
at examples.security.sslclient.SSLClient.tryConnection(SSLClient.java:15
1)
at examples.security.sslclient.SSLClient.jsseURLConnect(SSLClient.java:2
05)
at examples.security.sslclient.SSLClient.main(SSLClient.java:99)
JDK Protocol Handlers and Security Providers:
java.protocol.handler.pkgs - com.sun.net.ssl.internal.www.protocol
provider[0] - SUN - SUN (DSA key/parameter generation; DSA signing; SHA-1,
MD
5 digests; SecureRandom; X.509 certificates; JKS keystore)
provider[1] - SunRsaSign - SUN's provider for RSA signatures
provider[2] - SunJSSE - Sun JSSE provider(implements RSA Signatures, PKCS12,
SunX509 key/trust factories, SSLv3, TLSv1)
provider[3] - SunJCE - SunJCE Provider (implements DES, Triple DES, Blowfish,
PBE, Diffie-Hellman, HMAC-MD5, HMAC-SHA1)
Trying a new HTTPS connection using JDK client classes -
https://localhost:443/examplesWebApp/SnoopServlet.jsp
sconnection instanceof com.sun.net.ssl.HttpsURLConnection
using a com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection
===== inside tryConnection
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:100)
at javax.net.ssl.SSLSocket.<init>([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>([DashoPro-V1.2-1201
98])
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket([Dasho
Pro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([Da
shoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer(
[DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1
.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>([DashoP
ro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>([Dasho
Pro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V
1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V
1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connec
t([DashoPro-V1.2-120198])
at examples.security.sslclient.SSLClient.tryConnection(SSLClient.java:15
1)
at examples.security.sslclient.SSLClient.jsseURLConnect(SSLClient.java:2
30)
at examples.security.sslclient.SSLClient.main(SSLClient.java:99)
Connection refused: connect----
Does anyone know what happens..
i would appreciate if i get some code snippets or url pointers.
Thanks.
--Michael W.I try to run the weblogic 6.1 example under the examples\security\sslclient.
I follow the instruction and setup the server.
wlsWLS.bat is working fine.
but jsseWLS.bat is not working
It gives back following error.
===== in jsseURLConnect =====
JDK Protocol Handlers and Security Providers:
java.protocol.handler.pkgs - com.sun.net.ssl.internal.www.protocol
provider[0] - SUN - SUN (DSA key/parameter generation; DSA signing; SHA-1,
MD
5 digests; SecureRandom; X.509 certificates; JKS keystore)
provider[1] - SunRsaSign - SUN's provider for RSA signatures
provider[2] - SunJSSE - Sun JSSE provider(implements RSA Signatures, PKCS12,
SunX509 key/trust factories, SSLv3, TLSv1)
provider[3] - SunJCE - SunJCE Provider (implements DES, Triple DES, Blowfish,
PBE, Diffie-Hellman, HMAC-MD5, HMAC-SHA1)
Trying a new HTTP connection using JDK client classes -
http://localhost:80/examplesWebApp/SnoopServlet.jsp
====Permission =(java.net.SocketPermission localhost:80 connect,resolve)
===== inside tryConnection
Connection refused: connectjava.net.ConnectException: Connection refused: connec
t
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:100)
at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:277)
at sun.net.www.http.HttpClient.New(HttpClient.java:289)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:408)
at examples.security.sslclient.SSLClient.tryConnection(SSLClient.java:15
1)
at examples.security.sslclient.SSLClient.jsseURLConnect(SSLClient.java:2
05)
at examples.security.sslclient.SSLClient.main(SSLClient.java:99)
JDK Protocol Handlers and Security Providers:
java.protocol.handler.pkgs - com.sun.net.ssl.internal.www.protocol
provider[0] - SUN - SUN (DSA key/parameter generation; DSA signing; SHA-1,
MD
5 digests; SecureRandom; X.509 certificates; JKS keystore)
provider[1] - SunRsaSign - SUN's provider for RSA signatures
provider[2] - SunJSSE - Sun JSSE provider(implements RSA Signatures, PKCS12,
SunX509 key/trust factories, SSLv3, TLSv1)
provider[3] - SunJCE - SunJCE Provider (implements DES, Triple DES, Blowfish,
PBE, Diffie-Hellman, HMAC-MD5, HMAC-SHA1)
Trying a new HTTPS connection using JDK client classes -
https://localhost:443/examplesWebApp/SnoopServlet.jsp
sconnection instanceof com.sun.net.ssl.HttpsURLConnection
using a com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection
===== inside tryConnection
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:100)
at javax.net.ssl.SSLSocket.<init>([DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>([DashoPro-V1.2-1201
98])
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket([Dasho
Pro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([Da
shoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer(
[DashoPro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1
.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>([DashoP
ro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>([Dasho
Pro-V1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V
1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V
1.2-120198])
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connec
t([DashoPro-V1.2-120198])
at examples.security.sslclient.SSLClient.tryConnection(SSLClient.java:15
1)
at examples.security.sslclient.SSLClient.jsseURLConnect(SSLClient.java:2
30)
at examples.security.sslclient.SSLClient.main(SSLClient.java:99)
Connection refused: connect----
Does anyone know what happens..
i would appreciate if i get some code snippets or url pointers.
Thanks.
--Michael W. -
Built-in wlst ant task does not work in weblogic 10.3.1
Hi,
We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
[echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
tmp/wlstTemp/packages'
[echo] [wlst] java.io.IOException: No such file or directory
[echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
[echo] [wlst] at java.io.File.createTempFile(File.java:1792)
[echo] [wlst] at java.io.File.createTempFile(File.java:1828)
[echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
[echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
[echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
<target name="init-taskdefs">
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="ant-ext/ant-contrib.jar" />
</classpath>
</taskdef>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
<taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
</target>
<macrodef name="wlShutdownServer">
<attribute name="adminUser" default="${deploy.admin.username}" />
<attribute name="adminPassword" default="${deploy.admin.password}" />
<attribute name="adminUrl" default="${deploy.admin.url}" />
<attribute name="serverTarget" />
<sequential>
<trycatch property="server.error">
<try>
<wlst failonerror="true"
arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
<script>
adminUser=sys.argv[0]
adminPassword=sys.argv[1]
adminUrl=sys.argv[2]
serverTarget=sys.argv[3]
connect(adminUser,adminPassword,adminUrl)
target=getMBean("/Servers/"+serverTarget)
if target == None:
target=getMBean("/Clusters/"+serverTarget)
type="Cluster"
else:
type="Server"
print 'Shutting down '+serverTarget+'...'
shutdown(serverTarget,type,'true',15,force='true')
print serverTarget+' was shut down successfully.'
</script>
</wlst>
<!-- setDomainEnv.sh must have been called to set DOMAIN_HOME. Remove all leftover .lok files to allow server
to start back up again. -->
<echo message="Deleting any lok files that have not been removed..." />
<delete failonerror="false">
<fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
</delete>
</try>
<catch>
<fail message="@{serverTarget} shutdown failed. ${server.error}" />
</catch>
<finally/>
</trycatch>
</sequential>
</macrodef>
Any help would be appreciated. Thanks!Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change. -
WebLogic 5.1 sp6 .. session in cluster not working properly
It seems like there is a problem in Weblogic 5.1 with sessions in a
clustered environment. The problem is immediately visible with sp3 but
also appears in different form with sp6 . I discovered the problem is
actually with session while testing the cluster with a Session servlet
given with the Weblogic 5.1 kit.
I regiestered the servlet as servlet/session.
The environment is briefly as follows:
Solaris 2.6
Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
machine with two multihome addreses like home1:7001 and home2:7001
Cluster properties in mycluster/weblogic.properties are set as,
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
and also started with required cluster properties in startup.
iPlanet 4.0 webserver - obj.conf has entries like
WebLogicCluster="home1:7001,home2:7001"
All requests are made as http://<host>/servlet/session
sp3 ) After both members are booted up, the first call to session
servlet from any new browser session throws a NullException in server,
but subsequent calls work fine. Single server works fine.
After looking at sp6 release notes it appeared to me that it was a known
problem with cluster.
sp6 ) After both members are booted up, all calls to session servlet do
not complete and eventually it times out. Other servlets work fine.
It only works if we do these steps,
- one of the member is booted up and then session servlet is called and
response comes back.
- second member is booted up and it works well if session servlet is
called. Subsequent requests to both members work fine.
Another strange behaviour:
While running a snoop servlet in cluster subsequent requests show,
Requested url :
either http://<host>/servlet/snoop
or http://<host>:7001/servlet/snoop alternatively
which is strange.
You are not using the same service pack on both the servers. let try do that and see how it goes.
1. Also, if you are doing testing why do you so many threads.
2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
- Prasad
Sutanu Ghosh wrote:
> Here are the thread dumps from both members of the cluster. I took the dumps
> about 5 times in 10 secs interval. It will be helpful for us if you can give
> some insight about this problem.
> Also about the snoop servlet, can you explain why the requested url is
> different (one with weblogic port another without it) in every alternate
> requests ?
> thanks
>
> Prasad Peddada wrote:
>
> > Sutanu Ghosh wrote:
> >
> > > It seems like there is a problem in Weblogic 5.1 with sessions in a
> > > clustered environment. The problem is immediately visible with sp3 but
> > > also appears in different form with sp6 . I discovered the problem is
> > > actually with session while testing the cluster with a Session servlet
> > > given with the Weblogic 5.1 kit.
> > > I regiestered the servlet as servlet/session.
> > >
> > > The environment is briefly as follows:
> > > Solaris 2.6
> > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
> > > machine with two multihome addreses like home1:7001 and home2:7001
> > > Cluster properties in mycluster/weblogic.properties are set as,
> > > weblogic.httpd.clustering.enable=true
> > > weblogic.httpd.session.enable=true
> > > weblogic.httpd.session.persistence=true
> > > weblogic.httpd.session.persistentStoreType=replicated
> > > and also started with required cluster properties in startup.
> > >
> > > iPlanet 4.0 webserver - obj.conf has entries like
> > > WebLogicCluster="home1:7001,home2:7001"
> > >
> > > All requests are made as http://<host>/servlet/session
> > >
> > > sp3 ) After both members are booted up, the first call to session
> > > servlet from any new browser session throws a NullException in server,
> > > but subsequent calls work fine. Single server works fine.
> > > After looking at sp6 release notes it appeared to me that it was a known
> > > problem with cluster.
> > >
> > > sp6 ) After both members are booted up, all calls to session servlet do
> > > not complete and eventually it times out. Other servlets work fine.
> > > It only works if we do these steps,
> >
> > Take thread dumps in intervals of 10 seconds and post them again.
> >
> > > - one of the member is booted up and then session servlet is called and
> > > response comes back.
> > > - second member is booted up and it works well if session servlet is
> > > called. Subsequent requests to both members work fine.
> > >
> > > Another strange behaviour:
> > > While running a snoop servlet in cluster subsequent requests show,
> > > Requested url :
> > > either http://<host>/servlet/snoop
> > > or http://<host>:7001/servlet/snoop alternatively
> > > which is strange.
>
> ------------------------------------------------------------------------
> SIGQUIT
> A SIGQUIT has been received. Do you want to:
> [ 0 ] continue program
> [ 1 ] check & print one deadlock
> [ 2 ] check & print all deadlocks
> [ 3 ] dump thread stacks
> [ 4 ] dump lock registry
> [ 5 ] heap inspection
> [ 6 ] terminate program
> Type number corresponding to selected action: Found 0 deadlock
>
> Full thread dump:
> "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
>
> [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
> [3] java.lang.Thread.run(Thread.java:479)
> -------------------
> "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
> [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
> [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
> [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
> [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
> [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
>
> [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
> [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
> [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
> [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
> [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
> [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
> [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
> [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
> [9] weblogic.jndi.Environment.getContext(Environment.java:122)
> [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
> [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
> [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
> [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
> [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
> [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
> [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
> [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
> [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
> [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
> [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
> [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
> [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
> [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
> [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
> [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
> [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.ke -
Weblogic 10.3.1, jsf 1.2 will not work
I deployed the jsf 1.2 and myfaces 1.1.3 as libraries to weblogic domaind if I restart the server and point it to the jsf file which uses the fileupload tomhawk's tag I get this error:
java.lang.NoClassDefFoundError: Lorg/apache/myfaces/custom/fileupload/UploadedFile;
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at com.sun.faces.mgbean.BeanBuilder.scanForAnnotations(BeanBuilder.java:476)
at com.sun.faces.mgbean.BeanBuilder.loadBeanClass(BeanBuilder.java:449)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: org.apache.myfaces.custom.fileupload.UploadedFile
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
Truncated. see log file for complete stacktrace
I'm using the tomhawk's fileUpload
<t:inputFileUpload id="file" value="#{fnc.uploadedFile}" />
and I've modified the web.xml
<filter>
<filter-name>Extensions Filter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>Extensions Filter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
I've all 3 library references in my weblogic.xml file
<library-ref>
<library-name>jsf</library-name>
<specification-version>2.0</specification-version>
<implementation-version>2.0.3</implementation-version>
<exact-match>false</exact-match>
</library-ref>
<library-ref>
<library-name>jstl</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2.0.1</implementation-version>
<exact-match>false</exact-match>
</library-ref>
<library-ref>
<library-name>jsf-myfaces</library-name>
<specification-version>1.1</specification-version>
<implementation-version>1.1.3</implementation-version>
<exact-match>false</exact-match>
</library-ref>Create a new profile exclusively for the 4.0 beta version and create a desktop shortcut with -P "profile" appended to the target to launch that profile.
* http://kb.mozillazine.org/Testing_pre-release_versions
* http://kb.mozillazine.org/Creating_a_new_Firefox_profile_on_Windows
* http://kb.mozillazine.org/Shortcut_to_a_specific_profile
* http://kb.mozillazine.org/Using_multiple_profiles_-_Firefox -
Custom weblogic instrumentation does not work for me :(
Hello.
First of all excuse me about my english.
I have developed a simple class, I have compile it, and I have packaged it into a war file.
The application Works ok when I do a request: http://192.168.1.5:7100/simple/hello
But when I want to instrumentalize it, it cannot works. I have enabled instrumentation, but it I don't see anything in: Request Performance.
Can you help me?.
These are the files:
simple_temp3
|
+- hello.html
|
+- WEB-INF
+- web.xml
|
+- META-INF
+- weblogic-diagnostics.xml
|
+- classes
+- edu
+- ucla
+- hello.class
[weblogic@localhost simple_temp3]$ cat hello.html
<html>
<head><title>Hello World</title></head>
<body><h1>Hello World</h1></body>
</html>
[weblogic@localhost simple_temp3]$ cat META-INF/weblogic-diagnostics.xml
<wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/diagnostics.xsd">
<name>Sample WLDF resource</name>
<instrumentation>
<enabled>true</enabled>
<wldf-instrumentation-monitor>
<name>sample</name>
<enabled>true</enabled>
<action>TraceElapsedTimeAction</action>
<location-type>around</location-type>
</wldf-instrumentation-monitor>
</instrumentation>
</wldf-resource>
[weblogic@localhost simple_temp3]$ cat WEB-INF/web.xml
<web-app id="simple" version="2.4">
<welcome-file-list>
<welcome-file>hello.html</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>Hello</servlet-name>
<servlet-class>Hello</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Hello</servlet-name>
<url-pattern>/hello</url-pattern>
</servlet-mapping>
</web-app>
[weblogic@localhost simple_temp3]$ cat WEB-INF/classes/edu/ucla/Hello.java (this is the source Class)
import javax.servlet.Servlet;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
import java.io.PrintWriter;
public class Hello extends HttpServlet implements Servlet {
public Hello() {}
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
PrintWriter out = response.getWriter();
out.println("<HTML>");
out.println("<HEAD><TITLE>Hello World</TITLE></HEAD>");
out.println("<BODY>");
out.println("<H1>Hello World</H1>");
out.println("Today is: " + (new java.util.Date().toString()) );
out.println("</BODY></HTML>");
out.close();Can anyone help me?
-
WebLogic 8.1 SP4 on Linux - thread dump does not work
I have setup WebLogic 8.1 SP4 on RedHat Linux AS 3.3 with Sun JVM (142_05). When I try to perform a thread dump using weblogic.Admin, I receive the following error in the stderr file. I have also tried the kill -3 but still no thread dump. Is there some trick to this ?
cannot load libary 'stackdump': java.lang.UnsatisfiedLinkError: no stackdump in java.library.pathI am getting the same error as well
cannot load libary 'stackdump': java.lang.UnsatisfiedLinkError: no stackdump in java.library.path
I am creating a simple domain using the domain config wizard and I hope all the PATH and LD_LIBRARY_PATH are set by the default scripts. But I am still getting this error.
But Kill -3 <PID> works though!
Is is a know problem OR am I missing something?!
Bala -
Auto deploy does not work in Weblogic 6.1 !!!!
Hi everyone,
I am facing a problem in my weblogic 6.1 that whatever ejb componet I am deploying
(after modification) to the weblogic server, the changes are not getting reflected
if the server is running. Each time, I have stop the server and start it and then
only the changes done in ejb is getting reflected.
I am not setting startmode while starting the server. So by default it is false
means ie., the server is running in devlopment mode.
Does this problem exist if we do not have proper Service Pack ? Does this problem
exist in higher version of weblogic ?
thank you in advance."jyothip" <[email protected]> wrote:
>
Hi everyone,
I am facing a problem in my weblogic 6.1 that whatever ejb componet I
am deploying
(after modification) to the weblogic server, the changes are not getting
reflected
if the server is running. Each time, I have stop the server and start
it and then
only the changes done in ejb is getting reflected.
I am not setting startmode while starting the server. So by default it
is false
means ie., the server is running in devlopment mode.
Does this problem exist if we do not have proper Service Pack ? Does
this problem
exist in higher version of weblogic ?
thank you in advance. -
WebLogic does not validate minOccurs="1" in webservices
Hello,
My WebService is deployed on WebLogic 10.3.3.
WSDL/XSD describes input parameter number as mandatory:
<xs:element minOccurs="1" maxOccurs="1" name="number" type="xs:int"/>
MinOccurs="1" means that XML message must contain <number> tag, isn't it?
I expect WebLogic has to validate all requests and server error response should be thrown when request is invalid.
Unfortunatelly, my SOAP client is able to send SOAP request without <number> tag and my webservice implementation receives such an invalid request.
Could you tell me please, is it correct behavior or is it defect in WebLogic?
Should my webservice perform it's own XML validation?I added @SchemaValidation in my Java class, recompiled it and redeployed.
Server was restarted and cache and tmp folders were deleted.
Unfortunately, it does not work.
Scheme validation works without @SchemaValidation if add <validate-request>true</validate-request> into weblogic-webservices.xml.
My soap client received SOAP Fault and 500 Internal Server Error for request without mandatory tag.
But I use weblogic.wsee.tools.anttasks.JwscTask and it generate weblogic-webservices.xml without <validate-request>.
Therefore @SchemaValidation is the best solution for me.
Which reasons @SchemaValidation doesn't work?
Maybe you are looking for
-
Hi The Mail push function is not working properly. Sometimes it works for a couple of day, sometimes it is not working anymore. Do anybody know a solution for this? Thanks,
-
Shortcuts for Spaces keeps revert to default settings without cause
I have a Powerbook G4 that's running Leopard 10.5.8. It has plenty of free space on the hard drive (approx 35%). Whenever I start up my Powerbook or wake it from sleeping, the shortcut keys to switch between Spaces are no longer selected. It retains
-
How can I change the proportional font in Firefox?
I prefer helvetica font, so I have changed the fonts for webpages in Firefox settings to it (changed all fonts to helvetica, unchecked "Allow pages to choose their own fonts, instead of my selections above"). However, some webpages still display in w
-
Why won't Google Chrome show template page updates to a site I created?
I made template updates to a client site, but Google Chrome will not show the simple update. All other browsers show the update. I've tried clearing cache and reloading page, but still no luck. The website is at: http://www.donnellycommunications.
-
can we invoke a vb executable file using java can it be a two way process ie; java calls vb and from that we go back to java again on request if this can be done how ihave my code already in java so to do other app i need to use vb as no option is le