WLS Container Threads LOCKED
Apologize for this cross-post but I posted in in probably wrong group
Found several WLS Jrockit Threads LOCKED. We are using jrockit81sp2rp1_141_06
System got HUNG
All MUXERS are LOCKED show SocketResetException that seems funny ?
Thanks
Harish
[enablersthreaddump.txt]
Hi,
I'm also facing the same problem, but my server is WLI 8.1 SP2. When we restarted the server for couple of times, it started working fine. but why it is coming? also restarting production server is not a possible solution.
Any one has answers?
Thanks,
Chandra. T
Similar Messages
-
Thread lock in WL 8.1-on jRockit (queryMbeans)
I have noticed in our thread dumps of Weblogic 8.1 managed servers, the following lock:
"ExecuteThread: '2' for queue: 'weblogic.admin.RMI'" id=186 idx=0x182 tid=5292 prio=5 alive, in native, native_blocked, daemon
at jrockit/vm/Allocator.allocLargeArray(JIZ)Ljava/lang/Object;(Native Method)
at jrockit/vm/Allocator.allocArray(JIZ)Ljava/lang/Object;(Unknown Source)
at java/util/HashMap.resize(I)V(Unknown Source)
at java/util/HashMap.addEntry(ILjava/lang/Object;Ljava/lang/Object;I)V(Unknown Source)
at java/util/HashMap.put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at java/util/HashSet.add(Ljava/lang/Object;)Z(HashSet.java:192)
at com/sun/management/jmx/RepositorySupport.query(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(RepositorySupport.java:241)
at com/sun/management/jmx/MBeanServerImpl.queryMBeans(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanServerImpl.java:1042)
^-- Holding lock: weblogic/management/internal/RemoteMBeanServerImpl@0x2000000008e78fc0[fat lock]
at weblogic/management/internal/RemoteMBeanServerImpl.queryMBeans(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(RemoteMBeanServerImpl.java:911)
at com/sun/management/jmx/MBeanServerImpl.queryNames(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanServerImpl.java:1075)
at weblogic/management/internal/MBeanHomeImpl.mbeanServerQuery(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanHomeImpl.java:487)
at weblogic/management/internal/MBeanHomeImpl.getMBeansByClass(Ljava/lang/Class;Ljava/lang/String;)Ljava/util/Set;(MBeanHomeImpl.java:311)
at weblogic/management/internal/MBeanHomeImpl_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)
at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:492)
at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:435)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)
at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)
at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:430)
at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:35)
at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:183)
at jrockit/vm/RNI.c2java(JJJJ)V(Native Method)
-- end of trace
Then a big number of other threads are blocked by this lock. An example is:
"ExecuteThread: '1' for queue: 'HZOZMsgEjbExecuteThreadQueue'" id=17 idx=0x30 tid=5123 prio=5 alive, in native, blocked, daemon
-- Blocked trying to get lock: weblogic/management/internal/RemoteMBeanServerImpl@0x2000000008e78fc0[fat lock]
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at jrockit/vm/Locks.fatLockBlockOrSpin(JLjrockit/vm/ObjectMonitor;II)V(Unknown Source)
at jrockit/vm/Locks.lockFat(Ljava/lang/Object;JLjrockit/vm/ObjectMonitor;Z)Ljava/lang/Object;(Unknown Source)
at jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown Source)
at jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at com/sun/management/jmx/MBeanServerImpl.internal_addObject(Ljava/lang/Object;Ljavax/management/ObjectName;)V(MBeanServerImpl.java:2379)
at com/sun/management/jmx/MBeanServerImpl.registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(MBeanServerImpl.java:876)
at weblogic/management/internal/RemoteMBeanServerImpl.private_registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(RemoteMBeanServerImpl.java:614)
at weblogic/management/internal/RemoteMBeanServerImpl.registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(RemoteMBeanServerImpl.java:554)
at weblogic/management/runtime/RuntimeMBeanDelegate.register()V(RuntimeMBeanDelegate.java:166)
at weblogic/management/runtime/RuntimeMBeanDelegate.<init>(Ljava/lang/String;Lweblogic/management/runtime/RuntimeMBean;Z)V(RuntimeMBeanDelegate.java:122)
at weblogic/management/runtime/RuntimeMBeanDelegate.<init>(Ljava/lang/String;Lweblogic/management/runtime/RuntimeMBean;)V(RuntimeMBeanDelegate.java:85)
at weblogic/jms/frontend/FEConnection.<init>(Lweblogic/jms/frontend/FEConnectionFactory;Ljava/lang/String;Lweblogic/jms/common/JMSID;Lweblogic/jms/dispatcher/Dispatcher;IIJJJJLjava/lang/String;JZZIIIZZ)V(FEConnection.java:183)
at weblogic/jms/frontend/FEConnectionFactory$1.run()Ljava/lang/Object;(FEConnectionFactory.java:434)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)
at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)
at weblogic/jms/frontend/FEConnectionFactory.connectionCreateInternal(Lweblogic/jms/dispatcher/DispatcherWrapper;Z)Lweblogic/jms/client/JMSConnection;(FEConnectionFactory.java:430)
at weblogic/jms/frontend/FEConnectionFactory.connectionCreate(Lweblogic/jms/dispatcher/DispatcherWrapper;)Lweblogic/jms/client/JMSConnection;(FEConnectionFactory.java:371)
at weblogic/jms/client/JMSConnectionFactory.createConnectionInternal(Ljava/lang/String;Ljava/lang/String;Z)Lweblogic/jms/client/JMSConnection;(JMSConnectionFactory.java:148)
at weblogic/jms/client/JMSConnectionFactory.createQueueConnection()Ljavax/jms/QueueConnection;(JMSConnectionFactory.java:75)
at gr/cosmote/common/util/UtilLib.putObjToQueue(IILjava/io/Serializable;JLgr/cosmote/common/bus/LoginInfo;)V(UtilLib.java:664)
at gr/cosmote/common/util/UtilLib.putObjToQueue(IILjava/io/Serializable;Lgr/cosmote/common/bus/LoginInfo;)V(UtilLib.java:636)
at gr/cosmote/bus/session/HZOZQueueBean.handleMozartCallbackVO(Lgr/cosmote/common/bus/mozartVOs/MozartCallbackVO;)V(HZOZQueueBean.java:418)
at gr/cosmote/bus/session/HZOZQueueBean.onMessage(Ljavax/jms/Message;)V(HZOZQueueBean.java:191)
at weblogic/ejb20/internal/MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(MDListener.java:400)
at weblogic/ejb20/internal/MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(MDListener.java:333)
at weblogic/ejb20/internal/MDListener.onMessage(Ljavax/jms/Message;)V(MDListener.java:298)
at weblogic/jms/client/JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(JMSSession.java:2686)
at weblogic/jms/client/JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(JMSSession.java:2598)
at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:183)
at jrockit/vm/RNI.c2java(JJJJ)V(Native Method)
-- end of trace
What is this 'weblogic.admin.RMI' queue?
What I understand so far is that the object that appears as locked (RemoteMBeanServerImpl) is used to initiate and instantiate ejb/rmi calls from the managed servers. Does it attempt some sort of connection to the admin? Something else quite interesting that I read somewhere, that when this call (queryMBeans) is performed, the result is handled by a non thread-safe collection object which could (as a result of a weblogic bug) result in an infinite loop.
By the way, our set up is 1 cluster, 4 managed servers in 4 different machines. The admin is installed along with one of the managed. All servers are configured to start/stop/run independently.
Anybody any ideas?hi,
What is this 'weblogic.admin.RMI' queue has the threads executing the calls from remote managed servers to the Admin Server and from the Admin Server to the managed servers for internal status updates.
There was a bug in wls 8.1 where the call the to the admin server from all the managed server in the cluster used to create a thread lock state.
Contact the Oracle support for the related CR and the patch.
thanks,
Sandeep -
I'm trying to get a good handle on the reason there are restrictions on threading/locking
semantics used from within application code dealing with EJBs. I think the idea
is the application code shouldn't do anything to interfere with the locking of
the ejbs done from within the container at various stages in their lifecycle.
So, I shouldn't subject the bean implemenation class to any explicit synch. But
what about spawning threads from within my EJBs? In 3rd party classes used by
my EJBs?
Any clear explanation is gratefully appreciated.
MaxMax
See section 24.1.2 "Programming restrictions" in the ejb20 final release specification.
Thanks
Jim
Max wrote:
I'm trying to get a good handle on the reason there are restrictions on threading/locking
semantics used from within application code dealing with EJBs. I think the idea
is the application code shouldn't do anything to interfere with the locking of
the ejbs done from within the container at various stages in their lifecycle.
So, I shouldn't subject the bean implemenation class to any explicit synch. But
what about spawning threads from within my EJBs? In 3rd party classes used by
my EJBs?
Any clear explanation is gratefully appreciated.
Max[Reply.vcf] -
I have an iMac purchased in May 2011. OSX Lion 10.7.3. I deleted backup file from the external hard drive which operates from Time Machine.
Now, the trash can will not empty some of the files deleted from the backup harddrive.
The trash contains-- File folder: "Core Services" which contains a locked file: "boot.efi".
It will not delete.
How do I get the trash can empty of these files?Yes, the Old Master file has a folder for each year where I find all photos from that specific year. I am attaching a screen shot of the file.
In the meantime i have managed to download all photos (it did not download any video files though in mpg, avi, 3gp, m4v,mp4 and mov format) to a new iphoto library. Unfortunately the photos are quite mixed and often doubled up. I ma considering to purchase iphoto library which checks all duplicates in iphoto. this will save me a lot of time. What do you think? -
Hello Guru's,
we have a unusual problem in the syslog of our ERP System.
Enqueue: Elem.lock 0 contains unpermitted lock mode . lock object EZBEV_BO
We can't found any note or forum entry to solve this.
We checked SAP Notes: 1324099, 891372, 606425, 447242, 1260601 and searched in the forum, but nothing helpful found.
System Data:
ERP 6.0 / NW7.01 with EHP4
SAP Kernel : 701_REL
created on : Jan 18 2010 21:47:07
Kernel Patch number : 77
Source ID : 0.077
DBSL Patch No. : 075
Database
ORACLE 10.2.0.2
Operating System
AIX 5.3
Can someone help?
regards
Chrisdeveloper error
-
Enqueue: Elem.lock 0 contains unpermitted lock mode /. lock object
Hello All,
SCM 5.0 system which is upgraded from 4.1:
System log entries contains:
<b>Enqueue: Elem.lock 0 contains unpermitted lock mode /. lock object /sapapo/E</b>
Work process log file contains :
LOG GE8===>0 /sapapo/E_MATLOC
I have gone through few notes like 606425, 447242.( lower version)
From which I came to the conclusion that it is program error.
Also group GE and No:8 What does it mean?
Please let me know your thoughts.Thanks.
Regards,
Tushar
Message was edited by:
Tushar Chavan
Message was edited by:
Tushar ChavanHi,
I found one more note :
Note 891372 - Lock entries for TemSe obj remain after completion of proc
The issue looks pretty similar. I think the notes you found are better suited for sap apo.
Log a call with SAP and check what they have to say.
Regards,
Siddhesh -
Hi All,
Many times while working on MDM via MDM API's I received Thread Locking Exception. This Exception is so severe that it leads MDM Data Manager in hanged state and get resolved only by restarting the server. Sometimes I do not get this exception but Data Manager gets hanged, even I am unable to open Console also. Please answer this question.
Thanks ..
VibhaHello All,
Still we haven't able to resolve this issue. We already have SR with oracle. So many logs were captured.
Below is the snippet of seedSchedulerdata.log
${work.dir}Entered Validate methodExiting Validate method------------------------------------------------------------
Start seeding task
job name--> Password Expiration Task
schTaskName--> Password Expiration Task
task class name--> com.thortech.xl.schedule.tasks.tcTskPasswordExpiration
task job disable--> 0
task frequency--> DAILY
task maxRetries--> 5
task retryCount--> 0
task paramName--> Email Definition Name
task paramValue--> Password Expired
task paramTpe--> String
Updating Job :Password Expiration Task with keys
java.lang.Exception: Unable to seed scheduler data due to configuration problems. Contact System Administrator
at oracle.iam.scheduler.seed.SeedSchedulerData.startSeeding(SeedSchedulerData.java:770)
at oracle.iam.scheduler.seed.SeedSchedulerData.main(SeedSchedulerData.java:113)
If any of them faced such issue please help.
Thanks
DK -
Dear Moderator,
I wanted to know the answers of some questions which were asked to me during interview. So I posted those questions in the Forum on 1st December. But today when I logged in to check the answers, I found the thread locked. Can you please let me know on what basis a thread is locked.
Regards,
D. Mallick
Moved from Test and Playground forum.
Edited by: kishan P on Dec 3, 2010 11:22 PMI can remember moving one of them which several forum members where complaining about (understandably).
I mean... I can imagine encountering a thread called "questions" even although it is a meaninglessly stupid subject title, but what are we to find usefull in answers ??
Get some fresh air over the weekend. You have some reading to do next week.
Cheers,
Julius -
Using JCo as an RFCServer in a J2EE Container (Threading Issue)
Hello,
I want to use JCo as an RFCServer in a J2EE Container
(e.g. JBoss, BEA WLS or WAS6.40).
Threrefore I use a the JCo.Server class
as shown in Example5 in the JCo Examples.
But the JCo.Server class starts a thread (JCo.ServerThread) for each Server(Listener).
According to the J2EE specs it is not allowed
to start (user) threads in a J2EE Container,
because the container does the whole thread
manangement/lifecycle.
If JCo creates threads on its own, this might
lead to erros. For Example: BEA WLS stores
information in ThreadLocal variables and if you
call a SessionBean from the JCoServer.handleRequest method
the Container will (perhaps) fail, because the
thread created by JCo does not have the ThreadLocals
needed by the container.
I know that there is the IServerThread interface in JCo,
but I don't know how to use it in a J2EE Container.
What is the correct way to implement a JCo Server
in a J2EE container?
Does anyone know a working solution of a JCo Server
in the BEA Application Server?
Thanks,
JoachimJoachim,
As you wrote, it may not be a good idea to use JCO.Server's inside a J2EE container; i suggest you to build an 'adapter' for this purpose.
An adapter is a program that can listen for any type of event and, once the event has been identified (type and specific data), the adapter will handle it accordingly.
In this case, you can create a program that starts a JCO.Server (as in Example5) and use JMS to send messages (built from the info gathered from the JCO.Function call) to a Message Driven Bean in the J2EE container.
Hope this helps.
RaTB -
We are noticing performance issue with our production environment. Production environment has a cluster of 6 weblogic instances and the server hangs very often and entire system go down. I have attached thread dump collected from one of the weblogic server. Any idea where is the issue? can you help please.
"ExecuteThread: '19' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x04f92f38 nid=0xb8c runnable [0x0713e000..0x0713fd94]
at java.lang.Throwable.fillInStackTrace(Native Method)
- waiting to lock <0x164ec610> (a java.lang.ClassNotFoundException)
at java.lang.Throwable.<init>(Throwable.java:217)
at java.lang.Exception.<init>(Exception.java:59)
at java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:65)
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
- locked <0x173b3428> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
- locked <0x173b3428> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x173c1900> (a weblogic.utils.classloaders.GenericClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x17387ed8> (a weblogic.utils.classloaders.GenericClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x17dc9028> (a weblogic.utils.classloaders.GenericClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
- locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
- locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerMethod(BaseDeserializerFactory.java:201)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getGetDeserializer(BaseDeserializerFactory.java:289)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:171)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:115)
at org.apache.axis.encoding.ser.SimpleDeserializerFactory.getDeserializerAs(SimpleDeserializerFactory.java:107)
at org.apache.axis.encoding.DeserializationContextImpl.getDeserializer(DeserializationContextImpl.java:452)
at org.apache.axis.encoding.DeserializationContextImpl.getDeserializerForType(DeserializationContextImpl.java:467)
at org.apache.axis.message.MessageElement.getValueAsType(MessageElement.java:571)
at com.axeda.sdk.webservices.handlers.LoginHandler.findLogin(LoginHandler.java:153)
at com.axeda.sdk.webservices.handlers.LoginHandler.handleRequest(LoginHandler.java:99)
at com.axeda.sdk.webservices.handlers.LoginHandler.invoke(LoginHandler.java:78)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:287)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)Try setting the 'Inactive connection timeout' value on the jdbc data source. Looks like your data source hangs. Also would be a good idea to set the 'test connections on reserve' on with test table sql.
-
"Remember me" not working - Thread locked, no answer???
I'm having an issue where the remember me button on the wiki doesn't seem to have ANY effect on users. I would have replied to this thread, but isn't been locked with no resolution.
http://discussions.apple.com/thread.jspa?threadID=2369660&tstart=150Not nice,
Dear Apple just by ignoring the bug it doesn't go away ! Don't be evil ..
So please open the thread again dear Admins -
"new intel imac 7.2 where have my plugins gone!!!! argh"
seemed like a reasonable one to me, though the last post said something like "internal logic AUs are good, but I can't use them" which isn't correct. First, Logic's plugins aren't AU, second, the Logic plugins in 7.2 should be Universal, third, all the AU's which come with OS X on Intel should be Universal Binaries. I wonder what he was referring to?
The locked thread also discussed performance comparisons between Logic on the Intel iMac and PowerPC systems. Another reasonable topic of interest here.
Uh-oh... I hope I haven't crossed the line...I don't think it's so bad that the old thread was locked, since an answer to the original question had been established and the thread was accumulating misinformation and complaints. But I'll take advantage of this thread to (1) clarify a comment I made on the old thread and (2) ask a closely related question.
(1) First the clarification: someone pointed out that AUs and VSTs need to be universal binaries to run inside a UB host. In response, I wrote "I don't know about VSTs", but I only wrote that because I was focusing on Logic (which doesn't run VSTs at all, of course). I didn't mean to call into question whether a UB host could run non-UB VSTs; I expect one couldn't.
(2) Now the question: I understand that (ignoring the Rosetta option) an Intel Mac running Logic 7.2 can't host AU plug-ins unless those plug-ins are Universal Binaries. That makes sense to me. But what about Logic 7.2 running on the older G4/G5 architecture? Am I right to assume that Logic 7.2 running on a G5 (not an intel Mac) can host the same non-UB AUs as Logic 7.1?
Dual G5 2.0GHz Mac OS X (10.4.2) -
Why was "Mail not remembering passwords" thread locked out?
The problem wasn't resolved, yet the thread has been locked out! Does Apple monitor this board? If so, could someone from Apple at least acknowledge that there is a Mail-related problem and that someone is looking into it? The problem wasn't resolved with the latest Leopard release and even a cursory reading through the aforementioned thread reveals a lot of very frustrated users!
I had the same problem every once in a while with Tiger and now with Leopard. Sometimes, it works properly, i.e. remembering the passord. Sometimes, I am asked for my password repeatedly whether I check the "save" box. I have two different e-mail providers (gmail.com and gmx.net). I only get the troubles with the second one from time to time over a period of time.
I could "fix" it with the following workaround:
Mail > Preferences > General > Check for new mail: every 5 minutes.
Before, I had had set it to "check every 1 minute" what often resulted in the "loss" of the password. -
I'm just wondering if someone can tell me why the thread at "http://discussions.apple.com/thread.jspa?threadID=564703&tstart=0" has been locked?
Apple has taken my computer for repair, so I was intending to provide an update (a positive one, I hope) once I receive it back; I can't do that now.
ThanksThanks for your reply.
I was hoping my experience would help other people decide whether or not to ask for a fix. If the noise doesn't bother you, then why would you want to have random parts of your otherwise working computer replaced? But it bothered me, so I was willing to take the risk.
I note that another thread discussing problematic macbooks (http://discussions.apple.com/thread.jspa?threadID=567126&tstart=0) has been locked.
I was hoping to hear something from whoever locked it... -
Synchronized methods and thread locking
Hi can someone please explain the difference between these two examples in the context of object locking
public void method1(){
synchronized(this){
}And
StringBuffer aStringBufferObject = new StringBuffer("A");
public void method2(){
synchronized(aStringBufferObject){
}I know the first example will obtain a lock on the this instance and the second will obtain a lock of the aStringBufferObject instance. But i dont really understand what the effect or the difference of teh two is.
For example, in the second example, will threads still be able to execute the code inside the synchronized block because the lock is not related to the 'this' instance?
I know that synchronizing a method or a block of code prevents multiple threads to access that block/method at the same time but what is the purpose of specifying the object to lock on and what is the difference in the way the object is specified as in teh above examples.
Thanks
Edited by: ziggy on Jul 24, 2011 3:23 PMShortly put, the synchronized(object) doesn't lock the object reference in any way. It locks the code inside the synchronized's brackets, so that code can run it only when they have locked object (or in truth, when they have acquired object's monitor).
Since only one thread at a time can lock an object (obtain an object's monitor), this means that 2 threads executing blocks that synchronize on the same object can't run at the same time, ensuring thread safety (among other things).
Maybe you are looking for
-
Itunes 7....error (-200)?
Itunes will not come up and I keep getting this error. I have tried uninstalling/reinstalling to no avail. Thx
-
Oracle Application Server Control Console doesn't show any servers
Hi there. I'm configuring the Identity Manager, and in the process of doing so, I've to user tthe OASCC to do some operations. I've discovered how to launch the OASCC and I can access it. The problem is that after configuring the ias_admin password t
-
hello, i am trying to burn a dvd from idvd using professional encoding. twice at the end of burning (4 hours later) i get a message saying there has been an error during building (multiplexing?) i burned the same idvd project using high encoding and
-
Will the IMEI no. of Iphone 4 will change if board is changed? Also is there a check in Iphone that it has original Logic board installed on it.
-
Message type corresponding Functional area
Hi All, How can i get a Message type corresponding functional area? For example : MATMAS---- MM I have 900 message types i need Funational areas of all these Message type.Please let me know if we have any table or functional module to completes this