BEA-090513

I do see this asked in quite a few topics but I still have questions:
          BEA WLS 8.1.4
          App (MDB's) on Domain A is trying to connect to Domain B' JMS (subscribe to Topics on Domain B).
          The domain B's log is full of messages like this though the MDB's on Domain A's App do get the messages published to the Topics.
          ####<May 17, 2007 1:12:12 PM GMT> <Error> <Security> <server1.corp.com> <App1> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
          From what I have read, looks like we need to establish Domain Trust between the 2.
          My questions:
          1. Is this just a nuisance of a message which can be suppressed somehow ?
          2. What are the other ramifications of this (enabling Domain Trust) ? I don't want to open up some kind of security hole etc.
          3. An other way (apart from establishing Domain Trust) this can be fixed.
          Thanx,

And also the admin shows Health status of others OK very slowly it may take more than 30mins for all servers(13) to show the Heath state as OK untill then it shows Not reachable..

Similar Messages

BEA-090513 "ServerIdentity failed validation" on single domain single server

Hi!
I'm getting loads of
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading
to anonymous.>
errors though I'm running a single server in a single domain - so the information
in
http://e-docs.bea.com/wls/docs81/messages/Security.html
isn't very helpful. What can I do to remove this problem?
Thanks so much,
Hans-Peter Stoerr

Hi I get the similar error
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
<Sep 12, 2007 4:04:51 PM CDT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security>sb1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defau
lt (self-tuning)'> <<WLS Kernel>> <> <> <1189626452736> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security> > <sb1> <ExecuteThread: '8' for queue: 'weblogic.socket.Muxer'> <<WLS
Kernel>> <> <> <1189626452759> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security> < <sb1> <ExecuteThread: '8' for queue: 'weblogic.socket.Muxer'> <<WLS
Kernel>> <> <> <1189626452760> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
I tried the bea method to change the credentials that the domain is interacting with (trust certificate) but no help.The errors keep coming still.
iN order to rule out some possiblity i shutdown the other domain completley and i could still see same errors in my managed server logs.i would really appreciate anyones tips to fix this issue.

BEA-090513 -- ServerIdentity failed validation, downgrading to anonymous

I'm getting this error when starting up my instance. I only have one domain, so the information in the error message list about enabling trust between domains should not apply here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

I think, if you only have a single domain, the only thing that could be causing this is a misconfiguration. Can you recreate the domain? Can you confirm that the config.xml files on all servers are identical?

Server Crash : ServerIdentity failed validation, downgrading to anonymous

All,
Setup is as follows:
Domain has got an admin server and 2 managed servers.
Managed Server 1 on Machine 1
Managed Server 2 on Machine 2
Following error is continuously thrown in the logs :
<22-Jul-2010 09:54:45 o'clock> <Error> <Security> <managed1> <ExecuteThread: '2' for queue: 'weblogic.
socket.Muxer'> <<WLS Kernel>> <> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
Can this 090513 error on JMS queue lead to a server crash ?
I also get the below error
<ExecuteThread: '2' for queue: 'weblogic.adm
in.RMI' : Executing(weblogic.management.internal.MBeanHomeImpl)> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by r
mi server: weblogic.management.internal.MBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:109)
Regards,
Rashi

Does this domain have rmi communication with another weblogic domain? If so this error would normally occur if you have not enabled domain trust between the domains. You can enable domain trust by following the steps in the below link :
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/domain.html#wp1176064
Not sure is this alone will crash a server. Is there any other errors in the logs ?

Managed Servers are fluctuating .

