Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish

Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

Similar Messages

SimpleCallbackHandler no longer in weblogic.jar for WebLogic 10.3g

I was using the weblogic.security.SimpleCallbackHandler in WebLogic 9.2 to authenticate users. I looked at the documentation for 10.3g and it still mentions this class is available, however it is not in the weblogic.jar file nor in the javadocs. Here is the URL where I was looking. http://e-docs.bea.com/wls/docs103/security/thin_client.html#wp1035574.
The only CallbackHandler in the 10.3g release seems to be the weblogic.security.URLCallbackHandler class. I tried replacing the SimpleCallbackHandler with this class. When I put the weblogic.jar in my classpath and build, I get the following error.
class file for weblogic.security.acl.internal.AuthenticatedSubject not found
ServletAuthentication.runAs(mySubject, request);
Indeed, this class is not in the weblogic.jar file. Both SimpleCallbackHandler and AuthenticatedSubject were in the weblogic.jar for WebLogic 9.2
<code>
import javax.security.auth.Subject;
import weblogic.security.SimpleCallbackHandler;
import weblogic.security.services.Authentication;
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws Exception {
LoginForm loginForm = (LoginForm) form;
Subject subject = Authentication.login(new SimpleCallbackHandler(loginForm.getUsername(), loginForm.getPassword().getBytes()));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
<./code>
Why were these removed and not deprecated???

SimpleCallbackHandler does not exist in weblogic.jar. Used the following code to get around this. WebLogic documentation offers this as an alternative to using SimpleCallbackHandler.
Subject subject = Authentication.login(new URLCallbackHandler(uid, pwd));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
This code agrees with the snippet provided in WebLogic documentation
Project does not compile with the following error:
Project: C:\apps\11g\PrismMainApp\ViewController\ViewController.jpr
C:\apps\11g\PrismMainApp\ViewController\src\adr\prismmain\view\managed\PrismLogin.java
Error(70,28): cannot access weblogic.security.acl.internal.AuthenticatedSubject

Need WebLogic.jar for download

I need WebLogic.jar for development .Kindly let me no from where can i get?

Go to support.oracle.com
Search for document id 763603.1
OR
edelivery.oracle.com and use the BEA WebLogic Media Pack
Did you try creating a wlfullclient.jar?
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/jarbuilder.htm#BABCGHFH

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?

WebLogic 10.0 JMS Thin Client and JVM 1.4

As mentioned in [WebLogic JMS Thin Client|http://download.oracle.com/docs/cd/E11035_01/wls100/client/jms_thin_client.html#wp1026979], it can be used on JVM 1.4 client, but it seems that wljmsclient.jar and wlclient.jar compiled using java 1.5 compiler with no 1.4 compatibility.
Where can I get a 1.4 complied version of this jars for WebLogic 10 ?
Edited by: user10385140 on 02.10.2008 2:32

Hi,
The doc is correct that the 1.4 JVM is supported for thin 10.0 clients, but note that 1.4 is not supported for 10.3 (the latest version). If you confirm that there's a problem, I recommend contacting customer support. Meanwhile, as a work-around, you can use a client jar from an earlier version (such as 9.2 at the latest MP).
The latest updated version of the 10.0 client doc is at http://edocs.bea.com/wls/docs100/client/basics.html, the link you provided points to an older version of the edoc.
You might want to look at using a generated "full client" rather than a thin client unless a smaller jar size is important in your use case. The reasoning is stated in the updated edoc.
Regards,
Tom Barnes
WebLogic JMS Developer Team
Edited by: TomB on Oct 2, 2008 6:52 AM

Classpath for JMS standalone client

Hi,
I observed some problem, when I try to start my JMS client application. If in classpath is oc4j.jar it works, but when I replace oc4j.jar with oc4jclient.jar doesn't
I notice the message:
Exception in thread "main" java.lang.NoClassDefFoundError: com/evermind/server/jms/EvermindXAConnectionFactory
at com.evermind.server.jms.ConnectInfo.getPass(ConnectInfo.java:98)
at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicCon
nection(EvermindTopicConnectionFactory.java:83)
at sapconnector.MaterialMoverClient.main(MaterialMoverClient.java:52)
the line no. 52 exactly means:
TopicConnection connection = factory.createTopicConnection();
What the OC4J client jar (oc4jclient.jar) is not enough for starting JMS standalone client?
regards
Krzysztof

Hi, thanks for the reply.
Well, I figured out that problem. It was my jar file. One of the jar file, which is imqjmsra.jar wasn't really the right one and that was giving me the problem. Well, at least that is working not, but I am having new problems.
Right, I have been trying to make this work for about three days now. The truth is that my standalone JMS does work, when it is running on the same machine where the J2EE Server is located, but I am trying to make my JMS standalone client to connect to J2EE server from different location. Now I am getting connection refused error. Well, I guess I will be keep trying util I get this working.

Booting WLS Java classes for JMS C Client

 ** Workshop 8.1 Beta **
 I am trying to boot the WLS server with the WLS Java classes (used for supporting
 the JMS C Client from dev2dev) contained in the CLASSPATH. The JVM is exiting
 with the attached error.
 I have removed the credentials in the config.xml as suggested by the error log.
 Any ideas? Thanks, Craig.
 [errors.txt]


 Problem with loading JMSCHandler.class in the class loader. Added JMSCHandler.class
 to weblogic.jar and problem was resolved..
 "craig" <[email protected]> wrote:
 >
 >
 >
 >** Workshop 8.1 Beta **
 >
 >I am trying to boot the WLS server with the WLS Java classes (used for
 >supporting
 >the JMS C Client from dev2dev) contained in the CLASSPATH. The JVM is
 >exiting
 >with the attached error.
 >
 >I have removed the credentials in the config.xml as suggested by the
 >error log.
 >
 >Any ideas? Thanks, Craig.

Minimizing size of weblogic.jar for JavaWebStart

We have a number of in-house client-server Swing applications. They run through
JavaWebStart and talk to WebLogic EJB's on the backend. I'm working on a new app,
the first on WL7, and the sheer mass of weblogic.jar is a big problem: close to
40MB! It's so big that when I made the JWS web client into a WAR inside our app's
ear, I got an OutOfMemoryError deploying unless I gave the weblogic.Deployer at
least 256mb of memory! It also takes a long time to download, a long time to deploy,
etc.. I imagine only a fraction of those classes are actually needed at runtime,
but which ones?!? I have found nothing on Google or dev2dev, because I guess this
sort of config is a lot less common than a JSP/servlet type set-up. Help!
--kd

I guess you should search for VerboseToZip utility in WLS. Search on dev2dev
site. I saw a white paper. Title is something like "thin client jar..."
"Kyle Downey" <[email protected]> wrote in message
news:[email protected]..
>
We have a number of in-house client-server Swing applications. They runthrough
JavaWebStart and talk to WebLogic EJB's on the backend. I'm working on anew app,
the first on WL7, and the sheer mass of weblogic.jar is a big problem:close to
40MB! It's so big that when I made the JWS web client into a WAR insideour app's
ear, I got an OutOfMemoryError deploying unless I gave theweblogic.Deployer at
least 256mb of memory! It also takes a long time to download, a long timeto deploy,
etc.. I imagine only a fraction of those classes are actually needed atruntime,
but which ones?!? I have found nothing on Google or dev2dev, because Iguess this
sort of config is a lot less common than a JSP/servlet type set-up. Help!
--kd

Weblogic.jar for Weblogic 4.5.1

I'm trying to upgrade the Weblogic JSP Compiler optional Ant task so that it
will
work with newer version of Weblogic JSP Compiler. I got it to work for 6.1,
7.0 and 8.1.
The current released version of Ant supports only Weblogic JSP compiler
version 4.5.1.
I want to ensure backward compatibility with 4.5.1 jsp compiler but I don't
have the older version of Weblogic 4.5.1. I've gone to the Bea support site
and apparently, our company's support contract doesn't allow me to download
older versions of WebLogic.
How do I get my hands on the older version? I don't need the entire
product, I just need the portion that has the Weblogic JSP Compiler
(weblogic.jar)

4.5.1 isn't supported anymore so I wouldn't worry about it.
-- Rob
newsgroups.bea.com wrote:
I'm trying to upgrade the Weblogic JSP Compiler optional Ant task so that it
will
work with newer version of Weblogic JSP Compiler. I got it to work for 6.1,
7.0 and 8.1.
The current released version of Ant supports only Weblogic JSP compiler
version 4.5.1.
I want to ensure backward compatibility with 4.5.1 jsp compiler but I don't
have the older version of Weblogic 4.5.1. I've gone to the Bea support site
and apparently, our company's support contract doesn't allow me to download
older versions of WebLogic.
How do I get my hands on the older version? I don't need the entire
product, I just need the portion that has the Weblogic JSP Compiler
(weblogic.jar)

JDriver and weblogic.jar for the wlserver 6.1 sp2

Hi all,
After I download the jDriver for Ms sql 2000 server, I set the classpath as
document told, I test
it using the utils.dbping it works fine. But when I try to use it with the weblogic
server 6.1
I have the problem as following:
I included the jDriver classes in the classpath of the startWeblogic.cmd as
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;C:\weblogic\mssqlserver4v70\classes
saved the startWeblogic.cmd file
Then I start the wls with startWeblogic.cmd(the new classpath). It starts fine
Then I setup the connection sql pool using the weblogic.jdbc.mssqlserver4.Driver
It says "No suitable driver"
I found that in the weblogic.jar(shipped with the weblogic 6.1) and in the jDriver
classes, there are two files which have the same name is weblogic.jdbc.mssqlserver4.Driver.
Because in the classpath
.\lib\weblogic.jar comes first so weblogic server takes weblogic.jdbc.mssqlserver4.Driver
of the weblogic.jar rather than in the jDriver classes directory. So I thought
the matter of changing the order in the classpath (.\lib\weblogic_sp.jar;C:\weblogic\mssqlserver4v70\classes;.\lib\weblogic.jar")
will solve the problem, but when I changed the oder in the classpath the weblogic
server did not start AT ALL with the following errror.
------------------Begin error----------------------------
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
;.\lib\weblogic_sp.jar;C:\weblogic\mssqlserver4v70\classes;.\lib\weblogic.jar"
-Dweblogic.Domain=mydomain -Dweblogic.Name=myserver -Dbea.home="C:\\bea" -Dweblogic.management.password=
-Dweblogic.ProductionModeEnabled=true -Djava.security.policy="C:\bea\wlserver6.
1/lib/weblogic.policy" weblogic.Server
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoSuchMethodError
at weblogic.Home.getFileSource(Home.java:66)
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:81)
at weblogic.Home.getPath(Home.java:89)
at weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate
.java:77)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:200)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>goto finish
------------------End error----------------------------
I wonder how can I use the jDriver with weblogic server?
Do you have any idea what I have done wrong or how to get around with this problem?
Please help
Thanks in advance

