Javax.naming.event package supported in weblogic?
Hi,
Is JNDI event notification (i.e., javax.naming.event) supported in
weblogic's JNDI implementation?
I am 99% sure it isn't.
WLInitialContext and WLContext need to implement the EventContext interface
in order for it to work. In my case ( and I'm sure yours also ) I get a
ClassCastException when trying to cast a WLContext to an EventContext. This
says to me that no, the event package isn't supported.
I would appreciate confirmation from Weblogic on this though.
Grand Poobah wrote in message <[email protected]>...
Hi,
Is JNDI event notification (i.e., javax.naming.event) supported in
weblogic's JNDI implementation?
Thanks,
Robert
Similar Messages
-
Javax.naming.event package
Hi,
Is JNDI event notification (i.e., javax.naming.event) supported in
weblogic's JNDI implementation?
Thanks,
RobertI am 99% sure it isn't.
WLInitialContext and WLContext need to implement the EventContext interface
in order for it to work. In my case ( and I'm sure yours also ) I get a
ClassCastException when trying to cast a WLContext to an EventContext. This
says to me that no, the event package isn't supported.
I would appreciate confirmation from Weblogic on this though.
Grand Poobah wrote in message <[email protected]>...
Hi,
Is JNDI event notification (i.e., javax.naming.event) supported in
weblogic's JNDI implementation?
Thanks,
Robert -
Can you use CORBA Naming Service with javax.naming.event.EventContext?
Can you use CORBA Naming Service with javax.naming.event.EventContext?
It seems like it doesn't work. When I try to do something like
EventContext eCtx_ = (EventContext)namingCtx_.lookup("");
I'm using JacORB's naming service.
I just want to clarify that I cannot or can use javax.naming.event.EventContext with CORBA Naming Service.Can anyone tell me if it is doable or not doable.
I looked at the COSNaming SPI, and it seems like it doesn't implement javax.naming.event.EventContext.
Am I correct or not? -
We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
With this i am attaching the code snippet:
JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));
Thread.currentThread().setContextClassLoader(customLoader);
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
Kindly provide the necessary solutions to overcome this.I guess you did something wrong implementing your classloader(s).
This works with 7.0:
ClassLoader weblogicClassLoader;
Thread.currentThread().setContextClassLoader(
weblogicClassLoader = new URLClassLoader(
new URL[] { new URL("http://localhost:7001/classes/") }
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
env.put("java.naming.provider.url", "t3://localhost:7001");
InitialContext ctx = new InitialContext(env);
You may also look at these examples:
http://dima.dhs.org/misc/ThinClient.jsp
http://dima.dhs.org/misc/ThinClient2.jsp
B.Ravikumar <[email protected]> wrote:
We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
With this i am attaching the code snippet:
JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));
Thread.currentThread().setContextClassLoader(customLoader);
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
Kindly provide the necessary solutions to overcome this.--
Dimitri -
Does Weblogic Jndi support naming.event
Hi gurus,
our app needs to be notified in case an object (already bound) has changed. or rebound into the jndi tree..
i tried using javax.naming.event.*
and the call to
EventContext = (EventContext)(new InitialContext(env)).lookup("");
gives me a ClassCastException...
java.lang.ClassCastException: weblogic.jndi.toolkit.WLContextStub
Any pointers..
I plan to use NamespaceChangeListener and ObjectChangeListener to get notified. didnt find any material in weblogic docs...
thanks in Advance
NageshAs I know, WL does not implement directory events machinery. You should use
another mechanism to notify your app about JNDI changes. For example, you
can use any LDAP directory service to bind your objects to. In this case,
directory events should work.
kesha
"Nagesh" <[email protected]> wrote in message
news:39edfc4d$[email protected]..
>
Hi gurus,
our app needs to be notified in case an object (already bound) haschanged. or rebound into the jndi tree..
i tried using javax.naming.event.*
and the call to
EventContext = (EventContext)(new InitialContext(env)).lookup("");
gives me a ClassCastException...
java.lang.ClassCastException: weblogic.jndi.toolkit.WLContextStub
Any pointers..
I plan to use NamespaceChangeListener and ObjectChangeListener to getnotified. didnt find any material in weblogic docs...
thanks in Advance
Nagesh -
Javax.naming.NoInitialContextException: Cannot instantiate
IHi,
Iam trying to run my first application on WEBLOGIC SERVER 8.1. I have already deploed class file on server.i have already set path for my client jar .
When I use my client run on JDK to access the application.
I got following errror::::
Naming Error: catch block of getInitalContext()
javax.naming.NoInitialContextException: Cannot instantiate
class: weblogic.jndi.WLInitialContextFactory [Root exception is
java.lang.ClassNotFoundException:
weblogic.jndi.WLInitialContextFactory]
from catch block of jMenuItem1
error from NamingException.getMessage()is: Cannot instantiate
class: weblogic.jndi.WLInitialContextFactory
HERE IS THE CODE FOR CLIENT:
import java.awt.event.*;
import javax.rmi.*;
import java.rmi.*;
import javax.swing.event.*;
import javax.swing.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import java.util.Hashtable;
import java.util.Properties;
import javax.ejb.CreateException;
import org.omg.CosNaming.*;
import java.util.Hashtable;
import weblogic.jndi.*;
//import javax.weblogic.jndi.WLInitialContext;
public class Client {
public static void main(String[] args){
Context context= null;
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL,"t3://localhost:7001");
try{
context = new InitialContext(h);
Object obj = context.lookup("ServerObject"); //Server ejb-name
System.out.println(obj.getClass());
ServerHome serverhome =(ServerHome) javax.rmi.PortableRemoteObject.narrow(context.lookup("ServerObject"),ServerHome.class);
Server server = serverhome.create();
String Message = JOptionPane.showInputDialog("Enter Your Message");
JOptionPane.showMessageDialog(null, server.performAction(Message) );
catch(Exception e){
JOptionPane.showMessageDialog(null ,"Exception is " +e);
code for bean:::::::
//package EJBExample;
import javax.ejb.*;
import java.rmi.*;
import javax.swing.*;
public class ServerBean implements SessionBean
private SessionContext stx;
//In following five methods create is by contract others to be implemented by Container
public void ejbCreate(){}
public void ejbRemove(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void setSessionContext(SessionContext ctx)hi
Am facing the problem whenever i run the client jsp definitly run the first time but next time i get the particular error please let me clear about this error i m attaching the client code and also error screen..
client jsp
<%UserInfoSB objUserInfoSB;
System.out.println("########## 2 #########");
Properties props= System.getProperties();
System.out.println("########## 3 #########");
Context ctx = new InitialContext(props);
System.out.println("########## 4 #########");
props.put(Context.INITIAL_CONTEXT_FACTORY, "Weblogic.jndi.WlInitialContextFactory");
props.put(Context.PROVIDER_URL,"t3://localhost:7001");
System.out.println("########## 5 #########");
UserInfoSBHome objUserInfoSBHome =(UserInfoSBHome) ctx.lookup("UserInfoSBHome");
System.out.println("########## 6 #########");
objUserInfoSB = objUserInfoSBHome.create();
System.out.println("########## 7 #########");
//objUserInfoSB.processInterfaceUserHistoryDetails(objUserDetailVO);
ArrayList alResult = objUserInfoSB.processInterfaceGetAllUserDetail();
objUserInfoSB.remove();
System.out.println("########## 8 #########");
%>
It is error which i am facing plz let me clear
NoInitialContextException: Cannot instantiate class: Weblogic.jndi.WlInitialContextFactory. Root exception is java.lang.ClassNotFoundException: Weblogic.jndi.WlInitialContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:186)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:62)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.(InitialContext.java:195)
at jsp_servlet._jsp._epfindia._mydata.__userdisplayall._jspService(__userdisplayall.java:374)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) -
Javax.naming.NoInitialContextException! Urgent help needed
Hi All
I'm using Oracle Application Server(OC4J) for J2EE. i created an application of Stateless Session Bean & tested on j2sdkee1.3.1, & it is working fine on it. Same Application (an .ear file) i deployed on OC4J. But it is giving an error NoInitialContextException, lookup fails here.
Application contains method getEchoString(String):String & a index.jsp page calling a bean's method.
Can anybody tell me the solution to get handle of beans home interface for calling method.
Already i've wasted many days for this. Plz help. It's urgent
Thanks in AdvanceTo the best of my knowledge, the 'javax.naming.ldap' package is fairly new, and is only included in the most recent distributions of the JNDI API. I know that this package is included with J2SDK 1.3, and I can also confirm that the very latest JNDI distribution (from http://java.sun.com/products/jndi/#download) contains the package.
Good luck,
-Derek -
Javax.naming.ContextNotEmptyException
when we shutdown primary session state server..the second server in the cluster
got error messages.....
####<Jun 8, 2001 9:07:18 PM CST> <Info> <Adapter> <MTSMC8> <m8> <ExecuteThread:
'11' for queue: 'default'> <system> <> <000000> <Exception thrown by rmi server(class
weblogic.jndi.internal.RootNamingNode) [-6739358373872621029S:10.42.37.17:[7001,7001,7002,7002,7001,7002,-1]:prod/9]:
weblogic.jndi.internal.RootNamingNode@1fa12f>
javax.naming.ContextNotEmptyException; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.destroySubnodeHere(BasicNamingNode.java:658)
at weblogic.jndi.internal.ServerNamingNode.destroySubnodeHere(ServerNamingNode.java:180)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:620)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.BasicNamingNode.destroySubcontext(BasicNamingNode.java:632)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNamingNode_WLSkel.java:323)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:115)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:88)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
at weblogic.jndi.internal.ServerNamingNode_WLStub.destroySubcontext(ServerNamingNode_WLStub.java:469)
at weblogic.jndi.internal.WLContextImpl.destroySubcontext(WLContextImpl.java:109)
at weblogic.cluster.BasicServiceOffer.retract(BasicServiceOffer.java:93)
at weblogic.cluster.NodeInfo.retract(NodeInfo.java:147)
at weblogic.cluster.TreeManager.retract(TreeManager.java:70)
at weblogic.cluster.MemberServices.retractAllOffers(MemberServices.java:38)
at weblogic.cluster.RemoteMemberInfo.shutdown(RemoteMemberInfo.java:117)
at weblogic.cluster.MemberManager.peerGone(MemberManager.java:200)
at weblogic.rjvm.RJVMImpl$PeerGoneDeliverer.execute(RJVMImpl.java:960)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
There is no way to rename a non-leaf entry in either iPlanet DS or Netscape DS.
-
Javax.naming.NoInitialContextException: Cannot instantiate class:
I have written a client for my statleless ejb bean.The bea is deployed on weblogic server.when i am trying to access the bean through client with code
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:8001");
InitialContext ic = new InitialContext(env);
following Exception is being thrown at runtime
E:\EJBTest>java example.Client
Exception in thread "main" javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitial
ContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at example.Client.main(Client.java:23)
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)
... 5 more
the Same program was woking fine earlier ..
Unable to locate the problemCan anyone help on this ..
Thanks in advance.. -
Class javax.naming.InitialContext not find import
how should I set the classpath environment?
Where to find javax.naming.InitialContext package?
thanks for you helpYou should set the classpath environment to include wherever your javax.naming package is. If you're using Java 1.3 or later, javax.naming should be in the classpath already.
-
Javax.naming.NameNotFoundException using Spring with EJB3 and Weblogic 10
I'm deploying an EAR application from Weblogic 10 Administration Console... This
EAR has two modules: an EJB3 module, and a Web module. The deploy process finish,
but the status of the application is "Failed"... then in the log I get the
following error:
User defined listener
org.springframework.web.context.ContextLoaderListener failed:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'gruposUnidadesServiceFacade' defined in class path resource
[http://applicationContext.xml]: Invocation of init method failed; nested exception is
javax.naming.NameNotFoundException: Unable to resolve
'GruposUnidadesService'. Resolved ''; remaining name 'GruposUnidadesService'.
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'gruposUnidadesServiceFacade' defined in class path resource
[http://applicationContext.xml]: Invocation of init method failed; nested exception is
javax.naming.NameNotFoundException: Unable to resolve 'GruposUnidadesService'. Resolved
''; remaining name 'GruposUnidadesService' at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:394)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source) at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.naming.NameNotFoundException: Unable to resolve 'GruposUnidadesService'. Resolved
''; remaining name 'GruposUnidadesService' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380) at
javax.naming.InitialContext.lookup(InitialContext.java:392) at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:132)
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:88) at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:130) at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:155) at
org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:93)
at
org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
at org.springframework.ejb.access.AbstractRemoteSlsbInvokerInterceptor.lookup(AbstractRemoteSlsbInvokerInterceptor.java:97)
at
org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:105)
at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:92)
at
org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.afterPropertiesSet(SimpleRemoteStatelessSessionProxyFactoryBean.java:99)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method) at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:394)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source) at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
This my EJB3 bean code:
@Stateless(name="GruposUnidadesService",
mappedName="GruposUnidadesService")
public
class GruposUnidadesServiceBean implements GruposUnidadesService,
GruposUnidadesServiceLocal {
In the mappedName I have tried different ways like: "ejb/GruposUnidadesService"
but I always get the same exception.
This is my weblogic-ejb-jar.xml
<?xml version = '1.0' encoding =
'windows-1252'?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA
Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>GruposUnidadesService</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
In the web module, I have Spring with MyFaces, in my applicationContext.xml
I have:
<?xml version="1.0"
encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD
BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<bean id="gruposUnidadesServiceFacade" class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean">
<property name="jndiName"
value="GruposUnidadesService"/>
<property name="businessInterface" value="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacade"/>
</bean>
<bean
id="gruposUnidadesServiceFacadeBean" class="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacadeBean">
<property name="gruposUnidadesServiceFacade"
ref="gruposUnidadesServiceFacade"/>
</bean>
</beans>
Here, I have tried adding the resourceRef property set
to true and to false and always I get the exception.
Finally, in my web.xml I have:
<ejb-ref>
<ejb-ref-name>GruposUnidadesService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>penoles.infraestructura.business.services.gruposunidades.GruposUnidadesService</remote>
</ejb-ref>
And in my weblogic.xml:
<?xml version = '1.0' encoding =
'windows-1252'?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA
Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>GruposUnidadesService</ejb-ref-name>
<jndi-name>ejb/GruposUnidadesService</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
My environment is: Weblogic 10.3.0.0 on Linux Redhat 4
thnks
Edited by: user501097 on 08-oct-2008 8:29Well I Think it was a beginner mistake…
I added to the following to my web.xml
<ejb-ref>
<ejb-ref-name>SeguridadService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>penoles.infraestructura.business.services.seguridad.SeguridadService</remote>
<ejb-link>SeguridadService</ejb-link>
</ejb-ref>
And change the applicationContext.xml
<bean id="gruposUnidadesServiceFacade" class = "org.springframework.jndi.JndiObjectFactoryBean">
<property name="resourceRef" value="true"/>
<property name="proxyInterface" value="penoles.infraestructura.web.servicesfacades.gruposunidades.GruposUnidadesServiceFacade"/>
<property name = "jndiName" value = "GruposUnidadesService"/>
</bean>
thnks! -
JNDI lookup from OC4J to weblogic throws javax.naming.NameNotFoundException
Hi All,
We have the below setup in our production environment.
EJB application is deployed in the Weblogic 10.3.4.0 Server on Sun Solaris. The EJB version is 3.0
OC4J 10.2.0 is running on another Sun Solaris machine.
There are 2 webservice applications WEBSERV1 & TestSoapEJB running on this OC4J container.
We need to do lookup the EJBs deployed on the Weblogic server. For this we used the below logic in the web service's Stateless session bean:
String weblogicURL = "";
Properties props = new Properties();
try
props.load(Thread.currentThread().getContextClassLoader().getResourceAsStream("wl.properties"));
weblogicURL = props.getProperty("weblogicURL");
catch (FileNotFoundException e)
e.printStackTrace();
catch (IOException e)
e.printStackTrace();
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(Context.SECURITY_PRINCIPAL,"weblogic");
ht.put(Context.SECURITY_CREDENTIALS,"weblogic654");
ht.put(Context.PROVIDER_URL, weblogicURL);
ctx = NamingManager.getInitialContext(ht) ;
// tried using //ctx = new InitialContext(ht); same behavior.
TestEJB.AdministratorEJB ejb = (TestEJB.AdministratorEJB) ctx.lookup("TestEJB#TestEJB.AdministratorEJB");
ctx.close();
When we first test first WEBSER1, the lookup is fine.
But when we test the second webservice WEBSER2, the webservice name itself not able to lookup: It gives the below error:
javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB
Below is the stack throws thrown on browser:
500 Internal Server Error
javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB
at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)
at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:64)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.j2ee.ws.SessionBeanRpcWebService.init(SessionBeanRpcWebService.java:65)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.loadServlet(HttpApplication.java:2354)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.findServlet(HttpApplication.java:4795)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:680)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:662)
It seems that, the OC4J is looking in Weblogic context. But it should be looking in its own context. How to resolve this issue.
The same case happens if i restart the OC4J and first test the TestSoapEJB the lookup is fine . But if i test the WEBSERV1 , it throws the same error as above. In short, if one of the webservices lookup is working fine, the other webservice is not working. At the same time only one webservice's lookup is working.
Kindly help me to resolve this issue.
regards,
Zia
Edited by: PT Expert on Sep 9, 2012 3:16 AMI work now more that two days on this error!!!
-> I remade my complete jdev project, it did not work!
-> I deleted the jdev/system/j2ee/oc4j/workspace dir
-> I search for some .lock files
-> and many more tries!!! But without success...
Is there a way to reset the Embedded OC4J? -
We have started getting the above error message in a system that has worked happily
for the past 6 months or so (and continues to work happily from our disaster recovery
environment). I should probably add that this occurs when we are attempting to
write to the database via the connection pool.
Anyone have any ideas?
Thanks
Andrew
The full stack trace is
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication for user system denied in realm weblogic
<<no stack trace available>>
31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
thrown by rmi server(class com.esure.ibis.a
ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
[265127279722
6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
prdwls/296]: [BaseEJBObject]
home: com.esure.ibis.accesslaye
r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
Bean::validateUser()
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)We have started getting the above error message in a system that has worked happily
for the past 6 months or so (and continues to work happily from our disaster recovery
environment). I should probably add that this occurs when we are attempting to
write to the database via the connection pool.
Anyone have any ideas?
Thanks
Andrew
The full stack trace is
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication for user system denied in realm weblogic
<<no stack trace available>>
31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
thrown by rmi server(class com.esure.ibis.a
ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
[265127279722
6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
prdwls/296]: [BaseEJBObject]
home: com.esure.ibis.accesslaye
r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
Bean::validateUser()
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
Hi,
I am not able to resolve the JNDI name - ATGProductionDS
I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
/atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
/Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
onfig\data\config
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource Failed to resolve ATGProduct
ionDS javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource at weblogic.jndi.int
ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource at weblogic.jndi.int
Entries from Weblogic console -datasources
ATGBatchDS
Generic
ATGBatchDS
ATGProductionDS
Generic
ATGProductionDS
atg_production_lockserver, atg_publishing_lockserver
ATGPublishingDS
Generic
ATGPublishingDS
atg_publishing_lockserver
Please provide assistance.Hi,
if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files? -
Javax.naming package in j2se but not j2ee
Hello,
From on the documentation I see so far the javax.naming package exists in the J2SE. Unfortunately I d/l and installed J2EE. Shoudln't J2EE be a superset of j2se? Or the the packages just renamed to something else in it?Yes j2ee is a superset to jj2se. j2se contains all the standard packages that you need for writing java apps.
Maybe you are looking for
-
Paid Folios in-app purchase. How long to approve?
Please, I would like to know about the experience that other users when submit folios to sell by in-app purchase. How apple needs approve these follios before upload to app store. Usually how long Apple get to approve? Thanks
-
What tags I need to put a link in my text?
Hi there, I just want to place a link in my post and not the full address, just to let people click in a word. How do I do that?
-
MacBook pro morse code?!
I am in boot camp Windows 7 Enterprise, so I don't know if this is windows 7, but here's the story ========== I came in my room, after I turned the display off by turning the brightness off, and the screen was flashing. I didn't think to much of it,
-
Anyone else experiencing lag moving layers?
When I select a layer and start to move it there is a noticable delay for the layer to start moving with the cursor, it jumps. My computer with a solid state HD, great gfx card, overclocked processor and 12 gigs ram can handle moving a layer without
-
Media Manager On The Mac - OSX
Anyone have an idea when this will be available?