Defining application-scoped work manager in Plan.xml

I am having trouble getting my MDBs to recognize work managers that I have defined in my deployment plan using the admin console.
The work managers show up properly when I click the deployed application and go to the Deployments->myapp.ear->Configuration->Workload tab. They do not show up, however on the Deployments->myapp.ear->Monitoring->Workload tab.
Also, when the server boots, I get a log message like this:
<BEA-002919> <Unable to find a WorkManager with name FaxErrorQueue. Dispatch policy FaxErrorQueue will map to the default WorkManager for the application care360-backend-app-2008>even though FaxErrorQueue shows up under Configuration->Workload.
BACKGROUND
I am upgrading an 8.1 wls to 10MP1. Our MDBs are deployed as a single jar, included in 2 separate ears, which are deployed to 2 separate clusters. So, if we have 2 clusters with 2 managed servers in each cluster, we deploy each MDB to all 4 servers. We control the Execute Queues for each server in 8.1 with different values so that MDB#1 might have a single thread in one managed server and zero execute threads on another. Using the deployment plan is the only way I can think of to implement this. We would prefer not to use the 8.1 emulation, as the deprecated execution queues will have to be dealt with eventually. I am open to any other approaches to accomplish this as well.
Thanks,
Joe

Hello Fred,
Thank you very much for reply.
I totally agree with you but in my scenario, I have multiple domains on a single box.
and I am afraid that there could be a situation where one bad application of a particular domain may take most of the CPU usages.
What I can do is: I can define max thread constrain to all the applications of all the domains but it is not acceptable bcz we have hundreds of applications per domain.
So what I want is: to define some kind of thread constrain at the domain level [so that I can have CPU usages allocated to every domain] as well as some kind of thread constrain to few applications [non prioritize].
I tried this by defining Global Work Managers & Application-scoped Work Managers but I found that applications only respect to Application-scoped Work Managers.
or if I have some kind of way that make sure certain percentage of CPU usages is allocated to a particular domain?
hope I have made my self clear.
Thanks,
Qumar

Similar Messages

Work Manager both Global Work Managers & Application-scoped Work Managers

Hi all,
I want to use both Global Work Managers & Application-scoped Work Managers in my domain [single], is it possible?
Basically I want to make sure my domain have fix number of thread.
In my environment, I have multiple domains on a single machine, so I want to make sure every domain has fix number of threads to maintain the whole system integrity.
if I won't make sure this, there could be scenario that one particular domain is taking much of the CPU usages than others.
Thanks,
Qumar

Hello Fred,
Thank you very much for reply.
I totally agree with you but in my scenario, I have multiple domains on a single box.
and I am afraid that there could be a situation where one bad application of a particular domain may take most of the CPU usages.
What I can do is: I can define max thread constrain to all the applications of all the domains but it is not acceptable bcz we have hundreds of applications per domain.
So what I want is: to define some kind of thread constrain at the domain level [so that I can have CPU usages allocated to every domain] as well as some kind of thread constrain to few applications [non prioritize].
I tried this by defining Global Work Managers & Application-scoped Work Managers but I found that applications only respect to Application-scoped Work Managers.
or if I have some kind of way that make sure certain percentage of CPU usages is allocated to a particular domain?
hope I have made my self clear.
Thanks,
Qumar

Weblogic 10.3 : Work manager is not getting assigned to a application

Hi,
i have assigned a work manager to an application in weblogic-application.xml and able to see that under Deployments
-> Application name -> Configuration -> Workload tab of weblogic console.
But while starting server get a warning as
<Dec 17, 2008 9:45:16 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name RealWorkManager. Dispatch policy RealWorkManager will map to the default WorkManager for the application SmpMain>
Can some one help me out how to assign a work manager to a application.
Thanks,
Smita

Thanks for your help.
When i created a work manager from Deployments -> Configuration -> Workload -> New and the new Work Manager appears in the Application-Scoped Work Managers table. But was not able to see that in Monitering -> Workload Work managers table. Why is that so?
Regards,
Smita

Work Manager API in Sun Java Application Server 8.1

