Amazon and successfully deploy a thin client solution
We have a lot that we store cars on sometimes that has no lights and no power. Recently we've had some vandalism and we'd like to get some security cameras on that area. Any suggestions?
Thanks!
Hey SpiceHeads, Want to successfully deploy a thin client solution, or at least learn more about your options to do so? Thin clients can get you the flexibility, security, and cost savings you need, but do you know the right tips and best practices to make sure it’s truly successful? Get the skinny when you check out HP’s On Demand Presentation of “Secrets to a Successful Thin Client Deployment.” As a Bonus we will be giving away two $50 Amazon gift cards to two lucky registrants. So check it out today! Contest is open to registrants in the US & CA. Contest winners will be announced on 7/28
Similar Messages
-
Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 moreuday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more -
The iTunes Installation files include 4 driver dlls that I can install on a Windows thin client to enable the iPhone to be charged.
The iPhone hard drive or photos are not detected. I guess I need scanner driver support to cope with the camera.
Can anyone tell me which files from the iTune installation set are needed.
It is not practical (or even possible?) to install the whole iTunes package.
I've seen this question asked by a lot of people but never seen an answer.
Please, can someone help...Thanks for the reply.
A thin client is used to connect to a Terminal Server, or in my customer's case, a Citrix Server. I need the thin client to see the iPhone as a camera and pass it to the Citrix Client so the photos can THEN be either stored on a network storage device, or e-mailed.
Because the thin client doesn't even SEE a camera (i.e. the iPhone) it won't be able to connect to iCloud to do anything useful.
I think the question I should be asking, is how do I give the thin client Camera Support.
I've just seen a 2008 forum comment that said the iPhone DOESN'T handle photos through iTunes, but the PC (Scanner support) or MAC (iPhoto) handles them directly. I should be putting the question to HP.
This is still a good place for THIS question, because I've seen so many iPhone users asking it...
If I get a satisfactory answer I'll post it back here. -
BEA should forget workshop and build a Rich Thin Client IDE!!
Hello,
After my work place team just got back from a Macromedia Flex training session, we are all ready to abandon Weblogic and go with Cold Fusion.... Their flex tool builds front end interfaces that put beehive apps to shame... I would sure hope that BEA would quickly develop an alternative Rich thin client environment(Forget Beehive!).
Check out this URL:
https://reservations.ihotelier.com/onescreen.cfm?hotelid=2867I just saw this. Might be useful if you decide to go with coldfusion.
http://edocs.beasys.com/bluedragon/621/index.html -
XMII and Multiple Thin Clients
Hi,
I am thinking of deploying multiple thin clients, each accessing a single xMII instance and am posting a general "broad" question. Although probably not an "xMII" related thread, but any others using xMII content on thin client(s)?
Any issues or pointers or suggestions or "not to do's" with content / java script / applets / performance / refresh?
Thanks all, Rgds Kevin.
Edited by: Kevin Hibbins on Apr 28, 2008 10:58 AMA thin client is essentially a Web Browser, right? Or are you looking @ something else as well?
Just to add , this is from the MII help - "The following section provides a visual overview of the various applets provided with SAP xMII. By combining and linking these building blocks, incredibly powerful decision support applications that bridge a variety of disparate data sources can be quickly created and deployed on thin client platforms such as Web browser, personal digital assistants (PDAs), or other Web-aware mobile devices and internet appliances".
Help me understand if you have anything specific in mind when you say 'thin clients'. -
Q: Anonymous user and thin client jars
Hi all. I've recently upgraded from WLS 7.0 to WLS 8.1. One of the changes I
did with this was update my java client from using weblogic.jar to wlclient.jar
and wljmsclient.jar (the thin client jars). When I do this and attempt to connect
to my WLS instance anonymously, I get the following message:
SubjectManager not installed
If I either use the 8.1 weblogic.jar or use the thin client jars with JAAS, everything
works.
I'd still like to be able to have anonymous connections to my instance and use
the thin client jars. Is there an additional jar I need to include?
Thanks,
EdHi all. I did some more digging, and it looked like our client code was using
some class wrappers which assumed a JAAS Subject was being used, when it wasn't.
The end result was we were calling into an empty Subject instance. This is what
was causing the error. Pilot error on our part. :)
Ed
"Ed Hillmann" <[email protected]> wrote:
>
Hi all. I've recently upgraded from WLS 7.0 to WLS 8.1. One of the
changes I
did with this was update my java client from using weblogic.jar to wlclient.jar
and wljmsclient.jar (the thin client jars). When I do this and attempt
to connect
to my WLS instance anonymously, I get the following message:
SubjectManager not installed
If I either use the 8.1 weblogic.jar or use the thin client jars with
JAAS, everything
works.
I'd still like to be able to have anonymous connections to my instance
and use
the thin client jars. Is there an additional jar I need to include?
Thanks,
Ed -
J2SE JRE on a thin client problems!!!!!!!!!!
HELP!
I would like some help regarding a situation where a webstartable application totalling approx 400k as a prototype app is being sent to a thin client. This thin client is a Wyse computer with a 96mb flash card for its hard disk space. The Java app uses the Swing api and JBoss client jars. The application works smoothly on WinNT or Win2000, 256mb, 700Mhz PC installed with J2SE but the problem is that the target client has a Windows NT Embedded OS which only gives around 7.5mb free hard disk space on its flash card. This is a problem as the client OS needs Java 2 JRE which is a whopping 20.8mb. WebStart when installed totals to approx 1.9mb on a PC. So, the complete deployment for the application would reach approximately 24mb going way past the 7.5mb max limit. The client does have IE+MSJava but uninstalling this JVM is not an option as apparently, it is being used for some other app. I am aware of the option of upgrading the machine but that won't go down too well as it will involve upgrading hundreds of clients. Also, this demo needs to show off Swing to the max so that such an upgrade decision can be made. Getting the application+JRE+WebStart deployed within the limit means that there will be a chance for Java to grow on both the client and server side in Carphone Warehouse, one of the top mobile phone retail companies in the UK. However, if this is not achieved then the alternative is that IE will be used to provide an HTML-based limiting, slow user interface for our users in our stores.
A related question I have is whether J2Micro Edition is an avenue that may be useful to explore. I have looked at it a little and as a guess I'd say that the configurations I have found are for too simple for the device targetted by us as it is near enough to a PC's spec except that it has limited chip power, hard disk and memory space.
Please could someone help us with this as it would really promote Java in our company.
regards,
Amar Syed
Carphone Warehouse UK
Email: [email protected]Well, here are a few suggestions, although I'm not sure how feasible they are at this point...
1) Is it essential that you use WebStart and have the code on the client? That's not really a "Thin client" solution... ;-) Can you refactor your app as a JApplet, and just use the java plugin to run it (~5MB)? This would still enable you to use swing. (You could even just have a "launching" applet in a browser that launches your main GUI JFrame in front of the browser.)
2) I've never used this product, but it's worth a mention - WebCream, by CreamTect (http://www.creamtec.com/webcream/) - it runs your swing app on the server, and sends a DHTML representation of it to the client's browser. Looks pretty convincing from their examples...
3) J2ME is probably not an option, since it doesn't support Swing - it has its own limited API for displaying stuff on mobile devices' small screens.
4) Failing that, there's still server-side java - the JSP/Servlet option, creating your own customized HTML (or super-interactive DHTML) pages and sending them to a browser on the client machine.
Hope some of this helped a little! Let us know how you get on.
M -
Wyse Thin client not connecting to Windows 2008 R2 server
Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits -
Can any body please tell me in detail what is the difference between a Thick client and a Thin client. Also tell me using either of these in specific occassions.
And it's normally called a 'Rich Client' not 'Thick Client'.No, "rich client" is a newer developer.
s/developer/development/I think it's more than a when Sales/Marketing people wanted to promote thin client solutions (during the fashionable thin 90's) they used devisive language of (Thick/Fat) against the alternative traditional Client Server solutions even though these could be Rich or Thin. I remember when Applets where considered thin, then it had to be Web-Pages to be really Thin and now that things have gone full circle with the introduction of things like AJAX and WebStart they use the old^Wnew terminology, or Rich Clients to distance it from the negitive associations of Thick and Fat.
To me, fashions come and go but they will always be Thin or Rich :) -
Exception when running successfully deployed application in websphere 6
I get the following error in an application I have created, and successfully deployed in websphere 6. Does anyone have any idea of what it means?
[2005-08-15 21:31:37:891 CEST] 00000030 SystemErr R javax.naming.NameNotFoundException: Context: HP000D9D1DFE4BNode02Cell/nodes/BIZNode/servers/server1, name: ejb/se/htrc/beans/ProductCategoryLocalHome: First component in name beans/ProductCategoryLocalHome not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOptimizedNamingImpl.java:2000)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1321)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:3024)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.<init>(WsnOptimizedNamingImplBase.java:3489)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1427)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm._jsp._index._jspService(_index.java:70)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2841)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOptimizedNamingImpl.java:2000)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1321)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:3024)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.<init>(WsnOptimizedNamingImplBase.java:3489)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1427)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at javax.naming.InitialContext.lookup(InitialContext.java:361)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm._jsp._index._jspService(_index.java:70)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2841)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
[2005-08-15 21:31:37:906 CEST] 00000030 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))I changed the jndi name to java:comp/env/package...
Didn�t help, now I get this error:
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R javax.naming.NameNotFoundException: Name comp/env/se not found in context "java:".
at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1716)
at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1062)
at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:985)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1263)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:198)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:139)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm._jsp._index._jspService(_index.java:70)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2841)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1716)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1062)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:985)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1263)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:198)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:139)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at javax.naming.InitialContext.lookup(InitialContext.java:361)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm._jsp._index._jspService(_index.java:70)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2841)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
[2005-08-16 00:07:48:234 CEST] 0000002c SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R javax.naming.NameNotFoundException: Name comp/env/se not found in context "java:".
at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1716)
at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1062)
at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:985)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1263)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:198)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:139)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm._jsp._index._jspService(_index.java:70)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:94)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1716)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1062)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:985)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1263)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:198)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:139)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at javax.naming.InitialContext.lookup(InitialContext.java:361)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm._jsp._index._jspService(_index.java:70)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:94)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
[2005-08-16 00:07:49:359 CEST] 00000030 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) -
Q Thin Client with WES 7/8 virtual licensing
Dear Support,
Could you help us, do we need a VDA or SA if we will use
Thin Client PC with Windows Embedded Standard 7/8?
Thank you.Thanks man for the information.
Answers from microsoft are not really direct from the point.
VDA, Software Assurance and Windows Embedded Thin Clients
If you use Microsoft Software Assurance and you have a Windows Embedded Thin Client (Windows Embedded 7/Windows Embedded 8), then you can now move this into your SA, thus negating the need for VDA licensing. This means the total acquisition cost is potentially
lower than equivalent PC’s and even Linux based Thin Clients or Zero Clients due to the Annual Charge of VDA. -
How to determine using MDM rich client OR thin client?
We want to save but also want to make sure nothing missing
SO could you tell me how to decide rich client or thin client?
Thanks!Hi Jessica,
MDM Rich Clients: A rich client is a networked computer that has some resources installed locally (MDM Components) but also depends on other resources distributed over the network (MDM SERVER). It Provides rich functionality.
e.g MDM Components (MDM Console, MDM Import Manager, MDM Data Manager and MDM Syndicator)
MDM Thin Clients: If a user only needs to perform select tasks and does not need all the functionality of a standard computer or program, a thin client may be the right tool for the job. e.g. SAP Enterprise Portal (Iviews for Search and Read access)
You can verify that MDM Components are Rich clients and SAP Enterprise Portal is a Thin client on page 4/41 Components in a MDM landscape as given in below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/284a5534-0601-0010-da9f-b70996d5ce90?quicklink=events&overridelayout=true
Regards,
Mandeep Saini -
Hi
Pls help me in the following regard:
I copied all the files and folders of rw thin client (rw_thin_client.zip)on HP-UX .But when I run the command :
rwthinclient.bat report=test.rdf destype=file desformat=pdf desname=test.pdf userid=gaic_user/gaic_user@nt2db1 server=rep_gaic
I encounter the error :exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=50003,
java.lang.String errorString="Bad command line: %* ",
java.lang.String moduleName="REP"
can u help me in this regard.Your help will be appreciated.Hi
Please see the other thread where I have updated the info you wanted.
<rw thin client on HP-UX
Thanks,
Vinod. -
Hello,
I am looking for a configuration of a Mac Pro server with thin clients so that software and data is centralized on one location.
Is that possible with Mac OS X ? And does Apple have thin clients ?
HubertI have the same question. I am about to buy a Mac Mini with Leopard server, if I can connect thin clients to it. I have good old PCs with Win and Linux, I want to use them as thin clients
-
Thin Client IP phones for VDI solution
Is it possible to have a Cisco IP phone to act as a thin Client for VDI solution?
Can anybody suiggest meHello Sivakalam2
You ask an excellent question, and one that will likely trigger a heated discussion. I've had interest in the same topic for several years, and surprisingly found very little online. Everyone makes a thick client. WebRTC is a development project which is making inroads toward thin client softphone functionality. It's an excellent concept, but I haven't seen a production-ready client, yet. (Not saying there aren't any; I just have not seen them.)
Then I came upon this info in the Cisco Unified Communications System 9.0 SRND:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/9x/collabor.html
Cisco Virtualization Experience Client Architecture
Cisco Virtualization Experience Client (VXC) endpoints enable the end users to have secure real-time access to content and business applications as well as a rich collaborative user experience. These endpoints provide access to collaboration services that are part of the larger Cisco Virtualization Experience Infrastructure (VXI) solution. For information on a complete end-to-end VXI solution design, refer to the documentation available at
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns1100/landing_vxi.html
Deploying Cisco Virtualization Experience Clients
Cisco Virtualization Experience Clients (VXC) are endpoints in the Cisco Unified Communications portfolio; however, they are more than just simple endpoints because they interact with a user's working environment by providing voice, video, and virtual desktop capability and functionality. A user's work environment can assume various profiles (for example, task worker, knowledge worker, or mobile worker), and Cisco has various Virtualization Experience Clients to meet those different needs.
The Cisco VXC 2111 and VXC 2112 provide an integrated form factor that is paired with a Cisco Unified IP Phone 8961, 9951, or 9971 for a fully integrated voice, video, and virtual desktop environment. The Cisco VXC 2211 and VXC 2212 provide a standalone form factor that can be used as simply a virtual desktop (for a task worker), or they can be paired with an IP phone for a fully integrated user environment. The Cisco VXC 4000 provides a software-only solution by using a re-purposed PC to provide the user with voice and virtual desktop functionality, while the Cisco VXC 6215 provides a Linux-based thin client for fully integrated voice, video, and virtual desktop in a single device.
I do not have direct experience with these clients yet, having upgraded to CUCM9 recently. I'm definitely going to research it now. There's much more info in the SRND link above to read.
Thanks
TZ
Maybe you are looking for
-
I'm looking for help. I have two user accounts on my iMac. Both have their own iTunes library file but these both reference to a shared store of music files (to avoid duplicates). I would now like to move this shared music to an external HDD attached
-
No commitment item entered in item 00001 1000 5100004
Hi Gurus, I'm using IDES company code: 1000 company code for posting some invoices. I created my own G/L accounts and trying to post telephone expenses & it is giving the above error. It says to deactivate the Funds Management & Commitment management
-
Hi , I am getting the error while executing the adobe form using web dynpro application. Two days back I developed the ZTEST_TRAVEL_REQUEST2 application and works fine at that time. But now I am getting this error. I am getting this error not only f
-
Errors in app submission phase.
When I attempt to submit an app to the app-store via application loader I get hit with a wall of errors. (The app is intended only to test submission process before I move onto the next phase which, is rapid prototyping all it'sjust a simple abstract
-
I am trying to cancel an invoice using the following code but get back error code -5006. The document is one that has been entered today. Why can't I cancel it? int retVal = sapInvoice.Cancel(); if( retVal != 0 ) int errCode; string errMsg; S