Classpath for remote client

Hi,
Is there a minimum package of classes (.jar, .zip) that are required for
remote client application to call EJBs in WL 5.1 container ?
My remote application works fine if I include WL_HOME/classes in its
classpath. The problem is that WL_HOME/classes directory is huge. I am
looking for some lightweight package of classes that would contain only
client side implementation of WL's RMI, JNDI and EJB - just enough to
call EJBs from remote client application.
I couldn't find such .jar in the WL 5.1 installation.
Can anybody help ?
thanks,
Rafal

These is no such jar provided by BEA. You can try to create one using
verbose2zip: http://www.weblogic.com/docs51/techstart/utils.html#verbosetozip
If network speed allows for it, you can network classload from WebLogic :
http://dima.dhs.org/misc/ThinClient.jsp or
http://dima.dhs.org/misc/ThinClient2.jsp
(this will download few hundred k, so it is not acceptable for a client
connected via 28.8 modem).
Rafal Mantiuk <[email protected]> wrote:
Hi,
Is there a minimum package of classes (.jar, .zip) that are required for
remote client application to call EJBs in WL 5.1 container ?
My remote application works fine if I include WL_HOME/classes in its
classpath. The problem is that WL_HOME/classes directory is huge. I am
looking for some lightweight package of classes that would contain only
client side implementation of WL's RMI, JNDI and EJB - just enough to
call EJBs from remote client application.
I couldn't find such .jar in the WL 5.1 installation.
Can anybody help ?
thanks,
Rafal--
Dimitri

Similar Messages

Minimal requirements for remote client app to call a EJB 3 session bean

I'm just starting to get into EJBs, trying to learn the EJB 3 APIs. I kind of understand the setup on the server side to create a session bean. What I don't understand is what I would have to deploy for each of the remote client app (Swing-based GUI or something like that) installations. Of course, the client app code would have to be deployed to each client desktop, but what stuff related to the session bean? Just the session bean interface class?
For ease of discussion, let's say my bean is CalculatorBean, having two interfaces, CalculatorRemoteIface and CalculatorLocalIface. Let's also say my client app, CalculatorUI, is a simple Swing-based GUI that grabs a reference to a CalculatorBean.
Other than just the Swing-based classes and the JRE, what JARs/classes will I want to deploy to each desktop?
(Please assume the latest Sun Java System App Server 9 and Java EE 5, if you are familiar with them.)

Personally- I would deploy your backend
in EJB 3.0, but then expose it as a web service. It
is MUCH easier for your clients to connect to a web
service (and mantain that code), then to have them
connect via RMI/JNDI.Oh, I would say it's quite the opposite. RMI/JNDI is MUCH easier from a client point of view than web services. To make web services work easy from the client side you have to generate code and the tools that generate code from a web services wsdl file doesn't do a great job today. But that was not the question. But take some time reading this article about webservices...it's quite funny and spot on: http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-stands-for-simple
Now to your question, yes you will need the remote interface on the client side.
/klejs

Screen resolution for remote client

I have used Windows remote desktop and it has the fuction of setting the display resolution of the target machine when you login. So if i am on using a small laptop with small screen resolution (1024 x 768) and connect to a remote machine with a high resolution i can set the remote machine to display at 1024x768 nativly (no stretching or scalling).
DOES APPLE REMOTE DESKTOP HAVE THIS FUNCTIONALITY?

Ok so the solution was to user a different VNC client in Ubuntu. "Vinagre" allows you to view your remote session scaled to any size you like. It will however retain the dimentions of your MacBook screen.
One thing to be aware of is that when authentication your VNC session (entering your username and password) Vinagre only allows you to enter a password of 8 characters max. So if your password is longer then 8 characters you will have to shorten it to user Vinagre... A bit annoying but at least it works.
Techy notes:
It is actially the VNC server Vino that Vinagre uses that is enforcing the password length limit. So if using an alternative client that uses Vino as it's VNC server this limit will apply for that client also.
Even though you are scaling the client session down VNC sends the host's full resolution so you will still transfer a lot of data over the network.

Cluster-related error for remote client

          Hello,
          I am getting the following error when running a remote stand-alone client that attempts to access an entity bean that is running within WLS6.1sp2:
          java.lang.NullPointerException
          at weblogic.rmi.cluster.WeightBasedReplicaHandler.chooseReplica(WeightBasedReplicaHandler.java:65)
          at weblogic.rmi.cluster.BasicReplicaHandler.loadBalance(BasicReplicaHandler.java:258)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:223)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy1.findByPrimaryKey(Unknown Source)
          at ProductClient.main(ProductClient.java:40)
          We are not using clustering. The standalone client is using "copied" jars such as weblogic.jar on a win2000 pc. The error happens whether we run WLS on unix or on win2000.
          Any thoughts on how to avoid this problem?
          Thanks for any help,
          Clint Prouty
          DST Systems