Hi,
Installed WebLogic Server 10.3.5.
Having AdminServer + 8 Managed Servers.
AdminServer + ManagedServers-1/2/3/4 on machine X
ManagedServers-5/6/7/8 on machine Y
All 8 servers are in cluster.
Domain Name : mattermanagement
Issue :
ManagedServer-7 and ManagedServer-8 alone go down, and upon refresh in the console, servers show in Running mode. They're fluctuating.
Not sure whether they're really going down, and coming up.
From logs , i can see only 2 types of error messages like :
<03-Mar-2015 13:15:34 o'clock GMT> <Error> <JMX> <BEA-149500> <An exception occurred while registering the MBean null.
java.lang.IllegalArgumentException: Registered more than one instance with the same objectName :
mattermanagement:ServerRuntime=managed7_mattermanagement,MessageDrivenEJBRuntime=ReportingMDB_wli.reporting.jmsprovider.queue,Name=ReportingMDB_wli.reporting.jmsprovider.queue,ApplicationRuntime=JMS Reporting Provider,Location=managed7_mattermanagement,Type=EJBPoolRuntime,EJBComponentRuntime=jmsreportprovider.jar new:[email protected]e existing [email protected]5
        at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)
        at weblogic.management.mbeanservers.compatibility.internal.CompatibilityObjectNameManager.lookupObjectName(CompatibilityObjectNameManager.java:65)
        at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87)
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
Any idea why managedServers-7/8 alone having issue ? What casing this ?
Anything i need to check/verify ?
Thanks

Hi,
Can you check if there is a conflict or you have used the same name for two resources in Weblogic.
Because if the resources have the same name it causes a conflict.
Have a look at the below thread which have the same issue reported
https://community.oracle.com/thread/2290229
Mbean Null /// PermGen // Manifest.mf --- Many many errors.
weblogic error while starting the application
And for the below error message you can follow the recommendation in the below link and check
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
ServerIdentity failed validation, downgrading to anonymous. error (BEA/Weblogic forum at JavaRanch)
Hope it helps

What do these errors mean ? Web Logic

I am attempting to start Web Logic Server, and Web Logic Server for my application installed on my machine. I get the following errors, completely new to web Logic so I don't know what they mean. But it seems to be a privelege issue related to the admin account. Please note that I have in no way changed any settings to my admin account recently, nor my password or anything. Everything was working fine for a week until yesterday, and I can't think of anything I have changed. Any input is appreciated. Highlighted the main errors in bold.
When starting Web Logic Server for my application:
<Nov 21, 2010 3:49:48 PM CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSe
cure[1]" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, htt
ps.>
<Nov 21, 2010 3:49:48 PM CST> <Notice> <Server> <BEA-002613> <Channel "DefaultSe
cure" is now listening on 10.0.2.15:7002 for protocols iiops, t3s, ldaps, https.
>
<Nov 21, 2010 3:49:48 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default[1
]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<Nov 21, 2010 3:49:48 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default"
is now listening on 10.0.2.15:7001 for protocols iiop, t3, ldap, snmp, http.>
<Nov 21, 2010 3:49:48 PM CST> <Notice> <WebLogicServer> <BEA-000331> <Started We
bLogic Admin Server "examplesServer" for domain "wl_server" running in Developme
nt Mode>
<Nov 21, 2010 3:49:50 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to RUNNING>
<Nov 21, 2010 3:49:50 PM CST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
rted in RUNNING mode>
<Nov 21, 2010 3:50:00 PM CST> <Error> <Security> <BEA-090513> <ServerIdentity fa
iled validation, downgrading to anonymous.>
<Nov 21, 2010 3:50:01 PM CST> <Error> <Security> <BEA-090513> <ServerIdentity fa
iled validation, downgrading to anonymous.>
<Nov 21, 2010 3:50:01 PM CST> <Error> <Security> <BEA-090513> <*ServerIdentity fa*
iled validation, downgrading to anonymous.>
<Nov 21, 2010 3:50:01 PM CST> <Warning> <RMI> <BEA-080003> <RuntimeException thr
own by rmi server: weblogic.rmi.internal.AdminAccessOnlyServerRef@1f, implementa
tion: 'weblogic.server.channels.RemoteChannelServiceImpl@2332930', oid: '31', im
plementationClassName: 'weblogic.server.channels.RemoteChannelServiceImpl'
java.lang.SecurityException: Method 'getAdministrationURL' cannot be invoked wi
thout administrator access.
java.lang.SecurityException: Method 'getAdministrationURL' cannot be invoked wit
hout administrator access
at weblogic.rmi.internal.AdminAccessOnlyServerRef.getWorkManager(AdminAc
cessOnlyServerRef.java:29)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:316
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:944
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1138)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1020)
Truncated. see log file for complete stacktrace
when starting Web Logic Server for my application:
<Nov 21, 2010 4:15:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Nov 21, 2010 4:17:42 PM CST> <Error> <org.apache.beehive.netui.pageflow.interna
l.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized
correctly.>
<Nov 21, 2010 4:17:46 PM CST> <Notice> <Log Management> <BEA-170027> <The Server
has established connection with the Domain level Diagnostic Service successfull
y.>
<Nov 21, 2010 4:17:48 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to ADMIN>
<Nov 21, 2010 4:17:48 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to RESUMING>
<Nov 21, 2010 4:17:49 PM CST> <Emergency> <Security> <BEA-090087> <Server failed
to bind to the configured Admin port. The port may already be used by another p
rocess.>
<Nov 21, 2010 4:17:49 PM CST> <Error> <Server> <BEA-002606> <Unable to create a
server socket for listening on channel "Default[1]". The address 127.0.0.1 might
be incorrect or another process is using port 7001: java.net.BindException: Add
ress already in use: JVM_Bind.>
<Nov 21, 2010 4:17:49 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server f
ailed. Reason: Server failed to bind to any usable port. See preceeding log mess
age for details.>
<Nov 21, 2010 4:17:49 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Nov 21, 2010 4:17:49 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical
service failed. The server will shut itself down>
<Nov 21, 2010 4:17:49 PM CST> <Error> <Server> <BEA-002606> <Unable to create a
server socket for listening on channel "Default". The address 10.0.2.15 might be
incorrect or another process is using port 7001: java.net.BindException: Addres
s already in use: JVM_Bind.>
<Nov 21, 2010 4:17:49 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>

