Leopard Resources Management issue

I have using Leopard for about a month, I don't know if any other user has same issue with me, here is my problem with my Leopard:
- first time boot, my system has over than 1.5GB free memory
- I opened an application such as NetBeans, XCODE, ADOBE photoshop, and it runs well, my free memory about 100MB,
- After I close those apps, free memory doesn't change still on 100MB even drop, and what do I got, open dashboard, switching space is lagging and opening firefox took over than 8seconds or even my system got crashed during quicklook a movie or big pdf.
Many application will crashed and system runs slower than before I open and close big application, my application all Intel Native, so nothing wrong with the applications...
The problem is, I think Leopard got big problem on handling resources, specially when an application released their resources, Leopard can't reserved it to another application or system. This should be memory leak issue...cmiiw
Please give me an advice is there any solution for this or I have to wait till Apple release new update?
Thanks anyway.

_Try this as an isolation step:_
Turn the computer off. Press and hold shift. Turn the computer on. Continue to hold shift until you see the spinning gear below the Apple logo. Once it is started up, log in. Does it do the same thing here?
Let me know the results for further steps.

Similar Messages

XRPM Resource Management issue

Gurus,
In xRPM under Resource Management Tab. I am not able to find any resources under resource view.TAble is empty.
Although I have created Resource pool and assinged a resources to administrator.
Please let me know if i am missing any settings
Thanks in advance.

Hello Riya,
Here are the steps to assign the Resource Manager to a Resource Pool:
1) Create a Resource Pool
2) Add resources based on the selection criteria.
3) Add a Resource (BP in employee Role) as Resource Manager to this Resource Pool.
NOTE: this resource manager should be attached to your User.
to see which User this Resource Manager is attached to, go to Portfolio Management -> Administration -> Resources
find the resource with its Name or Resource ID (BP) and Display. you will see the linked user. If it is not linked to any user you can assign the user to this resource manager.
4) when you login with this Resource Manager's User, and navigate to Resource Management -> Resources, you will see all the resources under the Resource Pool where this current user is Resource Manager.
Hope this will help.
Thanks and Regards,
Piyusha

Colour Management Issue with PS CS3 and Leopard 10.5.2

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

>It was working perfectly in Tiger with the monitor profile.
You were lucky.
the monitor profile is so Photoshop can display your images correctly.
the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
you need to read up on color management:
http://www.gballard.net/psd.html
http://digitaldog.net/

Colour Management issue With Leopard and PS CS3

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

You need to use the correct printer profile for the paper you're using. If the printer didn't come with any pre-built profiles, check Canon's web site to see if they have any profiles available for your printer that you can download.
Printer profiles are very specific. You can't take take a profile for glossy Epson paper and expect it to work very well for Canon glossy paper.

Colour Management Issues with Leopard and Photoshop CS3

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

I'm having exactly the same problem, only my printer is a Canon Pixma iX4000. The colour is all bleached out, it looks exactly like when you've accidentally printed an RGB file on a CMYK printer, and at first I thought that was what I had done, but it isn't. This is very frustrating, I've spent all day going through the manuals, recalibrating etc, but no luck. This is a brand new Mac Pro and printer, but if its not going to print what I see on screen it's just expensive junk.
I wasn't sure if the problem was Leopard or the printer or CS3...

File Server Resource Manager 2012 - Fails to generate storage report - Event ID: 8242 and 602

Installed file server resource manager roll on new 2012 file server.   When I attempt to run a dup report on the local volume, I received an error message: "the report generation task failed with the following errors: Error generating report
job with task name". "
Event ID 8242 and 602 are logged in the event viewer.
Log Name:      Application
Source:        SRMSVC
Date:          6/24/2013 11:11:03 AM
Event ID:      8242
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxxxxxxxxxxx
Description:
Reporting or classification consumer '' has failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SRMSVC" />
    <EventID Qualifiers="32772">8242</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-24T16:11:03.000000000Z" />
    <EventRecordID>1276</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxxxxxxx</Computer>
    <Security />
