IdentityAssertion WLS8

Hello,
How to pass token using HTTP Header from one WLS domain to other?
Cookie works fine, but I need to user http header. I try to workout my problem using servlet filter, but it doesn't works :(
Best regards,
Pit

You'll need to use a custom Identity Asserter if you want to do something in the WLS security framework that simply looks for a particular header. There is an example on codeshare here:
https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=S189
You may want to describe your use-case a little more clearly as this may or may not be as secure as your requirements require. WLS can work with X509 certificates, which provide a secure option over SSL.

Similar Messages

Unable to start WLS8.1sp4 after extended with Integration &workshop Templat

Hi,
I've have configured three domains of WLS8.1sp4 on unique ports namely 6001, 7001 & 8001 but
only one domain can be started on the port 7001 but there is a problem starting the other ports.
All the three domains WLS were able to be started without any problem at all
before the domains were extended in the Weblogic Configuration
using the built-in Configuratino Wizard.
Could you assist ?
./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=:/dev_app/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/dev_app/bea/weblogic81/common/lib/log4j.jar:/dev_app/bea/weblogic81/server/lib/debugging.jar:/dev_app/bea/weblogic81/server/lib/knex.jar:/dev_app/bea/weblogic81/javelin/lib/javelin.jar:/dev_app/bea/weblogic81/server/lib/wlw-lang.jar:/dev_app/bea/jdk142_05/lib/tools.jar:/dev_app/bea/weblogic81/server/lib/weblogic_sp.jar:/dev_app/bea/weblogic81/server/lib/weblogic.jar:/dev_app/bea/weblogic81/server/lib/ant/ant.jar:/dev_app/bea/jdk142_05/jre/lib/rt.jar:::/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/dev_app/bea/weblogic81/server/lib/xbean.jar:/dev_app/bea/weblogic81/server/lib/wlxbean.jar:/dev_app/bea/weblogic81/server/lib/xqrl.jar:/dev_app/bea/weblogic81/server/lib/netui/netui-compiler.jar:/dev_app/bea/weblogic81/server/lib/wli.jar:/dev_app/bea/weblogic81/server/lib/fop.jar:/dev_app/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/dev_app/bea/weblogic81/server/bin:/dev_app/bea/jdk142_05/jre/bin:/dev_app/bea/jdk142_05/bin:/usr/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-480R/sbin:/opt/sun/bin::/opt/SUNWexplo/bin
* 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 *
starting weblogic with Java version:
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Starting WLS with line:
/dev_app/bea/jdk142_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=/dev_app/bea/weblogic81 -Dwls.home=/dev_app/bea/weblogic81/server -Dwli.home=/dev_app/bea/weblogic81/integration -Dlog4j.configuration=file:/dev_app/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=/dev_app/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Stopping the Weblogic Workshop debugger...
ERROR: Proxy already running...
weblogic.debugging.comm.SocketCommException
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:53)
at weblogic.debugging.comm.ServerSocketComm.accept(ServerSocketComm.java:53)
at weblogic.debugging.engine.ProxyThread.run(ProxyThread.java:81)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.InterruptedIOException: operation interrupted
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:47)
... 3 more
Debugger Stopped.
Stopping Pointbase server...
Pointbase server stopped.
Regards

Problem solved since default ports 8453 & 9093 were occupied
But behaviour on Windows for debug is different from Unix which requires unique potr althought windows still works.

Unable to start WLS8.1sp4 after extended with Workshop& Integration Templat

Hi,
I have configured three domains of WLS8.1sp4 on
unique ports namely 6001, 7001 & 8001 but
only one domain can be started on the port 7001
but there is a problem starting the other ports.
All the three domains WLS were able to be started
without any problem at all before the domains
were being extended with Workshop and Integration
Templates from the Basic Weblogic Server Domain
in the Weblogic Configuration using the built-in Configuratino Wizard.
Could someone please assist ?
./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=:/dev_app/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/dev_app/bea/weblogic81/common/lib/log4j.jar:/dev_app/bea/weblogic81/server/lib/debugging.jar:/dev_app/bea/weblogic81/server/lib/knex.jar:/dev_app/bea/weblogic81/javelin/lib/javelin.jar:/dev_app/bea/weblogic81/server/lib/wlw-lang.jar:/dev_app/bea/jdk142_05/lib/tools.jar:/dev_app/bea/weblogic81/server/lib/weblogic_sp.jar:/dev_app/bea/weblogic81/server/lib/weblogic.jar:/dev_app/bea/weblogic81/server/lib/ant/ant.jar:/dev_app/bea/jdk142_05/jre/lib/rt.jar:::/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/dev_app/bea/weblogic81/server/lib/xbean.jar:/dev_app/bea/weblogic81/server/lib/wlxbean.jar:/dev_app/bea/weblogic81/server/lib/xqrl.jar:/dev_app/bea/weblogic81/server/lib/netui/netui-compiler.jar:/dev_app/bea/weblogic81/server/lib/wli.jar:/dev_app/bea/weblogic81/server/lib/fop.jar:/dev_app/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/dev_app/bea/weblogic81/server/bin:/dev_app/bea/jdk142_05/jre/bin:/dev_app/bea/jdk142_05/bin:/usr/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-480R/sbin:/opt/sun/bin::/opt/SUNWexplo/bin
* 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 *
starting weblogic with Java version:
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Starting WLS with line:
/dev_app/bea/jdk142_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=/dev_app/bea/weblogic81 -Dwls.home=/dev_app/bea/weblogic81/server -Dwli.home=/dev_app/bea/weblogic81/integration -Dlog4j.configuration=file:/dev_app/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=/dev_app/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
Stopping the Weblogic Workshop debugger...
ERROR: Proxy already running...
weblogic.debugging.comm.SocketCommException
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:53)
at weblogic.debugging.comm.ServerSocketComm.accept(ServerSocketComm.java:53)
at weblogic.debugging.engine.ProxyThread.run(ProxyThread.java:81)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.InterruptedIOException: operation interrupted
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:47)
... 3 more
Debugger Stopped.
Stopping Pointbase server...
Pointbase server stopped.

Problem solved since default ports 8453 & 9093 were occupied
But behaviour on Windows for debug is different from Unix which requires unique potr althought windows still works.

Production issue; Please HELP !!! ...weired error while starting WLS8.1 server