As i mentioned earlier NPE is our problem.
          Pls try SP3 and if that doesn't solve, follow up with support.
          Kumar
          Clint Prouty wrote:
          > Hi Rajesh,
          >
          > Yes I do have the clustering license key in my license.bea file.
          > The error happens even if the client is running on the same
          > win200O PC as WLS. The error I listed comes from the client program, so I am
          > not sure how the license would come into play.
          >
          > Thanks,
          >
          > Clint
          >
          > Rajesh Mirchandani <[email protected]> wrote:
          >
          >>Do you have a clustering license key in your license.bea file ? It seems
          >>that we are looking for the cluster license even though you are not
          >>using clustering.
          >>
          >>Put the key in and see if it helps.
          >>
          >>Kumar Allamraju wrote:
          >>
          >>
          >>>you should report this problem to [email protected]
          >>>
          >>>I'm not sure if it's a known issue in SP2 and fixed in SP3. It's worth
          >>>trying SP3.
          >>>
          >>>--
          >>>Kumar
          >>>
          >>>Clint Prouty wrote:
          >>>
          >>>
          >>>>Hello,
          >>>>
          >>>>I am getting the following error when running a remote stand-alone
          >>>>
          >>client that attempts to access an entity bean that is running within
          >>WLS6.1sp2:
          >>
          >>>>java.lang.NullPointerException
          >>>> at weblogic.rmi.cluster.WeightBasedReplicaHandler.chooseReplica(WeightBasedReplicaHandler.java:65)
          >>>> at weblogic.rmi.cluster.BasicReplicaHandler.loadBalance(BasicReplicaHandler.java:258)
          >>>> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:223)
          >>>> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >>>> at $Proxy1.findByPrimaryKey(Unknown Source)
          >>>> at ProductClient.main(ProductClient.java:40)
          >>>>
          >>>>We are not using clustering. The standalone client is using "copied"
          >>>>
          >>jars such as weblogic.jar on a win2000 pc. The error happens whether
          >>we run WLS on unix or on win2000.
          >>
          >>>>Any thoughts on how to avoid this problem?
          >>>>
          >>>>Thanks for any help,
          >>>>
          >>>>Clint Prouty
          >>>>DST Systems
          >>>>
          >>>>
          >>--
          >>Rajesh Mirchandani
          >>Developer Relations Engineer
          >>BEA Support
          >>
          >>
          >>
          >

Issues with remote client accessing EJB3

Hi folks,
I tested Weblogic 10.3 these days and had some trouble to access a stateless session bean (EJB3) via a remote Java client. My development system is Windows Vista 32bit.
First, Weblogic doesn't like blanks in folder names! The Test Client throws an exception complaining that the business interface is not found:
Exception in thread "Main Thread" java.lang.AssertionError: java.lang.ClassNotFoundException: ejb3session.Trader
at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:69)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:205)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at ejb3session.Client.lookup(Client.java:99)
at ejb3session.Client.(Client.java:34)
at ejb3session.Client.main(Client.java:61)
Caused by: java.lang.ClassNotFoundException: ejb3session.Trader
at weblogic.ejb.container.deployer.DownloadRemoteBizIntfClassLoader.getClassBytes(DownloadRemoteBizIntfClassLoader.java:85)
at weblogic.ejb.container.deployer.DownloadRemoteBizIntfClassLoader.loadClass(DownloadRemoteBizIntfClassLoader.java:46)
at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:66)
In fact, the compiled class file of the business interface is located on the file system in a path that contains a blank. Debugging session shows that the internal weblogic class RemoteBusinessIntfGenerator fails to open the class file because of a wrong used URL file reference. If the path contains no blank, everything works fine. This is obviously a bug!
Second, generics don't work in the business interface. As soon as I insert a generic return type or method parameter, I get an exception at runtime, no matter if the actually called method is generic or not:
java.lang.NullPointerException
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:162)
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:53)
     at $Proxy0.saveContact(Unknown Source)
     at Main.testIt(Main.java:45)
     at Main.main(Main.java:34)
Third problem is already known by Oracle (CR373734): when using JPA and serializing entities to the remote client, serialization fails until you implement a writeObject() method in every entity.
What is your experience concerning these issues? For my opinion quite severe bugs...
Cheers, Thomas

But most of the O/S like Linux ,Solaries does not allow blankspaces in the classpath. Only the O/S that does allow is Windows. and there are a lot of issues regarding the spaces in the classpath.
If a blank in the classpath exist in the admin console as a remote start argument for a managed node, a patch exist.its CR375981.
But for the above case 808498 (blank for remote client classpath) Engineering did not given any patch and asked to go with the work around ie not to use a blank in the classpath.
Thanks !!