</System>
<EventData>
    <Data>
    </Data>
    <Data>
Error-specific details:
   Error: (0x80131501) Unknown error</Data>
    <Binary>2D20436F64653A20434E534D4D4F444330303030303234332D2043616C6C3A20434E534D4D4F444330303030303231322D205049443A202030303030333036302D205449443A202030303030333734382D20434D443A2020433A5C57696E646F77735C73797374656D33325C73726D686F73742E657865202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
Log Name:      Application
Source:        SRMREPORTS
Date:          6/24/2013 11:11:03 AM
Event ID:      602
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxxxxxxxxxxxxxx
Description:
Error generating report job with the task name ''.
Context:
- Exception encountered = System error.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SRMREPORTS" />
    <EventID Qualifiers="0">602</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-24T16:11:03.000000000Z" />
    <EventRecordID>1277</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxxx</Computer>
    <Security />
</System>
<EventData>
    <Data>Error generating report job with the task name ''.
Context:
- Exception encountered = System error.
</Data>
</EventData>
</Event>
When I click on schedule a new report task, I get an error "Class not registered".
nada

Hi,
When we schedule a new job, we add a scheduled task to the c:\windows\tasks folder.
The scheduled task will contain the following command line
"c:\WINDOWS\system32\storrept.exe reports generate /scheduled /Task:"FSRM_Report_Task{GUID.......}"
There is also a folder on the system drive
C:\StorageReports\Scheduled
We Also store information in the system volume information folder in the following files:
c:\system Volume Information\SRM\Settings\ReportSettings.xml (we use .old and .alt extentions}
c:\system Volume Information\SRM\reports\reportX.xml (where X = an incrementing number set, in writing to these files, we also use .old and .alt extentions}
When experiencing issues relating to scheduled report jobs, you will want to examine these files and check for NTFS permissions issues on these locations also.
Make sure you check the volume that you will be running the report on.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

RH8 hangs with 100% CPU when closing a topic. Resource Manager to blame?