Hi All/Rob,
Iam running WLS8.1+SP2 and i have 4 clusters each of these clusters contains 4
managed servers.
Now, iam getting a weired error when starting each of the instances ......this
is the Exception that iam getting:
PLEASE HELP AS THIS IS OUR PRODUCTION ISSUES ........
<Feb 25, 2004 11:42:29 AM EST> <Notice> <Security> <BEA-090082> <Security initializing
using security realm myrealm.>
<Feb 25, 2004 11:42:30 AM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting
WebLogic Managed Server "rsa_nova1t_s1" for domain "Mah-sub">
Failed setting Group
<Feb 25, 2004 11:42:39 AM EST> <Error> <Security> <BEA-090031> <Failed to Switch
to Group rsaadmin.>
Failed setting user
<Feb 25, 2004 11:42:39 AM EST> <Error> <Security> <BEA-090033> <Failed to Switch
to User rsaadmin.>
<Feb 25, 2004 11:42:39 AM EST> <Notice> <Cluster> <BEA-000138> <Listening for
announcements from cluster RSA on 237.0.3.11:8001.>
<Feb 25, 2004 11:42:39 AM EST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize
with other running members of RSA.>
<Feb 25, 2004 11:43:21 AM EST> <Warning> <HTTP> <BEA-101247> <admingui.war: Public
ID references the old version of the Servlet DTD. You must change the public ID
in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread
"ListenThread.Default" listening on port 8020, ip address 153.2.252.189>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <Cluster> <BEA-000102> <Joining cluster
RSA on 237.0.3.11:8001>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000330> <Started
WebLogic Managed Server "rsa_nova1t_s1" for domain "Mah-sub" running in Production
Mode>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server
started in RUNNING mode>
<Feb 25, 2004 12:02:23 PM EST> <Error> <Cluster> <BEA-000110> <Multicast socket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Feb 25, 2004 12:03:38 PM EST> <Error> <Cluster> <BEA-000110> <Multicast socket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Feb 25, 2004 12:09:11 PM EST> <Error> <Cluster> <BEA-000139> <There are two clusters
in the network that are possibly running different versions of WebLogic Server.
These two clusters probably name the same RSA and they are using same address
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:09:37 PM EST> <Error> <Cluster> <BEA-000110> <Multicast socket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Feb 25, 2004 12:09:59 PM EST> <Error> <Cluster> <BEA-000139> <There are two clusters
in the network that are possibly running different versions of WebLogic Server.
These two clusters probably name the same RSA and they are using same address
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:10:09 PM EST> <Error> <Cluster> <BEA-000110> <Multicast socket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Feb 25, 2004 12:12:43 PM EST> <Error> <Cluster> <BEA-000139> <There are two clusters
in the network that are possibly running different versions of WebLogic Server.
These two clusters probably name the same RSA and they are using same address
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:13:31 PM EST> <Error> <Cluster> <BEA-000139> <There are two clusters
in the network that are possibly running different versions of WebLogic Server.
These two clusters probably name the same RSA and they are using same address
237.0.3.11 and port 8001.>

Rob,
Each cluster uses UNIQUE IP address ......but here is the information that iam
getting .....if that is in any way related to this problem ....i ran this command
bash-2.03# java -cp /xx/bea/weblogic81/server/lib/weblogic.jar utils.MulticastTest
-A 237.0.3.11
***** WARNING ***** WARNING ***** WARNING *****
Do NOT use the same multicast address as a running WLS cluster.
Starting test. Hit any key to abort
Using multicast address 237.0.3.11:7001
Will send messages under the name 1077733276 every 2 seconds
Will print warning every 600 seconds if no messages are received
I (1077733276) sent message num 1
I (1077733276) sent message num 2
Received message 2 from 1077733276
I (1077733276) sent message num 3
Received message 3 from 1077733276
I (1077733276) sent message num 4
Received message 4 from 1077733276
I (1077733276) sent message num 5
Received message 5 from 1077733276
I (1077733276) sent message num 6
Received message 6 from 1077733276
I (1077733276) sent message num 7
Received message 7 from 1077733276
Rob Woollen <[email protected]> wrote:
First thing to check is that each cluster has its own multicast address.
It looks like the server is complaining that multiple clusters are using
237.0.3.11 and port 8001
-- Rob
steve wrote:
Hi All/Rob,
Iam running WLS8.1+SP2 and i have 4 clusters each of these clusterscontains 4
managed servers.
Now, iam getting a weired error when starting each of the instances......this
is the Exception that iam getting:
PLEASE HELP AS THIS IS OUR PRODUCTION ISSUES ........
<Feb 25, 2004 11:42:29 AM EST> <Notice> <Security> <BEA-090082> <Securityinitializing
using security realm myrealm.>
<Feb 25, 2004 11:42:30 AM EST> <Notice> <WebLogicServer> <BEA-000328><Starting
WebLogic Managed Server "rsa_nova1t_s1" for domain "Mah-sub">
Failed setting Group
<Feb 25, 2004 11:42:39 AM EST> <Error> <Security> <BEA-090031> <Failedto Switch
to Group rsaadmin.>
Failed setting user
<Feb 25, 2004 11:42:39 AM EST> <Error> <Security> <BEA-090033> <Failedto Switch
to User rsaadmin.>
<Feb 25, 2004 11:42:39 AM EST> <Notice> <Cluster> <BEA-000138> <Listeningfor
announcements from cluster RSA on 237.0.3.11:8001.>
<Feb 25, 2004 11:42:39 AM EST> <Notice> <Cluster> <BEA-000133> <Waitingto synchronize
with other running members of RSA.>
<Feb 25, 2004 11:43:21 AM EST> <Warning> <HTTP> <BEA-101247> <admingui.war:Public
ID references the old version of the Servlet DTD. You must change thepublic ID
in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application2.3//EN".>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000355><Thread
"ListenThread.Default" listening on port 8020, ip address 153.2.252.189>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <Cluster> <BEA-000102> <Joiningcluster
RSA on 237.0.3.11:8001>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000330><Started
WebLogic Managed Server "rsa_nova1t_s1" for domain "Mah-sub" runningin Production
Mode>
<Feb 25, 2004 11:47:33 AM EST> <Notice> <WebLogicServer> <BEA-000360><Server
started in RUNNING mode>
<Feb 25, 2004 12:02:23 PM EST> <Error> <Cluster> <BEA-000110> <Multicastsocket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Feb 25, 2004 12:03:38 PM EST> <Error> <Cluster> <BEA-000110> <Multicastsocket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Feb 25, 2004 12:09:11 PM EST> <Error> <Cluster> <BEA-000139> <Thereare two clusters
in the network that are possibly running different versions of WebLogicServer.
These two clusters probably name the same RSA and they are using sameaddress
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:09:37 PM EST> <Error> <Cluster> <BEA-000110> <Multicastsocket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Feb 25, 2004 12:09:59 PM EST> <Error> <Cluster> <BEA-000139> <Thereare two clusters
in the network that are possibly running different versions of WebLogicServer.
These two clusters probably name the same RSA and they are using sameaddress
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:10:09 PM EST> <Error> <Cluster> <BEA-000110> <Multicastsocket
receive error: java.io.StreamCorruptedException
java.io.StreamCorruptedException
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2350)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2660)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:900)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:379)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Feb 25, 2004 12:12:43 PM EST> <Error> <Cluster> <BEA-000139> <Thereare two clusters
in the network that are possibly running different versions of WebLogicServer.
These two clusters probably name the same RSA and they are using sameaddress
237.0.3.11 and port 8001.>
<Feb 25, 2004 12:13:31 PM EST> <Error> <Cluster> <BEA-000139> <Thereare two clusters
in the network that are possibly running different versions of WebLogicServer.
These two clusters probably name the same RSA and they are using sameaddress
237.0.3.11 and port 8001.>

