Messaging Bridge Migration to other Managed Server

          Hi
          I had encountered a difficulty when I deployed the Messaging Bridge using the
          Migratable Target. The Messaging Bridge stop function with no exception. I had
          double check that in my Managed Server (serverA) I had set the Migratable Target
          ServerA (Migratable) preferable to serverA itself. However if I deployed the
          Messaging Bridge to serverA directly it works perfectly. Can anyone share some
          ideas that I can setup the Bridge in order I can failover the Bridge from one
          Managed Server to another Managed Server manually without restart any Managed
          Servers?
          Thanks
          Stephen

hi,
this is file from - .../new-admin-server/config-store/server-farm.xml
in the .../old-admin-server/config-store/server-farm.xml it was not glass it was "rama1" of course.
i've edit this manually
i can deploy, stop-start instance from new-admin-server
<?xml version="1.0" encoding="UTF-8"?>

<server-farm>
<admin-server>glass</admin-server>
<node>
<host>glass</host>
<port>8989</port>
<description>This is the Administration Server node</description>
</node>
<node>
<host>kuku</host>
<port>8989</port>
</node>
</server-farm>

Similar Messages

JMS Server is not Migrating to other Managed Server using Databse Leasing

Hi,
WLS 10.3 on Linux Itanium.
I Tried JMS Server migration but its not working.
Below is the Configuration Details :-
1. Cluster with three managed servers( MS1,MS2,MS3 )
2.JMS Server is targeted on MS1(migratable)
3.created Persistant store as JDBC store for JMS Server and targeted it to MS1(migratable)
4.Environment -> Cluster->Migration Tab
-Migration Basis :- Database
-DataSource For Automatic Migration -> DS1
     -Auto Migration Table Name:(ACTIVE)
5.Created a table ACTIVE as per schema given in WL_HOME/server/db/dbname/leasing.ddl (I am using Oracle database at backend and Database is running and accessible)
6.Created Jms module (say module1)
-target module1 to Cluster.
7.Create Subdeployment(say "sub1") and target to JmsServer
8.Create Queue.and select subdeployment as "sub1" which was created above.
9.I am using default JMSXAconnectionfactory
10.Environment -> Migratable Targets->Select MS1(Migratable)->Migration tab
-Service Migration Policy->Auto Migration Exactly Once Service
               -Constrained Cadidate Servers :-
               Selected all the servers in that cluster
but when I check the Current Server for JMS Server (It should be MS1) which is not displayed. The field in the table is blank.
(Environment->Messaging->JMS Server->here i checked the Current Server for JMS Server )
with the above setting I did it successfully on windows platform. I am able to see Current Server as MS1.and when I shutdown MS1 it changes to either MS2 or MS3
but when I am doing it on Winodows I am explicitly creating connection factory and targeting it to cluster.but on linux platform I am not creating any connection factory(default JMS XA Connection Factory is used)
I have tried a lot to find why its not working but didnt get any idea why so happened?
Required your help
Thanks in Advance ........

I managed to start my managedserver.The issue was with startmanagedserver command.I modified it to my need.

Migration to other Administration server

hi,
how to migrate to other Administration server ?
i've tried just copy configs, but internal db integrity failed
i see null hosts, configs and etc
I can't put SJWS7 into production because can't implement disaster recovery...
come on.
Mihails

hi,
this is file from - .../new-admin-server/config-store/server-farm.xml
in the .../old-admin-server/config-store/server-farm.xml it was not glass it was "rama1" of course.
i've edit this manually
i can deploy, stop-start instance from new-admin-server
<?xml version="1.0" encoding="UTF-8"?>

<server-farm>
<admin-server>glass</admin-server>
<node>
<host>glass</host>
<port>8989</port>
<description>This is the Administration Server node</description>
</node>
<node>
<host>kuku</host>
<port>8989</port>
</node>
</server-farm>

Error occured in Message Bridging in Weblogic to MQ Server

Hi,
I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
<Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
--Please give me the suggestion to fix this.
Thanks in Advance,
Sureshkannan Nagarajan

Hello Priya
If u r loading thru flat file
1. Check the correct path in infopackage
2. Check if it is opened,if it is then close it and run package again
If loading thru R/3
1. Check DS is not opened in change mode
2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
3. Are you running init..then make sure no document is posted in R/3 side...
Thanks
Tripple k

Error message seen when starting a managed server (dsp_config.ear)

Hi ,
I am having issues when i start the managed server under the admin server.
Seems like when i undeploy dsp_config.ear the managed server seems to start without any issues.
But since the dsp_config.ear is removed the dspconsole is messed up.
The admin server runs fine without any issues with or without dsp_config.ear deployment.
The error trace
####<Jul 27, 2009 9:36:01 AM EDT> <Warning> <DeploymentService> <wdcsn383a> <cashflow1MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (
self-tuning)'> <<WLS Kernel>> <> <> <1248701761543> <BEA-290064> <Deployment service servlet encountered an Exception while handling the deployment service m
essage for request id "-1" from server "BEAAdminServer". Exception is: "java.lang.ClassNotFoundException: com.bea.wli.config.deployment.server.ServerVersion:
This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed o
n a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at java.util.HashMap.readObject(HashMap.java:1030)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
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.deploy.service.internal.DomainVersion.readExternal(DomainVersion.java:180)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readMessage(DeploymentServiceMessage.java:325)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readExternal(DeploymentServiceMessage.java:301)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDeploymentServiceMessage(DeploymentServiceServlet.java:618)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.internalDoPost(DeploymentServiceServlet.java:235)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.access$000(DeploymentServiceServlet.java:77)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet$1.run(DeploymentServiceServlet.java:210)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:207)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
Can anybody help me on this one?
it seems more of ODSI issue than weblogic server issue.

it sounds like you are deploying dsp_config.ear to a domain/server that is not ODSI-enabled.
com.bea.wli.config.deployment.server.ServerVersion is in <modules>/com.bea.common.configfwk.wlinterop_10.3.0.0.jar which is referenced by <modules>/features/odsi.server.modules_10.3.0.0.xml and used by com.bea.dsp.management.impl.DomainServiceImpl