Please refer to the following thread for background information: http://forums.adobe.com/thread/734972?tstart=0
I'm re-listing this issue, as it has rasied its ugly head again, and I've no resolution this time.
Summary:
The original issue was that RH8 would hang whenever I closed a topic for anywhere between 15-30 seconds before allowing me to interact with the application again. Attempting to interact with the GUI during this freeze would result in the 'Not Responding' message at the upper-left of the application window (suffice it to say I'm on a PC with Windows).
After much investigation it was suggested to me that my profile may be corrupt, and in order to test this, another user should log on and see whether they experienced the same problem. As it is, they did not. So I had my Systems Admin recreate my domain profile, and everything worked just fine.
...until now.
Last week we all upgraded from Windows XP to Windows 7 (32 bit). We also changed our anti-virus software. The awful hanging issue in RH has returned.
We've attempted the solution from last time, by recreating my profile on the domain, to no avail. We have in fact gone to the extent of reformatting the hard drive and reinstalling Windows, the anti-virus software and RH8 (plus all available patches) from scratch. In case anyone is wondering, we've tried running RH without the antivirus installed, and when installed have also tried excluding the RH application folder and all my project folders, just in case it was the anti-virus software at fault. Regardless, the RH problem exists.
I can't understand why I'm now having this problem. Truth be told, I never really understood why recreating my domain profile in the first place resolved the problem last time.
However, I have now discovered something else...
In my RH Resource Manager I have a few thousand images in the Image folder. Not much I can do about this - the applications I write Help for have many screens users can access, and I write the Help for half a dozen applications. When I delete the contents of the images folder within the Resources Manager, RH works perfectly - no hanging whatsoever. As soon as I import the images into this folder again, the hanging is back. I have tested this a few times now, and have rebooted and had another user log on to confirm, and it happens every time. I'm dumbfounded of course, particularly because the same set of images has been sitting in the Resource Manager for months (since my original post about this issue, last year), and RH has been working perfectly.
I've also tried Peter Grainge's suggestion to create an empty BaseCSS_res.dll file (http://www.grainge.org/pages/authoring/rh8/using_rh8.htm), but as I've installed all the RH8 updates, this shouldn't be an issue.
I've also tried deleting the CPD file without success.
Thanks in advance.

It seems this has been resolved!
Many thanks for all the suggestions. Peter ultimately forwarded the solution - something that he'd sourced from a rep at Adobe, as follows:
Every file/folder change in the root folder of RH8 Resource Manager triggers a rescan of all the sub-folder/files. That is why in case of thousand image it will take time. Like xxxx said we may ask user for root folder, it should not be project folder or frequently changing folder.
Probably he is using the default path given in the root folder and RoboHelp changes a temporary css file in that folder very frequently, in fact with every topic close.
That is causing the slowness and it should be easy to reproduce in the default scenario. This is RH8 only issue.
So, to fix my issue:
Open the Resource Manager Pod.
Click the Add/Edit Categories icon. The Add/Edit Categories window appears.
Within this window, change the 'Root Folder' path to something other than the default. In my case, I create a new folder on my root hard drive, outside of the Robohelp folder, just to be sure.
So far this is working perfectly - no 'hanging'. I'll keep an eye on it.
I love the comment "This is RH8 only issue."
Oh?! Is it? Was it fixed in a patch, Adobe? Please don't tell me that it was fixed in RH9, because there's no way known I should have to pay for an upgrade to resolve something that certainly looks like a bug. As happy and grateful I am to have this resolved, it has cost me a week's work.

How to see the topicrefs of a nested ditamap in the resource manager?

Hello,
I use FM 12. I am trying to move a 500 page document with several chapters into Dita 1.2. I use one ditamap per chapter. When I nest ditamaps under a main ditamap using maprefs, I do not see the topicrefs of each map. Also, the topics do not show up when PDF is generated. How can I make all topicrefs appear in the resource manager?
Thanks,
Rajashree

You can't see the topics in the chapter maps form the root map. When you open a map, you see the topicrefs for that map not the submaps. If you want to see the topicrefs, double-click the map reference and it'll open the chapter map. That might be a nice feature, but it doesn't currently work that way. If you want to see all of the topicrefs together, you'll need to put them all in one map.
The issue of the topics in the submaps not being included when you generate a PDF sounds like a bug (or you've set something up wrong). You might try changing the maprefs to topicrefs. A mapref is really just a special type of topicref, and the build process may not be set up to handle maprefs.
Cheers,
...scott

XAER_RMFAIL : Resource manager is unavailable

Weblogic 8.1, I don't recall which service pack, sp10? Maybe?
Anyway, here's the relevant stack trace. We had a strange WLS implosion last
night that we're tracking down. We saw these when our code was trying to get
a connection out of the datapool.
<Mar 1, 2006 10:09:12 PM PST> <Warning> <JTA> <BEA-110030> <XA resource
[weblogic.jdbc.wrapper.JTSXAResourceImpl] has not responded in the last 120
second(s).>
01 Mar 2006 22:09:21,652 WARN com.pfizer.ecms.as.MetricsSession - logEvent:
exception: start() failed on resource
'weblogic.jdbc.wrapper.JTSXAResourceImpl': XAER_RMFAIL : Resource manager is
unavailable
javax.transaction.xa.XAException: Internal error: XAResource
'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
at
weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceD
escriptor.java:1019)
at
weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResour
ceDescriptor.java:572)
at
weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInf
o.java:1068)
at
weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceI
nfo.java:1001)
at
weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceIn
fo.java:203)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:419)
at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
:298)
at
com.pfizer.ecms.asutil.DataAccessManager.getConnection(DataAccessManager.jav
a:117)
Here's our configuration:
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
MaxCapacity="150" Name="OraclePool"
Password="*****"
Properties="user=******" ShrinkPeriodMinutes="5"
Targets="myserver" TestConnectionsOnCreate="true"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="dbpool" Name="OracleSource"
PoolName="OraclePool" Targets="myserver"/>
Looking this up, I was pointed to a JTA FAQ page on edocs, and it basically
said we should be Refreshing the connection pool, but the RefreshMinutes
parameter is deprecated, and as you can see we're testing connections as is.
We're puzzled by a couple of things, almost certainly application related,
but still relevant. We have 150 connections allocated to the pool, but even
at peak load during the day we bounce around the 40 mark. When we got the
above exception, we were hitting the 150 ceiling. We don't quite know why
yet.
During this time, our DB server was pretty heaviliy loaded. There were some
horrendous queries running, some data imports, etc. Bascially a bunch of
stuff that happens at the beginning of the month. However, there weren't
necessarily a lot of actual users on the system, just a select few.
One of the things that was happening was a user was using the web interface,
and sent off a huge horrible query. When it didn't come back in a reasonable
amount of time, he simply hit "Refresh" on the page, thereby submitting the
query again (thank you Sir, may I have another!). This was partly why the
database was so heavily loaded.
Now, we're puzzled by a couple of things. One, is the spike of actual
connections in the DB Pool up to 150. This makes no sense.
Second, is this error detailed above. I've tried some contrived
experiements, and I can not raise this specific exception myself. My
experiment was to issue a "update table set column = 1 where id = 1" in a
generic SQL browser, thus locking the row, and then issue the identical
command through a Session Bean call. It has happily sat there for up to 10
minutes (600 seconds, which is our default <JTA Name="inf4.2"
TimeoutSeconds="600"/> setting), and it eventually times out, but not with
the same exception. Rather I get "java.sql.SQLException: ORA-01013: user
requested cancel of current operation" from Weblogic, and
"weblogic.transaction.internal.TimedOutException:" from my client.
Apparently, according to the original exception, an XA Resource has not
responded within 120 seconds, but through my testing, that XA resource isn't
necessarily a SQL connection waiting on a query.
Could someone provide insight as to what resource the system may be waiting
on? For in theory, to me, that's what is consuming our DB Pool. I'm assuming
that whatever they're waiting on (the DB apparently), they're ALL waiting on
it, and the reason that the pool spikes is because the system can never find
a "valid" connection, thus trying again with a new one. Is that what it
happening?
Clearly we basically have a tuning issue, but in fact, I'm looking for a
stability solution. When this occurred, our system run 3 load balanced
"legs". The middle leg was having the problem. When we dropped it, leg 3
picked up and then IT had the problem. However, once we killed all 3 of them
and restarted, they recovered.
So I'm looking for some idea to keep Weblogic alive, even at the expense of
booting off these offending transactions, and not having to restart the
servers.
Perhaps over time the system would have recovered on its own (most probably
in fact), but if we can get things cut off early (as well as beating users
that hit Refresh constantly when things "stick"), we can prevent these from
escalating the effectively downing the whole site.
Any thoughts would be appreciated.
Regards,
Will Hartung
([email protected])