The message weblogic.server.channels.RemoteChannelServiceImpl@2332930', oid: seems like there is some trouble
with your OID.
Another message in your loggng:
Unable to create a server socket for listening on channel "Default". The address 10.0.2.15 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use: JVM_Bind.
Tells you there is already a process running on port 7001 (you can use the netstat -a command to check if the port 7001 is taken).

ServerIdentity failed validation

I am porting over some code from WebLogic 6.1 to 8.1 and getting the following
errors. Any clue as to what these might be? Thanks.
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading
to anonymous.>
<Error> <JTA> <BEA-110200> <User [<anonymous>] is not authorized to invoke startCommit
on a transaction branch.>

The problem went away after I established trust between the two domains. Thanks
so much for your help.
Naresh
"Peter" <PeterB> wrote:
>
"Naresh Bhatia" <[email protected]> wrote in message
news:[email protected]..
I am porting over some code from WebLogic 6.1 to 8.1 and getting thefollowing
errors. Any clue as to what these might be? Thanks.
<Error> <Security> <BEA-090513> <ServerIdentity failed validation,downgrading
to anonymous.><messagedetail>
The ServerIdentity failed validation. Within this domain, the server
identity is downgraded to Anonymous.
</messagedetail>
<cause>
Trust has not been properly established between two domains.
</cause>
<action>
See the documentation on Enabling Trust Between WebLogic Domains at
http://e-docs.bea.com.
</action>

ServerIdentity failed validation, downgrading to anonymous

I'm getting this error when trying to run one of the application
deployed in my domain. I only have one domain, so the information in the
error message list about enabling trust between domains should not apply
here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

Here's a more complete stack trace from the server log:
####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Warning> <RMI> <ORLEX1090> <demoServer> <ExecuteThread:
'0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException
thrown by rmi server: weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:557)
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:453)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:347)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:764)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Steven Ostrowski <[email protected]> wrote:
I'm getting this error when trying to run one of the application
deployed in my domain. I only have one domain, so the information in
the
error message list about enabling trust between domains should not apply
here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

Error while creating a new Domain in BEA Weblogic