I am trying to build a parallel application using Work Manager api (javax.resource.spi.work.WorkManager;)
I studied the Websphere implementation of WorkManager there you need to make JNDI lookup for work manager and then use it to submit the work.
My question is if i make class which will implement the javax.resource.spi.work.WorkManager; interface and use that class to submit the work and execute it in parallel then will that class will handle the resource management and all j2ee services
Do we have separate implementation of work manager API for Sun Java Application Server 8.1 (any jar like asynch.jar in IBM websphere) so that we will just create a work manager using admin console and make JNDI lookup and use it
Please guide me

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

Looking up a custom work manager

Hi All,
I'm a little stumped with accessing a custom work manager in WLS 9.2. I think I've followed the docs exactly.
I tried to use the default wm by looking up "java:comp/env/wm/default" and that worked fine. I didn't in any was define that in any config files. I then created 2 custom work managers in weblogic.xml and named them "sync" and "async." In web.xml I added 2 resource refs to those same names, matching the "sync" and "async" names like the docs say. However looking them up by either "java:comp/env/wm/sync" or just "sync" gave me a NameNotFoundException.
I also tried defining the work managers in weblogic-application.xml and omitting the resource-ref, but that didn't work. I do see the work managers show up in the console. If I define them in weblogic.xml, they show up under the web app and if I define them in weblogic-application.xml, they show up under the app (ear.)
What step am I missing?
The instructions I'm using are at the bottom of this page: http://download.oracle.com/docs/cd/E11035_01/wls100/config_wls/self_tuned.html
thanks
john

I got it working. I don't know what I was doing wrong before.
My weblogic-application.xml contains this:
    <work-manager>
      <name>sync</name>
      <fair-share-request-class>
        <name>half share</name>
        <fair-share>100</fair-share>
      </fair-share-request-class>
    </work-manager>
    <work-manager>
      <name>async</name>
      <fair-share-request-class>
        <name>half share</name>
        <fair-share>100</fair-share>
      </fair-share-request-class>
    </work-manager>My web.xml contains this:
<resource-ref>
    <res-ref-name>sync</res-ref-name>
    <res-type>commonj.work.WorkManager</res-type>
    <res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
    <res-ref-name>async</res-ref-name>
    <res-type>commonj.work.WorkManager</res-type>
    <res-auth>Container</res-auth>
</resource-ref>And my jndi lookup looks like this:
WorkManager wm = (WorkManager)context.lookup("java:comp/env/sync");thanks

Unable to see Planning application under calculation Manager

Hello All,
I created a Planning application in workspace and choose the Sahred Service Project as APS server.Now I want to create business rules.For that when I m lunching Calculation Manager from workspace, I m not able to see the appliaction that I had created before ,under Planning option of Calculation Manager.
Thanks.......

I think you created a classic planning applications. Calc manager will not recognize classic planning applications in version 11.1.1.2 and prior.
You need to create a planning applications via EPMA and then you will see this in calc manager. If you have already opened calc manager, right click on the Planning node and do a refresh to synchronize the applications from EPMA.
Hope this helps.
~SM

Work Management Service Application

does anyone have a step by step guide on how to create from scratch a work management service application, i have deleted mine due to issues with task syncs i think it was the configuration of this application that was causing this issue,
any help welcome.
Cheers

Hi,
According to your post, my understanding is that you wanted to create Work Management Service Application.
The following Service Applications must be provisioned before you can deploy the Work Management Service Application:
Search
User Profile
In addition to this, the Work Management service account must have some further permissions configured:
Full Control on the User Profile Service Application
Grant Access To Process Identity
To Create Work Management Service Application, Navigate to Application Management in SharePoint central administration, select Manage Service Application link. In Service applications page, create new Work Management Service Application, and specify the
details.
After re-create a new Work Management Service Application, we need to:
Create a new Application Pool, but use the same account as for the Application Pool hosting your My Sites/Social or Portal.
Run a crawl
Incremental, continuous or full crawl should suffice.
More information:
http://consulting.risualblogs.com/blog/2013/10/23/sharepoint-2013work-management-service-application/
http://sureshpydi.blogspot.in/2013/11/work-management-service-application-in.html
http://zimmergren.net/technical/tip-work-management-service-application-keeps-telling-us-last-updated-at-111901-1200-am-fixes
http://blogs.technet.com/b/praveenh/archive/2013/08/22/work-management-service-application.aspx
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Work Management Service (WMS) Application on mulit-farms