Will Hartung wrote:
Weblogic 8.1, I don't recall which service pack, sp10? Maybe?Well, we're only up to sp5 here, so we'll have to catch up ;)
Please try this:
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="45"
MaxCapacity="45" Name="OraclePool"
Password="*****"
Properties="user=******"
Targets="myserver" TestConnectionsOnCreate="true"
TestConnectionsOnRelease="false" TestConnectionsOnReserve="true"
KeepXAConnTillTxComplete="true"
TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="dbpool" Name="OracleSource"
PoolName="OraclePool" Targets="myserver"/>
You don't want the pool in flux at runtime, either shrinking or
growing. Just have it make what you need at startup and keep it.
Test-on-release is a waste of cycles. Also, I set keep-xa-con
till tx complete, to ensure that only one connection is ever
used for a given tx. XA allows connections to be changed at the
granularity of a single JDBC call, but that provides no real
benefit, and some overhead.
Let me know if this helps, and do let me know what real
service pack you're running.
thanks
Joe
Anyway, here's the relevant stack trace. We had a strange WLS implosion last
night that we're tracking down. We saw these when our code was trying to get
a connection out of the datapool.
<Mar 1, 2006 10:09:12 PM PST> <Warning> <JTA> <BEA-110030> <XA resource
[weblogic.jdbc.wrapper.JTSXAResourceImpl] has not responded in the last 120
second(s).>
01 Mar 2006 22:09:21,652 WARN com.pfizer.ecms.as.MetricsSession - logEvent:
exception: start() failed on resource
'weblogic.jdbc.wrapper.JTSXAResourceImpl': XAER_RMFAIL : Resource manager is
unavailable
javax.transaction.xa.XAException: Internal error: XAResource
'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
at
weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceD
escriptor.java:1019)
at
weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResour
ceDescriptor.java:572)
at
weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInf
o.java:1068)
at
weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceI
nfo.java:1001)
at
weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceIn
fo.java:203)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:419)
at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
:298)
at
com.pfizer.ecms.asutil.DataAccessManager.getConnection(DataAccessManager.jav
a:117)
Here's our configuration:
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
MaxCapacity="150" Name="OraclePool"
Password="*****"
Properties="user=******" ShrinkPeriodMinutes="5"
Targets="myserver" TestConnectionsOnCreate="true"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="dbpool" Name="OracleSource"
PoolName="OraclePool" Targets="myserver"/>
Looking this up, I was pointed to a JTA FAQ page on edocs, and it basically
said we should be Refreshing the connection pool, but the RefreshMinutes
parameter is deprecated, and as you can see we're testing connections as is.
We're puzzled by a couple of things, almost certainly application related,
but still relevant. We have 150 connections allocated to the pool, but even
at peak load during the day we bounce around the 40 mark. When we got the
above exception, we were hitting the 150 ceiling. We don't quite know why
yet.
During this time, our DB server was pretty heaviliy loaded. There were some
horrendous queries running, some data imports, etc. Bascially a bunch of
stuff that happens at the beginning of the month. However, there weren't
necessarily a lot of actual users on the system, just a select few.
One of the things that was happening was a user was using the web interface,
and sent off a huge horrible query. When it didn't come back in a reasonable
amount of time, he simply hit "Refresh" on the page, thereby submitting the
query again (thank you Sir, may I have another!). This was partly why the
database was so heavily loaded.
Now, we're puzzled by a couple of things. One, is the spike of actual
connections in the DB Pool up to 150. This makes no sense.
Second, is this error detailed above. I've tried some contrived
experiements, and I can not raise this specific exception myself. My
experiment was to issue a "update table set column = 1 where id = 1" in a
generic SQL browser, thus locking the row, and then issue the identical
command through a Session Bean call. It has happily sat there for up to 10
minutes (600 seconds, which is our default <JTA Name="inf4.2"
TimeoutSeconds="600"/> setting), and it eventually times out, but not with
the same exception. Rather I get "java.sql.SQLException: ORA-01013: user
requested cancel of current operation" from Weblogic, and
"weblogic.transaction.internal.TimedOutException:" from my client.
Apparently, according to the original exception, an XA Resource has not
responded within 120 seconds, but through my testing, that XA resource isn't
necessarily a SQL connection waiting on a query.
Could someone provide insight as to what resource the system may be waiting
on? For in theory, to me, that's what is consuming our DB Pool. I'm assuming
that whatever they're waiting on (the DB apparently), they're ALL waiting on
it, and the reason that the pool spikes is because the system can never find
a "valid" connection, thus trying again with a new one. Is that what it
happening?
Clearly we basically have a tuning issue, but in fact, I'm looking for a
stability solution. When this occurred, our system run 3 load balanced
"legs". The middle leg was having the problem. When we dropped it, leg 3
picked up and then IT had the problem. However, once we killed all 3 of them
and restarted, they recovered.
So I'm looking for some idea to keep Weblogic alive, even at the expense of
booting off these offending transactions, and not having to restart the
servers.
Perhaps over time the system would have recovered on its own (most probably
in fact), but if we can get things cut off early (as well as beating users
that hit Refresh constantly when things "stick"), we can prevent these from
escalating the effectively downing the whole site.
Any thoughts would be appreciated.
Regards,
Will Hartung
([email protected])

