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,
Ed

Hi 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

Similar Messages

LabVIEW license for terminal servers and thin clients (e.g. LTSP)

Does NI plan to provide a license agreement for terminal servers and thin
clients?
I've been told to purchase a multi-seat license. That doesn't make much
sense since the thin clients won't be accessing DAQ hardware. They're
just used for developing the LV source.
Comments/suggestions?

On Thu, 04 Nov 2004 13:43:58 -0600, jbrohan wrote:
> As far as I know it's the capability to edit the source code that NI has
Yes, this is a very good point. Quite a unique situation when compared to
text based languages. Keep in mind I certainly don't mind paying for that
but I see no need to pay for much of the other features - like running it.
This is certainly one of the other features you pay for with LV. Since
we never plan to run the app on the thin client, why pay for that
feature?
What we do is crank out source code on the thin clients. We then send the
source code to this wireless mobile DAQ station running WindowsXP. From
there we can roll it up to our clients' target systems. That machine is
used for debugging then compilin
g so it has its own LV Prof Dev license
installed on it. Also, it can be operated locally or remotely via remote
desktop (one user at a time).
I know it may sound strange but it works great. And as the NI Software
License Agreement(NISLA) specifies, we have separate licenses on all
machines that load LV into local memory. The thin clients load nothing
into local memory, hence no need for a separate license.
> I express myself clearly in the hope of guidance. I am a one man shop
Yes, this is understandable. Installing one license on multiple machines
is a big no-no. However, that is not what I'm trying to do. Take a peek
at the "Grant of License" and "Single Seat License" sections of the NISLA.
> You say "That doesn't make much sense since ..." One of my clients has a
Ha! How about this scenario: As wireless hardware (bluetooth, wifi)
becomes more common, perhaps NI will have a peer scanner on all PCs with
LV installed. That way if you get within 100 feet of a P
C with the same
LV serial number, you get locked out and it sends a small message to the
NI batcave.
Thanks for the response. I'm hoping NI chimes in soon.

How to create mandatory (read-only) profile for Terminal Services user (HP Thin Client) on Server2003... aaarrgghhh!

I've been tearing my hair out for a couple of days now...
I'm trying to create a mandatory profile for users logging in from hp thin clients on a 2003 server at a school.
I've set up a prototype user, then copied the proto user's NTUSER.DAT to NTUSER.MAN and renamed
NTUSER.DAT to NTUSER.DAT_unused.
At that point, logging in as the prototype user looks ok. It was my understanding that renaming NTUSER.DAT to NTUSER.MAN would make it a mandatory profile, and the user (in this case the proto user) would be unable to change it. However, in this
case the user can still modify the desktop and those modifications are preserved across logins. The NTUSER.MAN file is being updated, judging by the timestamp changes.
What am I missing?
I've tried putting the NTUSER.MAN in the user's dir on the server
(C:\Documents and Settings\ProtoUser),
in the DefaultUser, and in AllUsers.
Right now I'm getting a default, unmodifiable profile which I have no idea where it comes from.
In case it matters, the original user and directory tree from which the NTUSER.MAN I'm trying to use has been deleted, but I wouldn't think that should matter.
For example, I have the option to not show the security tab set in the group policy, but it is showing up.
The Start menu is showing as the classic start menu, and I had it set for the "new" (2 column) one.
I've got hide network places on the desktop set, but it's showing up.
Is there a way to tell where a profile is coming from?
I'm pretty confused at this point; any clarifications / tips would be much appreciated.
Related questions:
If both an NTUSER.DAT and an NTUSER.MAN exist, which is used?
If no profile is found for a user in the normal place, what happens?

Hi,
Thank you for posting in Windows Server Forum.
A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users. With mandatory user profiles, a user can modify his or her desktop, but the changes are not saved when the user
logs off. The next time the user logs on, the mandatory user profile created by the administrator is downloaded. There are two types of mandatory profiles: normal mandatory profiles and super-mandatory profiles.
User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) on the server to NTuser.man. The .man extension causes the user profile to be a read-only profile.
User profiles become super-mandatory when the folder name of the profile path ends in .man; for example, \\server\share\mandatoryprofile.man\.
More information:
Mandatory User Profiles
http://msdn.microsoft.com/en-us/library/windows/desktop/bb776895(v=vs.85).aspx
Using User Profiles in Windows Server 2003
http://technet.microsoft.com/en-us/library/cc776120(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Rich client and thin client