WebLogic Builder remote-client-timeout

Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

I think the tool sets the default value for this flag. The default value
should not have any effect. However, I would expect the tool (weblogic
builder) not to insert this element in the descriptor.
More details on this setting can be found here -
http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
--Sathish
<Colin Yeung> wrote in message news:[email protected]..
Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the
weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
specifies a rmi level timeout in seconds for remote clients that call the
home and remote methods of the ejb. The method call(s) timeout on the
client side after the specified number of seconds. The server will
continue to process the request(s) and may change the state. The rmi level
timeout shall be set by the container only for non-transactional methods
(i.e,
method with tx-attributes of Never or Not-Supported). Please ensure that
the parameter is used only for methods that are idempotent in nature.>

Stand alone client for remote EJB corba error

Regarding problem below, I've checked System env variables
that weblogic server is using for CORBA classes:
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBClass weblogic.corba.orb.ORB
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
But these are server classes and not found in wlclient.jar and wljmsclient.jar. What classes should be used for client? What needs to be set in order to get successful remote RMI/EJB call to weblogic server?
Original post:
I have a stand alone spring client for simple stateless session EJB deployed on weblogic 9.2. I'm using spring (jdk 1.5) to call this remote EJB and the only way I can succeed is to have full weblogic.jar in my bootstrap classpath. Otherwise I get corba error:
CORBA BAD_PARAM 0 No; nested exception is:
org.omg.CORBA.BAD_PARAM: vmcid: 0x0 minor code: 0 completed: No
Interestingly, within same client I have JMS call to weblogic JMS and that fails if weblogic.jar is in boot classpath. Getting rid of weblogic.jar from boot classpath works if I have wlclient.jar and wljmsclient.jar in regular classpath (as per weblogic docs). I would think that for stand alone client all I would need is to weblogic client jars, why should I need to have full weblogic.jar?
I can't get those work together with same classpath. I wonder if anybody has some pointers and/or advice. I was looking to set system parameters for corba for weblogic client that maybe could help:
org.omg.CORBA.ORBClass
org.omg.CORBA.ORBSingletonClass
javax.rmi.CORBA.UtilClass
javax.rmi.CORBA.StubClass
javax.rmi.CORBA.PortableRemoteObjectClass
But I can't find definitive answer.
Regards,
-pp
Edited by mr.papini at 06/28/2007 9:05 AM

I'm stuck exactly with the same issue while trying to port my application from weblogic to jboss.
I tried to specify different ORB implementations (JacORB, OpenORB) for jvm option org.omg.CORBA.ORBClass, but JBoss couldn't get them instantiated. Native Sun implementation which is used in JBoss by default and can be instantiated, apparently is not fully compatible with weblogic security module.
So did you manage to find out the solution?
Edited by DigitalDude at 04/09/2008 11:47 PM

NAT for remote access VPN clients

Hello,
I have a simple remote access VPN setup on a 2811 router. The remote subnet of the clients connecting have access to the local LAN subnet, but I am wondering if it is possible to somehow NAT those remote access users, so that they can go beyond the local LAN, and through the VPN routers outside connection, giving them access to other resources.
The remote subnet would need to be added to the NAT overload pool that the local LAN is on somehow, but since no interface is created, I am unsure where I would need to put "ip nat inside" if it even needs to be done, or if I am just missing something.
I guess really what I want to do is tunnel all traffic, and have that remote client IP translate to the NAT pool on the router for internet access.
Thanks.

Have a look here for solution
http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_configuration_example09186a008073b06b.shtml
Regards

Error when uninstalling App-V RDS client: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder path 'C:' contains an invalid character

Issue: experienced when attempting to uninstall the App-V 5.0 SP2 RDS client.
Event Log: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder
path 'C:' contains an invalid character
Symptoms (when in this current state):
Unable to uninstall the SP2 client
You can upgrade the client (via hotfix) and uninstall the hotfix, but you will not be able to remove the SP2 client
AppvVfs filter driver will not create an instance, therefore applications will not be able to read into existing streamed VFS content, or trigger sparse files to stream content. (you can still stream the content via other means, like the UI or powershell)
Because of the AppvVfs filter driver not instantiating, applications that depend on licences that exist in VFS will not be able to be read causing certain applications to react as if the license does not exist or is an incorrect format