JMS Messaging Bridge WLS8.1

          Hello All,
          I am trying to hook up 2 Queues as source and target destinations for the WLS8.1
          Messaging Bridge[MB] functionality.
          So when I send a message to Q1[source destination], the MB forwards the message
          to Q2[target destination].
          I have 1 MDB deployed and listening on Q2.
          I verify the messages received via the admin console in wls8.1 as well as the
          MDB I have deployed.
          Thus, the MB works.
          However, when I deploy a MDB on Q1 as well, the message is lost(not forwaded to
          Q1 by the MB).
          Assuming that the source destination is of type Queue, and this behaviour is expected,
          I went to test with a Topic as source destination for the MB and a Queue as the
          target destination for the MB.
          However, I failed to receive any messages in the dest[Q2] via the MB.
          This is with / without a MDB listening on the Topic[source destination].
          One MDB is always listening on the Queue[target destination].
          MB does not work.............
          Can anyone help ?
          TIA.


There is no native code specific to this use case, except
          perhaps for IBM code, and I know of no issues.
          Raja wrote:
          > I have tested Messaging Bridge(jms-xa-adp.rar),Foreign JMS provider in WLS8.1-SP1
          > on windows NT m/c.Can any body tell me whether there will any problem while setting
          > up and running the same test on Solaris.
          >
          > Thanks in advance,
          > Raja

Complex types in fault messages - is this possible in WLS8.1?

Hi all,
I'm writing a standard WSDL and want to return a complex type (or at least, a customised simple type) in a fault. This has been previously discussed here: http://forums.bea.com/bea/thread.jspa?threadID=600004053&tstart=15. I've given full details below, but the short story is that if a <fault> message if a complex type, then wsdl2service fails with odd errors. If on the same WSDL/schema I change the exception type to a builtin type (like xsd:string), it all works fine.
Google yields nothing, but if anyone has some pointers on how to do it or where to read, I'd be grateful.
Cheers,
-Tim West
Details:
I have a message and operation:
<message name="AirlineException">
 <part name="AirlineException" element="tns:AirlineException"/>
</message>
<portType name="AirlinePort">
 <operation name="getCustomer">
 <input message="tns:getCustomerIn"/>
 <output message="tns:getCustomerOut"/>
 <fault name="AirlineException" message="tns:AirlineException"/>
 </operation>
</portType>Where AirlineException is defined thus:
 <complexType name="AException">
 <sequence>
 <element name="message" type="string" nillable="true"/>
 </sequence>
 </complexType>
 <element name="AirlineException" type="tns:AException"/>(If I can get this to work, I will flesh out the complexType with some more information).
When I attempt to generate bindings with autotype and wsdl2service, autotype works but wsdl2service fails like this:
generate-server-binding-jar:
[autotype] Autotyping for wsdl Deploy/airline/airline-ws-server_war/WEB-INF/airline.wsdl
[wsdl2service] Generating web service from wsdl Deploy/airline/airline-ws-server_war/WEB-INF/airline.wsdl
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:13:
 package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] private org.jacksonwest.airline.binding.types.AException info;
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:15:
 package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public AirlineException(org.jacksonwest.airline.binding.types.AException t) {
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:19:
 package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public org.jacksonwest.airline.binding.types.AException getAirlineException() {
[wsdl2service] ^
[wsdl2service] C:\...\org\jacksonwest\airline\binding\AirlineException.java:23:
 package org.jacksonwest.airline.binding.types does not exist
[wsdl2service] public void setAirlineException(org.jacksonwest.airline.binding.types.AException t) {
[wsdl2service] ^
[wsdl2service] 4 errors
[wsdl2service] java.io.IOException: Compiler failed executable.execNow, if I change the type of element 'AirlineException' to a built-in type like 'string', it all works fine. Also, I can use the generated 'AException' type in an <input> or <output> message - it's the combination of complexType and <fault> that causes the problem.
My service was originally document/literal, and I've since rewritten it as rpc/literal, as I've had more success with rpc than document on Java platforms. The problem exists in both WSDL styles.
I've read at http://e-docs.bea.com/wls/docs81/notes/new.html that WLS8.1 should be now able to handle complexTypes in faults, but for the life of me I can't do it!

I got it :)
The bizarre compile errors were being caused by the old version of the classes being present on the classpath that I supplied to wsdl2service. When I removed them (leaving only weblogic.jar and webservices.jar on the classpath), it worked fine first time.
So, my guess is that the ones on the classpath (the old ones) were taking precedence over the newly-generated ones, and these were obviously not compatible!
Cheers,
-Tim

WLS8.1sp2 - PKCS#11 Provider for WebCertificates error

I'm trying to startup a WLS Server, which has his web certificates stored in a
HW Devices. Der CryptoProvider read via PKCS#11 the certificates out of the HW
Module. Unfortunatly the possibile operation via PKCS#11 are not the same as via
a PKCS#12 (basically: you can not read a PrivateKey out of a PKCS#11 as you do
out of Sun JKS implementation).
I got following error:
<29.04.2004 13.55 Uhr CEST> <Notice> <Security> <BEA-090170> <Loading the private
key stored under the alias Wxxxxxx.csintra.net from the CS_PKI keystore file C:\apps\Tip300\cs\pki\pki420\api\config\pkiapi_Websrv_etit.properties.>
<29.04.2004 13.55 Uhr CEST> <Notice> <Security> <BEA-090171> <Loading the identity
certificate stored under the alias Wxxxxxx.csintra.net from the CS_PKI keystore
file C:\apps\Tip300\cs\pki\pki420\api\config\pkiapi_Websrv_etit.properties.>
<29.04.2004 13.55 Uhr CEST> <Error> <WebLogicServer> <BEA-000297> <Inconsistent
security configuration, java.lang.Exception: The public key from the configured
server certificate and the configured server private key do not match.>
<29.04.2004 13.55 Uhr CEST> <Emergency> <Security> <BEA-090034> <Not listening
for SSL, java.io.IOException: Inconsistent security configuration, The public
key from the configured server certificate and the configured server private key
do not match..>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic
Admin Server "myserver" for domain"cfwdomain" running in Production Mode>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000360> <Server started
in RUNNING mode>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default"
listening on port 7770, ip address *.*>
Is anyone already sperimenting with PKCS#11 and WLS8.1sp2?
Has anyone had the same problem or does it depend from the crypto provider we
are using?
Best Regards
carlo

The error happened when the ssl implementation tried to test the keys. To check
whether they match it obtained raw RSA Cipher (RSA/ECB/NoPadding) and tried to
encrypt some text with the private key and decrypt it with the public key. Since
the private key is not a real key it failed. So if you had an RSA cipher provider
installed that could work with your hw accelerator to encrypt with that private
key you could work around this problem.
In 8.1 we support nCipher HW accelerator, and we had to work around several issues
to make it work. One of the workarounds was to ignore the KeyManagementException
that happens during this key match check when nCipher is installed. Apparently
in your case this exception does not happen and this check executes normally,
but returns the negative result.
Pavel.
"Carlo de Rossi" <[email protected]> wrote:
>
I'm trying to startup a WLS Server, which has his web certificates stored
in a
HW Devices. Der CryptoProvider read via PKCS#11 the certificates out
of the HW
Module. Unfortunatly the possibile operation via PKCS#11 are not the
same as via
a PKCS#12 (basically: you can not read a PrivateKey out of a PKCS#11
as you do
out of Sun JKS implementation).
I got following error:
<29.04.2004 13.55 Uhr CEST> <Notice> <Security> <BEA-090170> <Loading
the private
key stored under the alias Wxxxxxx.csintra.net from the CS_PKI keystore
file C:\apps\Tip300\cs\pki\pki420\api\config\pkiapi_Websrv_etit.properties.>
<29.04.2004 13.55 Uhr CEST> <Notice> <Security> <BEA-090171> <Loading
the identity
certificate stored under the alias Wxxxxxx.csintra.net from the CS_PKI
keystore
file C:\apps\Tip300\cs\pki\pki420\api\config\pkiapi_Websrv_etit.properties.>
<29.04.2004 13.55 Uhr CEST> <Error> <WebLogicServer> <BEA-000297> <Inconsistent
security configuration, java.lang.Exception: The public key from the
configured
server certificate and the configured server private key do not match.>
<29.04.2004 13.55 Uhr CEST> <Emergency> <Security> <BEA-090034> <Not
listening
for SSL, java.io.IOException: Inconsistent security configuration, The
public
key from the configured server certificate and the configured server
private key
do not match..>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000329> <Started
WebLogic
Admin Server "myserver" for domain"cfwdomain" running in Production Mode>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000360> <Server
started
in RUNNING mode>
<29.04.2004 13.55 Uhr CEST> <Notice> <WebLogicServer> <BEA-000355> <Thread
"ListenThread.Default"
listening on port 7770, ip address *.*>
Is anyone already sperimenting with PKCS#11 and WLS8.1sp2?
Has anyone had the same problem or does it depend from the crypto provider
we
are using?
Best Regards
carlo