Hello experts,
Rich contents are data manager, console, import manager and syndicator GUI clients
thin contents are portal way of looking mdm using iviews.
is this true??
Regards
Eva M

Hi Eva,
Good Day !
You are right .
A thing client (generally a software application/portal) depends primarily on a central server ( MDM server in this case) .It will drive communicating inputs from user to server and delivering back outputs from server to the user.Thin clients are independent of the machine you are using .
Eg:Portal
A thick client passes on data from an MDM user to Server . Such clients are generally used for performing data storage and processing activities directly at server level.Thiick clients need dedicated installations of GUIs and are machine dependant.
Eg:data manager, console, import manager and syndicator GUI clients
Hope this clarifies your query.
Regards,
Vinay M.S

In applet,how can i got the thin client jar for JMS from weblogic.jar?

who can give it to me?
and,when i used the weblogic.jar coming from weblogic 7sp2 for linux advance server
2.1 as the client jar,i still got a error message that Class (.....Stub.class)is
not found,why?What should i do?

That approach is a hack and an absolute nightmare. It never worked
completely. I could not get any support for durable subscriptions etc. You
can add this (Thin JMS client) as a request for new feature (but it should
have been available long time ago).
-- Vish Magapu
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]..
Hello,
You might want to take a look at the JMS white paper and asociated
discussion for supporting thin clients: check the reference on:
http://e-docs.bea.com/wls/docs70/faq/jms.html#252418
HTHs,
Bruce
jerry8006 wrote:
who can give it to me?
and,when i used the weblogic.jar coming from weblogic 7sp2 for linux advance
server
2.1 as the client jar,i still got a error message that Class
(.....Stub.class)is
not found,why?What should i do?

Use of SQL*Loader and Thin Client

I have a java application that is currently using the thin client. For portability issues, I am unable to use an OCI driver. My application also uses SQL*Loader.
My big issue is that The Thin client requires the HOST and SID for a connection.
But, for SQL*Loader to work in a client/server environment it needs to use the SERVICE_NAME and net8. Is there any way to have SQL*Loader use similar information that the thin client is using?
I know the right solution is to use the OCI drivers, but right now that is not feasible.
Thanks for any help in advance
Jeff McNurlan
Navigation Technologies.

I assume you are using an ObjectInputStream. Without seeing your code or a snippet I can't be certain...
The JDBC spec says the following about ObjectInputStream :
"An ObjectInputStream deserializes primitive data and objects previously written using an ObjectOutputStream"
Since there was nothing written by ObjectOutputStream, ObjectInputStream has nothing to deserialize and this exception would be raised.

Runtime error - class not found using JDBC driver and thin client