Resolution:
Check for the existence of a hidden folder named %appdata% in the C:\Program Files\Microsoft Application Virtualization\Client folder. (You will need to un-check the folder options box in windows explorer for "Hide
protected operating system files" to see it)
If the hidden %appdata% folder exists, delete it.
Proceed to uninstall the App-V client
After a clean uninstall and removal of remnants of the client, reinstall the client again and apply the latest hotfix available (Hotfix 2 for SP2 at a minimum).

Character encoding problems when using javascript client-sdk for remoting

Hi,
I have recently downloaded LCDS to try. I was interested in using Javascript for remoting. I have a Java-based web application on the server side, and use HTML + Javascript (dataservices-client.js) to send/receive messages asynchronously in AMF format.
I can both send and receive data (not only simple types, but objects with several attributes), however when I receive data from the server side that contains special chars (e.g. á, ï), I get some gibberish in my javascript objects. This is not same when I send content to the server: All special characters are received (printed) correctly in Java (server side).
I inspired my coding with the simple example shown in https://blogs.adobe.com/LiveCycleHelp/2012/07/creating-web-applications-using-html5javascr ipt-remoting-client-sdk-with-livecycle-data-services.html
Is there any bug on the serialization?
My software version is Adobe LiveCycle es_data_services_JEE_4_7_all_win
Java container is WebLogic 11g.
Thanks
=======
Edited Apr 11 2014
In my attempts, I tried using AMFX serialization so that I could see the message in a more comprehensible format inside my browser (eg using firebug). After configuring an HTTP channel and destination in the server side, and adjusting accordingly in the client side code, the Javascript API still sends binary!
Sadly, I concluded that client-SDK isn't mature enough...
By the way, if you send an String like "&aacute" from the server, in the client you get "á"... instead of the raw "&aacute" ... they forgot escaping.

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Remediation for the remote clients

Hi Folks,
One of my main customer concerns is the patch/update process that NAC will force it on the remote clients to do the remediation (Bandwidth issue). The client does not want this update to happen from the HQ; instead it should happen from a cashed local server.
let me know if there a cost effective way to achieve this goal.

You can configure Auto Remediation for all requirement types except File Distribution and Local Check

VPN between XP client IPSec and IOS for remote access

Solved.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Virtual%20Private%20Networks&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd7d54c/0
Hi,
I am trying to implement remote access for XP clients using their IPSec built-in feature and my 805 router configured with dynamic crypto map, but it's not working. Apparently the remote client IKE phase1 is successful but it stucks there.
Does any one face it before.
The client is behind a adsl router but I am allowing the traffic 500 through it and I am not seeing traffic leaving the cisco router. So it's in the 805.
Thanks in advance
David

If you setup a VPN server on your Mac (server) at home, and configure it to root all traffic via the VPN connection by defining the network 0.0.0.0 as being 'private' this will cause all traffic to go via your home Mac and therefore bypass the hospital filter.
You can test this by going to the following address when not connected to the VPN and after connecting to the VPN, the public IP address should change to show when connected to the VPN the public IP address becomes your home address.
See http://www.whatismyip.com (or similar site)
This approach can also get round 'geo-ip' protection. For example if your abroad on holiday and still want to get access to BBC iPlayer or Hulu.

Error retrieving JDBC connection from remote client (WLS 10.0)

Hallo,
I get an error when I try to retrieve a JDBC connection from a WLS datasource using a remote client. My Weblogic server version is: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184
I use the following code to retrieve the JDBC connection:
Hashtable<String,String> ctxEnv = null;
InitialContext ctx = null;
DataSource dataSource = null;
Connection con = null;
ctxEnv = new Hashtable<String,String>();
ctxEnv.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ctxEnv.put(InitialContext.PROVIDER_URL, "t3://localhost:7001");
ctx = new InitialContext(ctxEnv);
dataSource = (DataSource) ctx.lookup("datasources/XXX");
con = dataSource.getConnection();
When I execute this code with the weblogic.jar in the classpath everything works fine. However, when I put the wlfullclient.jar in the classpath which I created using the JAR Builder Tool I get the follwoing error:
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.common.internal.RmiDataSource_1001_WLStub.getConnection(Unknown Source)
at net.schufa.enterprise.utilities.database.test.JDBCSupportTest.test_getConnection_manually(JDBCSupportTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
... 17 more
Caused by: weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:938)
at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1009)
at weblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:452)
at weblogic.rjvm.t3.MuxableSocketT3.hasException(MuxableSocketT3.java:373)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:755)
at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:708)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:307)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
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.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.diagnostics.instrumentation.rtsupport.InstrumentationSupportImpl.getMonitor(InstrumentationSupportImpl.java:54)
at weblogic.diagnostics.instrumentation.InstrumentationSupport.getMonitor(InstrumentationSupport.java:201)
at weblogic.jdbc.rmi.SerialConnection.<clinit>(SerialConnection.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
at java.lang.reflect.Field.getLong(Field.java:527)
at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1586)
at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:408)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:531)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:223)
at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:174)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:435)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:808)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
... 4 more
Can please anyone tell me what's going on there? What really astonishes me is that the class mentioned in the stacktrace is neither present in the wlfullclient.jar nor in the weblogic.jar, but using the weblogic.jar everything works fine. Any hint would be appreciated so much ...
Here is the log written when is created the wlfullclient.jar:
C:\Programme\bea\weblogic10.0\server\lib>java -jar ../../../modules/com.bea.core.jarbuilder_1.0.1.0.jar
Setting Manifest:Class-Path = schema/weblogic-container-binding.jar schema/weblogic-domain-binding.jar schema/diagnostic
s-binding.jar schema/diagnostics-image-binding.jar schema/kodo-conf-binding.jar wlcipher.jar xmlx.jar ojdbc14.jar jconn2
.jar jConnect.jar EccpressoAsn1.jar EccpressoCore.jar EccpressoJcae.jar mysql-connector-java-commercial-5.0.3-bin.jar w
lbase.jar wlutil.jar wlsqlserver.jar wldb2.jar wlsybase.jar wloracle.jar wlinformix.jar wlw-langx.jar ../../common/lib/p
dev.jar debugging.jar wlw-system.jar ../../javelin/lib/javelinx.jar jcom.jar weblogic-L10N.jar
Setting Manifest:Implementation-Vendor = BEA Systems
Setting Manifest:Implementation-Title = Client jar for WebLogic Server 10.0 Thu Oct 18 20:17:44 EDT 2007 1005184
Setting Manifest:Implementation-Version = 10.0.1.0
Creating new jar file: wlfullclient.jar
Integrating jar -->(0)/(0)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(0)/(31337)/(31337)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar -->(0)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
Integrating jar <--(0)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
Integrating jar <--(1)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ja_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ko_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.CN_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.TW_10.0.1.0.jar
Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
Integrating jar <--(1)/(31410)/(73)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
Integrating jar -->(1)/(31410)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(31487)/(77)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
Integrating jar -->(1)/(31487)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
Integrating jar <--(1)/(32047)/(560)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
Integrating jar -->(1)/(32047)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
Integrating jar <--(1)/(32265)/(218)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
Integrating jar -->(1)/(32265)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
Integrating jar <--(1)/(32277)/(12)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
Integrating jar -->(1)/(32277)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
Integrating jar <--(1)/(32294)/(17)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
Integrating jar -->(1)/(32294)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
Integrating jar <--(1)/(32321)/(27)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
Integrating jar -->(1)/(32321)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar <--(1)/(32446)/(125)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar -->(1)/(32446)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
Integrating jar <--(1)/(32895)/(449)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
Integrating jar -->(1)/(32895)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
Integrating jar <--(1)/(32908)/(13)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
Integrating jar -->(1)/(32908)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
Integrating jar <--(1)/(32963)/(55)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
Integrating jar -->(1)/(32963)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger$LoggableMessageSpiImpl.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar <--(1)/(33817)/(854)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
Integrating jar -->(1)/(33817)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
Integrating jar <--(1)/(33901)/(84)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
Integrating jar -->(1)/(33901)/C:\Programme\bea\modules\javax.activation_1.1.jar
Integrating jar <--(1)/(33945)/(44)/C:\Programme\bea\modules\javax.activation_1.1.jar
Integrating jar -->(1)/(33945)/C:\Programme\bea\modules\javax.annotation_1.0.jar
Integrating jar <--(1)/(33958)/(13)/C:\Programme\bea\modules\javax.annotation_1.0.jar
Integrating jar -->(1)/(33958)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
Integrating jar <--(1)/(33964)/(6)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
Integrating jar -->(1)/(33964)/C:\Programme\bea\modules\javax.ejb_3.0.jar
Integrating jar <--(1)/(34022)/(58)/C:\Programme\bea\modules\javax.ejb_3.0.jar
Integrating jar -->(1)/(34022)/C:\Programme\bea\modules\javax.jdo_2.0.jar
Integrating jar <--(1)/(34119)/(97)/C:\Programme\bea\modules\javax.jdo_2.0.jar
Integrating jar -->(1)/(34119)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
Integrating jar <--(1)/(34162)/(43)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
Integrating jar -->(1)/(34162)/C:\Programme\bea\modules\javax.jms_1.1.jar
Integrating jar <--(1)/(34221)/(59)/C:\Programme\bea\modules\javax.jms_1.1.jar
Integrating jar -->(1)/(34221)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
Integrating jar <--(1)/(34319)/(98)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
Integrating jar -->(1)/(34319)/C:\Programme\bea\modules\javax.jws_2.0.jar
Integrating jar <--(1)/(34335)/(16)/C:\Programme\bea\modules\javax.jws_2.0.jar
Integrating jar -->(1)/(34335)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
Integrating jar <--(1)/(34602)/(267)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
Integrating jar -->(1)/(34602)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
Integrating jar <--(1)/(34637)/(35)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
Integrating jar -->(1)/(34637)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
Integrating jar <--(1)/(34730)/(93)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
Integrating jar -->(1)/(34730)/C:\Programme\bea\modules\javax.resource_1.5.jar
Integrating jar <--(1)/(34799)/(69)/C:\Programme\bea\modules\javax.resource_1.5.jar
Integrating jar -->(1)/(34799)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
Integrating jar <--(1)/(34869)/(70)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
Integrating jar -->(1)/(34869)/C:\Programme\bea\modules\javax.transaction_1.1.jar
Integrating jar <--(1)/(34889)/(20)/C:\Programme\bea\modules\javax.transaction_1.1.jar
Integrating jar -->(1)/(34889)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
Integrating jar <--(1)/(34989)/(100)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
Integrating jar -->(1)/(34989)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
Integrating jar <--(1)/(35019)/(30)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\jaxp-api.jar
Ignoring unresolved jarC:\Programme\bea\modules\jax-qname.jar
Ignoring unresolved jarC:\Programme\bea\modules\activation.jar
Ignoring unresolved jarC:\Programme\bea\modules\servlet.jar
Integrating jar -->(1)/(35019)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar <--(1)/(35063)/(44)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar -->(1)/(35063)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
Integrating jar <--(1)/(35110)/(47)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
Integrating jar -->(1)/(35110)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
Ignoring Duplicate Entry javax/xml/namespace/QName.class also in C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar <--(1)/(35167)/(57)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
Integrating jar -->(1)/(35167)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
Integrating jar <--(1)/(35423)/(256)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
Integrating jar -->(1)/(35423)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
Integrating jar <--(1)/(36825)/(1402)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
Integrating jar -->(1)/(36825)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar <--(1)/(36964)/(139)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar -->(1)/(36964)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
Integrating jar <--(1)/(36976)/(12)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
Integrating jar -->(1)/(36976)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Ignoring Duplicate Entry utils/Schema.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry utils/dbping.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCConnectionPoolParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDriverParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertiesBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertyBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCXAParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37133)/(157)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Integrating jar -->(1)/(37133)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/SettableBean.class also in C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/LegalChecks.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/StringHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/XMLHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar <--(1)/(37226)/(93)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
Integrating jar -->(1)/(37226)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/diagnostics/type/UnexpectedExceptionHandler.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37264)/(38)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
Integrating jar -->(1)/(37264)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
Integrating jar <--(1)/(37289)/(25)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
Integrating jar -->(1)/(37289)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
Integrating jar <--(1)/(37335)/(46)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
Integrating jar -->(1)/(37335)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
Integrating jar <--(1)/(37343)/(8)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
Integrating jar -->(1)/(37343)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar <--(1)/(37389)/(46)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean$Helper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanBinder.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanImplBeanInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/BaseModelMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/Commo$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/Commo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoMBeanInstance.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanAttributeInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanConstructorInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanInfoSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanNotificationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanOperationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoOperationsException.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$1.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$VoidValue.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupportBase.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/RequiredModelMBeanWrapper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/SecurityMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/StandardInterface.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/TypedMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/ant/taskdefs/management/commo/antlib.xml also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CustomMBeanImpl.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DiabloCustomMBeanIntf.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/commo.dtd also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/internal/mbean/SecurityReadOnlyMBean.template also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar <--(1)/(37389)/(0)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37548)/(159)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
Integrating jar -->(1)/(37548)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37583)/(35)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
Integrating jar -->(1)/(37583)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/rmi/extensions/server/_HeartbeatHelper_Stub.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37612)/(29)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
Integrating jar -->(1)/(37612)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
Integrating jar <--(1)/(38016)/(404)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
Integrating jar -->(1)/(38016)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
Integrating jar <--(1)/(38217)/(201)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
Integrating jar -->(1)/(38217)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
Integrating jar <--(1)/(38543)/(326)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
Integrating jar -->(1)/(38543)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
Skipping native/aix/ppc64/libwlfileio2.so
Skipping native/aix/ppc/libwlfileio2.so
Skipping native/hpux11/IPF32/libwlfileio2.so
Skipping native/hpux11/IPF64/libwlfileio2.so
Skipping native/hpux11/PA_RISC64/libwlfileio2.sl
Skipping native/hpux11/PA_RISC/libwlfileio2.sl
Skipping native/linux/i686/libwlfileio2.so
Skipping native/linux/ia64/libwlfileio2.so
Skipping native/linux/x86_64/libwlfileio2.so
Skipping native/solaris/sparc64/libwlfileio2.so
Skipping native/solaris/sparc/libwlfileio2.so
Skipping native/solaris/x64/libwlfileio2.so
Skipping native/solaris/x86/libwlfileio2.so
Skipping native/win/32/wlfileio2.dll
Skipping native/win/64/wlfileio2.dll
Skipping native/win/x64/wlfileio2.dll
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(38695)/(152)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
Integrating jar -->(1)/(38695)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
Integrating jar <--(1)/(38728)/(33)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
Integrating jar -->(1)/(38728)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(38943)/(215)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
Integrating jar -->(1)/(38943)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
Skipping native/aix/ppc64/libterminalio.so
Skipping native/aix/ppc/libterminalio.so
Skipping native/hpux11/IPF32/libterminalio.so
Skipping native/hpux11/IPF64/libterminalio.so
Skipping native/hpux11/PA_RISC64/libterminalio.sl
Skipping native/hpux11/PA_RISC/libterminalio.sl
Skipping native/linux/i686/libterminalio.so
Skipping native/linux/ia64/libterminalio.so
Skipping native/linux/s3990/libterminalio.so
Skipping native/linux/x86_64/libterminalio.so
Skipping native/macosx/pps/libterminalio.jnilib
Skipping native/solaris/sparc64/libterminalio.so
Skipping native/solaris/sparc/libterminalio.so
Skipping native/solaris/x64/libterminalio.so
Skipping native/solaris/x86/libterminalio.so
Skipping native/win/32/terminalio.dll
Skipping native/win/64/terminalio.dll
Skipping native/win/x64/terminalio.dll
Ignoring Duplicate Entry weblogic/utils/StackTraceUtilsClient.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(39367)/(424)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
Integrating jar -->(1)/(39367)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
Integrating jar <--(1)/(39415)/(48)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
Integrating jar -->(1)/(39415)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
Integrating jar <--(1)/(39429)/(14)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
Integrating jar -->(1)/(39429)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
Integrating jar <--(1)/(39550)/(121)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
Integrating jar -->(1)/(39550)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
Ignoring Duplicate Entry commonj/timers/CancelTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/StopTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/Timer.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/TimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/TimerManager.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(39581)/(31)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
Integrating jar -->(1)/(39581)/C:\Programme\bea\modules\com.bea.core.weblogic.workmanager_1.0.1.0.jar
Ignoring Duplicate Entry commonj/work/RemoteWorkItem.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/Work.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkCompletedException.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkEvent.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkExcep

