RMI in 1.3.1 vs. 1.1.7 - code that works in 1.1.7 fails in 1.3.1
I have an RMI server and client that works great under JRE 1.1.7. At initialization, the server installs RMISecurityManager, creates a registry using LocateRegistry.createRegistry(), creates a remote-server object and registers it in the registry. This set-up takes roughly 1 second. Clients are able to locate the remote object by its registry entry and make remote calls without trouble.
Under JRE 1.3.1_03, this same code, unchanged, is totally worthless. The server initialization takes nearly 3 minutes. The LocateRegistry.createRegistry() call alone takes 40 seconds. Client code takes 2 minutes to locate the remote object by its registry entry, and then all remote calls fail with this exception: java.rmi.UnmarshalException: invalid method hash.
I realize that "invalid method hash" is supposed to mean that the remote interface used by the client is out of synch with that used by the server, but I can't figure out how this might be. I've deleted all .class files from my project and rebuilt entirely from scratch. Everything compiles cleanly.
I'm running this under NT 4.0 Workstation SP6. My code is built with Visual Cafe 4.1. (Please don't hold that against me. I know Cafe sucks, but it did produce working code.) I've tried switching Cafe's VM to 1.3 but that didn't help. I've tried creating new stubs manually with "rmic -vcompat" but those stubs are identical to the ones created by Cafe.
When I threw out 1.3.1_03 and reinstalled JRE 1.1.7, all my code worked again.
Any ideas? I'm stumped and will appreciate any suggestions.
-hersker
Progress report for those who might be interested:
* Persuade Visual Cafe to not generate ANY stubs or skeletons.
Either use -normi with the sj.exe compiler,
or change the project options to use the Sun compiler.
* Use JDK's rmic with -v1.2 to generate the stubs (no skeletons)
* Create the RMI server's Jar directly with JDK's jar utility.
Cafe's archiver appears to be stuck on having skeletons
and can no longer be used for the server Jar. It can still be
used to create the client Jars, however.
This produces an RMI server and client that run under 1.3.1
without the "invalid method hash" UnmarshalExceptions.
Of course, it will no longer run under 1.1.x -- <sigh>.
But the performance problems remain:
* LocateRegistry.createRegistry() takes 40 seconds
* Client code takes 2 minutes to locate the remote object by its registry entry
I'd welcome suggestions from the experts out there.
-hersker
Similar Messages
-
RMI Objects running on single cluster memb. only avail on that
Hi,
My setup:
An RMI object shall be bound to a single cluster member.
Only one cluster member has therefore the startup entry. The
RMI Object is thus instantiated only in this one cluster member.
I now expected to have the weblogic.rmi.myclass JNDI entry
replicated into all cluster member's jndi context (thus having
a simple way for implementing a singleton? does this work??).
All clients, which are loadbalanced to a cluster-member
that does not the startup entry will fail to lookup the rmi object's
entry
with the following.
Why is the entry not replicated into the other machines naming context?
javax.naming.NameNotFoundException: 'mybindname'; remaining name
'mybindname'
at
weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
at
weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
at
weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
at mypackage.MyClass.lookup(...);
Thank you for any help on this & happy new year
Toby
We too are looking to achieve the same thing. Anyone know the answer to
Tobias's question?
david
Tobias Christen wrote:
> Hi,
>
> My setup:
> An RMI object shall be bound to a single cluster member.
> Only one cluster member has therefore the startup entry. The
> RMI Object is thus instantiated only in this one cluster member.
> I now expected to have the weblogic.rmi.myclass JNDI entry
> replicated into all cluster member's jndi context (thus having
> a simple way for implementing a singleton? does this work??).
>
> All clients, which are loadbalanced to a cluster-member
> that does not the startup entry will fail to lookup the rmi object's
> entry
> with the following.
>
> Why is the entry not replicated into the other machines naming context?
>
> javax.naming.NameNotFoundException: 'mybindname'; remaining name
> 'mybindname'
> at
> weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
> at
> weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
> at
> weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
> at mypackage.MyClass.lookup(...);
>
> Thank you for any help on this & happy new year
> Toby
David Michaels <[email protected]>
Director of Technology
ShockMarket Corporation (650) 330-4665
[david.vcf]
-
We need to access stored Java classes inside the Oracle 8i (8.1.7) database using RMI from a remote machine. Is this possible? How?
Basically we have stored PL/SQL procedures/packages we want to create interfaces for (Using JPiblisher) and access them remotely via RMI.We need to access stored PL/SQL packages from outside the database via RMI. That's the requirement. First we need to wrap the PL/SQL packages with Java classes (JPublisher can help us here). Then there are, in my opinion, three possible ways to achieve this:
- direct Java RMI calls
- CORBA
- EJB
Because I need to evaluate all ways, I am just trying the 1st ( I know, not scalable) way - direct RMI calls. I can do a direct RMI call from the database to an outside server. That works fine. My problem is the other way round, to call an object inside 8i. I understand that using CORBA or EJB the Oracle ORB is used (handled by the TNS Listener). Using a direct RMI call I would need to run the RMIREGISTRY program (inside or outside 8i?)...But I have no clue, how this could work. -
Trying to find some examples of using JDK 1.5 and the SslRMIServerSocketFactory, SslRMIClientSocketFactory.
Anyone help?If you check out the java.rmi.server.RMISocketFactory class, it has a static setSocketFactory(RMISocketFactory) method. However, neither of the SSLRMI Socket Factory classes are actually a RMISocketFactory as that requires implementation of both the RMIClientSocketFactory and RMIServerSocketFactory interfaces. What you could do is create your own class that extends RMISocketFactory. This is an abstract class and has two abstract methods. Simply wrap the SSLRMI Socket Factory classes in your own class and return whatever Socket they would return. That should do it.
I have not done this myself with the new SSL RMI socket factories, but I have done something similar and that works great. -
Why do I get a ClassCastException?
Hello!
I'm playing around with hibernate, axis2 and Weblogic 8.1.6 and I got I really tricky problem.
My Weblogic 8.1.6 got consist of 3 servers.
1 Adminserver (myserver)
1 Managedserver (ejbserver)
1 Managedserver (webserviceserver)
My play_around_example is built around a database called names in a mysql-databas.
To access data I got a package called nameshibernate.jar, that works fine used from an standalone application called namesjavaapplication.jar.
(namesjavaapplication->nameshibernate->database)
I also got an ejb in a packaged called namesejb.jar that uses the nameshibernate.jar. The namesejb.jar is deployed under "Ejb Modules" and the target is "ejbserver". If I call the ejb from my standalone application called namesjavaapplication.jar it works fine.
(namesjavaapplication->namesejb->nameshibernate->database)
I also got an webserviceapplication that uses axis2 in a aar-file called nameswebservice.aar. This application uses the namesejb.jar. The Axis2-server is deployed in the server under "Web Application Modules" and the target is "webserviceserver". In this Axis2-server the nameswebservice.aar is deployed. This i supposed to work like:
(namesjavaapplication->nameswebservice->namesejb->nameshibernate->database)
If I call the webservice from my standalone application called namesjavaapplication.jar I get a calsscast exception:
java.lang.ClassCastException: Cannot narrow remote object to namesejb.client.NameManagerEJBHome
I really can not find out the problem since it works fine if I go directly to the ejb like:
(namesjavaapplication->namesejb->nameshibernate->database)
Below is the method inside my standalone application that calls the ejb directly.
This is the code that works:
(namesjavaapplication->namesejb->nameshibernate->database)
public void getNamesEJB() throws Exception
try
System.out.println("getNamesEJB start");
Context context = getWebLogicInitialContext();
Object object = context.lookup("namesejb/client/NameManagerEJBHome");
System.out.println("\t1: " + object.getClass().getName());
Class c = Class.forName("namesejb.client.NameManagerEJBHome");
System.out.println("\t2: " + c.getName());
System.out.println("\t3: " + NameManagerEJBHome.class.getName());
System.out.println("\t4: " + (object instanceof NameManagerEJBHome));
System.out.println("\tjava.class.version: " + System.getProperty("java.class.version"));
System.out.println("\tjava.class.path: " + System.getProperty("java.class.path"));
System.out.println("\tjava.library.path: " + System.getProperty("java.library.path"));
System.out.println("\tjava.compiler: " + System.getProperty("java.compiler"));
System.out.println("\tjava.ext.dirs: " + System.getProperty("java.ext.dirs"));
System.out.println("\tuser.dir: " + System.getProperty("user.dir"));
System.out.println("\tjava.home: " + System.getProperty("java.home"));
if(object instanceof namesejb.server.NameManagerSessionBean)
System.out.println("\t"+ ((namesejb.server.NameManagerSessionBean)object).getSerialVersionUID() );
else
System.out.println("\tNOT instanceof NameManagerSessionBean");
NameManagerEJBHome nameManagerEJBHome = (NameManagerEJBHome)PortableRemoteObject.narrow(object, NameManagerEJBHome.class);
NameManangerEJBObject nameManangerEJBObject = nameManagerEJBHome.create();
String nameString = "";
List names = nameManangerEJBObject.getNames();
for (int i = 0; i < names.size(); i++)
Name theName = (Name) names.get(i);
nameString = nameString + "\n" + theName.getName();
textAreaEJB.setText(nameString);
catch(RemoteException e)
e.printStackTrace();
catch(NamingException e)
e.printStackTrace();
catch(Exception e)
e.printStackTrace();
From this I get this output:
getNamesEJB start
1: namesejb.server.NameManagerSessionBean_o0oo54_HomeImpl_816_WLStub
2: namesejb.client.NameManagerEJBHome
3: namesejb.client.NameManagerEJBHome
4: true
java.class.version: 50.0
java.class.path: namesjavaapplication.jar
java.library.path: /home/fredrik/Applications/Java/Java_ee_sdk_5-04/jd k/jre/lib/i386/server:/home/fredrik/Applications/Java/Java_ee_sdk_5-04 /jdk/jre/lib/i386:/home/fredrik/Applications/Java/Java_ee_sdk_5-04/jdk /jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
java.compiler: null
java.ext.dirs: /home/fredrik/Applications/Java/Java_ee_sdk_5-04/jdk/jr e/lib/ext:/usr/java/packages/lib/ext
user.dir: /home/fredrik/eclipse_workspace/namesjavaapplication
java.home: /home/fredrik/Applications/Java/Java_ee_sdk_5-04/jdk/jre
NOT instanceof NameManagerSessionBean
Below is my methods inside the ejb:
public void ejbCreate()
try
Class c = Class.forName("namesejb.client.NameManagerEJBHome");
System.out.println("1: " + c.getName());
System.out.println("2: " + NameManagerEJBHome.class.getName());
System.out.println("java.class.version: " + System.getProperty("java.class.version"));
System.out.println("java.class.path: " + System.getProperty("java.class.path"));
System.out.println("java.library.path: " + System.getProperty("java.library.path"));
System.out.println("java.compiler: " + System.getProperty("java.compiler"));
System.out.println("java.ext.dirs: " + System.getProperty("java.ext.dirs"));
System.out.println("user.dir: " + System.getProperty("user.dir"));
catch(Exception e)
System.out.println(e.getMessage());
e.printStackTrace();
public ArrayList getNames() throws Exception {
Class c = Class.forName("namesejb.client.NameManagerEJBHome");
System.out.println("4 " + c.getName());
NameManager nameManager = new NameManager();
return nameManager.getNames();
From these methods I get this output from the ejbserver:
1: namesejb.client.NameManagerEJBHome
2: namesejb.client.NameManagerEJBHome
java.class.version: 48.0
java.class.path:/home/fredrik/Applications/bea/jrockit81sp6_142_10/lib/tools.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/weblogic_sp.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/weblogic.jar::/home/fredrik/Applications/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/home/fredrik/Applications/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/rt.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/webservices.jr:
java.library.path:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/i386/jrockit:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/i386:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/../lib/i386:/home/fredrik/Applications/bea/weblogic81/server/lib/linux/i686:/home/fredrik/Applications/bea/weblogic81/server/lib/linux/i686/oci920_8
java.compiler: null
java.ext.dirs: /home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/ext
user.dir: /home/fredrik/Applications/bea/user_projects/domains/mydomain
4 namesejb.client.NameManagerEJBHome
THIS WORKS FINE
Below is the method inside my webservice that calls the ejb directly.
This is the code that throws the Exception:
(namesjavaapplication->nameswebservice->namesejb->nameshibernate->database)
public String getNamesWSEJB() throws Exception
String errorMessage = "Error: ";
try
System.out.println("getNamesWSEJB start");
Context context = getWebLogicInitialContext();
Object object = context.lookup("namesejb/client/NameManagerEJBHome");
System.out.println("\t1: " + object.getClass().getName());
Class c = Class.forName("namesejb.client.NameManagerEJBHome");
System.out.println("\t2: " + c.getName());
System.out.println("\t3: " + NameManagerEJBHome.class.getName());
System.out.println("\t4: " + (object instanceof NameManagerEJBHome));
System.out.println("\tjava.class.version: " + System.getProperty("java.class.version"));
System.out.println("\tjava.class.path: " + System.getProperty("java.class.path"));
System.out.println("\tjava.library.path: " + System.getProperty("java.library.path"));
System.out.println("\tjava.compiler: " + System.getProperty("java.compiler"));
System.out.println("\tjava.ext.dirs: " + System.getProperty("java.ext.dirs"));
System.out.println("\tuser.dir: " + System.getProperty("user.dir"));
System.out.println("java.home: " + System.getProperty("java.home"));
if(object instanceof namesejb.server.NameManagerSessionBean)
System.out.println("\t"+ ((namesejb.server.NameManagerSessionBean)object).getSerialVersionUID() );
else
System.out.println("\tNOT instanceof NameManagerSessionBean");
NameManagerEJBHome nameManagerEJBHome = (NameManagerEJBHome)PortableRemoteObject.narrow(object, NameManagerEJBHome.class);
NameManangerEJBObject nameManangerEJBObject = nameManagerEJBHome.create();
String nameString = "";
List names = nameManangerEJBObject.getNames();
for (int i = 0; i < names.size(); i++)
Name theName = (Name) names.get(i);
nameString = nameString + "\n" + theName.getName();
return nameString;
catch(RemoteException e)
errorMessage = errorMessage + e.getMessage();
e.printStackTrace();
catch(NamingException e)
errorMessage = errorMessage + e.getMessage();
e.printStackTrace();
catch(Exception e)
errorMessage = errorMessage + e.getMessage();
e.printStackTrace();
return errorMessage;
1: namesejb.server.NameManagerSessionBean_o0oo54_HomeImpl_816_WLStub
2: namesejb.client.NameManagerEJBHome
3: namesejb.client.NameManagerEJBHome
4: false
java.class.version: 48.0
java.class.path:/home/fredrik/Applications/axis2-1.3/lib/jalopy-1.5rc3.jar:/home/fredrik/Applications/bea/jrockit81sp6_142_10/lib/tools.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/weblogic_sp.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/weblogic.jar::/home/fredrik/Applications/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/home/fredrik/Applications/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/rt.jar:/home/fredrik/Applications/bea/weblogic81/server/lib/webservices.jar:
java.library.path: /home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/i386/jrockit:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/i386:/home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/../lib/i386:/home/fredrik/Applications/bea/weblogic81/server/lib/linux/i686:/home/fredrik/Applications/bea/weblogic81/server/lib/linux/i686/oci920_8
java.compiler: null
java.ext.dirs: /home/fredrik/Applications/bea/jrockit81sp6_142_10/jre/lib/ext
user.dir: /home/fredrik/Applications/bea/user_projects/domains/mydomain
NOT instanceof NameManagerSessionBean
java.lang.ClassCastException: Cannot narrow remote object to namesejb.client.NameManagerEJBHome
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteObjectDelegateImpl.java:242)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at nameswebservices.NamesWebService.getNamesWSEJB(NamesWebService.java:49)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:165)
at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:98)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
I really can not find out what might be the problem since it works to call tje ejb from a standalone application.
The "same" code executed from a webservice throws the exception.
One strange thing that I notice is that from the standalone the java.class.version gets 50.0 and from the webserver it gets 48.0 But the standalone uses 1.6 when I run it and the Weblogic uses 1.4. (I do not think that weblogic can run with 1.6)
Pretty long thread but I hope for some mercy!
Best regards
FredrikHello Thok, this code is from a quistion in a studybook for preparation of the SCJP 5.0 exam.
When i compile i get this warning:
Shapes.java:13: warning: [unchecked] unchecked cast
found : java.util.ArrayList
required: java.util.ArrayList<generics.Rectangle>
ArrayList <Rectangle> c = (ArrayList<Rectangle>) b;
^
1 warningWhen running this line causes an exception:
for ( Rectangle o : c){My questions are
How do i re-write the code so that i will get an warning and exception free program?
Tnx Auke -
JSP Object Cannot be resolved to a type
hi!
i'm new to the jsp business nd i tried to create a 3 tier program with a web interface where the web pulls out data from the data base through RMI. here UserDataObject is the interface that extends Remote interface.
However this same code works perfectly when i run it from a servlet. but it dusnt seem to work with JSP...i use tomcat 5.5 and everything is in place..(WEB-INF etc)
this is the code:
<%
try {
UserDataObject udo = (UserDataObject) Naming.lookup("//localhost:1099/Item");
Vector v = udo.getByStatus(username,0);
} catch (NotBoundException e) {
e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates.
} catch (SQLException e){
e.printStackTrace();
%>and this is the error i get!
An error occurred at line: 110 in the jsp file: /selling.jsp
Generated servlet error:
UserDataObject cannot be resolved to a typeI am quite confident that there's nothing wrong with RMI, since data runs back and forth in the servlets and the other application i made..
my problem is How come the same code that works perfectly in servlet doesnt work in jsp...?
plz help me out
thnx
nandunwell...thnx for all the replies...how ever i did solve this problem after struggling with it for about 8 hrs...
thr trick is to put the class UserDataObject in a pakcage and import it at the top of the jsp page..
ie.
<%@ page import = "rmi.UserDataObject"%> etc...
rmi is the package i stuffed it in...
hope some1 finds this helpful and think good thoughts about me!
cheers
nandun -
Livecycle/Dataservices 2.6.1 [Transient] property
Hi Guys and Girls
I am using livecyle 2.6.1 with AIR 2.0.2 and a java backend, with the flex 3.4 SDK.
I have a managed collection with a property that has a [Transient] variable set which is used as a flag for products that have been ordered.This variable is only used locally.
This collection/dataservice connection has been set to autoSync enabled, however when I change this flag the collection is updated to the server, is there a way to have this changed to not update to the collection to the server when this flag is set.
I thought (wrongly apparently) having a property denoted as [Transient] was to avoid this default behaviour.
[Transient]
public var isOrdered:Boolean=false;
Any help you can offer would be much appreciated.
Cheers
JasenDustin,
Without the ColdFusion based data management destination defined on the LCDS server, the destination will not show up in the RMI registry. It is only the CF adapter code that does this. The 'stock' LCDS adapter does not support invoking via RMI the way the CF version does.
I would recommend you run the LCDS MessageBrokerServlet inside the ColdFusion web application. This will give you two things:
1. You will not have the overhead of RMI between CF and LCDS as they will share the same VM (better performance!).
2. You will be able to use the CF Data Management Gateway to pass messages to Java-based destinations. The APIs the gateway uses should work fine with either CF or Java based Data Management destinations.
The CF/LCDS integration doesn't support what you are trying to do when you run two seperate instances. -
LiveCycle 2.6.1 Data Management with The ColdFusion 8.0 DataManagement Event Gateway Issue
Hello all,
I've recently been developing a project that involves sending out events from ColdFusion to LiveCycle 2.6.1 using the Data Management event gateway to Flex 4.0 clients (LiveCycle and ColdFusion are on different Instances, but the same server). To begin with, I used ColdFusion assemblers, DAO's, and models and everything worked fine locally. After deploying this setup to a beta site, I decided that this setup would be very troublesome in terms of configuring clustered instances across multiple servers. I then decided to convert my assemblers, DAO's, and models to Java. The conversion went well and the flex clients see the exact same data as they did with the ColdFusion adapter.
Once I tried to send an update through from my ColdFusion application to a Flex client, I get an error stating that:
"Unable to find the Flex adapter for destination My_Dest in the RMI registry on localhost:1099.The Flex adapter may not be running or the destination may be incorrect."
After seeing this error, downloaded a Java-based RMI inspector to see what was going on. To get a good idea of what was happening when the ColdFusion adapter was being used, I switched my data-management-config file back to the CF adapter. I noticed that the RMI entry was as follows:
localhost:1099/cfdataserviceadapter/My_Dest
localhost:1099/cfassembler/my_cf_instance
Once I gathered this data as the base, I converted back to the Java adapter in my data-management-config file, restarted the servers, and ran the RMI inspector again. Only the "localhost:1099/cfassembler/my_cf_instance" was showing. (This one shows because I have "Enable Remote Adobe LiveCycle Data Management Access" checked in my CF instance's CF Admin -> Flex Integration). Since I don't need this checked anymore, I unchecked it and re-ran the RMI inspector. As it should, the "localhost:1099/cfdataserviceadapter/My_Dest" went away. Since no destination shows up, it means that the Flex adapter isn't registering my "my_Dest" destination with RMI. Since it isn't registered, I can't see it when I try to send a message through the CF Data Management event gateway.
Can anyone help me out here? I certainly may be missing something when it comes to RMI (I don't work with Java very often). Any advice would be greatly appreciated!
Thank you,
Dustin BlomquistDustin,
Without the ColdFusion based data management destination defined on the LCDS server, the destination will not show up in the RMI registry. It is only the CF adapter code that does this. The 'stock' LCDS adapter does not support invoking via RMI the way the CF version does.
I would recommend you run the LCDS MessageBrokerServlet inside the ColdFusion web application. This will give you two things:
1. You will not have the overhead of RMI between CF and LCDS as they will share the same VM (better performance!).
2. You will be able to use the CF Data Management Gateway to pass messages to Java-based destinations. The APIs the gateway uses should work fine with either CF or Java based Data Management destinations.
The CF/LCDS integration doesn't support what you are trying to do when you run two seperate instances. -
Problems setting up foreign provider
Hi, I'm trying to get my Weblogic 8.1 server to talk to a remote Websphere server (this is the trial installation of WS so it's not a full version of MQ).
Basically I set up a connection factory and topic on the websphere machine. THen in Weblogic I created a foreign server containing the initial context factory com.ibm.websphere.naming.WsnInitialContextFactory and the provider url iiop://xxx.xx.xx.xx:2809 (no user/password). Then I proceded to setup a connection factory and a topic.
I have a stand-alone client running outside the server that tries to connect to the local name of the foreign connection factory but I get an InvalidName exception when it tries to look up the connection factory. From teh stack trace it looks like it is actually trying to look it up on the foreign server but failing.
portion of config.xml that defines the foreign JMS server:
<ForeignJMSServer ConnectionURL="iiop://10.0.00.00:2809"
InitialContextFactory="com.ibm.websphere.naming.WsnInitialContextFactory"
JNDIProperties="" Name="websphere" Targets="myServer">
<ForeignJMSConnectionFactory LocalJNDIName="com.abc.def.WSCF"
Name="Websphere CF" RemoteJNDIName="com.abc.def.connectionFactory"/>
<ForeignJMSDestination LocalJNDIName="com.abc.def.WSXYZ"
Name="WSXYZ" RemoteJNDIName="XYZ"/>
</ForeignJMSServer>
In the code I set up the initial context with a provider URL that points to the local server (same machine actually) and the standard weblogic initial context factory class.
The code is very simple JMS client code that works when talking to the local server with a normal connection factory etc and a local topic but when I change the connection factory to "com.abc.def.WSCF" and the topic to "com.abc.def.WSXYZ" I get the following error:
javax.naming.InvalidNameException: Exception in lookup. [Root exception is org.omg.CosNaming.NamingContextPackage.InvalidName: IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:47)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:235)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at kmr.jms.PublishToTopic.main(PublishToTopic.java:95)
Caused by: org.omg.CosNaming.NamingContextPackage.InvalidName: IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0
at weblogic.iiop.OutboundRequestImpl.sendReceive(OutboundRequestImpl.java:187)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.corba.cos.naming.NamingContextAny_IIOP_WLStub.resolve_any(Unknown Source)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 3 more
Caused by: org.omg.CosNaming.NamingContextPackage.InvalidName: IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0 IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0
at org.omg.CosNaming.NamingContextPackage.InvalidNameHelper.read(InvalidNameHelper.java:60)
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:324)
at weblogic.iiop.IIOPInputStream.readWithHelper(IIOPInputStream.java:2071)
at weblogic.iiop.IIOPInputStream.read_IDLEntity(IIOPInputStream.java:2060)
at weblogic.iiop.IIOPInputStream.read_IDLEntity(IIOPInputStream.java:2051)
at weblogic.iiop.ReplyMessage.getThrowable(ReplyMessage.java:360)
at weblogic.iiop.InboundResponseImpl.getThrowable(InboundResponseImpl.java:59)
at weblogic.iiop.OutboundRequestImpl.sendReceive(OutboundRequestImpl.java:174)
... 7 more
I took the iiop stuff in the stack trace to mean that it is actually trying to go over to the websphere server and do the lookup but it's not working for some reason...
Can anybody give me some suggestions on what to try??Thanks for the response Tom. Here is the classpath:
/h/COTS/BEAPLT/weblogic81/server/lib/webservices.jar:/h/COTS/BEAPLT/weblogic81/server/lib/ejbgen.jar::::/h/COTS/BEAPLT/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/h/COTS/BEAPLT/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/h/COTS/BEAPLT/weblogic81/common/eval/pointbase/lib/pbtools44.jar::/utils_common.jar:/h/COTS/BEAPLT/jdk142_06/lib/tools.jar:/h/COTS/BEAPLT/weblogic81/server/lib/weblogic_sp.jar:/h/COTS/BEAPLT/weblogic81/server/lib/weblogic.jar
wlclient.jar is the thin one right? I don't see any here that are thin and the thick one is at the end.
Also, I'm using "t3://localhost:80" for the provider url into weblogic (I know 80 is not default but this server was configured ot use 80 for some reason).
Thanks again for the response - any addtnl info is greatly appreciated. -
Java.io.NotSerializableException: weblogic.ejb20.internal.EntityEJBContextImpl
Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
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:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>Ignacio,
6.1 used pass-by-reference by default, so parameters to beans were
passed by reference.
It's very likely that you are getting this error because in 8.1 this default
was turned off. This causes serialization of parameters by default and
that's why your code that worked started failing - you just did not know
that you were passing non-serializable objects around.
To fix this you could either turn on the pass-by-reference explicitly and/or
find out where your code is passing non-serializable objects. This is a useful
exercise anyways.
Hope this helps.
Regards,
Slava Imeshev
"Ignacio G. Dupont" <[email protected]> wrote in message news:41b8c93f@mail...
Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
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:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> -
Anyone get CLOB.createTemporary to work in WebLogic w/ Ora 9.0.1?
I've got code that works in java for temporary CLOB in Oracle 9.0.1. It works using JDBC Client API or Oracle connection pooling. But when I deploy to WebLogic App Server, I get
"java.lang.reflect.InvocationTargetException null" on the statement:
myClob = CLOB.createTemporary(conn, false, CLOB.DURATION_SESSION);
I read that temporary clob was an Oracle extension. That would lead one to believe that WebLogic may not support it. And I tried tweeking classpath/path to use Oracle's jars first, etc. I've also tried different ways of connecting: JDBC Client, straight RMI, and JNDI lookups, trying to get around "WebLogic"... Is this a losing battle and do I have to modifiy my code to use the EMPTY_CLOB() functions, or has someone gotten this to work? THANKS!I've talked with BEA on this issue. They say that the CLOB.createTemporary() method signature indicates that it takes a
generic JDBC object, but it in fact takes an Oracle-specific object. They say "Oracle is lying to us" and say that
as a result, my code will not work if using a WebLogic Connection Pool. I realize the risks of using vendor-specific
extension methods, but I would think that if I configure the WL app server to use the oracle classes12.zip and put it in
front of CLASSPATH, etc. that this would work. It does not, with the BEA reason stated above. I really like this
CLOB.createTemporary method and refuse to change my code. Any words of wisdom, especially from an
Oracle insider? Thanks!
I've got code that works in java for temporary CLOB in Oracle 9.0.1. It works using JDBC Client API or Oracle connection pooling. But when I deploy to WebLogic App Server, I get
"java.lang.reflect.InvocationTargetException null" on the statement:
myClob = CLOB.createTemporary(conn, false, CLOB.DURATION_SESSION);
I read that temporary clob was an Oracle extension. That would lead one to believe that WebLogic may not support it. And I tried tweeking classpath/path to use Oracle's jars first, etc. I've also tried different ways of connecting: JDBC Client, straight RMI, and JNDI lookups, trying to get around "WebLogic"... Is this a losing battle and do I have to modifiy my code to use the EMPTY_CLOB() functions, or has someone gotten this to work? THANKS! -
Hi
I have multiple clients accessing EJBs deployed on WebLogic4.5.1
When I run the clients concurrently, the server throws the following
exception and closes the client connection. This occurs with ServicePacks 7
and 9!!! Can you please help me?
Regards,
Madhavi.
The exception -
Tue Nov 07 10:33:04 MST 2000:<E> <RJVM> java.net.SocketException: blocking
winsock call in progress: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(Compiled Code)
at weblogic.socket.MBuf.writeTo(Compiled Code)
at weblogic.socket.JVMSocketT3.sendMsg(Compiled Code)
at weblogic.rjvm.ConnectionManager.sendMsg(Compiled Code)
at weblogic.rjvm.SlidingWindow.sendMsg(Compiled Code)
at weblogic.rjvm.RJVMImpl.send(Compiled Code)
at weblogic.rjvm.RJVMImpl$OutStream.flushAndSendRaw(Compiled Code)
at weblogic.rjvm.RJVMImpl$OutStream.flushAndSend(Compiled Code)
at weblogic.rjvm.RJVMImpl$OutStream.sendOneWay(RJVMImpl.java:887)
at
weblogic.rmi.extensions.AbstractRemoteObjectReference$BasicOutgoingRequest.s
endOneWay(AbstractRemoteObjectReference.java:335)
at weblogic.rmi.extensions.BasicRequest.sendOneWay(BasicRequest.java:36)
at
weblogic.rmi.internal.DGCServer_WLStub.renewLease(DGCServer_WLStub.java:121)
at weblogic.rmi.internal.DGCClientImpl$HeartBeat.execute(Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)YEAHHH
God bless these forums !!! thats been bugging me for ages - youve no idea , so my code that works now looks like :
public class SSLSocketClient {
public static void main(String[] args) throws Exception {
System.setProperty
("javax.net.ssl.trustStorePassword", "Passw0rd");
System.setProperty ("javax.net.ssl.trustStore", "trust.store");
Security.addProvider((Provider)Class.forName
("com.sun.crypto.provider.SunJCE").newInstance());
java.security.Security.addProvider
(new com.sun.net.ssl.internal.ssl.Provider());
System.setProperty ("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
try {
System.setProperty
("javax.net.ssl.keyStoreType", "pkcs12");
System.setProperty
("javax.net.ssl.keyStorePassword", "Passw0rd");
System.setProperty
("javax.net.ssl.keyStore", "b2b_ssltestweb.p12");
SSLSocketFactory factory =
(SSLSocketFactory)SSLSocketFactory.getDefault();
SSLSocket socket =
(SSLSocket)factory.createSocket("b2b-dev.fmr.com", 443);
/* now handshare is complete and god to go */
Thanks for your help ejp,
joe -
JMS subscriptions through firewall on port 80
We need to access weblogic app server and JMS across firewall.
The firewall opens only port 80/HTTP. We also need support for
topics. In one of the BEA's documents that discuss about web
services, it mentioned that support for topics is deprecated and
may not be supported in future versions. Our applications are
standalone java applications commnicating app server. Currently,
we are not sure if weblogic's 't3' protocol can be recognized.
Publisher is usually on the server and JMS client can be inside
or outside firewall. If supported, how does JMS client (and
server) can be configured to make subscriptions to any topic and
receive events. Since tunneling across firewall 'may' only allow
request/ response messaging, does our client needs to have
special code to poll for messages published to a specific topic
or is this all transparent? What is the impact of this on
scalability, performance and reliability?
We are also evalutaiting products like jproxy that enable
communication through firewalls. They promise no changes to the
existing code that works inside firewall, but we are having some
problems with it.
Since we are already using weblogic, if it supports JMS accross
firewalls it would be ideal. According to my understanding,
weblogic allows communication with app server and enterprise
beeans through webservices (JAVAX-RPC) and I didn't find much
information about JMS. Any help would be appreciated.
Sincerely,
Bhagat Bandlamudi
Hi
Thanks for the information. We are also looking at the same problem -
asynchronous delivery through firewalls (to standalone clients and to
applications). Started looking at JProxy but we are also having some
problems with WLS 7.0.
The downside potentially of WLS http tunnelling is that it is likely
proprietry.
Dermot
Tom Barnes <[email protected]> wrote in message
news:[email protected]...
> Hi!
>
> Since its wee early days, WebLogic has supported http
> tunneling in addition to t3. If you are using JMS or RMI, merely
> substitute "http" for "t3" in your URL -- but make sure
> that "http-tunneling-enabled" is set to true for the WL server.
>
> When using HTTP, there is no need to do polling. WebLogic
> does this magic for you under-the-covers. From a WL client
> perspective, http tunneling does anything t3 can, (but
> http is slower).
>
> I do not know what is meant by "support for topics is deprecated
> and may not be supported in future releases". This is
> definitely not the case for JMS - but may be the case for
> certain web-services???? Or maybe some doc writer
> is trying to put me out of a job! :-)
>
> Tom
>
> P.S. Note that WL 7.0 and up allows you to configure additional
> ports on the server (as many as you want).
>
> Bhagat Bandlamudi wrote:
> > We need to access weblogic app server and JMS across firewall.
> > The firewall opens only port 80/HTTP. We also need support for
> > topics. In one of the BEA's documents that discuss about web
> > services, it mentioned that support for topics is deprecated and
> > may not be supported in future versions. Our applications are
> > standalone java applications commnicating app server. Currently,
> > we are not sure if weblogic's 't3' protocol can be recognized.
> >
> > Publisher is usually on the server and JMS client can be inside
> > or outside firewall. If supported, how does JMS client (and
> > server) can be configured to make subscriptions to any topic and
> > receive events. Since tunneling across firewall 'may' only allow
> > request/ response messaging, does our client needs to have
> > special code to poll for messages published to a specific topic
> > or is this all transparent? What is the impact of this on
> > scalability, performance and reliability?
> >
> > We are also evalutaiting products like jproxy that enable
> > communication through firewalls. They promise no changes to the
> > existing code that works inside firewall, but we are having some
> > problems with it.
> >
> > Since we are already using weblogic, if it supports JMS accross
> > firewalls it would be ideal. According to my understanding,
> > weblogic allows communication with app server and enterprise
> > beeans through webservices (JAVAX-RPC) and I didn't find much
> > information about JMS. Any help would be appreciated.
> >
> > Sincerely,
> > Bhagat Bandlamudi
>
-
Urgent Help Required For Starting RMI server from servlet.
I am currently working on rmi project.
I want to send request to remote machine(Web host) where my application is from desktop client .For that we are using RMI.
I am writing servlet and inside it i am binding object to registry for rmi server.
which will be deployed on remote server.
code ....
Registry reg;
reg=LocateRegistry.createRegistry(1099);
Server server=new Server("server");//class whose remote object to be accessed
//extends unicast remote object.Implement ServerInt interface which extends Remote.
reg.bind("server",server);
When i am trying to access this object i am getting following exception.
javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalExcepti
on: error unmarshalling return; nested exception is:
java.lang.ClassNotFoundException: ServerModule.ServerInt]
at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
at RequstReplication.main(RequstReplication.java:27)
Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested excep
tion is:
java.lang.ClassNotFoundException: ServerModule.ServerInt
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
... 4 more
Caused by: java.lang.ClassNotFoundException: ServerModule.ServerInt
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyInterfaces(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader.loadProxyClass(Unknown Source)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(Unknown Source)
at java.io.ObjectInputStream.readProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
... 5 more
I can access naming enumeration of registry and object bound to it.
by following program.I shows corect objects.
Context namingContext=new InitialContext();
NamingEnumeration<NameClassPair> e=namingContext.list("rmi:");
while(e.hasMore())
System.out.println(e.next().getName());
While when i start RMI server from simple java program i can access these objects from registry.
I am not getting what is problem problem.Is there any other way to send request?
Plese give quick response.I am currently working on rmi project.
I want to send request to remote machine(Web host) where my application is from desktop client .For that we are using RMI.
I am writing servlet and inside it i am binding object to registry for rmi server.
which will be deployed on remote server.
code ....
Registry reg;
reg=LocateRegistry.createRegistry(1099);
Server server=new Server("server");//class whose remote object to be accessed
//extends unicast remote object.Implement ServerInt interface which extends Remote.
reg.bind("server",server);
When i am trying to access this object i am getting following exception.
javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalExcepti
on: error unmarshalling return; nested exception is:
java.lang.ClassNotFoundException: ServerModule.ServerInt]
at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
at RequstReplication.main(RequstReplication.java:27)
Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested excep
tion is:
java.lang.ClassNotFoundException: ServerModule.ServerInt
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
... 4 more
Caused by: java.lang.ClassNotFoundException: ServerModule.ServerInt
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyInterfaces(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader.loadProxyClass(Unknown Source)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(Unknown Source)
at java.io.ObjectInputStream.readProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
... 5 more
I can access naming enumeration of registry and object bound to it.
by following program.I shows corect objects.
Context namingContext=new InitialContext();
NamingEnumeration<NameClassPair> e=namingContext.list("rmi:");
while(e.hasMore())
System.out.println(e.next().getName());
While when i start RMI server from simple java program i can access these objects from registry.
I am not getting what is problem problem.Is there any other way to send request?
Plese give quick response. -
Please help: RMI and Swing/AWT issue
Hi guys, I've been having a lot of trouble trying to get a GUI application to work with RMI. I'd appreciate any help. Here's the story:
I wrote a Java application and its GUI using Netbeans. In a nutshell, the application is about performing searches. I am now at the point where I need exterior programs to use my application's search capabilities, thus needing RMI. Such exterior programs are to call methods currently implemented in my application.
I implemented RMI, and got the client --> server communication working. However, the GUI just breaks. It starts outputting exceptions, gets delayed, doesn't update properly, some parts of it stop working.... basically hysterical behavior.
Now take a look at this line within my server class:
Naming.rebind("SearchProgram", mySearchProgram);
If I take it out, RMI obviously does not work... but the application and its GUI work flawlessly. If I put it in, the RMI calls work, but the GUI's above symptoms occur again. Among the symptoms are null pointer exceptions which all look similar, are related to "AWT-EventQueue-0", and keep ocurring. Here's just snippet of the errors outputted:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at javax.swing.plaf.metal.MetalScrollBarUI.getPreferredSize(MetalScrollBarUI.java:102)
at javax.swing.JComponent.getPreferredSize(JComponent.java:1615)
at javax.swing.JScrollBar.getMinimumSize(JScrollBar.java:704)
at javax.swing.ScrollPaneLayout.minimumLayoutSize(ScrollPaneLayout.java:624)
at java.awt.Container.minimumSize(Container.java:1598)
at java.awt.Container.getMinimumSize(Container.java:1583)
at javax.swing.JComponent.getMinimumSize(JComponent.java:1697)
at java.awt.BorderLayout.minimumLayoutSize(BorderLayout.java:634)
at java.awt.Container.minimumSize(Container.java:1598)
at java.awt.Container.getMinimumSize(Container.java:1583)
at javax.swing.JComponent.getMinimumSize(JComponent.java:1697)
at java.awt.BorderLayout.minimumLayoutSize(BorderLayout.java:634)
at java.awt.Container.minimumSize(Container.java:1598)
at java.awt.Container.getMinimumSize(Container.java:1583)
at javax.swing.JComponent.getMinimumSize(JComponent.java:1697)
at javax.swing.BoxLayout.checkRequests(BoxLayout.java:433)
at javax.swing.BoxLayout.layoutContainer(BoxLayout.java:375)
at java.awt.Container.layout(Container.java:1401)
at java.awt.Container.doLayout(Container.java:1390)
at java.awt.Container.validateTree(Container.java:1473)
at java.awt.Container.validateTree(Container.java:1480)
at java.awt.Container.validateTree(Container.java:1480)
at java.awt.Container.validateTree(Container.java:1480)
at java.awt.Container.validateTree(Container.java:1480)
at java.awt.Container.validate(Container.java:1448)
at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:379)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:113)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at javax.swing.plaf.basic.BasicMenuItemUI.getPreferredMenuItemSize(BasicMenuItemUI.java:400)
at javax.swing.plaf.basic.BasicMenuItemUI.getPreferredSize(BasicMenuItemUI.java:310)
at javax.swing.JComponent.getPreferredSize(JComponent.java:1615)
at javax.swing.BoxLayout.checkRequests(BoxLayout.java:434)
at javax.swing.BoxLayout.preferredLayoutSize(BoxLayout.java:251)
at javax.swing.plaf.basic.DefaultMenuLayout.preferredLayoutSize(DefaultMenuLayout.java:38)
at java.awt.Container.preferredSize(Container.java:1558)
at java.awt.Container.getPreferredSize(Container.java:1543)
at javax.swing.JComponent.getPreferredSize(JComponent.java:1617)
at javax.swing.JRootPane$RootLayout.layoutContainer(JRootPane.java:910)
at java.awt.Container.layout(Container.java:1401)
at java.awt.Container.doLayout(Container.java:1390)
at java.awt.Container.validateTree(Container.java:1473)
at java.awt.Container.validate(Container.java:1448)
at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:379)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:113)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
There are no complaints about anything within my code, it's all GUI related whenever I make a bind() or rebind() call.
Again, any help here would be great... cause this one's just beating me.
Thanks!Maybe you want to change that worker thread to
not do RMI but anything else (dummy data) to see if it really is RMI, I doubt it, I think you are updating some structures that have to do with swing GUI and hence you will hang.
Just check this out.
Maybe you are looking for
-
How to set number of rows in filters?
Hi, we need to set another number of rows which is displayed in filters on bex or web template? Thanks for advice
-
[SOLVED]No Keyboard/Mouse on Xorg
Hi, After an update a few days ago, my network devices weren't working anymore, but running dhcpcd could fix that. Today i updated again and used pacdiff to merge some new configs (i can't remember which one - great i know) and now there is no reacti
-
Please help me to reset my password in my iPhone on opening
Sir / Madam, I changed my old password through settings in my iPhone but when i tried my new password its coming trying, then again i tried my new password but it was disabled. Please help me to fix it, i cannot make a call and cannot use my iPhone c
-
Deleted territory on invoice correction
Dear Gurus, When invoice correction is created for invoices with deleted territories the correction should go to the new territory but it doesn't happen in a case.. In our case the territory on the correction is always the deleted territory. Partner
-
I updated my server from 10.6.6 to 10.6.7 this morning. Now Open Directory isn't working, slapd isn't running, and every 10 seconds the following lines are added to /var/log/slapd.log: Apr 2 15:12:35 mac001 slapd[3658]: @(#) $OpenLDAP: slapd 2.4.11 (