I am getting the below mentioned error while creating a new Domain in BEA Weblogic
Preparing...
Extracting Domain Contents...
Creating Domain Security Information...
Saving the Domain Information...
Storing Domain Information...
String Substituting Domain Files...
Performing OS Specific Tasks...
Performing Post Domain Creation Tasks...
Domain Creation Failed!
Domain Location: C:\bea\user_projects\domains\base_domain_1
Reason: Got error in writing the node manager C:\bea\wlserver_10.0\common\nodemanager\nodemanager.domains property file!
Exception:
java.lang.Exception: Got error in writing the node manager C:\bea\wlserver_10.0\common\nodemanager\nodemanager.domains property file!
     at com.bea.plateng.domain.DomainNodeManagerHelper.registerDomainToNodeManager(DomainNodeManagerHelper.java:138)
     at com.bea.plateng.domain.DomainNodeManagerHelper.registerDomainToNodeManager(DomainNodeManagerHelper.java:170)
     at com.bea.plateng.domain.DomainGenerator.generate(DomainGenerator.java:435)
     at com.bea.plateng.wizard.domain.gui.tasks.DomainCreationGUITask$1.run(DomainCreationGUITask.java:232)

Hi,
It look two ways either you dont have permission to write any new thing to that domain.properties file or might file is got corrupted.
Please check for the permission to that file.
Regards,
Kal.

Error when starting weblogic 10.0: BEA-149508

When starting our weblogic 10.0 server, we get a <BEA-149508> error, indicating JMX cannot talk to the admin server. This is unusual, because immediately before we get this error, we log:
<BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://(our IP address) /jndi/weblogic.management.mbeanservers.domainruntime.>
Our investigation is getting nowhere, and we'd appreciate any help you can offer. Thanks.
-Matt Kaiser
full error message:
<BEA-149508> <Unable to establish JMX Connectivity with the Adminstration Server.
StackTrace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
     java.io.StreamCorruptedException: invalid type code: AC
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:217)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
     at javax.management.remote.rmi.RMIConnectionImpl_1000_WLStub.invoke(Unknown Source)
     at weblogic.management.remote.common.RMIConnectionWrapper$15.run(ClientProviderBase.java:639)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.security.Security.runAs(Security.java:61)
     at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:637)
     at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:978)
     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:134)
     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:82)
     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.io.StreamCorruptedException: invalid type code: AC
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1356)
     at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1642)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
     at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
     at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
     at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
     at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

What's your jvm version ?
You must use 1.5 jvm.
Example: If you use jvm 1.6, the managed servers starts but error <BEA-149508> and you cannot admin you instance.
With an official 1.5, no probs
Fax

Deploy sip servlet to Occas5.0(weblogic) occurs exception: com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException

hi,
I install Occas on OS win7 64bit, jdk 1.6.0.45.
I got the following error message while I start Occas server:
because error occurs when parsing sip related annotations of "testservicecomplexobject-application"
WLST-WLS-1396579151484: com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException
at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init><SipAnnotationData.java:155>
Also, when I deploy a sip servlet package(sar) to the Occas server, after deploy finish, at the deployment manager page,
health term is none.
and also I found many error info in AdminServer/logs/domain.log as below blue font:
####<Apr 4, 2014 11:09:21 AM CST> <Error> <WLSS.Setup> <E76C3BE51B4188> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1396580961513> <BEA-331210> <Skip SIP related logic, because error occurs when parsing sip related annotations of "b2bua-sip-servlet-1.0.0-SNAPSHOT"
com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException:
    at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init>(SipAnnotationData.java:155)
    at com.bea.wcp.sip.util.DeploymentUtil.getOrCreateAnnotationData(DeploymentUtil.java:74)
    at com.bea.wcp.sip.util.DeploymentUtil.getAnnotationData(DeploymentUtil.java:89)
    at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:129)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.LinkageError: loader constraint violation: when resolving overridden method "antlr.debug.LLkDebuggingParser.removeMessageListener(Lantlr/debug/MessageListener;)V" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, antlr/debug/LLkDebuggingParser, and its superclass loader (instance of sun/misc/Launcher$AppClassLoader), have different Class objects for the type antlr/debug/MessageListener used in the signature
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
    at java.lang.Class.privateGetPublicMethods(Class.java:2556)
    at java.lang.Class.getMethods(Class.java:1412)
    at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.classAnnotationParsing(SipAnnotationData.java:344)
    at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.jarAnnotationParsing(SipAnnotationData.java:288)
    at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.annotationParsing(SipAnnotationData.java:223)
    at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init>(SipAnnotationData.java:144)
    at com.bea.wcp.sip.util.DeploymentUtil.getOrCreateAnnotationData(DeploymentUtil.java:74)
    at com.bea.wcp.sip.util.DeploymentUtil.getAnnotationData(DeploymentUtil.java:89)
    at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:129)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Apr 4, 2014 11:09:21 AM CST> <Error> <WLSS.Engine> <E76C3BE51B4188> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1396580961523> <BEA-330004> <Failed to deploy SIP application "b2bua-sip-servlet-1.0.0-SNAPSHOT"