Non-XA behavior in WLS8.1 different from WLS7.0?

Hello,
I recently upgraded from WLS 7 to WLS8.1.
My code that was using EJBs with transactionAttrbute set to Required has a method
that makes calls to 2 databases: one SELECT and another UPDATE.
In WLS7.0 I was using a non-XA driver and there was no error issued.
In WLS8.1 with the same driver I get: Exception: java.sql.SQLException: Connection
has already been created in this tx context for pool named iSitePool. Illegal
attempt to create connection from another pool: GDSPool
I understood this error message when I read in the WLS 8.1 documentation
(http://e-docs.bea.com/wls/docs81/faq/JTA.html#737730) where it states that I
cannot have 2 non-XA connections to different dbs withing a distribute txn even
if EnabledTwoPhaseCommit=true.
However, what surprised me is that this exact same warning is specified in WLS
7.1 documentation also (http://e-docs.bea.com/wls/docs70/faq/JTA.html#738373).
I am not able to understand how my code worked in WLS7.1! Is it that WLS 8.1 just
tightened the screws on a warning that it issued with 7.1?
Before I move to an XA driver, I wanted to confirm that that is indeed the case.
Thanks
Pankaj

Pankaj Tandon wrote:
Thanks for that confirmation. Just to bring this topic to closure..
I found out that I had configured the wrong data source.
In WLS7 we had TxDataSources and regular DataSources, whereas in WLS8.1 there
is a 'Honor Global Transactions' checkbox which means the same thing. The upshot
is that I cannot have 2 TxDataSources in a distributed txn. So, correspondingly,
In 8.1, I cannot have two 'Honor...' set to true in the same distributed txn.Correct. You have it right.
Joe
>
>
>
Joe Weinstein <[email protected]> wrote:
Pankaj Tandon wrote:
Hello,
I recently upgraded from WLS 7 to WLS8.1.
My code that was using EJBs with transactionAttrbute set to Requiredhas a method
that makes calls to 2 databases: one SELECT and another UPDATE.
In WLS7.0 I was using a non-XA driver and there was no error issued.
In WLS8.1 with the same driver I get: Exception: java.sql.SQLException:Connection
has already been created in this tx context for pool named iSitePool.Illegal
attempt to create connection from another pool: GDSPool
I understood this error message when I read in the WLS 8.1 documentation
(http://e-docs.bea.com/wls/docs81/faq/JTA.html#737730) where it states
that I
cannot have 2 non-XA connections to different dbs withing a distributetxn even
if EnabledTwoPhaseCommit=true.
However, what surprised me is that this exact same warning is specifiedin WLS
7.1 documentation also (http://e-docs.bea.com/wls/docs70/faq/JTA.html#738373).
I am not able to understand how my code worked in WLS7.1! Is it thatWLS 8.1 just
tightened the screws on a warning that it issued with 7.1?
Before I move to an XA driver, I wanted to confirm that that is indeedthe case.
Hi. No, in both servers, you should have been stopped from involving
two
DBMSes in a non-XA transaction.. I have not heard of any other case in
7.1 where
two non-XA (jts) connections were allowed to partake in a given tx.
Joe
Thanks
Pankaj

Unable to find "OAM IdentityAsserter" in weblogic

Hi alll,
I'm trying to setup SSO for the development purpose (Test Environment). I installed all the application as specified in the oracle document.
While configuring the weblogic, under the Security Realms -> my realm -> Providers -> Authentication -> its asked to create "New Authentication Provider"
Then i'm giving the as mentioned "OAM ID ASSERTER" then i need to select Type as "OAM IdentityAsserter", but I'm unable to find that option.
Please guide me how to get that. is there any plugin required or am I missing something here..
Please help..
Thanks
Lakshmi

hi,
i installed OAM,OHS,Webgate,weblogic in one machine and installed only weblogic in second machine. Deployed a webapplication in second machine weblogic server and i am trying to protect the webapplication using OAM. I am trying to install Access Gate in second machine but i did not find any Access Gate installer for OAM 11g.where can i download configure Acessgate.exe . is Access Gate Required for weblogic server.
Thanks,

Handling of IdentityAsserter's SecurityException on extend client

Coherence 3.7.1.7
I have a custom implementation of com.tangosol.net.security.IdentityAsserter for authorization of extend clients.
It looks something like this:
 public Subject assertIdentity(Object credentials, Service service) throws SecurityException {
 if (!userNameValid(credentials) {
 throw new SecurityException("Username is not valid");
 if (!passwordValid(credentials) {
 throw new SecurityException("Password is not valid");
 return subject;
If I throw any SecurityException with any error message in IndenityAsserter I get the same error on extend client:
2014-10-17 18:27:41.655/29.828 Oracle Coherence GE 3.7.1.7 <D5>: Connecting Socket to 10.75.82.176:8200
2014-10-17 18:27:41.702/29.875 Oracle Coherence GE 3.7.1.7 <Info>: Connected Socket to 10.75.82.176:8200
2014-10-17 18:27:45.108/33.281 Oracle Coherence GE 3.7.1.7 <D5>: Redirecting Socket to 10.75.82.182:8201
2014-10-17 18:27:45.155/33.328 Oracle Coherence GE 3.7.1.7 <Info>: Connected Socket to 10.75.82.182:8201
2014-10-17 18:27:46.217/34.390 Oracle Coherence GE 3.7.1.7 <Info>: Error establishing a connection with 10.75.82.182:8201: com.tangosol.net.messaging.ConnectionException: connection rejected
2014-10-17 18:27:47.389/35.562 Oracle Coherence GE 3.7.1.7 <D5>: Redirecting Socket to 10.75.82.158:8201
2014-10-17 18:27:47.436/35.609 Oracle Coherence GE 3.7.1.7 <Info>: Connected Socket to 10.75.82.158:8201
2014-10-17 18:27:48.499/36.672 Oracle Coherence GE 3.7.1.7 <Info>: Error establishing a connection with 10.75.82.158:8201: com.tangosol.net.messaging.ConnectionException: connection rejected
2014-10-17 18:27:48.499/36.672 Oracle Coherence GE 3.7.1.7 <D5>: Redirecting Socket to 10.75.82.176:8200
2014-10-17 18:27:48.545/36.718 Oracle Coherence GE 3.7.1.7 <Info>: Connected Socket to 10.75.82.176:8200
2014-10-17 18:27:49.639/37.812 Oracle Coherence GE 3.7.1.7 <Info>: Error establishing a connection with 10.75.82.176:8200: com.tangosol.net.messaging.ConnectionException: connection rejected
2014-10-17 18:27:49.639/37.812 Oracle Coherence GE 3.7.1.7 <Error>: Error while starting service "ExtendTcpService": com.tangosol.net.messaging.ConnectionException: could not establish a connection to one of the following addresses: [10.75.82.176:8200, 10.75.82.182:8201, 10.75.82.138:8200, 10.75.82.158:8201, 10.75.82.176:8200]; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator.openConnection(TcpInitiator.CDB:120)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:11)
at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:5)
at com.tangosol.coherence.component.net.extend.RemoteService.doStart(RemoteService.CDB:11)
at com.tangosol.coherence.component.net.extend.RemoteService.start(RemoteService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:39)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:1105)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
It's impossible to determine the real reason why connection was rejected from this exception. Is it because username was incorrect? Or password? Or any other credentials? Or maybe coherence cluster is indeed down? I would like to handle each of such situations differently.
My question: is it possible to intercept and handle exceptions thrown in IdentityAsserter on client side?

Hi 
 
 I'm using version 9.2.0.0 with the following patches:
 <ul>
 <li>CR286749</li>
 <li>CR277158</li>
 <li>CR307754</li>
 <li>CR295248</li>
 <li>CR304536</li>
 </ul>
 
 
 It is possible to grant access to the user to the jndi node (e.g. weblogic.jms.connection), so he will be able to perform this operation over whole subtree, but this is not very neat and, what is more important, he will have access to the jndi objects, that he shold not.
 
 
 In fact I have decided to grant this user full access to the jndi tree, but gave limited access at the JMS level and no access to other resources (like EJB, JDBC, etc). This seems to work well.
 
 regards 
 Lukas 
 WLS 9.2

J2EE vs WLS8.1 security

In J2EE we can define permissions and roles in web.xml and ejb-jar.xml, and
in WLS6.1 we define role-principal mapping in weblogic.xml or
weblogic-ejb-jar.xml. We have methods like getUserPrincipal() or
isUserInRole() in HttpServletRequest and EJBContext.
In WLS8.1 we can define global roles, scoped roles, security policies in the
console. How do these interact with the J2EE model? For example, can I put
a global role name in isUserInRole()? If I have configured security
policies on a webapp, when I redeploy it does it revert back to the
definitions in web.xml and weblogic.xml? Is there any documentation on
these issues? Thanks.
-- Chuck

"Chuck Zhao" <[email protected]> wrote:
In J2EE we can define permissions and roles in web.xml and ejb-jar.xml,
and
in WLS6.1 we define role-principal mapping in weblogic.xml or
weblogic-ejb-jar.xml. We have methods like getUserPrincipal() or
isUserInRole() in HttpServletRequest and EJBContext.
In WLS8.1 we can define global roles, scoped roles, security policies
in the
console. How do these interact with the J2EE model? For example, can
I put
a global role name in isUserInRole()? If I have configured security
policies on a webapp, when I redeploy it does it revert back to the
definitions in web.xml and weblogic.xml? Is there any documentation
on
these issues? Thanks.
-- Chuckhttp://edocs.bea.com/wls/docs81/secwlres/types.html#1208206

Errors being used by a bean in wls8.1

i have many ss ejbs running in wls 6.1 under domain1. i have one ss ejb (called
Submit) running in wls 6.1 under domain2 which makes calls to the beans in domain1.
this is working fine.
i'm migrating domain2 to use wls8.1, and am getting all kinds of errors when using
the Submit ejb. i'm using the below service pack. any ideas why this is happening
and what I can do to resolve these errors? things I've tried unsuccessfully so
far are:
1. build everything using the 1.4.x jdk included w/ 8.1
2. ensure Submit bean is being built by 8.1 (ant scripts were using ejbc from
the 6.1 area).
that's about it.
wls service pack:
CR064650_CR064449_CR065213_CR064391_61sp2.jar
errors:
####<Dec 4, 2003 12:31:39 PM EST> <Error> <Default> <mlybarger> <myserver> <ExecuteThread:
'12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <000000> <EventSubmitBean.submit()
- error: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception
is:
 java.lang.ClassNotFoundException: sun.util.calendar.ZoneInfo
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
 java.lang.ClassNotFoundException: sun.util.calendar.ZoneInfo
java.lang.ClassNotFoundException: sun.util.calendar.ZoneInfo
 at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:179)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:195)
 at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:126)
 at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:211)
 at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:300)
 at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.skipToEndOfBlockData(ObjectInputStream.java:1494)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1436)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1412)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1412)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
 at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
 at com.cbc.isac.ejb20.event.EventMaintenanceBean_gwclhj_EOImpl_WLSkel.invoke(Unknown
Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
 at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
 java.lang.ClassNotFoundException: sun.util.calendar.ZoneInfo

You're only addressing other users here - you might want to try feedback:
http://www.apple.com/feedback/

Sybase jdbc throws Resource PermissionsException wls8.1 sp2

HI,
I just upgraded from wls 6.1 to wls 8.1 sp2. My Connection pools are not working
anymore.
I am using sybase server 11.5.1 with the jconnect 5. I am making database calls
(that
used to work). Here's the strange thing, I have a startup class that runs an
sql query when weblogic server comes up (in the main thread i am assuming) and
it works. But calling the same exact sql query fails when i click on my webapp
that leads to the same query (it is called from a different thread).
Any ideas? I am assuming it's a security issue where the main thread uses the
correct username and password and the other threads don't. Heres my config file
and my exception trace:
<JDBCTxDataSource JNDIName="FOO" Name="MyJDBC Data Source"
PoolName="MyJDBC Connection Pool-1" Targets="portal"/>
<JDBCConnectionPool DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Name="MyJDBC Connection Pool-1" Password="xxx"
Properties="user=vwap;url=jdbc:sybase:Tds:myhost:9501/vwap;networkProtocol=Tds;portNumber=9501;userName=vwap;databaseName=vwap;serverName=myhost"
Targets="portal"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:sybase:Tds:myhost:9501/vwap"/>
I also tried it with weblogic sybase driver and same results:
<JDBCConnectionPool DriverName="weblogic.jdbc.sybase.SybaseDriver"
Name="MyJDBC Connection Pool" Password="xxx"
Properties="user=vwap;url=jdbc:bea:sybase://myhost:9501;portNumber=9501;databaseName=vwap;serverName=myhost"
Targets="portal"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sybase://myhost:9501"/>
error.weblogic.common.resourcepool.ResourcePermissionsException: User "<anonymous>"
does not have permission to perform operation "reserve" on resource "MyJDBC Connection
Pool-1" of application "null" of type "ConnectionPool"
weblogic.jdbc.extensions.PoolPermissionsSQLException: weblogic.common.resourcepool.ResourcePermissionsException:
User "<anonymous>" does not have permission to perform operation "reserve" on
resource "MyJDBC Connection Pool-1" of application "null" of type "ConnectionPool"
 at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:157)
 at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
 at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444)
 at weblogic.jdbc.jts.Driver.connect(Driver.java:138)
 at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
 at com.itginc.strategyServers.common.database.Database.initializeUserCache(Database.java:729)
 at com.itginc.strategyServers.common.database.Database.connect(Database.java:104)
 at com.itginc.strategyServers.common.database.Database.getClients(Database.java:157)
 at com.itginc.strategyServers.common.servlets.ClientsServlet.doPost(ClientsServlet.java:41)
 at com.itginc.strategyServers.common.servlets.BaseServlet.doGet(BaseServlet.java:110)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at com.itginc.strategyServers.common.servlets.BaseServlet.service(BaseServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:301)
 at com.itginc.strategyServers.common.servlets.LoginServlet.doPost(LoginServlet.java:230)
 at com.itginc.strategyServers.common.servlets.LoginServlet.doGet(LoginServlet.java:242)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