It works now.
Thanks Laurent.
Tom
Laurent Goldsztejn <[email protected]> wrote:
Hi Tom,
Can you please make sure that the driver is defined as
weblogic.jdbc.mssqlserver4.Driver
and that the url starts with jdbc:weblogic:mssqlserver4
Thank you,
Laurent Goldsztejn
Developer Relations Engineer
BEA Support

J2EE Client Application (weblogic.ClientDeployer)

Hello,
I'm experimenting with the ClientDeployer utility as described in the 6.1
documentation, and I face some odd behavior.
I created a jar file (cli.jar) containing the class files of my client application,
and a META-INF/application-client.xml file.
This jar file then gets stored in an ear file, together with a cli.runtime.xml
file
and a META-INF/application.xml file.
Afterwards, I tried running this client application by using
java weblogic.ClientDeployer clients.ear cli
Now, all of this works, as long as I leave the cli.runtime.xml file in the
current directory. But as soon as I remove this file from the current
directory, it stops working. This means that ClientDeployer doesn't read
the cli.runtime.xml file from the ear file, but only from the current directory.
Is that the way it is supposed to work ? I would expect it to read the
runtime file form the ear file ?
Thanks,
Francois Staes.

Hi Sandy,
If I understand you correctly, then you are asking how to make
a stand-alone java client, right? According to the J2EE spec, a
stand-alone java client also needs to be deployed to a container.
A long time ago (before OC4J, when there was only OrionServer)
I struggled for about a week before finally figuring out how to
do this.
However, I then discovered that, with OrionServer (and therefore
also with OC4J), your stand-alone java client does not have
to be deployed to a container and can be launched from the command
line with the "java" command.
If you do want to deploy your java client, then the only way
I know to launch it is by using the "applicationlauncher.jar"
file. This file was part of the first OC4J (version 1.0.2.2).
It disappeared in the next version (9.0.2) and now has reappeared
in the latest version (9.0.3) -- go figure! Like I said, by the
time I started using OC4J, I was only using non-deployed clients,
so I had no need for "applicationlauncher.jar", so the fact it
was missing from version 9.0.2 didn't affect me.
In any case, I recall information on how to use the "applicationlauncher.jar"
file on the following web sites:
http://www.orionserver.com
http://www.orionsupport.com
http://www.atlassian.com
http://www.elephantwalker.com
I also recall answering similar questions several times previously
on this forum, so a search of the forum archives may also help.
I hope I have correctly interpreted your question and given you
a helpful answer.
Good Luck,
Avi.