java.lang.NullPointerException
    at com.bea.wcp.sip.engine.server.setup.SipDeploymentDescriptor.<init>(SipDeploymentDescriptor.java:285)
    at com.bea.wcp.sip.engine.server.setup.SipDeploymentDescriptor.parse(SipDeploymentDescriptor.java:148)
    at com.bea.wcp.sip.engine.server.CanaryContext.initContext(CanaryContext.java:396)
    at com.bea.wcp.sip.engine.server.CanaryContext.<init>(CanaryContext.java:334)
    at com.bea.wcp.sip.engine.server.CanaryServer.installContext(CanaryServer.java:1001)
    at com.bea.wcp.sip.engine.server.SipService.setupSipServletContext(SipService.java:126)
    at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:130)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
    at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone give some suggession?
Thanks in advance!
BR//Margin

Hi,
I changed my jvm from sun jdk to latest jrockit and the issue was solved :)

Oracle ifs and BEA weblogic

Oracle ifs and BEA weblogic
We have one application server with weblogic and and ifs 1.0.9 , and one db server with Oracle 8.1.7.
with the following configuration:
Web server
appl server with weblogic 6.0 and ifs 1.1.9
Oracle 8i Enterprise with interMedia text
We need to use the iFS API call for our application.
As I know, weblogic 6.0 support JDK1.3 but ifs 1.1.9 supports up to JDK1.2.
Is this configuration possible?
Any conflict if two version JDK co-exist inside same machine?
Any suggestion?
If I separate the appl. server into two machines, that is,
one server installed with weblogic, the other one installed with ifs.
How could I make use the ifs API call from appl. server?
Is there any configuration guides for this setting?
Thanks a lot.
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Luis:
The iFS API is 100% pure Java. You can use it from any other Java application, be it JSP, EJB, or a standalone application.
So it really comes down to the CLASSPATH. The iFS API is split among a set of .jar files, and some of the configuration information is stored in .properties files that are outside of these .jar files. All of this stuff needs to be in the CLASSPATH of whatever JVM is calling the iFS API.
The iFS API uses the Oracle JDBC driver to communicate with the Oracle database. This is another requirement. You can't use another JDBC driver; you have to use ours.
So again, it's all about configuration.<HR></BLOCKQUOTE>
Would you mind to share more detail on configurating weblogic to integrate the iFS API?
null

BEA query is taking long time to run

Hi All,
I am using BEA Weblogic 10.2. I am performing seraching in the repository.
The query string is:
cm_lifeCycleStatus==4&&SERVICE == 'RBT' &&COPYRIGHTTO >= toDate('yyyy-MM-dd', '2010-07-01')&&COPYRIGHTFROM <= toDate('yyyy-MM-dd', '2010-07-01')
Here SERVICE,COPYRIGHTTO,COPYRIGHTFROM are the property.
If i am using cm_midifiedDate instead of COPYRIGHTTO,COPYRIGHTFROM , it giving result very fast.
But the the need is to use COPYRIGHTTO,COPYRIGHTFROM .
Please suggest me how can i optimize this query.
The code to fecth is:
ctx = new ContentContext(this.getRequest());
IVersionManager ivm = ContentManagerFactory.getVersionManager();
Expression exp = ExpressionHelper.parse(query);
Search search = new Search();
search.setExpression(exp);
search.setFullTextSearch(false);
nodeList = ivm.search(ctx, search);
Thnaks
Arvind