Migrating from other Application Server - security questions

Hello guys,
I am newbie with BEA Weblogic, migrating from JBoss/Tomcat.
I am interested in security techniques used in Weblogic.
For example, how can I configure web auth./protected area with authorisation from SQL (MySQL in my case) database? In JBoss/Tomcat I've used to configure JDBC security realm for Tomcat, but in Weblogic 8.1 I can hardly find such ability to configure such realm. I need to say that I see only one default realm.
I am using Weblogic Server 8.1.
Looking forward any your help, thanks!
If you can share some usefull links/articles - this would be great!
P.S. This just the first question. I have many of them dealing with EJB security... :-)

You can write your own "providers"
There are samples available with instructions at
http://dev2dev.bea.com/codelibrary/code/security_prov81.jsp

JMS Messaging Bridge Problems with WLS 8.1 sp2

 Thank you in advance for your help.
 I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
 Q. I have this working wonderfully in an environment without clustering but once
 I try to deploy to a cluster, I am having two major problems.
 1) When the managed servers are restarted, the messaging bridges immediately complain
 about not being able to find the resource adaptor. After I manually un-target
 the messaging bridge from the cluster and re-target them, they find the resource
 adaptor but cannot connect to the source... which leads to my next problem.
 2) The messaging bridges cannot connect to the source destination whether it is
 an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
 see relative:
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
 Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
 Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
 Bridge.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
 is deployed as a migratable.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
 Bridge as a migratable.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
 source configurations are:
 AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
 Classpath=null
 ConnectionURL = file:/e:/private/JNDI/eBusDev02
 DestinationType = Queue
 DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
 InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
 ConnectionFactoryJNDIName = jms.oes.MQ-QCF
 .>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
 target configurations are:
 AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
 Classpath=null
 ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
 DestinationType = Queue
 DestinationJNDIName = jms/oes/ADV-REPLYQ
 InitialContextFactory = weblogic.jndi.WLInitialContextFactory
 ConnectionFactoryJNDIName = jms/oes/QCF
 .>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
 is successfully initialized.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
 has been successfully initialized as a migratable.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
 Bridge.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
 has been successfully activated..>
 ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
 <Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
 two adapters.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
 <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
 Getting source connection.>
 ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
 <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
 <Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
 and will try again in 15 seconds. (java.lang.NullPointerException)>
 I know the queues are up and I am pretty sure my MQ client configuration is correct.
 Is there anyway to get more information about the NullPointerException or the
 error being encountered?


Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
 If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
 Tom

Message Bridge problems

Hi Tom,
          Message Bridge is configured to transfer messages from AQ to DQ.
          When the Message Bridge is deployed on Admin Server & Cluster, it works successfully. But, a closer look reveals that it’s the instance deployed on the Admin Server (and not the ones on the cluster) which is doing the job of looking up AQ & DQ and transferring messages from AQ to DQ. Monitoring Message Bridge instances on the cluster shows "WARN: failed to look up the source adapter." The corrective action for this is "Check if the adapter is deployed or the JNDI name in the source JMSBridgeDestination instance is correct.". But the adapter is correctly deployed and the JNDI name of the AQ is correctly bound, else the Message Bridge wouldn't have shown "Forwarding messages." for Admin Server's Message Bridge instances. The same set of configuration (MB destinations and MB) is shared by the Message Bridge instances on Admin Server & Cluster. So, the question of incorrect configuration of the JMS destinations i.e. AQ & DQ doesn't arise.
          Can you point out where the problem could be ? ?:|
          Cheers
          Dips

Patch for this problem should be added to the front of your WLS instance's CLASSPATH prior to any weblogic classes. This issue is resolved in WLS 8.1 SP3 and this is the recommended path to resolution, the patch should be used only if one can't upgrade to SP3.
          CR126671
          Setup a cluster configuration on 8.1SP1 with at least on managed server in the cluster. Deploy the bridge adapter jms-xa-adp.rar to the cluster. Configure a bridge and target it to the cluster.Bridge never receives Add
          Notification for the adapter. However, if you retarget the adapter to the individual servers in the cluster it works fine.
          Dips

Managed server independence mode startup : VERY slow (2h~)