farnaz wrote:
I changed the following line in my fileRealm.properties and fixed the problem.
Is this the correct thing to do?
acl.reserve.weblogic.jdbc.connectionPool=system
changed to
acl.reserve.weblogic.jdbc.connectionPool=everyoneyes.
Joe
>
>
>
>
"farnaz" <[email protected]> wrote:
A few issues, i've been stuck on this problem for 2 days now, please
HELP!
1. My acl settings (i looked at them via the console) seems to have "everyone"
permission for all jdbc operations: reserve, shrink, etc.
2. If acl is not the way to set security policies why is it shown in
the console?
3. I cannot find anywhere in the wls8.1 documentation on how to set security
policies
for jdbc.
Can i see an example?
4. I was not using any java securtiy when i got that error, so then I
added the
-Djava.security.manager to my startup cmd line for starting weblogic
using the
default weblogic policy in $WLSHOME/server/lib/weblogic policy (unmodified)
and
got the following exception on startup, help!
The Horizon Portal could not be started, because the Application Manager
failed
to initialize. access denied (java.lang.RuntimePermission weblogic.kernelPermission)
java.security.AccessControlException: access denied (java.lang.RuntimePermission
weblogic.kernelPermission)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java:270)
 at java.security.AccessController.checkPermission(AccessController.java:401)
 at weblogic.security.service.SubjectManagerImpl.checkKernelPermission(SubjectManagerImpl.java:202)
 at weblogic.security.service.SubjectManagerImpl.getKernelIdentity(SubjectManagerImpl.java:181)
 at weblogic.security.subject.SubjectManager.isKernelIdentity(SubjectManager.java:102)
 at weblogic.security.service.SubjectManagerImpl.checkKernelIdentity(SubjectManagerImpl.java:214)
 at weblogic.security.subject.DelegatingSubjectStack.getCurrentSubject(DelegatingSubjectStack.java:31)
 at weblogic.security.service.SubjectManagerImpl.getCurrentSubject(SubjectManagerImpl.java:61)
 at weblogic.security.service.SecurityManager.getCurrentSubject(SecurityManager.java:43)
 at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:330)
 at weblogic.jndi.internal.ServerNamingNode.checkModify(ServerNamingNode.java:306)
 at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:166)
 at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:382)
 at weblogic.jndi.internal.WLEventContextImpl.rebind(WLEventContextImpl.java:118)
 at javax.naming.InitialContext.rebind(InitialContext.java:363)
 at com.itginc.strategyServers.common.database.DatabaseLookup.bind(DatabaseLookup.java:45)
 at com.itginc.strategyServers.horizon.services.AppManager.Initialize(AppManager.java:66)
 at com.itginc.strategyServers.horizon.services.AppManager.<init>(AppManager.java:44)
 at com.itginc.strategyServers.horizon.services.AppManager.makeClass(AppManager.java:22)
 at com.itginc.strategyServers.horizon.services.Startup.startup(Startup.java:27)
 at weblogic.t3.srvr.StartupClassService.invokeStartup(StartupClassService.java:177)
 at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:158)
 at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
 at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116)
 at weblogic.t3.srvr.PostDeploymentStartupService.resume(PostDeploymentStartupService.java:22)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
 at weblogic.Server.main(Server.java:32)