Java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'myDomain': XAER_RMFAIL : Resource manager is unavailable

Hi All,
I am facing below issue without any change in the config from weblogic
Managed servers are coming up and running without any issue
But when we are doing any operation from application then its failing
java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'myDomain': XAER_RMFAIL : Resource manager is unavailable
Regards
Lokesh

Hi,
Can you please try increase the below MaxXACallMillis setting in Weblogic set 'Maximum Duration of XA Calls' to a bigger value
MaxXACallMillis: Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain.
http://docs.oracle.com/cd/E12840_01/wls/docs103/jta/trxcon.html
The parameter is exposed through administration console: services --> jta --> advanced --> "Maximum Duration of XA Calls:"
Check the below docs for more information
WLS 10.3: Intermittent XA error: XAResource.XAER_RMERR (Doc ID 1118264.1)
Hope it Helps

RESOURCE MANAGER IN E-BUSINESS SUITE DATABASE

Hi All,
I have little problem with database resource manager in E-Business database.
I have set up some resource plan, assigned consumer group and user APPS to this consumer group (of course it is new initial consumer group for that user). At instance level I've set up RESOURCE_MANAGER_PLAN to new plan.
When I'm on console and use sqlplus, or from my workstation use SQLNavigator and connect as APPS - its resource_consumer_group column from v$session is set to desired new consumer group, but when I start application most of sessions connected as APPS are in DEFAULT_CONSUMER_GROUP - please advice, anyone has any ideas ???
Best Regards
Radek