Hello there,
I'm posting this thread to ask for some help.
In my production environnement, where I am running a cluster of several ALSB nodes, a problem showed up when a network card was unplugged on our admin server hardware.
You have to know that for some reason, we are not using a node manager for our admin operations on the managed servers, but rather scripts that are scheduled by a tool we use for several other things (backup,etc..). This tool runs WLST scripts to do some basic stuff on our servers.
So, during the shutdown/startup process, when we tried to bring back all the managed servers up, we faced this problem : When the managed servers were not able to contact the admin server, the startup process takes approx 2 hours, but only 10min when admin server is up and running. This is a real problem in our high availibility environnement, if we have to face this "no admin server" situation again.
My environnement is :
Weblogic 10.0
Solaris 10.6.0
Java HotSpot(TM) Server VM Version 1.5.0_16-b02
<Jul 22, 2010 10:07:03 AM MEST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/xx/JMSReportingProviderStartupClass.jar:/xx/SID_AMM_ALSB_SECURITY.jar:/xx/content_system.jar:/xx/p13n-schemas.jar:/xx/p13n_common.jar:/xx/p13n_system.jar:/xx/wlp_services.jar:/xx/analytics_sys.jar:/xx/commerce_system.jar:/xx/groupspace_system.jar:/xx/netuix_common.jar:/xx/netuix_schemas.jar:/xx/netuix_system-full.jar:/xx/netuix_system.jar:/xx/nf-jspcmods.jar:/xx/nf-system.jar:/xx/wlp-schemas.jar:/xx/wlp_content_system.jar:/xx/wps_system.jar:/xx/wsrp-client.jar:/xx/wsrp-common.jar>
WebLogic Server Temporary Patch for CR382552 Fri Dec 12 13:12:27 IST 2008
WebLogic Server Temporary Patch for 9112835 Thu Nov 12 10:53:52 EST 2009
WebLogic Server Temporary Patch for CR368155 Mon Jul 07 15:51:15 PDT 2008
WebLogic Server Temporary Patch for CR370311 Tue Jun 03 14:40:28 IST 2008
WebLogic Server Temporary Patch for CR360676 Fri Apr 18 19:41:49 IST 2008
WebLogic Server Temporary Patch for CR360117 Wed Mar 12 14:47:42 PDT 2008
WebLogic Server Temporary Patch for CR354395 Mon Dec 10 08:10:43 PST 2007
WebLogic Server Temporary Patch for CR345092 Wed Oct 24 11:10:56 IST 2007
WebLogic Server Temporary Patch for CR338239 Fri Jan 11 17:14:11 EST 2008
WebLogic Server Temporary Patch for CR328282 Thu Nov 08 13:44:54 EST 2007
WebLogic Server Temporary Patch for CR315317 Mon Feb 25 09:45:40 PST 2008
WebLogic Server Temporary Patch for CR315317 Mon Feb 25 09:45:40 PST 2008
WebLogic Server Temporary Patch for CR344429 Mon Nov 26 16:11:55 EST 2007
WebLogic Server Temporary Patch for CR351304 Thu Feb 21 10:23:22 EST 2008
WebLogic Server Temporary Patch for CR350614 Sun Nov 11 18:02:20 PST 2007
WebLogic Server Temporary Patch for CR344375 Fri Oct 19 11:08:33 PDT 2007
WebLogic Server Temporary Patch for CR353586 Mon Feb 25 18:59:49 EST 2008
WebLogic Server Temporary Patch for CR353586 Mon Feb 25 18:59:49 EST 2008
WebLogic Server Temporary Patch for CR339736, CR346639 Mon Nov 26 18:13:36 PST 2007
WebLogic Server Temporary Patch for CR343580 Mon Oct 29 17:41:35 EDT 2007
WebLogic Server Temporary Patch for CR315317 Fri Feb 15 11:13:21 PST 2008
WebLogic Server Temporary Patch for CR351685, CR320630 Thu Dec 06 14:04:31 CST 2007
WebLogic Server Temporary Patch for CR345472 Thu Jan 17 16:13:48 EST 2008
WebLogic Server Temporary Patch for CR355338 Mon Jan 21 13:08:48 EST 2008
WebLogic Server Temporary Patch for CR356295 Wed Dec 19 15:37:45 EST 2007
WebLogic Server Temporary Patch for CR348244 Fri Oct 19 11:57:37 PDT 2007
WebLogic Server Temporary Patch for CR346064 Fri Oct 19 13:27:18 PDT 2007
WebLogic Server Temporary Patch for CR346063 Fri Oct 05 14:48:13 PDT 2007
WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
WebLogic Server Temporary Patch for CR346060 Thu Oct 18 15:28:01 PDT 2007
WebLogic Server Temporary Patch for CR350528 Fri Nov 02 16:19:36 PDT 2007
WebLogic Server Temporary Patch for CR354048 Thu Dec 06 13:52:09 IST 2007
WebLogic Server Temporary Patch for CR348229 Wed Oct 24 13:49:07 PDT 2007
WebLogic Server Temporary Patch for CR362972, CR357095 Fri Mar 07 15:38:53 IST 2008
WebLogic Server Temporary Patch for CR358677 Wed Jan 23 16:28:40 PST 2008
WebLogic Server Temporary Patch for CR354390 Wed Feb 27 09:57:23 PST 2008
WebLogic Server Temporary Patch for CR357287 Thu Jan 31 14:51:56 PST 2008
WebLogic Server Temporary Patch for CR359323 Fri Mar 07 02:24:20 EST 2008
WebLogic Server Temporary Patch for CR322355 Tue Oct 23 10:53:45 PDT 2007
WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >
<Jul 22, 2010 10:10:36 AM MEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://xx.xx.xx.xx:xx.>
<Jul 22, 2010 10:10:36 AM MEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Jul 22, 2010 10:10:36 AM MEST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : xxxxxx>
<Jul 22, 2010 10:10:36 AM MEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 22, 2010 10:10:36 AM MEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<22/07/2010#10:10:36.794#+0200> <Notice> <Log Management> <BEA-170019> <The server log file xxxxxxx.log is opened. All server side log events will be written to this file.>
<22/07/2010#10:10:41.578#+0200> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<22/07/2010#10:10:42.75#+0200> <Alert> <Security> <BEA-090167> <Cannot retrieve identity certificate and private key on server xxmanaged1xx, because the keystore entry alias is not specified.>
<22/07/2010#10:10:42.77#+0200> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /xxxkeystore.>
<22/07/2010#10:16:02.665#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<22/07/2010#10:16:02.666#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<22/07/2010#10:45:48.374#+0200> <Alert> <ALSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. AquaLogic Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need ALSB service account support.>
<22/07/2010#10:45:48.564#+0200> <Error> <ClusterTimer> <BEA-000000> <Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0
java.rmi.UnknownHostException: Could not discover URL for server 'xxadminxx'
 at weblogic.protocol.URLManager.findURL(URLManager.java:143)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getInitialContext(RemoteClusterTimerAuthority.java:72)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getTimerAuthority(RemoteClusterTimerAuthority.java:84)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getClusterTimerAuthorityCurrentTime(RemoteClusterTimerAuthority.java:44)
 at com.bea.wli.timer.ClusterTimerService.clusterTimeAuthorityCurrentTimeMillis(ClusterTimerService.java:173)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#10:45:48.567#+0200> <Error> <ClusterTimer> <BEA-000000> <Cannot contact the admin server. Therefore constructing the Cluster Authority Urzeit from the persisted value
java.rmi.UnknownHostException: Could not discover URL for server 'xxadminxx'
 at weblogic.protocol.URLManager.findURL(URLManager.java:143)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getInitialContext(RemoteClusterTimerAuthority.java:72)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getTimerAuthority(RemoteClusterTimerAuthority.java:84)
 at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getUrzeit(RemoteClusterTimerAuthority.java:57)
 at com.bea.wli.timer.ClusterTimerService.initialize(ClusterTimerService.java:87)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#10:45:52.154#+0200> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