Joe Weinstein <[email protected]> wrote:
Hi. Two things:
Your test table SQL is wasteful. sysobjects is a big table. No needto
count everything
in it every time to check the connections. Try "SQL select 1" for abetter
one.
The problem isn't in the pool definition. It's a security issue. You
should edit your
weblogic.policy file to allow jdbc access to everyone.
Joe
farnaz wrote:
HI,
I just upgraded from wls 6.1 to wls 8.1 sp2. My Connection pools
are
not working
anymore.
I am using sybase server 11.5.1 with the jconnect 5. I am making
database
calls
(that
used to work). Here's the strange thing, I have a startup class thatruns an
sql query when weblogic server comes up (in the main thread i am assuming)and
it works. But calling the same exact sql query fails when i clickon my webapp
that leads to the same query (it is called from a different thread).
Any ideas? I am assuming it's a security issue where the main threaduses the
correct username and password and the other threads don't. Heres
my
config file
and my exception trace:
<JDBCTxDataSource JNDIName="FOO" Name="MyJDBC Data Source"
PoolName="MyJDBC Connection Pool-1" Targets="portal"/>
<JDBCConnectionPool DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Name="MyJDBC Connection Pool-1" Password="xxx"
Properties="user=vwap;url=jdbc:sybase:Tds:myhost:9501/vwap;networkProtocol=Tds;portNumber=9501;userName=vwap;databaseName=vwap;serverName=myhost"
Targets="portal"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:sybase:Tds:myhost:9501/vwap"/>
I also tried it with weblogic sybase driver and same results:
<JDBCConnectionPool DriverName="weblogic.jdbc.sybase.SybaseDriver"
Name="MyJDBC Connection Pool" Password="xxx"
Properties="user=vwap;url=jdbc:bea:sybase://myhost:9501;portNumber=9501;databaseName=vwap;serverName=myhost"
Targets="portal"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sybase://myhost:9501"/>
error.weblogic.common.resourcepool.ResourcePermissionsException: User"<anonymous>"
does not have permission to perform operation "reserve" on resource"MyJDBC Connection
Pool-1" of application "null" of type "ConnectionPool"
weblogic.jdbc.extensions.PoolPermissionsSQLException: weblogic.common.resourcepool.ResourcePermissionsException:
User "<anonymous>" does not have permission to perform operation "reserve"on
resource "MyJDBC Connection Pool-1" of application "null" of type
"ConnectionPool"
 at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:157)
 at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
 at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444)
 at weblogic.jdbc.jts.Driver.connect(Driver.java:138)
 at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
 at com.itginc.strategyServers.common.database.Database.initializeUserCache(Database.java:729)
 at com.itginc.strategyServers.common.database.Database.connect(Database.java:104)
 at com.itginc.strategyServers.common.database.Database.getClients(Database.java:157)
 at com.itginc.strategyServers.common.servlets.ClientsServlet.doPost(ClientsServlet.java:41)
 at com.itginc.strategyServers.common.servlets.BaseServlet.doGet(BaseServlet.java:110)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at com.itginc.strategyServers.common.servlets.BaseServlet.service(BaseServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:301)
 at com.itginc.strategyServers.common.servlets.LoginServlet.doPost(LoginServlet.java:230)
 at com.itginc.strategyServers.common.servlets.LoginServlet.doGet(LoginServlet.java:242)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