EBS installs come with the database packaged with the install. You do not need a separate database install. Pl post EBS related issues in the EBS forums at http://forums.oracle.com/forums/category.jspa?categoryID=3
HTH
Srini

NI VXI Resource Manager keeps on saying locked up

Whenever I run resource manager, it keeps saying it locks up last time when it was running although it was not really locked up last time. Anybody knows how to fix this? Thanks.

I have some additional information and questions regarding this issue.
What version of NI-VISA and MAX do you have installed? There is
an issue with MAX 4 and Resman crashing when run outside of MAX.
A patch for this issue is on our website. However, I have never seen the issue this patch fixes not hang Resman. So my guess is that this is not what is happening in your case since you say it works for a month or so.
What happens when you run Resman twice in a row? Do you get the
hang message the second time? If you do, it's likely that you
have a registry permission problem. To detect lockups, Resman
writes a value to the registry when it starts, and deletes it just
before it exits. If the registry value is still present when
Resman starts, it says it detected a lockup. Thus if the key has
been created but not deleted due to registry permissions problems,
Resman will -always- say it locked up. Are you logged in as
Administrator? What permissions do you have on the computer?
Robert Mortensen
Software Engineer
National Instruments

USER PROFILE OR RESOURCE MANAGER

If we want to use Resource Manager to control the usage of system resources, and the DB users are already assigned profiles that limits the resource usage, so in this case which one (Resource Manager settings OR User Profile) will be used?

Use the APIs to check if the user is enabled or disabled?
As the disable event usually cascades there shouldn't be any issues with race conditions.
Best regards
/Martin

Resource Manager Unavailable