I'm not completely sure that the Version tables have indices that are optimized for query performance. Based on your original post, I'm assuming that you are eventually getting the correct results back but it just takes too long? You might want to do some database diagnostics to see how the query is being executed and if any index is being consulted. I would assume not and that is where your performance issue might be coming from. The published content tables (such as CM_NODE) are optimized for query response.
Explicit properties only apply to the Published CM_NODE table. To do this, you'd add a column to the CM_NODE database table, ensure that the datatype on the column matches your desired Property data type. Then, in your Content Type definition, in the Portal Admin, you'd mark the "Is Explicit" attribute on the Property and enter the name of the database column which you created to store the values. Of course, in the database, you'd probably want to create an index on this new column to make it faster for searching.
Brad

Will BEA release an IDE with WebLogic Server 10 in march?

Hi
Thank you for reading my post.
Can some one tell me whether bea release an IDE with its new version of Weblogic server 10 in March?
Thanks

Have you seen the Web Services tutorial:
http://e-docs.bea.com/workshop/docs92/ws_platform/introduction/conWorkshopTutorials.html
What specific features would you like to see, relative to EE5. We're
working on support for EE5 annotations, but what are you most interested?
br
legolas wood wrote:
can you please give me some links to workshop feature matrix ?
specially i am looking at what does it provide to ease web service development based on jee 5 standards and what does it provide in term of soa development.
thanks

SSL and BEA-090482 (BAD Certificate)

Hi All,
I am trying to get self-signed certificates to work with the keytool and I have followed just about every instruction to get everything to work. But no matter what I try I keep getting the BAD CERTIFICATE error. My Setup is the following:
- I have Oracle Enterprise Linux (5.8) installed
- I have Weblogic 10.3.4.0 installed
- I start nodemanger through wlst
- I have 1 weblogic installation with 3 domains and each domain has it's own IP address (virtual IP adresses).
For 1 SOA Server (soa_server1) I want to enable SSL so here's wat I did:
1. I use the keytool to create identity.jks (keytool -genkey -alias mycert -keyalg RSA -keypass weblogic1 -keystore identity.jks -storepass weblogic1 -validity 365)
2. I export the certificate (keytool -export -alias mycert -file root.cer -keystore identity.jks -storepass weblogic1)
3. I import the certificate into trust.jks (keytool -import -alias mycert -trustcacerts -file root.cer -keystore trust.jks -storepass weblogic1)
4. I setup Weblogic (tab keystores) with the appropriate setting (identity.jks and trust.jks)
5. I setup Weblogic (tab SSL) with a private key alias and it's password
6. I enable SSL in Weblogic
Our servername = MYSRV005 and our domain name = yyy.lan
When going to the AdminServer each domain can be reached by it's own name (for example test.yyy.lan etc.)
I have configured our listen-address for our soa_server1 for test.yyy.lan
I have set our certificate common name to test.yyy.lan
My nodemanager runs on localhost (I can start any server from our AdminServer console)
We disabled hostname verification in startWeblogic.sh, startNodeManager.sh and in the soa_server1 console
I even added CertGenCa.der into our trust.jks (keytool -import -alias mycert-trustcacerts -file “<location of CertGenCA.der>” -keystore trust.jks)
No matter what I try, I keep getting BEA-090482 (BAD Certificate .....).
I hope someone can help me out on this issue. I've been at it for 2 days now and still can't solve the problem. Are there any other things I have to be thinking of?
Thanks for any help. :)

Well,
Once again I solved my problem. Am not sure what I did, but it seems that switching to the java utils.CertGen utility did the trick. That way certificates will get signed with the CertGenCA.der certificate. However I am not entirely sure this was our problem since I have changed so many settings in the last couple of days. Noticed that the keytool doesn't change the issuer and the issuer will be the same as what you fill out. Wonder why everyt tut on the net used the keytool while that wasn't working for us. :( Guess I have to dive into that. :)

BEA-090513

Similar Messages

Maybe you are looking for