Hi guys,
Is there any limitation for configuration the Work Management Service (WMS) Application on multi-farms?
I have 2 farms – farm A hosts all SAs and farm B hosts only web contents.
I understand there is dependency between WMS and search and UPS. Does that mean I cannot deploy my WMS on farm A?
Thanks

Hi,
According to your post, my understanding is that you want to configuration the Work Management Service (WMS) Application on multi-farms.
Per my knowleadge, you can deploy Work Management Service on farm A.
Though there is dependency between WMS and search and UPS, , some service applications such as Search and User Profile can be shared across server farms in SharePoint 2013.
In addition, you can also configure a SharePoint Server 2013 content farm that receives search queries to trust the SharePoint Server 2013 farm that sends the queries.
More information:
Share service applications across farms in SharePoint 2013
Configure trust for search between two SharePoint Server 2013 farms
SharePoint 2013: Work Management Service Application
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Filtering lists in Syclo Agentry SAP Work Manager application

Hello Experts,
I am trying to filter a displayed list at run time ( while running the application). the list fetches the data from an existing object.
I am trying to customize few things while displaying the filters on the list.
So far, I could only find a single property under Agentry application configuration to deal with filtering list values, as per the screenshot below.
Moreover, I could see that I can allow filtering the list based on a set of particular fields.
Here, I cannot determine if the Agentry Editor will allow me to customize the look and feel of the filters being displayed.
Is there any other way I can filter the lists and which provides me with the flexibility to customize the look and feel of the filters being displayed?
For example, i could add an image in the list and might want to filter the list based on a particular image. will this be possible and supported by SAP Work Manager 5.3 (Agentry 6.0) ?

Hi Arihant,
I tried this filter and sort list tile in ATE. Please refer my example regarding the filtering and sorting:
Step1: No Filter.
Here there is no filter, so ATE is not hvaing any filtering.
Step2: Add filtering property to the List Tile.
Filtering properties:
Test in ATE.
Click on that filter symbol, we will get the following.
Step3: Add Sorting to the List Tile.
Sort Properties are: Add the CompanyName as sort property
Check in ATE.
Apply sort by clicking the symbol
List rows are sorted based on company name as below:
I to checked in iphone but the sort property is not coming. I will check the gaps and update.
Thanks,
Swaroopa.

Custom Work Manager not shown in WL Server Admin Console

An application scoped custom work manager is to be configured, for which the files weblogic-application.xml, weblogic-ejb-jar.xml, weblogic.xml have been defined. After it is deployed on the server, custom work manager is not being shown in the list on console -> deployments -> application -> monitoring -> workload.
What could be the reason? Is there something which is missed out?

Hi Justin,
According to the error message and the issue can be caused by the edition of your SSRS is not support for the custom data provider. For example the express edition have limitation support on this:
Features Supported by the Editions of SQL Server 2012 .
If your edition is the supportted edition and the issue can be caused by the custom data provider do not necessarily support all the functionality supplied by Reporting Services data processing extensions. In addition, some OLE DB data providers and ODBC
drivers can be used to author and preview reports, but are not designed to support reports published on a report server. For example, the Microsoft OLE DB Provider for Jet is not supported on the report server. For more information, see
Data Processing Extensions and .NET Framework Data Providers (SSRS).
If you are running on a 32-bit platform, the data provider must be compiled for a 32-bit platform. If you are running on a 64-bit platform, the data provider must be compiled for the 64-bit platform. You cannot use a 32-bit data provider wrapped with 64-bit
interfaces on a 64 bit platform.
More details information:Data Sources Supported by Reporting Services (SSRS)
Similar thread for your reference：
ERROR: An attempt has been made to use a data extension 'SQL' that is not registered for
this report server.
Error when viewing SSRS report with SQL Azure as data source
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

How to use a work manager dedicated for an URI