Dirk Ludwig wrote:
Joe Weinstein wrote:[...]
Hi. You should open an official support case,
but it may be that we do not support
external client JDBC with the client jar.Actually, I misspoke. I think we do supply a client
jar, and that may be true
what I said, but I see you're making your own. Can
you find out what jar you're
loading the InstrumentationSupport class from? That's
the original location of
the error, and that class doesn't exist in 10.0.Hi Joe, thanks for your reply.
First of all, let me clarify what we did and why we did it: We have a stand-alone client application that needs to communicate with a Weblogic server using the t3 protocol (we don't want IIOP or HTTP tunneling). According to the official BEA documentation (see http://e-docs.bea.com/wls/docs100/client/basics.html and http://e-docs.bea.com/wls/docs100/client/t3.html) we needed to create the wlfullclient.jar file. We did this using the Weblogic JAR Builder Tool (see http://e-docs.bea.com/wls/docs100/client/jarbuilder.html). Unfortunatley we discovered the problem mentioned in my original post when we tried to run the client with that wlfullclient.jar.
Regarding your classloading question: The InstrumentationSupportImpl class is located in the wlfullclient.jar, so it does exist in WLS 10.0 (it is also contained in the weblogic.jar). Unfortunately this JAR does not contain the required class "weblogic.diagnostics.instrumentation.InstrumentationDebug". I searched for this class and found it in the OSGI module "com.bea.core.diagnostics.instrumentor_1.0.1.0.jar" shipped with the Weblogic server. Obviously the JAR Builder Tool did not include the contents of this OSGI bundle into the wlfullclient.jar. I tried to include this OSGI bundle into the classpath of the client app manually (just for testing purposes), but this onyl resultet in another NoClassDefFoundError. This time the class "com.bea.objectweb.asm.Constants" could not be found.
What astonishes me is the fact that the connection retrieval works fine when we only have the weblogic.jar in the client applications classpath, but fails when we have the wlfullclient.jar in the classpaht. It seems that the t3 communication is handled completely different, depending on what JARs I have in the classpath. Also, JMS communication works fine in both cases (i.e. for the weblogic.jar and the wlfullclient.jar). The only thing that causes problems (at least as far as we have discovered) is getting a JDBC connection from a datasource. I simply fail to see why this is the case.
Best regards,
DirkInteresting. I hope the official support case solves your problem.
I would like to dig further, but it's too far afield for me with
the workload I have at the moment.
Joe

Accessing EJB components from a Remote Client

Hi,
When an web component (Servlet/JSP/Java appl.) need to invoke an business method from an EJB, it first lookup for the registered name from the Application server and obtain the remote reference i.e. the EJB Remote interface. To do this, the client must have got the client-jar file containing the stub. Now, if in a distributed environment, my client is in a different machine and need to access the J2EE server across network, what would be the scenereo.
Is it so, for every EJB the client need to call, it must have got the client-jar file in it's local classpath ? this seems to be not at all feasible.
Is it so, the client loads the Stub acroos the network while obtaining the remote reference ?
Please inform me, what actually happens when a client invokes a EJB call deployed in any application server, across the network !!!
Regards,
Kaustuv Bhattacharya

Greetings,
Hi,
When an web component (Servlet/JSP/Java appl.) need to
invoke an business method from an EJB, it first lookup
for the registered name from the Application server
and obtain the remote reference i.e. the EJB Remote
interface. To do this, the client must have got the
client-jar file containing the stub. Now, if in aFor web components running in the same application context, the client-jar is not required - the server-jar also contains the necessary stubs. However, for application clients, the client-jar is required...
distributed environment, my client is in a different
machine and need to access the J2EE server across
network, what would be the scenereo.The client-jar must be distributed with your application, or accessible from a shared network resource, either way...
Is it so, for every EJB the client need to call, it
must have got the client-jar file in it's local
classpath? this seems to be not at all feasible.Yes, the client-jar must be included in the client's classpath... Why isn't it feasible? The client-jar(s) can easily be distributed with your application. The necessity to include them in the application's CLASSPATH does not necessitate their inclusion into the client-machine's CLASSPATH. Simply include the jar(s) as part of the JVM's -cp option.
Is it so, the client loads the Stub acroos the network
while obtaining the remote reference?A copy of the remote interface's stub file is included for casting purposes. However, a copy of the stub containing the correct communication parameters (such as TCP/IP port number, reference ID, etc. per vendor implementation...), for the remote reference does get downloaded.
Please inform me, what actually happens when a client
invokes a EJB call deployed in any application server,
across the network !!!The exact details are vendor specific and depends on the actual protocol in use by the stub-layer. However, the general behaviour is in-line with RMI(-IIOP) communication.
Regards,
Kaustuv BhattacharyaRegards,
Tony "Vee Schade" Cook

Remote Client Copy Errors

Dears,
Today I am going to do remote client copy from PRD to QAS.
For it yesterday i scheduled Test run in simulation mode.As i am having two CPU for both Dev and PRD so I scheduled it with 6 Parallel Processes.
But my Test run failed with errors:
Copy Type                   Remote copy
                                  Test Run
Profile                          SAP_ALL
Status                          Ended with Errors
User                             SAP*
Start on                        14.08.2008 / 01:30:54
Last Entry on                14.08.2008 / 05:57:54
Statistics for this Run
- No. of Tables                 30,806 of       30,808
- Deleted Lines                     15
- Copied Lines               72748,776
Warnings and Errors
Table/Object       Component                Error
BKPF                 FI                       Read or Conversion Error
BSIS                   FI                       Read or Conversion Error
Thus showing read or Conversion Error in these two tables.
In System log of source system I also see these error:
ORA-01652 unable to extend temp segment by 2560 in PSAPTEMP
Database Error 1652 at SEL access to table BKPF.
Database Error 1652 at SEL access to table BSIS.
Please suggest how to resolve the issue.
Shivam
Edited by: Shivam Mittal on Aug 14, 2008 6:08 AM

Hello Shivam
How is your remote copy going on?
Did you increase the size of psap temp in order to carryon with the copy?
Your Source system is PRD system.Are you doing this copy while users are using the PRD system.
If not then this may not be result of client copy? or
if no user is logged in in your PRD system,You have to decide if this is due to client copy.
Let me know what corrective measure taken by you to completed the remote client copy?
normally we dont get this dump in the source system but I have psaptemp around 30 GB or more in al my systems so may be this might have not surfaced in my environment.
Thanks
Amit

Classpath for remote client

Similar Messages

Maybe you are looking for