Document for JMS Failover Implementation On WebLogic

Hi,
I am looking some good links and techniques to implement JMS failover using WebLogic 10.3.
FailOver* [As we do with our Databases (Concept of Clustring)]
System will consist of two app servers and each will have its own application deployments but if one failed for some reason the application messages should redirected to the other servere and vice versa.
Above efinition is very brief but if anyone can help provide some good documents and info how to implement it it will be appriciated.
Thanks :-)

Thanks alot guys for your help. We successfully implemented it at our servers here by creating distributed queues targetting all servers in a cluster.
One point which I think is worth mentioning and I want to share with all us here is that; when App Server [where MDB will post the message finally after retrieving from queue] if that goes down what will happen, what MDB will do with that message?.
We impleneted the DLQ (error destination) and deploy one more MDB_DLQ_SERVER2 (Let say App SERVER 1 is down) which gets triggered when any message comes to DLQ and post that message to some other App Server, Let say message has been read by MDB_SERVER1 on SERVER1 but offcourse actaull server is down so message should get Re-directed to its Error Destination after it expiration peiod or whatever the settings are. DLQ (Error Destination) which is also a distributed destinatrion again targetting all servers in cluster same as actaull Request or Reply queues BUT MDB_DLQ_SERVER2 which is deployed on Server2 is NOT able to read this message. It get triggered but can not access the message.
After debugging for almost a day we found out its because message has been transafed to DLQ but actaully its resides in a FILESTORE_SERVER1 and MDB_DLQ_SERVER2 is not able to access it.
To work with that we have to define MDB_DLQ_SERVER1 to cater the SERVER1 failure and MDB_DLQ_SERVER2 to cater SERVER2 failure.
Reason I am mentioning this because as I said DLQ is also a normal Distributed Queue but at the same time its NOT as Distributed as its says.
Hope you all understand what I just wrote above.
Now I need to implement exactly the same scenario using four seperate physicall machine containing my four servers. I tried this scenario by creating four machines where node manager for each server is running and listning but when I am trying to start the server it gives me Certificate Exception with bad user name and password. Anyway I have seen some posts here regarding this; So i think i'll be fine.
Thanks Again,
Sheeraz