WLS8.1 and tightly coupled transactions?

I have the following scenarion that does not seem to work.
          1. A client calls a method in EJB1
          2. EJB1 inserts a row in a database
          3. EJB1 calls a method in EJB2
          4. EJB2 tries to read or reference the row inserted by EJB1.
          5. The database waits and eventualy an Exception is thrown.
          It seems as WLS treats the XA-transaction as loosley-coupled (see the XA-specification). The behaviour that I want is a tightly-coupled transaction, but that does not seem to be the case.
          - I'm using WLS8.1sp4
          - EJB1 and EJB2 are stateless session beans using CMT and default behaviour.
          - EJB1 and EJB2 uses different database pools.
          - I'm using Informix 7.31 Database and Informix JDBC XA Driver 2.21JC6
          Anybody that have any ideas about this?

Hakan Waller wrote:
          > I have the following scenarion that does not seem to work.
          >
          > 1. A client calls a method in EJB1
          > 2. EJB1 inserts a row in a database
          > 3. EJB1 calls a method in EJB2
          > 4. EJB2 tries to read or reference the row inserted by EJB1.
          > 5. The database waits and eventualy an Exception is thrown.
          >
          > It seems as WLS treats the XA-transaction as loosley-coupled (see the XA-specification). The behaviour that I want is a tightly-coupled transaction, but that does not seem to be the case.
          >
          > - I'm using WLS8.1sp4
          > - EJB1 and EJB2 are stateless session beans using CMT and default behaviour.
          > - EJB1 and EJB2 uses different database pools.
          > - I'm using Informix 7.31 Database and Informix JDBC XA Driver 2.21JC6
          >
          > Anybody that have any ideas about this?
          I think the issue is that the data inserted in EJB1 is not available
          for anyone else to see until that EJB's transaction is committed.
          If EJB2 is defined so that it joins the same transaction, it should
          be able to see the not-yet committed data, but if it's a different
          tx, it shouldn't. However, how is EJB2 able to access the data via
          a different pool than the one used to insert the (not-yet committed)
          data?
          Joe

Oracle.security.jps.JpsPermission IdentityAssertion

