Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.lang.SecurityException: Invalid Subject

13 views
Skip to first unread message

Liugang

unread,
Apr 16, 2003, 12:13:56 AM4/16/03
to
I create two domain(bridgedomain, targetdomain) with different
server(myserver, targetserver), and create and bridge that transfer message
for bridgedomain to targetdomain,and I confing the security relationship as
documention saying:
If you want two 7.0 domains to interoperate, perform the following procedure
in both domains.

To establish a trust relationship between WebLogic Server domains:


1.. Expand the Domains node.

2.. Select the Security-->Advanced tab.

3.. Click the Change... link in the Credential attribute.

4.. Enter a password for the domain. Choose the password carefully. BEA
Systems recommends using a combination of upper and lower case letters and
numbers.

5.. Confirm the password.

6.. Click Apply.

7.. Reboot WebLogic Server.

It can transfer message well,but only throws following exception:


<2003-4-16 下午12时04分20秒> <Notice> <WebLogicServer> <000360> <Server
started
in RUNNING mode>
java.lang.SecurityException: Invalid Subject: principals=[system,
Administrators
]
at
weblogic.security.service.SecurityServiceManager.seal(SecurityService
Manager.java:943)
at
weblogic.security.service.RoleManager.getRoles(RoleManager.java:271)
at
weblogic.security.service.AuthorizationManager.isAccessAllowed(Author
izationManager.java:609)
at weblogic.jms.JMSService.checkPermission(JMSService.java:1064)
at weblogic.jms.JMSService.checkRecvPermission(JMSService.java:1076)
at
weblogic.jms.frontend.FESession.consumerCreate(FESession.java:944)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2247)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.jav
a:552)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.ja
va:275)
at
weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1585)
at
weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1447)
at
weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1297)
at
weblogic.jms.adapter.JMSBaseConnection.setMessageListenerInternal(JMS
BaseConnection.java:931)
at
weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConn
ection.java:885)
at
weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnec
tionHandle.java:121)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.connector.common.internal.ConnectionWrapper.invoke(Connectio
nWrapper.java:98)
at $Proxy101.setMessageListener(Unknown Source)
at
weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(Messagin
gBridge.java:862)
at
weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
java:942)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

have any suggestion? thank you.

Dongbo Xiao

unread,
Apr 16, 2003, 1:00:11 PM4/16/03
to
Here is what in the current doc.
"Configure the WebLogic Server 7.0 security interoperability as follows:

Expand the Domains node (for example, Examples).

Select the Security � Advanced tab.

Clear the Enable Generated Credential check box, if necessary.

Click the Credential: Change attribute to open the Change Credential window.

In the New Credential field, specify a password for the domain. This password
must match the password used for the domain that you are interoperating with.

Confirm the password by re-entering it in the Retype to confirm field.

Click Apply. "

Look like you missed the step "Clear the Enable Generated Credential check box,
if necessary."

Hope this helps.
Dongbo

0 new messages