<22/07/2010#11:54:55.765#+0200> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'ALSB Framework Starter Application'.
RegistrationException : java.rmi.RemoteException: [Deployer:149147]Could not reach the admin server via any of its URLS: 'http://xx.xx.xx.xx:xx'.
 at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.registerHandler(TargetDeploymentService.java:166)
 at weblogic.deploy.service.internal.DeploymentService.registerHandler(DeploymentService.java:177)
 at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.register(ServerDeploymentReceiver.java:82)
 at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.<init>(ServerDeploymentReceiver.java:75)
 at com.bea.wli.config.weblogic.WebLogicConfigService$DeploymentReceiverLauncher.endOfStart(WebLogicConfigService.java:190)
 Truncated. see log file for complete stacktrace
RegistrationException : java.rmi.RemoteException: [Deployer:149147]Could not reach the admin server via any of its URLS: 'http://xx.xx.xx.xx:xx'.
 at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.registerHandler(TargetDeploymentService.java:166)
 at weblogic.deploy.service.internal.DeploymentService.registerHandler(DeploymentService.java:177)
 at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.register(ServerDeploymentReceiver.java:82)
 at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.<init>(ServerDeploymentReceiver.java:75)
 at com.bea.wli.config.weblogic.WebLogicConfigService$DeploymentReceiverLauncher.endOfStart(WebLogicConfigService.java:190)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#11:54:56.271#+0200> <Error> <ConfigFwk> <BEA-000000> <Failed in endLoadNotification. Ignoring.
java.lang.NullPointerException
 at com.bea.wli.sb.resources.globaloperations.GlobalOperationsResourceLifecycleListener.endLoadNotification(GlobalOperationsResourceLifecycleListener.java:112)
 at com.bea.wli.config.impl.ResourceListenerNotifier.sendLoadNotificationsInContext(ResourceListenerNotifier.java:236)
 at com.bea.wli.config.impl.ResourceListenerNotifier.access$400(ResourceListenerNotifier.java:41)
 at com.bea.wli.config.impl.ResourceListenerNotifier$1.execute(ResourceListenerNotifier.java:151)
 at com.bea.wli.config.transaction.TransactionalTask._doExecute(TransactionalTask.java:217)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#11:54:57.153#+0200> <Error> <ConfigFwk> <BEA-000000> <Failed in endLoadNotification. Ignoring.
java.lang.NullPointerException
 at com.bea.wli.sb.service.ServiceChangeListener.updateAlerts(ServiceChangeListener.java:243)
 at com.bea.wli.sb.service.ServiceChangeListener.endLoadNotification(ServiceChangeListener.java:175)
 at com.bea.wli.config.impl.ResourceListenerNotifier.sendLoadNotificationsInContext(ResourceListenerNotifier.java:236)
 at com.bea.wli.config.impl.ResourceListenerNotifier.access$400(ResourceListenerNotifier.java:41)
 at com.bea.wli.config.impl.ResourceListenerNotifier$1.execute(ResourceListenerNotifier.java:151)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#11:54:59.828#+0200> <Error> <ALSB Statistics Manager> <BEA-473004> <Cannot recover from persistent Store : java.lang.NullPointerException
java.lang.NullPointerException
 at com.bea.wli.monitoring.statistics.collection.Collector.readPersistedRawSnapshot(Collector.java:357)
 at com.bea.wli.monitoring.statistics.StatisticsManager.onStatConfigLoad(StatisticsManager.java:347)
 at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.onStatConfigLoad(ALSBStatisticsManager.java:379)
 at com.bea.wli.sb.service.ServiceStatisticsListener.updateRuntime(ServiceStatisticsListener.java:200)
 at com.bea.wli.sb.service.ServiceStatisticsListener.endLoadNotification(ServiceStatisticsListener.java:168)
 Truncated. see log file for complete stacktrace
>
<22/07/2010#11:55:02.434#+0200> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<22/07/2010#11:55:02.557#+0200> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<22/07/2010#11:55:02.557#+0200> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of xxCLUSTERxx.>
<22/07/2010#11:55:32.595#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<22/07/2010#11:55:32.595#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<22/07/2010#11:57:17.835#+0200> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xx.xx.xx.xx:14101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<22/07/2010#11:57:17.835#+0200> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "xxmanaged1xx" for domain "xxDOMAINxx" running in Production Mode>
<22/07/2010#11:57:17.840#+0200> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server xxadminxx at <JMXServiceURL:null>.>
<22/07/2010#11:57:20.13#+0200> <Notice> <Cluster> <BEA-000102> <Joining cluster xxCLUSTERxx on xx.xx.xx.xx:7001>
<22/07/2010#11:57:20.28#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
I have a hard time trying to see what's happening here.
If you have any input for me to use, I would be very thankful.
And by the way, please excuse me for my poor english (french here ^^)
Best regards,
Serge