Applet -ejb ; weblogic.jar

Hi,
I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge I want to use thin clients. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=localhost remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
age fully, size =1204
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
0 LocateReply
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
PInputStream object
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
stamp
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
age from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL: vmcid: SUN minor cod
e: 217 completed: Maybe]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
at sun.applet.AppletPanel.run(AppletPanel.java:353)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 6 more

Hi,
I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge I want to use thin clients. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=localhost remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
age fully, size =1204
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
0 LocateReply
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
PInputStream object
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
stamp
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
age from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL: vmcid: SUN minor cod
e: 217 completed: Maybe]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
at sun.applet.AppletPanel.run(AppletPanel.java:353)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 6 more

Stand-Alone JMS SAF Client

Im interested in using a WL Stand-Alone JMS SAF Client to send messages to a server-side JMS destination,
 regardless of the servers availability.
 This is for a J2SE Swing Application. There currently is no app server interaction.
 I found the doc http://e-docs.bea.com/wls/docs92/client/saf_client.html
 It describes almost everything except for what the actual client will look like.
 Im stuck after "Modify Your JMS Client Applications.." section.
 Questions:
 A) Suggestions for other docs?
 B) Is anyone using a Stand-Alone JMS SAF Client?
 C) Does anyone know of any code examples?
 The odd thing is that a search on the net for "JMS SAF Client" or variants of yields nothing other than the WL docs...
 Thanks!