Hello Experts,
Please note that I am getting the below error in my production box.
####<Mar 4, 2013 9:42:33 AM AST> <Notice> <Diagnostics> <RB1-SOA-01> <soa_server1> <[ACTIVE] ExecuteThread: '57' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <932e7620e6d94c34:-21663e16:13d1b17f9fa:-8000-0000000000018e6e> <1362379353667> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'soa_server1' has triggered at Mar 4, 2013 9:42:33 AM AST. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = Mar 4, 2013 9:42:33 AM AST SERVER = soa_server1 MESSAGE = [ServletContext@2063961084[app:ConductInspections module:ConductInspections.war path:/workflow/ConductInspections spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@461540c5[
POST /workflow/ConductInspections/notification/secure?bpmWorklistContext=%3B%3BGKX%2B61AxigI0UYXdsRHyr09KMN%2BsG%2BYttpyIOOkr%2BIoYDudg7FSa25wMK0NYyCLmou5ptBAzdFjUHBHsPZkB0gpzXHzE5F%2Fabwj7jj72lTY%3D&bpmWorklistTaskFormFwdUrl=%2Ffaces%2Fadf.task-flow%3Ftz%3DAsia%252FRiyadh%26df%3Dmedium%26dt%3Dboth%26tf%3Dshort%26lg%3Den%26cy%3DUS%26bpmWorklistTaskId%3D72d60354-cb92-407c-8e8e-5ea4dbc14ebb%26bpmWorklistTaskVersion%3D1%26bpmWorklistContext%3D0575fa9d-25cf-408e-98da-8671dd5f5857%253B%253BzoAe2Jnbf2CnGbrUn8RGQsUA9bo5ouv%252FI0cQbEQ3PX80o4EpRP3HS7r1PLIDz%252FURFYg5Bc9cLk6d6xE6e71E22IuirGFJcstHHurrf24O7PK8Dilf8cuZwyhuNouljYuSZFrbydpzi9uwlxSFeFqFfmxnFdC7SLrhmCAVANCQL8IWikPJVcN6pGSsnImOz1%252B72PjSRH8KnUsQ6sYbkl3wb47WOMb7u2KudFsYjId4Rg4Qp43jDTsa3LRL08Y2LqX%26bpmClientType%3DnotificationClient%26org.apache.myfaces.trinidad.agent.email%3Dtrue%26_id%3DApproveInspectionReport_TaskFlow%26_document%3DWEB-INF%252FApproveInspectionReport_TaskFlow.xml HTTP/1.1
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows NT 5.0) Oracle HTTPClient Version 10h
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context: 1.0000Joo8Zr4Dg^15zvS4yW1HBT^E001Y_e;kfvE
Content-type: application/octet-stream
Content-Length: 0
]] Root cause of ServletException.
java.security.AccessControlException: access denied (oracle.security.jps.JpsPermission IdentityAssertion)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
 at java.security.AccessController.checkPermission(AccessController.java:546)
 at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:378)
 at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:438)
 at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:460)
 at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.checkPermission(AbstractSubjectSecurity.java:113)
 at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.getActionExecutor(AbstractSubjectSecurity.java:76)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter$1.run(WorkflowFilter.java:231)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.invokeFilterChainSecurely(WorkflowFilter.java:228)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:156)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:527)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
 at oracle.bpel.services.workflow.client.worklist.servlet.SecureNotificationServlet.securelyForwardToUrl(SecureNotificationServlet.java:100)
 at oracle.bpel.services.workflow.client.worklist.servlet.SecureNotificationServlet.service(SecureNotificationServlet.java:83)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '32' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = RB1-SOA-01 TXID = CONTEXTID = 932e7620e6d94c34:-21663e16:13d1b17f9fa:-8000-0000000000018e6d TIMESTAMP = 1362379353651
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
>
please advise.
Mohammed. Abdul Muqeet

Hello Experts,
Please note that I am getting the below error in my production box.
####<Mar 4, 2013 9:42:33 AM AST> <Notice> <Diagnostics> <RB1-SOA-01> <soa_server1> <[ACTIVE] ExecuteThread: '57' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <932e7620e6d94c34:-21663e16:13d1b17f9fa:-8000-0000000000018e6e> <1362379353667> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'soa_server1' has triggered at Mar 4, 2013 9:42:33 AM AST. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = Mar 4, 2013 9:42:33 AM AST SERVER = soa_server1 MESSAGE = [ServletContext@2063961084[app:ConductInspections module:ConductInspections.war path:/workflow/ConductInspections spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@461540c5[
POST /workflow/ConductInspections/notification/secure?bpmWorklistContext=%3B%3BGKX%2B61AxigI0UYXdsRHyr09KMN%2BsG%2BYttpyIOOkr%2BIoYDudg7FSa25wMK0NYyCLmou5ptBAzdFjUHBHsPZkB0gpzXHzE5F%2Fabwj7jj72lTY%3D&bpmWorklistTaskFormFwdUrl=%2Ffaces%2Fadf.task-flow%3Ftz%3DAsia%252FRiyadh%26df%3Dmedium%26dt%3Dboth%26tf%3Dshort%26lg%3Den%26cy%3DUS%26bpmWorklistTaskId%3D72d60354-cb92-407c-8e8e-5ea4dbc14ebb%26bpmWorklistTaskVersion%3D1%26bpmWorklistContext%3D0575fa9d-25cf-408e-98da-8671dd5f5857%253B%253BzoAe2Jnbf2CnGbrUn8RGQsUA9bo5ouv%252FI0cQbEQ3PX80o4EpRP3HS7r1PLIDz%252FURFYg5Bc9cLk6d6xE6e71E22IuirGFJcstHHurrf24O7PK8Dilf8cuZwyhuNouljYuSZFrbydpzi9uwlxSFeFqFfmxnFdC7SLrhmCAVANCQL8IWikPJVcN6pGSsnImOz1%252B72PjSRH8KnUsQ6sYbkl3wb47WOMb7u2KudFsYjId4Rg4Qp43jDTsa3LRL08Y2LqX%26bpmClientType%3DnotificationClient%26org.apache.myfaces.trinidad.agent.email%3Dtrue%26_id%3DApproveInspectionReport_TaskFlow%26_document%3DWEB-INF%252FApproveInspectionReport_TaskFlow.xml HTTP/1.1
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows NT 5.0) Oracle HTTPClient Version 10h
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context: 1.0000Joo8Zr4Dg^15zvS4yW1HBT^E001Y_e;kfvE
Content-type: application/octet-stream
Content-Length: 0
]] Root cause of ServletException.
java.security.AccessControlException: access denied (oracle.security.jps.JpsPermission IdentityAssertion)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
 at java.security.AccessController.checkPermission(AccessController.java:546)
 at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:378)
 at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:438)
 at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:460)
 at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.checkPermission(AbstractSubjectSecurity.java:113)
 at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.getActionExecutor(AbstractSubjectSecurity.java:76)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter$1.run(WorkflowFilter.java:231)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.invokeFilterChainSecurely(WorkflowFilter.java:228)
 at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:156)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:527)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
 at oracle.bpel.services.workflow.client.worklist.servlet.SecureNotificationServlet.securelyForwardToUrl(SecureNotificationServlet.java:100)
 at oracle.bpel.services.workflow.client.worklist.servlet.SecureNotificationServlet.service(SecureNotificationServlet.java:83)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '32' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = RB1-SOA-01 TXID = CONTEXTID = 932e7620e6d94c34:-21663e16:13d1b17f9fa:-8000-0000000000018e6d TIMESTAMP = 1362379353651
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
>
please advise.
Mohammed. Abdul Muqeet

IdentityAssertion WLS8

Similar Messages

Maybe you are looking for