As a test, I shutdown my admin server and then killed the managed server from the command line so that node manager would start it ( and not be able to find the admin server ).
I'm using WL 10.3.3 ( 11g + OSB + SOA ) on oracle linux (64bit) and the managed server started in 3 minutes.
So I tried the same in my 10g environment WL 10.3 running OSB 10g ( oracle linux 32-bit ) and the server started in 2 minutes.
I see a couple of times when your trace shows a pause:
1. when loading certificates22/07/2010#10:10:42.75#+0200> <Alert> <Security> <BEA-090167> <Cannot retrieve identity certificate and private key on server xxmanaged1xx, because the keystore entry alias is not specified.>
<22/07/2010#10:10:42.77#+0200> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /xxxkeystore.>
<22/07/2010#10:16:02.665#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
For this server, is the keystore alias entered in the server's SSL tab?
2. Just after entering STARTING<22/07/2010#10:16:02.666#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<22/07/2010#10:45:48.374#+0200> <Alert> <ALSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. AquaLogic Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need ALSB service account support.>
In my test, the "user password credential" message was preceded by messages about the Singleton Marker applications. Are the singleton apps deployed to this server, or to some other managed server? If they are deployed to some other managed server, are they deployed to a managed server on the same host as the (unreachable) admin server?
<Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Cluster Singleton Marker Application">
<Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Domain Singleton Marker Application">
<Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Framework Starter Application">
<Jul 19, 2010 11:11:56 AM EDT> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
3. activating ALSB Framework 22/07/2010#10:45:52.154#+0200> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
<22/07/2010#11:54:55.765#+0200> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'ALSB Framework Starter Application'.
In my test, this was logged immediately after the "user password credential mapper" message, with the following between:
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl.getInstance>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl.initialize>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <initializing WssHandlerImpl>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssHandlerImpl constructor>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssAuditor initilizing>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <auditingEnbled set to false>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <auditingEnbled set to false>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssAuditor successfully started>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl was successfully initialized>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityModule> <BEA-000000> <jndiLookup: [jndi-name: com.bea.alsb.internal.clusterTimerAuthority]>
<Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityModule> <BEA-000000> <jndiLookup: [jndi-name: com.bea.alsb.internal.clusterTimerAuthority]>
<Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
<Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
<Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
<Jul 19, 2010 11:11:56 AM EDT> <Info> <Deployer> <BEA-149059> <Module Dummy of application ALSB Framework Starter Application is transitioning from STATE_NEW to STATE_PREPARED on server
The clusterTimerAuthority involves contacting the admin server in 11g, but not quite sure about 10g. ( I have a separate bug in 11g when the ClusterTime can't be reached if the admin server is using 2way SSL )
I can't run the same test in my multi-node environments, but is it possible for you to change the targets of the 2 Singleton applications to a managed server which runs on some machine other than the Admin server's machine? Then try starting that managed server while the Admin server is down, and also try restarting another managed server ( which is not on the admin server's host and is not targetted by the Singleton applications. )
I suspect the managed server with the singleton apps will start more quickly than the one without.

JMS topic-cache topic is not getting broadcasting in other managed servers

Hi All,
Please give me some idea in fixing the issue that im facing.
I have created the JMS topic in my weblogic console server which has 2 managed servers.
I have a feature in my application which is kept in a cache that will be used by my JMS topic. If my request hits managed 1 server im able to see the newly created feature.
But the same feature is not working when i make the request hit managed 2 server.
It means the JMS topic is not getting broadcasted properly in other managed server. I dont want to go for a server recycle which will resolve the issue.
Please let me know if im not clear enough.
Below is the description provided by my partner on the same issue in his words..
"The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.
The same problem is observed in Production as well. Let us know if there is anything wrong in the way the JMS Topic is created or any other configuration is missing, that is not allowing the proper functioning of the Topic."
fyi...i have all my firewall enabled between the managed servers.And multicast property is also declared correctly only.

Please let me know if im not clear enough.No. Please explain again.
The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.Is it a distributed topic? Or does it mean a topic message doesnt get delivered to all subscribers?
ram.

NodeManager or managed server cant find admin server

<15-05-2003 11:31:58 PDT> <Info> <[email protected]:5555> <Starting Server
Admin server on Machine A.
Managed server on machine B.
using the demo ssl configuration.
When I try to start my managed sever from the admin console I get the following
error :
nesDomain::ophelia ...>
<15-05-2003 11:31:59 PDT> <Info> <[email protected]:5555> <Server nesDomain::ophelia
started, process id = 264>
Starting WebLogic Server...
<15-05-2003 11:32:05 PDT> <Error> <Management> <141079> <Error encountered attempting
to contact AdminServer at http://localhost:7001/wl_management_internal2/Bootstrap
to obtain configuration information. Will attempt to to start an independent
ManagedServer. No server log avaliable, Exception was: java.net.ConnectException:
Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost',
port: '7001'>
<15-05-2003 11:32:09 PDT> <Notice> <Management> <140005> <Loading configuration
C:\ophelia\user_domains\nesDomain\config.xml>
I looks like the managed server tries to find the admin server on localhost, but
I cant find where to change this ...

I'm getting the same problem as posted by Sumitkhapli when I try to start a managed server either through the Admin Console or through the command line. Any ideas?
Output and Exception Message trying to start the managed server:
C:\WebLogicSPK3\weblogic81\common\bin>startManagedWebLogic MyServer1 http://SBREWSTER1:7777
C:\WebLogicSPK3\weblogic81\common\bin>echo off
CLASSPATH=C:\WEBLOG~1\JROCKI~1\lib\tools.jar;C:\WEBLOG~1\WEBLOG~1\server\lib\weblogic_sp.jar;C:\WEBLOG~1\WEBLOG~1\server\lib\weblogic.jar;C:\WEBLOG~1\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\WEBLOG~1\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\WEBLOG~1\JROCKI~1\jre\lib\rt.jar;C:\WEBLOG~1\WEBLOG~1\server\lib\webservices.jar;C:\WEBLOG~1\JROCKI~1\lib\tools.jar;C:\WEBLOG~1\WEBLOG~1\server\lib\weblogic_sp.jar;C:\WEBLOG~1\WEBLOG~1\server\lib\weblogic.jar;
PATH=C:\WEBLOG~1\WEBLOG~1\server\bin;C:\WEBLOG~1\JROCKI~1\jre\bin;C:\WEBLOG~1\JROCKI~1\bin;C:\WEBLOG~1\WEBLOG~1\server\bin;C:\WEBLOG~1\JROCKI~1\jre\bin;C:\WEBLOG~1\JROCKI~1\bin;C:\WEBLOG~1\WEBLOG~1\server\bin;C:\WEBLOG~1\JROCKI~1\jre\bin;C:\WEBLOG~1\JROCKI~1\bin;.;C:\Java\j2re1.4.2_04\bin;C:\Java\jakarta-tomcat-3.2.4;C:\OrbixE2A\etc\bin;C:\OrbixE2A\asp\6.0\bin;C:\OrbixE2A\bin;C:\JBuilder7\jdk1.3.1\jre\bin\hotspot;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\PROGRA~1\MKSTOO~1\bin;C:\PROGRA~1\MKSTOO~1\bin\x11;C:\PROGRA~1\MKSTOO~1\mksnt;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\MSSQL7\BINN;C:\Program Files\Hummingbird\Connectivity\9.00\Accessories\;Y:\bin;I:\Tools\Stingray\ObjectiveStudio\Lib;C:\bin;C:\WEBLOG~1\WEBLOG~1\server\bin\oci920_8;C:\WEBLOG~1\WEBLOG~1\server\bin\oci920_8;C:\WEBLOG~1\WEBLOG~1\server\bin\oci920_8
* 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 *
<Jan 20, 2005 11:39:04 AM EST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Jan 20, 2005 11:39:09 AM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_04 JVM Version ari-31788-20040616-1132-win-ia32 from BEA Systems, Inc.>
<Jan 20, 2005 11:39:09 AM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://SBREWSTER1:7777 to check if there exists a running admin server at this URL.>
<Jan 20, 2005 11:39:09 AM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 20, 2005 11:39:09 AM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Jan 20, 2005 11:39:09 AM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://SBREWSTER1:7777 to retrieve the initial configuration.>
<Jan 20, 2005 11:39:11 AM EST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through URL: http://SBREWSTER1:7777/wl_management_internal2/Bootstrap, user: weblogic
java.lang.ClassNotFoundException: weblogic.management.mbeans.custom.ApplicationConfiguration
at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at java.util.ArrayList.readObject(Ljava.io.ObjectInputStream;)V(ArrayList.java:547)
at java.lang.LangAccessImpl.readObject(Ljava.lang.Class;Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(Ljava.lang.String;)Ljava.util.List;(ManagedServerAdmin.java:543)
at weblogic.management.ManagedServerAdmin.initialize()V(ManagedServerAdmin.java:150)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:771)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://SBREWSTER1:7777/wl_management_internal2/Bo
otstrap, user: weblogic
java.lang.ClassNotFoundException: weblogic.management.mbeans.custom.ApplicationConfiguration
at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at java.util.ArrayList.readObject(Ljava.io.ObjectInputStream;)V(ArrayList.java:547)
at java.lang.LangAccessImpl.readObject(Ljava.lang.Class;Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(Ljava.lang.String;)Ljava.util.List;(ManagedServerAdmin.java:543)
at weblogic.management.ManagedServerAdmin.initialize()V(ManagedServerAdmin.java:150)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:771)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://SBREWSTER1:7777/wl_management_internal2/Bootstrap, us
er: weblogic
java.lang.ClassNotFoundException: weblogic.management.mbeans.custom.ApplicationConfiguration
at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at java.util.ArrayList.readObject(Ljava.io.ObjectInputStream;)V(ArrayList.java:547)
at java.lang.LangAccessImpl.readObject(Ljava.lang.Class;Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava.lang.Object;Ljava.io.ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(Ljava.lang.String;)Ljava.util.List;(ManagedServerAdmin.java:543)
at weblogic.management.ManagedServerAdmin.initialize()V(ManagedServerAdmin.java:150)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:771)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
C:\WebLogicSPK3\weblogic81\common\bin>

IndexOutOfBonds on managed server

Hi all I got adobe livecycle server with formserver and when i used my interface i got the following message all the time! Can somebody help me, please! <ExecuteThread: '34' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was: javax.ejb.EJBException: EJB Exception: : java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:507) at java.util.ArrayList.get(ArrayList.java:324) at com.adobe.fm.workflow.notification.WorkflowNotificationSessionBean.onTaskCreated(Workflow NotificationSessionBean.java:433) at com.adobe.fm.workflow.notification.WorkflowNotificationSessionBean.onMessageImpl(Workflow NotificationSessionBean.java:185) at com.adobe.fm.workflow.notification.WorkflowNotificationSessionBean_lwa0gg_ELOImpl.onMessa geImpl(WorkflowNotificationSessionBean_lwa0gg_ELOImpl.java:103) at com.adobe.fm.workflow.notification.WorkflowNotificationBean.onMessage(WorkflowNotificatio nBean.java:100) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) ; nested exception is: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0.