Hi,
We are running a small Java application on a Sun server which acts as a thin client connecting to an Oracle 8i server running on a different server.
JDK version: 1.3.1_01
OS version: Solaris 7
JDBC classes file: classes12.zip
It compiles fine, but get a runtime error (the DriverManager.registerDriver method )
cruncher [40]% javac -classpath /export/home/mrscot/classes12.zip JDBCtest.java
cruncher [41]% java JDBCtest
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleDriver
at JDBCtest.main(JDBCtest.java:7)
cruncher [42]%
Program:
import java.sql.*;
import java.math.*;
class JDBCtest {
public static void main (String args []) throws SQLException {
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin@xxxxxxxxx:1521:xxxx", <userid>,<password>);
Statement stmt = conn.createStatement ();
ResultSet rset = stmt.executeQuery (".............");
while (rset.next ())
System.out.println (rset.getString ("......."));
rset.close();
stmt.close();
conn.close();
} catch (Exception e) {
System.out.println("Error: " + e);
Any ideas? Probably something very, very stupid I'm overlooking!
Thanks
Scotty ([email protected])

Supplementary question:
Hi,
We are running a small Java application on a Sun server which acts as a thin client connecting to an Oracle 8i server running on a different server.The Oracle version is 8.1.6
Will the 'classes12.zip' for 8.1.7 work with
1.3.1 of the Java JDK, and Oracle 8i 8.16 ??
Thanks Scotty

ISE Profilinh and Thin Clients

I have ISE 1.2 and HP T610 thin client on the network
802.1x authorization is working correctly but clients are profiled as generic HP-devices or HP printers
I don't know how to create custom profiling policy for 'HP-Thin-Client' device.
What OUI conditions to assign for HP T610 clients?
Thanks in advance,
Vice

I have advanced license
Also I checked Feed Service, it is enabled but there is no updates listed under 'Update Information and Options'
I have configured external syslog server but I don't know which logging categories needs to be enabled to get syslog messages from Profiler Feed Service
Thanks in advance,
Vice
Sent from Cisco Technical Support iPad App

Fat Client and Thin Client

Hello, everyone
I am a newbie with websphere 5. I am wondering if anyone know fat clients(Swing GUI) work with websphere. I know thin clients(web-based interface) work with websphere. My scenario is like this and this is all experimental purposes:
I want to program a Swing GUI interface as the client that accesses the enterprise javabeans that is installed on websphere. So the Swing GUI is the client and Websphere is the server, which makes it a 2-tier Application. My question is basically, does websphere only work with web-based application or does it work with both desktop application clients and web-based application clients also?
Any Ideas?

Thanks, that's the kinda of straight answer I am looking for. I have been researching for this answer to this question for a long time and even posted several similar questions on Java forum, but no one seemed to have a straight answer. What I was thinking of programming is:
client/server program using websphere.
Client:
GUI interface using Swing that is just like a regular desktop application and not a web browser (I notice the most common application using websphere are web based applications like portals).
Server:
Using Websphere to accept connection when requested by the client and act as a bean container, which holds EJBs. The EJBs will connect to the database (mssql server) to pull data from.
Does this sound OK and can this be done using Websphere? I am using Websphere 5.
Thank you, I am just a newbie in j2ee, just trying to get started in this area of programming.

Wireless broadcom pci mini adapter and thin client t620

Hi
I need toknow if part code 582564-001 will work in the thin client F5A54AT. Are there driver availalbe?
Thanks

I finally solved this problem by retrying the steps posted elsewhere in the community. I did NOT revert my o/s to Windows 8 and reinstall the upgrade to 8.1. I simply went into Device Manager and uninstalled the wireless adapter and its software. I then downloaded and installed the Realtek 8188CE Windows 8 driver from the Lenovo H520 drivers page. Finally, I followed the steps to update that driver, selecting the option to choose the driver myself. You should see a Microsoft driver and a Realtek driver - pick the Realtek driver and you should be good to go.

Webi Thick and Thin Client difference

Experts ,
what are the differences between WebI server thin and WebI Thick client.
Can any one give solid 3-4 pros and cons for the same
thanks

Hi,
not that much:
- Webi Rich Client is Offline compatible
- You can build Reports on local Dokuments such as .xls or .txt
Regards
-Seb.

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 more

uday 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

Thin clients, labs, and applications

We have thin clients in some labs and have a specific virtual desktop load specific for that lab. The issue; students do NOT have to log into the network and we want to change this.
Our issue:
We have 10 licenses for an application in a lab. The virtual desktop has this application for 10 computers within the specific lab.
If we have students log onto the network, they will have to option of selecting which virtual desktop to open (multiple courses taken by the student, multiple labs = multiple virtual desktops)
If a student logs in from the library, they will see all the virtual desktops as well and could use one of the 10 mentioned above, thus using up one of the virtual desktop application licenses.
This leaves one student in the lab not able to connect.
Question:
Is there a way to either limit what the student can select based on location/IP address or is there another way to make sure that virtual desktop is only used within that lab?
I have been told that virtual desktops are user based and therefore cannot be altered in this way...so, checking here.
TIA,
--cdburns

We have a similar requirement, as we are replacing physical labs with VDI zero and thin clients and want them to behave similarly. Our physical lab environment had different software setups for different locations (Geology, Audiology, Nursing, etc.). We have locked down access to the VDI environment (the broker) from on-campus only, and the majority of our zero and thin clients are setup to auto-login to a specific pool - getting rid of the areas where students can select which pool to log into.
There is one exception where we had to be more harsh because of compliance reasons. We could only let students log into a specific lab pool if they were using specific thin/zero clients. You've already mentioned our solution to this as we used VLANs to restrict this access. The VMs in the pool resides in a VLAN that only allows the PCoIP protocol access from another VLAN where the authorized zero/thin clients reside. While authorized students would be able to see the pool selection if presented on their own or unrestricted device - they wouldn't be able to fully take control as the PCoIP connection wouldn't work.
Another option is to use the broker labels. We abandoned this option as it didn't seem to be scalable and we'd have to potentially setup multiple broker servers in order to accomplish this.
I'm waiting for vmware to come out with a better solution. You'd expect there to be a desire to restrict access to various pools based on the client endpoint or location.

Authorization Issue with Custom Pending Value Object and Anonymous Users

Hi,
I am just converting my demo from version 7.1 to 7.2. I am not doing upgrade. The demo uses a custom pending value object USER_REQUEST. The idea is that new employee goes to Java AS as anonymous user and enters her details and store where she will work. After submitting request there is an approval process using custom entry type USER_REQUEST. If the request is approved then IdM converts USER_REQUEST into MX_PERSON entry. This works nice in 7.1 but I am having problems with replicating this in 7.2. I created new UI task accessible by anonymous that creates new USER_REQUEST entry. I also assigned role idm.anonymous with UME action idm_anonymous to UME built in group Anonymous users.
My problem is with the field STORE. This field is a reference field to another custom entry type STORE (this entry type will be used in context based assignment). Every new employee must selects a store where she will work. The problem is when user clicks on button "Select". Web dynpro terminates and returns authorization error. I also tested this with entry type MX_ROLE. I added attribute MXREF_MX_ROLE and same issue. So it seems that just assigning UME action idm_anonymous is not enough to list objects from identity store. I found a workaround for this issue. When I assign also UME action idm_authenticated to Anonymous users then it does not dump and I get a pop up window where I can search for store. It does not seem right to assign idm_authenticated to anonymous users.
Another issue is with display task for entry type USER_REQUEST. I assigned a display task to entry STORE and I set that Anonymous have access to this task in Access control tab. I assigned default value to the field store. So when a user opens page she can see a hyper link to display already assigned store. When user clicks on this hyper link it opens a new pop up window and user must authenticate against Java AS. After successful authentication the display task for entry STORE is displayed. I would assume that anonymous user can display it without authentication.
So to me it seems like authorization checks have been changed in 7.2 versions and are more strict for anonymous tasks. Hence my question is how can I implement my scenario. Am I missing some configuration or what's the proper solution to my two issues? I don't count assigning idm_authenticated to Anonymous users as a solution. This workaround does not solve my second issue.
Thanks

Some of the folks from Trondheim labs check, but rather infrequently. There's another person who I guess is in consulting that also checks from time to time.
Sorry I can't help you with your main question...
Matt

What is thin client and Fat Client

Hi Experts,
I would like to know about Fat Client and Thin client in detailed words.
Thanks and Regards.
Chilla..

Hi Chilla,
     The thin clients are clients that reduce the load on servers.
Let me explain hw thin clients will get works.
     Thin clients are stores,all required library files in you local system,so that the corresponding applications which are using will be used the library files in your local system and it get execute and where as in the case of Fat clients the library files are not stored in your local system.
   Please let me know if you have any doubts regarding this.
Thanks and Regards,
Chandu.

Q: Anonymous user and thin client jars

Similar Messages

Maybe you are looking for