I could not make stand-alone jms saf client work. Followed the doc, created ClientSAF.xml, made the change for intial-context factory. Tried using with provider_url and without it.
 I am not using default queue and connection factory. The client code is working fine when I don't use saf, i.e. "weblogic.jndi.WLInitialContextFactory" and provider_url.
 Getting following error:
 javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl]
 at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
 at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
 at javax.naming.InitialContext.init(Unknown Source)
 at javax.naming.InitialContext.<init>(Unknown Source)
 at weblogic.jms.safclient.agent.internal.ClientEnvironmentImpl.getContext(ClientEnvironmentImpl.java:76)
 at weblogic.jms.forwarder.Forwarder.getInitialContext(Forwarder.java:334)
 at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:210)
 at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:265)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 Caused by: java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl
 at weblogic.corba.client.ClientORBInitializer.initialize(ClientORBInitializer.java:106)
 at weblogic.jndi.WLInitialContextFactory.<init>(WLInitialContextFactory.java:29)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at java.lang.Class.newInstance0(Unknown Source)
 at java.lang.Class.newInstance(Unknown Source)
 ... 12 more
 java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl
 at weblogic.corba.client.ClientORBInitializer.initialize(ClientORBInitializer.java:106)
 at weblogic.jndi.WLInitialContextFactory.<init>(WLInitialContextFactory.java:29)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)Stack level 1
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at java.lang.Class.newInstance0(Unknown Source)
 at java.lang.Class.newInstance(Unknown Source)
 at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
 at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
 at javax.naming.InitialContext.init(Unknown Source)
 at javax.naming.InitialContext.<init>(Unknown Source)
 at weblogic.jms.safclient.agent.internal.ClientEnvironmentImpl.getContext(ClientEnvironmentImpl.java:76)
 at weblogic.jms.forwarder.Forwarder.getInitialContext(Forwarder.java:334)
 at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:210)
 at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:265)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 disconnect stack trace finished
 QUEUE NAME: jmssysmodule-ois!oisQueue

RMI problem with weblogic.jar

We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

I'd suggest that you run the vm with the debug flag (-verbose) and see where the classes are being loaded; and examine the classpath to determine where the old jar or classes are occurring.
Rita wrote:
We have re-jarred the Stub.class and put it under weblogic/rmi/extensions, but when the java app runs, it still tries to look in weblogic/rmi/extensions/server. So, I think somewhere in the weblogic.jar, the path specified is still weblogic/rmi/extensions. Do you know what need to be done?
Thanks,
Rita
Eduardo Ceballos <[email protected]> wrote:
Yes, please regenerate your stub classes. That is, re-run rmic or ejbc.
David Furlong wrote:
We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

Small weblogic.jar for jms/j2ee clients of weblogic

Similar Messages

Maybe you are looking for