After some messages i got this error :
Managed Server MANAGEDServer is disconnected from the admin server. This may be either due
to a managed server getting temporarily partitioned or the managed server process exiting.

Foreign JMS Servers vs. Messaging Bridge

 Can anyone tell me what is the difference between setting up an MQ JMS provider
 as a "Foreign JMS Server" or through the "Messaging Bridge"? I currently have
 it setup as a Foreign JMS Server since that was relatively easy, but I can't get
 MQ to participate in a XA transaction. Am I required to set it up through the
 "Messaging Bridge" to obtain this functionality?
 Thank you in advance for your help.


The two things are very different. All a "ForeignJMSServer" does is allow
 you to link JMS objects from some other JNDI provider (like the one that MQ
 uses) into the WLS JNDI tree. Once you've done that, you can use the JNDI
 names you created using the "ForeignJMSServer" feature inside an MDB, an
 EJB, a servlet, a messaging bridge, or wherever you want, without having to
 copy the MQ-specific configuration information to every one of those places.
 The messaging bridge, on the other hand, gives you a sort of "store and
 forward" feature, in that it copies messages from one JMS queue or topic to
 another. The two features can be used together, but they dont' have to be.
 What are you trying to do, anyway? What is it inside WLS that you're trying
 to make work with an XA transaction?
 greg
 "Jason Peck" <[email protected]> wrote in message
 news:40630089$[email protected]..
 >
 > Can anyone tell me what is the difference between setting up an MQ JMS
 provider
 > as a "Foreign JMS Server" or through the "Messaging Bridge"? I currently
 have
 > it setup as a Foreign JMS Server since that was relatively easy, but I
 can't get
 > MQ to participate in a XA transaction. Am I required to set it up through
 the
 > "Messaging Bridge" to obtain this functionality?
 >
 > Thank you in advance for your help.

Programming Managed Server to Server Communication