Hi,
When the transaction takes more than 2 mins .I get the following error message. I have Oracle thin Driver.
with 2 emulate turn on ( which is same as XA Driver).
Please Help
start() failed on resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl':
XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource
'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
at
weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:1019)
at
weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:572)
at
weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1068)
at
weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1001)
at
weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:203)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:298)
at
com.ml.mlim.lps.util.LPSConnection.makeConnection(LPSConnection.java:103)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManagerBean.makeConnection(PCCListManagerBean.java:1051)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManagerBean.getPartnerList(PCCListManagerBean.java:2633)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManager_7ylrjm_EOImpl.getPartnerList(PCCListManager_7ylrjm_EOImpl.java:2638)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManager_7ylrjm_EOImpl_WLSkel.invoke(Unknown Source)
at

I am experiencing the same issue and found this link... hope it helps.
http://tinyurl.com/drff7

Resource Manager problems

Hi All,
I've tried to create plan using :
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN');
Without specyfying groups, so i've got an error.
Next when i've tried to create plan again using :
execute DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN',CONSUMER_GROUP1 => 'SYS_GROUP', GROUP1_CPU => 100,
CONSUMER_GROUP2 => 'OTHER_GROUPS', GROUP2_CPU => 100);
I've got an error ora-29364 saying that :
'plan directive ESERVICE_RSRC_PLAN, SYS_GROUP already exists'
So when i've tried to delete directive using :
EXECUTE DBMS_RESOURCE_MANAGER.DELETE_PLAN_DIRECTIVE (plan => 'ESERVICE_RSRC_PLAN',group_or_subplan => 'SYS_GROUP');
I've got an error :
ORA-29358: resource plan ESERVICE_RSRC_PLAN does not exist
Appreciate for any help.
Best Regards Arkadiusz Masny

You have two issues,
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN will create a simple resource manager plan with new groups you have to use new group names for it to work.
The total CPU at each level must total 100, to use a simple plan the following will work..
execute DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN
(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN',
CONSUMER_GROUP1 => 'NEW_GROUP_1', GROUP1_CPU => 90,
CONSUMER_GROUP2 => 'NEW_GROUP_2', GROUP2_CPU => 10);
to use the existing group the follwoing SQL should work (NB I copied and pasted out of dbconsole, trying to manage this stuff using SQL is too much typing...)
BEGIN
dbms_resource_manager.clear_pending_area();
dbms_resource_manager.create_pending_area();
dbms_resource_manager.create_plan( 'ESERVICE_RSRC_PLAN', '');
dbms_resource_manager.create_plan_directive(
plan => 'ESERVICE_RSRC_PLAN2',
group_or_subplan => 'OTHER_GROUPS',
comment => '',
cpu_p1 => 10, cpu_p2 => NULL, cpu_p3 => NULL, cpu_p4 => NULL,
cpu_p5 => NULL, cpu_p6 => NULL, cpu_p7 => NULL, cpu_p8 => NULL,
parallel_degree_limit_p1 => NULL,
active_sess_pool_p1 => NULL,
queueing_p1 => NULL,
switch_group => '',
switch_time => NULL,
switch_estimate => false,
max_est_exec_time => NULL,
undo_pool => NULL,
max_idle_time => NULL,
max_idle_blocker_time => NULL,
switch_time_in_call => NULL
dbms_resource_manager.create_plan_directive(
plan => 'ESERVICE_RSRC_PLAN2',
group_or_subplan => 'SYS_GROUP',
comment => '',
cpu_p1 => 90, cpu_p2 => NULL, cpu_p3 => NULL, cpu_p4 => NULL,
cpu_p5 => NULL, cpu_p6 => NULL, cpu_p7 => NULL, cpu_p8 => NULL,
parallel_degree_limit_p1 => NULL,
active_sess_pool_p1 => NULL,
queueing_p1 => NULL,
switch_group => '',
switch_time => NULL,
switch_estimate => false,
max_est_exec_time => NULL,
undo_pool => NULL,
max_idle_time => NULL,
max_idle_blocker_time => NULL,
switch_time_in_call => NULL
dbms_resource_manager.submit_pending_area();
END;

Leopard Resources Management issue

Similar Messages

Maybe you are looking for