JMS Client Eeconnect After JMS Server Restart

Hi,
How can I force the JMS clients to reconnect again, when JMS Server restarts.
thx in advance for any help!

Pass an ExceptionListener into the Connection and when onException is called, start a reconnect cycle (wait x seconds and try to reconnect x times).

Similar Messages

How JMS client operate on JMS server side objects?

For example, JMS client got an instance of ConnecitonFactory by JNDI call from a remote side JMS server. Thereafter, the client uses this object to set upconnections. My question is that what kind of remote tech this is? Is it RMI or CORBA or something?

I suspect it boils down to who your JMS Provider is.

WebLogic JMS client frozen during JMS connection stopping (race condition)

Hello,
Our application is using the WebLogic 10.3.1 JMS client generated with wlfullclient5.jar.
We have sometimes a race condition when the WebLogic server is stopped.
In about 10% of the cases where the server is stopped, the client application is frozen in the "stop" call (see stack trace #1 below).
Our understanding is that each JMS API call by the application is translated by a request-response message on the TCP connection to the JMS server. The JMS library sends the request and then wait for the response. From our observations, it looks like there is no local timeout in the JMS library. This means that if the WebLogic server is being stopped just after receiving the "stop" request, it will never send the "stop" response, which means that the application will be stuck forever.
The same problem also occurs when using JMS bridges between 2 JMS servers (see stack trace #2 below).
How can we activate a local timeout for all JNDI/JMS calls ?
Regards,
metatech
"AppThread" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
- locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
- locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
at AppSession.closeJMSSession(ConnectorSession.java:499)
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.jms.client.JMSXASession@1d363e4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.jms.client.JMSSession.waitForState(JMSSession.java:4778)
weblogic.jms.client.JMSSession.stop(JMSSession.java:1310)
weblogic.jms.client.JMSConnection.stop(JMSConnection.java:773)
weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
weblogic.jms.adapter.JMSBaseConnection.closeInternal(JMSBaseConnection.java:570)
weblogic.jms.adapter.JMSBaseConnection.access$000(JMSBaseConnection.java:85)
weblogic.jms.adapter.JMSBaseConnection$2.run(JMSBaseConnection.java:552)

Hi Tom,
Thanks for looking at the issue.
I tried to post the full thread dump as an attachment, but it is not allowed by the forum, so you find it hereunder.
Regards,
metatech
=================
2010-05-28 12:33:19
Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode):
"Attach Listener" daemon prio=3 tid=0x0000000100c5b800 nid=0x24 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"ExecuteThread: '0' for queue: 'JmsAsyncQueue'" daemon prio=3 tid=0x0000000100759800 nid=0x23 in Object.wait() [0xffffffff643ff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
     - locked <0xffffffff6f4ed828> (a weblogic.kernel.ServerExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"Timer-0" daemon prio=3 tid=0x000000010078c800 nid=0x21 in Object.wait() [0xffffffff647ff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
     at java.lang.Object.wait(Object.java:485)
     at java.util.TimerThread.mainLoop(Timer.java:483)
     - locked <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
     at java.util.TimerThread.run(Timer.java:462)
"weblogic.timers.TimerThread" daemon prio=3 tid=0x00000001008e0000 nid=0x20 in Object.wait() [0xffffffff649ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
     - locked <0xffffffff6f4e75d0> (a weblogic.timers.internal.TimerThread)
"ExecuteThread: '3' for queue: 'default'" daemon prio=3 tid=0x0000000100709000 nid=0x1e waiting for monitor entry [0xffffffff65afe000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.jms.client.JMSConnection.stateChangeListener(JMSConnection.java:1413)
     - waiting to lock <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:682)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'default'" daemon prio=3 tid=0x000000010055c800 nid=0x1d in Object.wait() [0xffffffff65cff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
     - locked <0xffffffff6f427a80> (a weblogic.kernel.ServerExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"ExecuteThread: '1' for queue: 'default'" daemon prio=3 tid=0x000000010055c000 nid=0x1c in Object.wait() [0xffffffff65eff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
     - locked <0xffffffff6f427da0> (a weblogic.kernel.ServerExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"ExecuteThread: '0' for queue: 'default'" daemon prio=3 tid=0x00000001006fa800 nid=0x1b in Object.wait() [0xffffffff660ff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
     - locked <0xffffffff6f4280c0> (a weblogic.kernel.ServerExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"StateHolder" daemon prio=3 tid=0x0000000100584800 nid=0x1a waiting on condition [0xffffffff66aff000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
     at java.lang.Thread.sleep(Native Method)
     at StateHolder.run(StateHolder.java:80)
     at java.lang.Thread.run(Thread.java:619)
"Thread-1" daemon prio=3 tid=0x0000000100554000 nid=0x18 waiting on condition [0xffffffff66cff000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
     at java.lang.Thread.sleep(Native Method)
     at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:104)
"Low Memory Detector" daemon prio=3 tid=0x00000001003d3800 nid=0x16 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"CompilerThread1" daemon prio=3 tid=0x00000001003cf000 nid=0x15 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"CompilerThread0" daemon prio=3 tid=0x00000001003cd800 nid=0x14 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=3 tid=0x00000001003cb800 nid=0x13 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=3 tid=0x00000001003a4800 nid=0x12 in Object.wait() [0xffffffff680ff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
     - locked <0xffffffff6f4c7670> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
     at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=3 tid=0x00000001003a3000 nid=0x11 in Object.wait() [0xffffffff682ff000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
     - locked <0xffffffff6f401370> (a java.lang.ref.Reference$Lock)
"Worker" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:485)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
     - locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
     at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
     at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
     - locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
     at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
     at ConnectorSession.closeJMSSession(ConnectorSession.java:499)
     at ConnectorSession.receiveRequest(ConnectorSession.java:617)
     at ConnectorSession.processRequest(ConnectorSession.java:341)
     at Worker.mainApplication(Worker.java:127)
     at Worker.mainMethod(Worker.java:298)
     at Worker.main(Worker.java:163)
"VM Thread" prio=3 tid=0x000000010039c800 nid=0x10 runnable
"GC task thread#0 (ParallelGC)" prio=3 tid=0x000000010011b000 nid=0x3 runnable
"GC task thread#1 (ParallelGC)" prio=3 tid=0x0000000100121000 nid=0x4 runnable
"GC task thread#2 (ParallelGC)" prio=3 tid=0x0000000100122800 nid=0x5 runnable
"GC task thread#3 (ParallelGC)" prio=3 tid=0x0000000100126000 nid=0x6 runnable
"GC task thread#4 (ParallelGC)" prio=3 tid=0x0000000100127800 nid=0x7 runnable
"GC task thread#5 (ParallelGC)" prio=3 tid=0x0000000100129000 nid=0x8 runnable
"GC task thread#6 (ParallelGC)" prio=3 tid=0x000000010012b000 nid=0x9 runnable
"GC task thread#7 (ParallelGC)" prio=3 tid=0x000000010012c800 nid=0xa runnable
"GC task thread#8 (ParallelGC)" prio=3 tid=0x000000010012e000 nid=0xb runnable
"GC task thread#9 (ParallelGC)" prio=3 tid=0x000000010012f800 nid=0xc runnable
"GC task thread#10 (ParallelGC)" prio=3 tid=0x0000000100131800 nid=0xd runnable
"GC task thread#11 (ParallelGC)" prio=3 tid=0x0000000100133000 nid=0xe runnable
"GC task thread#12 (ParallelGC)" prio=3 tid=0x0000000100134800 nid=0xf runnable
"VM Periodic Task Thread" prio=3 tid=0x00000001003d5800 nid=0x17 waiting on condition
JNI global references: 818

JDBC Connection pool recovery after DB server restart

I am finding that Kodo is throwing the following exception after I restart
my database server (mysql). I am doing the database server restart while my
application server is idle, so it is not during a transaction.
Communication link failure: java.net.SocketException [code=0;state=08S01]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code? For example, WebLogic Server's JDBC connection pool has a setting that
enables testing a connection and recovering from such failures before
allocating it from the pool.
Ben

This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code?Not right now. You can log an enhancement request with our bug database:
http://bugzilla.solarmetric.com/

Best Practice to troubleshoot a Crawler Issue after SQL Server restarts

Hi Everyone
I am after some general advice or a suggested place to start when troubleshooting crawler issues after an unplanned, out-of-sequence server restart.
Specifically, the SQL Database in the SharePoint 2010 farm. Better yet, is there a standard practice way of resolving such issues?<o:p></o:p>
So far articles I have found suggest options from reviewing the crawl logs, creating a new crawl component, right through to using fiddler to monitor the crawler.
Are these sufficient places to start / methodologies to follow, what else should be considered?
Any advice greatly appreciated.
Thanks,
Mike

Well, as I said before, there are lots of different potential issues & resolutions for crawlers. It really depends on the issue. I would say that the base troubleshooting steps start the same no matter which service/feature you are looking
at. So, I'll try to keep this sort of generic, but beyond finding the details of the problem, the SOP or process will vary greatly based on what the error is. I hope this helps, and sorry if it's not specific enough.
1 - check the ULS logs
2 - check the windows application logs
3 - verify related services are running (get-spserviceinstance), possibly stop/start them to reprovision the instance on the affected server
4 - clear the config cache (this alone will clear about 30% of your basic problems)
6 - verify disk space & resource consumption on affected server (& SQL, SQL is always the potential to be the true "affected" server)
7 - iisreset
8 - verify connectivity between all servers in the farm and SP
9 - verify requir3ed features activated
10- check if any changes were made to environment recently (new hardware, updates to OS or apps, updates to GPOs, new solutions, etc)
11- check if the issue is reproducible in another environment (only reliable if this is a similar environment, i.e. same patch level test farm or dr farm). see if it occurs in other site collections within the web app, different web apps, different
servers/browsers, etc, basically just try to nail down the scope of the problem
There is a whole slew of thiings you could check from verifying certificates & perms, to rerunning psconfig, to checking registry keys, again I go back to it depends. hopefully this can get you started though. in the end ULS is where all
the real info on the issue is going to be, so make sure you check there. don't go in with tunnel vision either. if you see other errors in ULS, check them out, they may or may not be related; SharePoint is an intricate product with way more moving
parts than most systems. fix the little quick ones that you know you can handle, this will help to keep the farm clean and healthy, as well as crossing them off the list of potential suspects for your root cause.
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Composite with dependency not working after soa server restart

Hello,
I have composite application that invokes another composite application. After deploying those work fine. But after restarting soa server the one having dependency does not work any more. To soa server log I get following:
<Jul 1, 2010 11:45:29 AM EEST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
oracle.fabric.common.FabricException: Error in getting XML input stream: http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
Caused By: java.io.FileNotFoundException: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
<Jul 1, 2010 11:45:30 AM EEST> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "POProcessing" failed: Unable to find a WSDL that has a definition for service {http://oracle.com/sca/soapservice/POProcessing/POProcessing/receivePO}receivePO and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..>
So POProcessing does not work any more after server restart. validationForCC works fine also after server restart. Url http://...validationForCC/getStatusByCC?WSDL points to wsdl file and is visible by browser.
I use soa suite 11g patch set 2 (11.1.1.3) running on redhat enterprise linux 5.
Any idea what is the problem?
Is it somehow possible to configure which composites are started first during server startup?
regards, Matti
Edited by: user10197965 on Jul 1, 2010 2:28 AM

Yes, I did that. I'm not all that happy about this as a solution either, but it's better than making multiple copies.
We have since found out that his is a known bug and that it is fixed in some, but not all, deployments.
-------- see below -------------
Composites With WSDL Dependencies Fail To Deploy Following SOA Server Restart [ID 1272070.1]
Modified:Jul 19, 2012 Type:PROBLEM Status:MODERATED Priority:3
In this Document
     Symptoms
     Cause
     Solution
     References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Applies to:
Oracle SOA Platform - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
Symptoms
A SOA Project has an external reference to a Web Service or a reference to another Composite.
When the SOA Server is started, the Composite is trying to access the WSDL of it's referenced Web Service in order to load data structures. If SOA can not find the WSDL then the Composite fails to load/deploy.
Once this happens the Composite can not be started, or shutdown, from Enterprise Manager Fusion Middleware Control Application.
Related Error Messages:
[ERROR] [SOA-20020] ... Unable to find a WSDL that has a definition for service ... Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.]
javax.wsdl.WSDLException: WSDLException: faultCode=INVALID_WSDL: Error reading import of oramds
Cause
When SOA Server is restarting the Composite can not access the WSDL of it's referenced Web Service (it is not available).
In the first scenario there are two Composites on the same server: CompositeA and CompositeB.
In SOA Suite 11g there is no possibility to specify the load order for the composites. If CompositeA references CompositeB and if CompositeA is firstly loaded then it can not access the WSDL from CompositeB and the issue occurs.
In the second situation there is one Composite on the server (CompositeA) which references an external WebService (ExternalWS). If the ExternalWS is not available when the SOA Server is starting then this issue occurs.
Solution
Solution 1
Redeploy the affected Composite into the SOA Server.
You can do that but it is not advisable in a production environment and in a development environment it will take a lot of time to redeploy the composite manually
Solution 2
Copy the abstract WSDL locally into the project.
This is documented in these articles in our Knowledge base:
•     Document:1155033.1 Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
•     Document:1151973.1 Boot Order Of The Composites Upon Soa Suite Restart
Steps:
o     a. Copy and use the WSDL file in the Project
o     b. Edit the WebService Adapter
o     c. Change the "WSDL URL" to point to the WSDL copied into the project
o     d. Redeploy the Project
o     e. Make this configuration with all the Projects that have a references with other Web Services
Solution 3
Use shared artifacts in Metadata Service (MDS). A WSDL used by more than one composite is a shared artifact per definition. If the WSDL structure is changed (that is not happening frequently in a production environment), you will normally deploy a composite with a new version because overwriting it will break your production environment. Moreover, in a development environment you will need a proper process in place where different developers access the same artifacts within MDS. In addition, when you use external WSDLs (owned by third parties), you will have a proper process/agreement in place to be notified about modifications affecting your applications.
1.     In order to use shared artifacts a MDS connection must be configured in jDeveloper:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85488
2.     Deploy the shared artifacts:
o     a. Create a JAR profile and include the artifacts to share
o     b. Create a SOA bundle that includes the JAR profile
o     c. Deploy the SOA bundle to the application server
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85472
If the shared artifacts (WSDLs) needed are from other composites this step can be skipped
3.     Create a new WebService
o     a. When completing the "WSDL URL" click on "Find existing WSDL's"
o     b. Select "Resource Palette"
o     c. Go to the SOA-MDS
o     d. Select a WSDL from a Composite or the one deployed at step 2.
Known Restriction 1
The port and the location for the WSDL reference is not completed automatically by jDeveloper in the composite.xml file. This information must be inserted manually. In Bug:10287325 is raised this issue and it is available for SOA 11gPS2+.
Known Restriction 2
Another issue regarding MDS caching is raised in Bug:10218147 - the MDS cache is not refreshed when an artifact is deployed or deleted.
In order to refresh this cache the server must be restarted. This Bug resolves the issue but in a production environment the server restart will be the preferred option. The reason for that is because in a production environment you never deploy single composites under the same version after artifacts (WSDLs) have been modified.
The fix for the Bug:10218147 can be an acceptable solution in development environment where redeployment would be quicker than restarting the server.
Bug:10218147 is available for SOA 11gPS2+.
To find out more information about how to use Shared Metadata check the following documentation:
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
41 Deploying SOA Composite Applications
41.7.3 Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper
URL:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CACFEAJJ
Solution 4
The last solution is to use an UDDI (Universal Description Discovery and Integration).
Oracle recommends Oracle Service Registry 11g (OSR). The advantage is that you can use OSR and SOA Suite in a Shared WebLogic Domain.
http://www.oracle.com/technetwork/middleware/registry/overview/index.html
http://blogs.oracle.com/governance/2010/05/oracle_service_registry_11gr1.html
To find out more information about Oracle Service Registry check the following documentation:
Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g
33 Configuring Service and Reference Binding Components
33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10226/bc_config.htm#SOAAG37248
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
A BPEL Process Activities and Services
A.4 Publishing and Browsing the Oracle Service Registry
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_appx_ref.htm#SOASE85561
Oracle Fusion Middleware Service Registry 11g
http://download.oracle.com/otndocs/tech/soa/OSR11gR1ProductDocumentation.pdf
Solution 5
In case you have BPM Components in the Composites deployed check the following note:
Document 1317803.1 Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
The issue is caused by the Bug:11822470 SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
References
BUG:10218147 - WSDL CHANGES NEED SOA SUITE SERVER RESTART
BUG:10278478 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
BUG:10287325 - ABSTRACT WSDL NOT AVAILABLE WHEN COMPOSITE STARTED
BUG:10311698 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES CAN NOT BE STARTUP / SHUTDOWN
BUG:11822470 - SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
@ BUG:9267312 - MDS ARTIFACTS ARE STILL CACHED AFTER DELETING
@ BUG:9708488 - AFTER SOA RESTART, ALL PROCESSES HAVE TO BE REDEPLOYED
@ BUG:9749845 - SCHEMA CACHE STARTS EMPTY AFTER RE-START, BUT NOT AFTER DEPLOYMENT
NOTE:1151973.1 - Boot Order Of The Composites Upon Soa Suite Restart
NOTE:1155033.1 - Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
NOTE:1317803.1 - Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
Bug 11822470 : SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
               Bug Attributes
Type     B - Defect     Fixed in Product Version     11.1.1.6
Severity     2 - Severe Loss of Service     Product Version     11.1.1.4
Status     80 - Development to QA/Fix Delivered Internal     Platform     912 - Microsoft Windows (32-bit)
Created     Mar 1, 2011     Platform Version     2003
Updated     Oct 12, 2012     Base Bug     N/A
Database Version     N/A     Affects Platforms     Generic
Product Source     Oracle
Abstract: SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
*** 03/01/11 08:07 am ***
Customer has a project consists of two services for interaction with the
process and one reference to an external service.
On deployment of the process to an Enterprise Environment, the process works
as expected. However, upon a restart of the managed server, the process will
then fail to deploy.
Workaround used is to redeploy the project again.
Bug 10278478 : WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
               Bug Attributes
Type     B - Defect     Fixed in Product Version
Severity     2 - Severe Loss of Service     Product Version     11.1.1.3.0
Status     92 - Closed, Not a Bug     Platform     226 - Linux x86-64
Created     Nov 10, 2010     Platform Version     RED HAT ENTERPRISE LINUX 5
Updated     Dec 10, 2010     Base Bug     N/A
Database Version     N/A     Affects Platforms     Generic
Product Source     Oracle
Abstract: WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
Detailed Problem Description
====================
When a SOA composite get dependencies with other SOA composites located on the same server, if the dependency is still not loaded, the SOA composite will not be loaded, and there is no possibilities for Entreprise Manager console to restart it (EM crash). The only way to make it working is to redeployed the SOA composite from jDeveloper that is not acceptable in a production environment.
The composite that has the issue cannot be start-up or shut-down, although the Enterprise Manager do not show any errors with it.

BPEL process instance doesn't restart execution after BPEL server restart

I am using Oracle BPEL server 10.1.2 on Windows with the Oracle lite 10G dehydration datastore.
I have a one BPEL process (proc1) that invokes another BPEL process (proc2) synchronously. proc1 also invokes proc3 (also a BPEL process, but probably doesn't matter) synchronoulsy in parallel with proc2.
proc2 has a wait of ~30seconds in it. As soon as proc1 invokes proc2, I shutdown BPEL. Now, when I restart the BPEL server, proc2 instance finishes its execution. But, I don't see instances of proc1 and proc3 in the BPEL console.
Here are my questions:
1. If proc1 invokes proc2 and proc3 in parallel, shouldn't I see instances of proc2 and proc3 at the same time? I only see proc2 not even proc1.
2. Why doesn't proc1 resume its execution after BPEL server is restarted?
Any pointers appreciated.

1. If proc1 invokes proc2 and proc3 in parallel, shouldn't I see instances of proc2 and proc3 at the same time? I only see proc2 not even proc1.
Please read this thread:
ParallelFlows + sync flow

Autorun WebDynpro Application after J2EE Server Restart

Hi All
I have developed an application which registers the event capturer for KM in webdynpro.This application doesnot have any UI output.
I need to run this application after every J2EE server restart.
I changed the portalapp.xml and added startup = true property, but of no use.
Is there any way to do this ?
Points will be rewarded for helpful answers.

You should create a portal service and set startup = true in portalapp.xml

JMS Queue loosing messages on Server restart

Hi ,
We are having a problem with a queue that is loosing pending messages if the server is restarted.
We have following setup of Oracle Weblogic version 9.2 mp1.
The JMS Server is backed up by a DB based persistent store.we are having a message driven bean that process the message in the queue asynchronously.
the message that is delivered to the queue has Delivery Mode 'persistent'
and the mdb using transactionType=MessageDriven.MessageDrivenTransactionType.CONTAINER.
What is strange that we are loosing pending message in the queue , when server is restarted .even checking in the xxx'_WLSSTORE table in db i can see the message
was persisted.
If anyone of you have seen this situation kindly let me know.
thanks in advance.
Rgds
roy

You can follow this article to troubleshoot pending message issues.
http://weblogic-wonders.com/weblogic/2011/01/10/working-with-jms-and-the-standard-issues-in-jms/
-Faisal

Standalone JMS client in SJS App Server 8.0

Hi
I am trying to retrieve a message from a JMS queue from astandalone client.
The code the client uses to lookup JMS resources is:
try
          /* Create the object of InitialContext interface */
Properties env = new Properties( );
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL,"iiop://localhost:3700");
     jndiContext = new InitialContext(env);
          /* Find the connection factory object */
     QConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("jms/QConnectionFactory");
     /* Find the queue */
          queue = (Queue) jndiContext.lookup("jms/Queue");
catch (NamingException e)
     System.out.println("Error: " + e.toString());
The code throws the following exception:
Error: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.N
amingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
Exception in thread "main" java.lang.NullPointerException
at QReceiver.main(QReceiver.java:51)
What might be the problem? Pls help. The code works fine when executed as an Application client of SJS Appserver without using the JNDI Context part.
Thanks in advance
JLRocky

Also have a problem similar to this. I have found that
1. JMS between beans on the same server work fine
2. JMS between standalone client and server work fine if you start the bundled imq as a standalone message server
3. If you are using the Appserver then standalones cannont connect, but it you are using the imq beans cannot connect.
so i haven't had time to try this yet but my possible solution is:
configure the app server to use an external JMS server (its in the admin console some place) make the external server to be an imq running as a standalone, hopefully it can be started on localhost with out any port changes.
I think rather than bundling the two so both could be used they embeded the imq in the appserver and shielded it from outside comminication

Windows Time source resets after service/server restart

We have two completely separate domains. Our main domain has 4 DCs: the PDCe is looking to an outside source for its time source and the other 3 DCs are looking to the PDCe for their time source. The second domain, our DMZ, is setup the exact
same way. The PDCe is looking to an outside source for time and the other 3 DCs are looking to the PDCe for their time. If the Windows Time service is restarted or the server is restarted (during patching, for example), the time source changes
from the outside address to "Local CMOS Clock". From there, everything else will get thrown off. And now that I think of it, they might also revert to "Local CMOS Clock" after the service is restarted.
I configured the PDCe using the following command, which completes successfully:
w32tm /config /manualpeerlist:0.pool.ntp.org /syncfromflags:manual /reliable:yes /update
I can then run w32tm /query /status and confirm the setting is correct, but if I do the recommended "net stop..." and "net start..." commands, it will revert to "Local
CMOS Clock". If I leave it alone and the server reboots, it will again revert. This problem does not exist in our main domain. I have the appropriate rights and I don't see anything in the event logs that would indicate what the problem
is. Thoughts?
Chris

so the first thing is that only your PDCe should be going out to the internet (or another reliable NTP source) to get the time and that's done with:
w32tm /config /manualpeerlist:0.pool.ntp.org /syncfromflags:manual /reliable:yes /update
all your other DCs then go to the PDCe to get their time and we do that with:
w32tm /config /syncfromflags:domhier /update
so when you say you tested it on "test DC", you need to ensure the right settings are being pushed relevant to that DC's role and I'm not really certain about this test environment you have here
reading up on this, it all keeps going back to VMs doing time sync with the host, GPOs, scheduled tasks, or startup scripts
you can check the Systems event logs though, there will be messages in there stating why it reverted back to local cmos. it might do it if it can't reach the time source you specified and that part is normal but you need to check the logs first. even a successful
time sync message will help eliminate some of the causes
I think unregistering/registering the service starting with your PDCe should make it stick, as long as it can actually communicate with "0.pool.ntp.org". to verify this and to make sure UDP port 123 is open, run "w32tm /stripchart /computer:0.pool.ntp.org"
- if you get a time chart then communication is fine but if you get something else then you may have problems hitting that source and it's reverting back to cmos.

Applications stopped to work after application server restarted

Hi all,
Does anybody face the following problem? Applications which worked properly before application server (WLS Release 11.1.1) restart change their behavior. Particularly, instead label text of arguments of entity objects pages display arguments original names like control hints had not been configured. Only after redeployment the same ear file applications return back to normal. It never happens on local JDeveloper (11.1.1.3) environment. I guess that something wrong in application server application.
Thanks,
SNikiforov

For jdev 11.1.1.3 you need a wls 10.3.3 server. otherwise you run into problems. For more info check http://wp.me/pcBZk-7S
Timo

Expired Tasks not firing after Application Server restart

Hi all,
We have a problem with some production instances and their expiration times. The application server was down due to a power failure and did not come back up until this morning. By this time, many human workflow instances had expired. The dehydration has been updated to set the tasks as EXPIRED but there is no process flow any more in our BPEL. The BPEL is awaiting an Asynchronous call back from the TaskService. Does anybody know how we can continue the process flow?
We have tried using the worklist API's, setting the duration to a lower value (ie a minute) and the re-initiating the workflow but we want them to expire now (ASAP)
Thank in you advance
Jason
Edited by: user9980771 on 02-Dec-2008 07:51

After redeploy, check if your web application's
target is configured for the virtual server you
created.
Applications --> Web Applications --> [your web app]
--> Targets
If not, you should update the target and review your
redeploy script.This web application is a part of enterprise application. After deploy it's not in Web Applications but in Etnerprise Applications. There are 2 components in enterprise app - EJBModule and WebModule. I did't find anything about target there. No one option which I can set to my virtual server.

Cannot mount database after force server restart.

The server is hung. After forced reboot all databases was successfully mounted except one public folder, that gives an error:
MapiExceptionSearchEvaluationInProgress: Unable to mount database. (hr=0x80004005, ec=1177)
The error ocured on Exchange Server 2010 SP3 Standard Update Rollup 5.
Update to Rollup 7 does not solve the problem.
Eseutil 14.03 shows no errors.

Move all the log files include all other files to another location and try to mount it.
Post the update
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

XI JMS adapter after JMS provider reboot

Hi All,
I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
In JMS adapter we have folloving settings and we are connected straight into queue:
Transport Protocol = SonicMQ JMS Provider
General JMS Settings:
Transactional JMS Session is in use
Delivery Mode of Message Producer = Persist JMS messages..
+ Queue user & pw
Error Handling Settings:
Wait After Message Error(msecs) = 60000
Wait Before Reconnect(msecs) = 60000
Does anyone ran into this earlier?
Thanks in advance.
-Kimmo

Hi Saravana,
It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

JMS Client Eeconnect After JMS Server Restart

Similar Messages

Maybe you are looking for