Hi
We have a start up class that sets system properties used by our EJB's. We would like to be able to call a class that reloads these properties at any time without having to restart the server.
We tried using JMX, but we had problems with the MBean calling down to classes in our EAR. Since they were loaded by different classloaders. We also would try like to keep the system classpath clean as possible.
Currently we have a solution using a Stateless Session Bean, but this will only set the properties on the Manager Server that it is running on. So I was wondering if it is possible to communicate from one Managed Server to another as I would like to be able to call the same Bean on any other Managed Server that is running.
Declan O'Reilly
PS: If there is a better way to solve to problem in general, I would be delighted to hear.

hi,
One solution here could be to deploy the modifying component ( see below for details ) on the admin server. Set the properties that should be configurable in the JNDI tree, ensure that these properties are set in a replicated context. The settings will then be replicated in the cluster to all the managed servers participating in the cluster.
As for the modifying component, you could go for MBeans, JSPs or web-services. For this kind of configuration I would choose between mbeans or JSPs depending on the type of usage this modifying component will have.
For details on JMX see
http://e-docs.bea.com/wls/docs81/jmx/
For details on JNDI and replication see
http://e-docs.bea.com/wls/docs81/jndi/index.html
- Anders M.

Managed Server stuck in starting

Hi every, thank you for reading.
We have a Oracle SOA domain running on WLS 10.3.6. The OS is windows server 2003.
Adminserver and soa_server1 are on vmmachine1.
proxy server and soa_server2 are on vmmachine2.
soa_server1 and soa_server2 are in a cluster.
This domain has been working normally for serveral months. Managed server is controlled by nodemanager.
Yesterday, we increased the memory of vmmachine1 and vmmachine2 from 8g to 16g.
After that, soa_server2 cannot be started while other managed server of the domain starts normally.
I looked into the soa_server2.log and found that the log stucks at "<Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\ctst_soa_domain\servers\soa_server2\logs\soa_server2.log is opened. All server side log events will be written to this file.> " forever.
The task manager shows that the memory of java.exe process of the stucked managed server is about 350m and at an increase rate of about 4k.
The cpu consumption of the process is 0 percent.
Below is part of JRockit Mission Control fly record event of the stucked JVM:
1,359,447,962,480,625,883 4,453,053,500 weblogic.timers.TimerThread Java Wait
1,359,447,962,480,688,068 4,453,037,334 [ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' Java Wait
1,359,447,962,558,579,199 109,474,384 VDE Transaction Processor Thread Java Wait
1,359,447,962,564,083,662 869,606,634 RMI TCP Connection(26)-192.9.200.148 Socket Read
1,359,447,962,668,068,530 109,075,316 VDE Transaction Processor Thread Java Wait
1,359,447,962,777,159,184 109,367,902 VDE Transaction Processor Thread Java Wait
1,359,447,962,886,542,218 109,638,015 VDE Transaction Processor Thread Java Wait
1,359,447,962,996,257,842 109,285,831 VDE Transaction Processor Thread Java Wait
1,359,447,963,105,558,278 109,143,508 VDE Transaction Processor Thread Java Wait
1,359,447,963,214,709,536 109,312,043 VDE Transaction Processor Thread Java Wait
1,359,447,963,324,052,457 109,455,297 VDE Transaction Processor Thread Java Wait
1,359,447,963,433,516,028 109,259,502 VDE Transaction Processor Thread Java Wait
1,359,447,963,433,924,695 93,414,304 RMI TCP Connection(26)-192.9.200.148 Socket Read
1,359,447,963,527,635,047 2,515,422,874 RMI TCP Connection(26)-192.9.200.148 Socket Read
1,359,447,963,542,789,729 152,068,282 VDE Transaction Processor Thread Java Wait
1,359,447,963,694,879,147 113,581,233 VDE Transaction Processor Thread Java Wait
1,359,447,963,697,060,581 1,002,528,122 RMI TCP Connection(idle) Socket Read
1,359,447,963,808,488,263 109,555,192 VDE Transaction Processor Thread Java Wait
1,359,447,963,918,076,105 109,076,613 VDE Transaction Processor Thread Java Wait
1,359,447,964,027,167,650 109,358,282 VDE Transaction Processor Thread Java Wait
1,359,447,964,136,541,541 109,442,748 VDE Transaction Processor Thread Java Wait
1,359,447,964,245,999,192 109,830,184 VDE Transaction Processor Thread Java Wait
1,359,447,964,324,342,462 2,015,390,696 Timer-1 Java Wait
1,359,447,964,355,844,714 108,827,865 VDE Transaction Processor Thread Java Wait
1,359,447,964,464,687,365 109,297,368 VDE Transaction Processor Thread Java Wait
1,359,447,964,574,003,355 109,396,656 VDE Transaction Processor Thread Java Wait
1,359,447,964,683,418,068 109,366,571 VDE Transaction Processor Thread Java Wait
1,359,447,964,705,600,116 743,862,091 RMI TCP Connection(idle) Socket Read
1,359,447,964,792,799,741 109,347,456 VDE Transaction Processor Thread Java Wait
1,359,447,964,902,156,236 109,395,625 VDE Transaction Processor Thread Java Wait
1,359,447,965,011,567,244 109,331,778 VDE Transaction Processor Thread Java Wait
1,359,447,965,120,914,342 109,367,906 VDE Transaction Processor Thread Java Wait
1,359,447,965,230,297,996 109,602,297 VDE Transaction Processor Thread Java Wait
1,359,447,965,339,915,098 109,369,203 VDE Transaction Processor Thread Java Wait
1,359,447,965,449,297,323 109,126,121 VDE Transaction Processor Thread Java Wait
1,359,447,965,449,946,395 265,099,402 RMI TCP Connection(idle) Socket Read
1,359,447,965,558,468,725 109,441,305 VDE Transaction Processor Thread Java Wait
1,359,447,965,667,925,444 109,229,624 VDE Transaction Processor Thread Java Wait
1,359,447,965,720,533,365 322,363,229 RMI TCP Connection(idle) Socket Read
1,359,447,965,777,169,428 109,580,914 VDE Transaction Processor Thread Java Wait
1,359,447,965,886,766,019 109,140,868 VDE Transaction Processor Thread Java Wait
Any help is welcome.

Thread Dump:
"Main Thread" id=1 idx=0x4 tid=1728 prio=5 alive, waiting, native_blocked
-- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x00000001
82879510[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x0000000
182879510[fat lock]
at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager
.java:459)
at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServices
Manager.java:166)
^-- Holding lock: java/lang/Class@0x0000000182852658[biased lock]
at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:568)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:469)
at weblogic/Server.main(Server.java:71)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x8 tid=4040 prio=5 alive, daemon
"(OC Main Thread)" id=3 idx=0xc tid=2300 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 1)" id=? idx=0x10 tid=220 prio=5 alive, daemon
"(GC Worker Thread 2)" id=? idx=0x14 tid=2056 prio=5 alive, daemon
"(GC Worker Thread 3)" id=? idx=0x18 tid=1096 prio=5 alive, daemon
"(GC Worker Thread 4)" id=? idx=0x1c tid=2580 prio=5 alive, daemon
"(Code Generation Thread 1)" id=4 idx=0x20 tid=3404 prio=5 alive, native_waiting
, daemon
"(Code Optimization Thread 1)" id=5 idx=0x24 tid=3228 prio=5 alive, native_waiti
ng, daemon
"(VM Periodic Task)" id=6 idx=0x28 tid=1564 prio=10 alive, native_blocked, daemo
n
"(Attach Listener)" id=7 idx=0x2c tid=640 prio=5 alive, native_blocked, daemon
"Finalizer" id=8 idx=0x30 tid=248 prio=8 alive, native_waiting, daemon
at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native
Method)
at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
at jrockit/memory/Finalizer$4.run(Finalizer.java:183)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"Reference Handler" id=9 idx=0x34 tid=2092 prio=10 alive, native_waiting, daemon
at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;
(Native Method)
at java/lang/ref/Reference.access$100(Reference.java:11)
at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"(Sensor Event Thread)" id=10 idx=0x38 tid=3548 prio=5 alive, native_blocked, da
emon
"VM JFR Buffer Thread" id=11 idx=0x3c tid=3768 prio=5 alive, in native, daemon
"Timer-0" id=14 idx=0x40 tid=3800 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0x000000018238DF88[fat l
ock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x000000018238DF88[fat
lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"Timer-1" id=15 idx=0x44 tid=1572 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0x0000000185AC9490[fat l
ock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0x0000000185AC9490[fat
lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'"
id=16 idx=0x48 tid=3360 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: com/octetstring/vde/backend/standard/Transac
tionProcessor@0x000000018A83F800[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at com/octetstring/vde/backend/standard/TransactionProcessor.waitTransaction
sCompleted(TransactionProcessor.java:353)
^-- Lock released while waiting: com/octetstring/vde/backend/standard/Transa
ctionProcessor@0x000000018A83F800[fat lock]
at com/octetstring/vde/backend/standard/BackendStandard.<init>(BackendStanda
rd.java:275)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljav
a/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeConstructorAccessorImpl.newInstance0(Ljava/lang/reflect
/Constructor;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
 at sun/reflect/NativeConstructorAccessorImpl.newInstance(NativeConstructorAc
cessorImpl.java:39)
 at sun/reflect/DelegatingConstructorAccessorImpl.newInstance(DelegatingConst
ructorAccessorImpl.java:27)
 at java/lang/reflect/Constructor.newInstance(Constructor.java:513)
 at com/octetstring/vde/backend/BackendHandler.<init>(BackendHandler.java:248
 at com/octetstring/vde/backend/BackendHandler.getInstance(BackendHandler.jav
a:344)
 at weblogic/ldap/EmbeddedLDAP.start(EmbeddedLDAP.java:299)
 at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic/work/ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic/work/ExecuteThread.run(ExecuteThread.java:221)
 at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
 -- end of trace
"JFR request timer" id=17 idx=0x4c tid=2260 prio=5 alive, waiting, native_blocke
d, daemon
 -- Waiting for notification on: java/util/TaskQueue@0x0000000185B49530[fat l
ock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x0000000185B49530[fat
lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"weblogic.time.TimeEventGenerator" id=19 idx=0x50 tid=600 prio=9 alive, waiting,
native_blocked, daemon
-- Waiting for notification on: weblogic/time/common/internal/TimeTable@0x00
0000018C653048[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0x0
00000018C653048[fat lock]
at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.j
ava:117)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"JMAPI event thread" id=20 idx=0x54 tid=2916 prio=5 alive, in native, daemon
"weblogic.timers.TimerThread" id=21 idx=0x58 tid=3288 prio=9 alive, waiting, nat
ive_blocked, daemon
-- Waiting for notification on: weblogic/timers/internal/TimerThread@0x00000
0018C6ABCA0[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:262)
^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0x0000
00018C6ABCA0[fat lock]
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'
" id=22 idx=0x5c tid=1368 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: weblogic/work/ExecuteThread@0x000000018C2A1C
00[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:205)
^-- Lock released while waiting: weblogic/work/ExecuteThread@0x000000018C2A1
C00[fat lock]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:226)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=25 idx=0x60 tid=1484
prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSo
cketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=26 idx=0x64 tid=2540
prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSo
cketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=27 idx=0x68 tid=3640
prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSo
cketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'" id=28 idx=0x6c tid=1904
prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSo
cketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
"VDE Transaction Processor Thread" id=31 idx=0x70 tid=1520 prio=2 alive, waiting
, native_blocked, daemon
-- Waiting for notification on: com/octetstring/vde/backend/standard/Transac
tionProcessor@0x000000018A83F800[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
d)
at java/lang/Object.wait(J)V(Native Method)
at com/octetstring/vde/backend/standard/TransactionProcessor.waitwrite(Trans
actionProcessor.java:378)
^-- Lock released while waiting: com/octetstring/vde/backend/standard/Transa
ctionProcessor@0x000000018A83F800[fat lock]
at com/octetstring/vde/backend/standard/TransactionProcessor.run(Transaction
Processor.java:228)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
===== END OF THREAD DUMP ===============

Messaging Bridge Migration to other Managed Server

Similar Messages

Maybe you are looking for