Hello,
I have a servlet able to manage different use cases, based on differents URI (the servlet is mapped on /*, and depending of the URI and the configuration, I do different work)
I would like to set a workmanager on each of my use cases.
Is it possible to set a workmanager on a use case without any update of the descriptor files ? (without multi mapping the servlet because my use cases are pluggables)
I've seen it is possible to acces a workmanager programaticaly (commonJ work managers) but it seems to be mandatory to reference the commonJ work manager inside the web.xml file to allow loca JNDI lookup on this work manager. Thus If I add a work manager, I have to update the web.xml. There is another possibility without updating any deployment descriptors ?
Thank you very much for your answers,
Best Regards,
C.

James,
thank you for your update.
1) Concerning the first solution (CommonJ WM), it sounds good for my needs but I still have to update the web.xml to add the resource-ref to access the WorkManager by JNDI:
<resource-ref>
    <res-ref-name>wm/TestWorkManager</res-ref-name>
    <res-type>commonj.work.WorkManager</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>So I have to update my ear, it is not exactly what I want :(
2) Concerning the deployment plans, it is also a good idea, I can multiinstance a servlet to use different mapping and then apply different workmanager for different uris,
This is working. I update the web.xml using a deployment plan.
The only negative point is I can't only apply the deployment plan but I have to redeploy the entire application (wich is not recommended for production because it occurs a out of service period)
Do you know any solutions for this two points ?
Thank you a lot
Best regards,
C.

JMS Adapter Config issues with Plan.xml

Hi All,
I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
Oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
The deployment plan reads as follows :
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>connectors</application-name>
<variable-definition>
<variable>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<value>eis/wls/Queue</value>
</variable>
<variable>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<value>weblogic.jms.XAConnectionFactory</value>
</variable>
</variable-definition>
<module-override>
<module-name>JmsAdapter.rar</module-name>
<module-type>rar</module-type>
<module-descriptor external="false">
<root-element>weblogic-connector</root-element>
<uri>META-INF/weblogic-ra.xml</uri>
<variable-assignment>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>connector</root-element>
<uri>META-INF/ra.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
</deployment-plan>
Thanks
JB
Edited by: 939260 on Jun 20, 2012 5:13 AM

Hi JB,
Please follow the below steps from beginning...
1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
2. create new JMS Module.
3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
If you have followed the abpve steps correctly, you should not face any problem.
Hope this helps,
N

Namespaces in plan.xml - can't override weblogic.xml

So, we've tried every combination we can think of, but we can't seem to get a plan.xml that successfully overrides items in weblogic.xml. It seems to be an issue around namespaces:
<May 19, 2009 10:40:57 AM MDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor /nas/scart/domain_tmps/tcatshopDomain/servers/tcatshop1/tmp/_WL_user/MasterEar/v99i42/MasterWebPortal.war/WEB-INF/weblogic.xml of module MasterWebPortal.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/nas/scart0/prod_ecom2/local/apps/apps92/tcatshop/THUNDER_01.09.06.004/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'description@http://www.bea.com/ns/weblogic/90 weblogic-version@http://www.bea.com/ns/weblogic/90 security-role-assignment@http://www.bea.com/ns/weblogic/90 run-as-role-assignment@http://www.bea.com/ns/weblogic/90 resource-description@http://www.bea.com/ns/weblogic/90 resource-env-description@http://www.bea.com/ns/weblogic/90 ejb-reference-description@http://www.bea.com/ns/weblogic/90 service-reference-description@http://www.bea.com/ns/weblogic/90 message-destination-descriptor@http://www.bea.com/ns/weblogic/90 session-descriptor@http://www.bea.com/ns/weblogic/90 jsp-descriptor@http://www.bea.com/ns/weblogic/90 auth-filter@http://www.bea.com/ns/weblogic/90 container-descriptor@http://www.bea.com/ns/weblogic/90 charset-params@http://www.bea.com/ns/weblogic/90 virtual-directory-mapping@http://www.bea.com/ns/weblogic/90 url-match-map@http://www.bea.com/ns/weblogic/90 security-permission@http://www.bea.com/ns/weblogic/90 context-root@http://www.bea.com/ns/weblogic/90 wl-dispatch-policy@http://www.bea.com/ns/weblogic/90 servlet-descriptor@http://www.bea.com/ns/weblogic/90 work-manager@http://www.bea.com/ns/weblogic/90 logging@http://www.bea.com/ns/weblogic/90 library-ref@http://www.bea.com/ns/weblogic/90' instead of *'session-descriptor@http://www.w3.org/2001/XMLSchema-instance' here in element weblogic-web-app@http://www.bea.com/ns/weblogic/90:<nullplan.xml>*
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:229)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:216)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
This is in WLP 9.2...
Plan:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/90">
<application-name>MasterEar.ear</application-name>
<variable-definition>
<variable>
<name>ThundercatCookieName</name>
<value>JSESSIONID_THUNDERCAT_PLAN_XML</value>
</variable>
<variable>
<name>ThundercatCookieDomain</name>
<value>.qwest.com</value>
</variable>
</variable-definition>
<module-override>
<module-name>MasterWebPortal.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<variable-assignment>
     <name>ThundercatCookieName</name>
     <xpath>/weblogic-web-app/session-descriptor/cookie-name</xpath>
</variable-assignment>
<variable-assignment>
     <name>ThundercatCookieDomain</name>
     <xpath>/weblogic-web-app/session-descriptor/cookie-domain</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
We've tried a lot of combinations of namespaces and such to try and get it to work, and it always spits out the same error....
Thanks,
Tim

Hi Folks -
Below is the weblogic.xml (or at least one version of it).
We're trying to override the session-descriptor cookie-name and cookie-domain ...
Thanks!!
Tim
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
<context-root>home</context-root>
<jsp-descriptor>
<page-check-seconds>-1</page-check-seconds>
<precompile>true</precompile>
<precompile-continue>true</precompile-continue>
<verbose>false</verbose>
<print-nulls>false</print-nulls>
</jsp-descriptor>
<session-descriptor>
     <cookie-name>JSESSIONID_THUNDERCAT</cookie-name>
     <cookie-domain>.tservicesq.com</cookie-domain>
</session-descriptor>
<library-ref>
<library-name>wlp-tools-visitor-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-commonui-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-services-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-full-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>p13n-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-controls-1.0-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>weblogic-controls-1.0-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-wsrp-producer-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-lookandfeel-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-light-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-common-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-struts-1.2-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>struts-1.2</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>wls-commonslogging-bridge-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>jstl</library-name>
<specification-version>1.1</specification-version>
<implementation-version>1.1.2</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-netui-resources-1.0</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-netui-1.0</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>QwestCmsLibrary</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.3.4.2</implementation-version>
</library-ref>
<library-ref>
<library-name>SIWebPortal.war</library-name>
</library-ref>
<library-ref>
<library-name>StylesWebPortal.war</library-name>
<specification-version>2.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>ShopWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>ProfileWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>CommonsWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>EBillWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>EPayWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>AdminWebPortal.war</library-name>
<specification-version>2.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
</weblogic-web-app>

Application scoped WorkManager

We have an application (.ear) which has two web apps (war's). We want to setup workmanager with max-threads-constraint for both the application. I was able to create application scoped workmanager through deployment descriptors However, I was not able to set the thread count other than the default (-1).
Note: The application (.ear) is targeted to a cluster.
Here is the snippet of the workmanager that I created in the weblogic.xml
<wl-dispatch-policy>workmanager-app1</wl-dispatch-policy>
<work-manager>
<name>workmanager-app1</name>
<max-threads-constraint>
<name>max-app1-threads</name>
<count>30</count>
</max-threads-constraint>
</work-manager>
Please let me know if any thing is wrong in the work-manager configuration. Any pointers on this is highly appreciated.

I need a mechanism to limit one of the webapp to use not more than 30 threads and the second webapp not more than 10 threads while targetting to the same cluster.

Can't Find Custom Work Manager For Resource Adapter

I'm creating an inbound resource adapter and wish to throttle the number of connections via a custom work manager.
If I understand the BEA docs, I can declare and define a resource adapter's work manager inside of its entry in weblogic-ra.xml .
For example:
<?xml version = "1.0"?>
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
<jndi-name>InboundRA</jndi-name>

<work-manager>
     <name>CustomWM</name>
     <max-threads-constraint>
<name>maxthreads</name>
     <count>3</count>
     </max-threads-constraint>
</work-manager>
However, upon startup I see :
<BEA-002919> <Unable to find a WorkManager with name CustomWM . Dispatch policy CustomWM will map to the default WorkManager for the application appsdirCustom_ear> .
So it uses the default work manager.

Well, I did it again. Solved my own problem two hours after I posted it. Which, I guess, is better than not solving it.
I mistakenly thought that the <work-manager> entry in weblogic-ra.xml is a declaration. It is apparently a reference.
I declared a WorkManager of the same name in the WLS 9 console, restarted the server, and it appears that I am now using the custom work manager.
The max-threads constraint also works.

Defining application-scoped work manager in Plan.xml

Similar Messages

Maybe you are looking for