Problems with RMI
hi friends,
I am doing my project in grid computing.I am using RMI. but sometimes what happens is when i submit the jobs to the machines and after completion when i collect the values and display the output, sometimes i am not able to get the whole image completed back.Some part of the image doesn't appear there. What might be the proble?
The problem might be that you do not provide any details and expect us to be visionaries...
Similar Messages
-
Problem with RMI in ADB T75 receiver
Hi:
I have a problem with an xlet that uses the RMI (IXC) API in the ADB T75 development settop box.
I export an object (of type MyObject) implementing the Remote interface, and, later, I import it with no problem.
The problem appears after importing the object, when I try to cast the imported object to the type of the exported object (type MyObject) for using it (example on page 371 of the marvelous Morris book).
If I import the object in the same xlet where I export it (a little bit useless), the process works fine as the class of the imported object (remoteObject.getClass().getName()) is the same of the exported object.
But, when importing the object from another xlet, doing the cast fails (ClassCastException). This time, remoteObject.getClass().getName() returns the name "stub_MyObject_ca_ba" ( "ca" is the OrgID and "ba" is the AppID of the exporting xlet). That is, the middleware is returning to the importing xlet an object of the stub class.
The ClassCastException seems to be right, as the the superclass of the "stub_MyObject_ca_ba" is directly java.lang.Object. That is, the types of the exported object (MyObject) and the returned object (stub_MyObject_ca_ba) are not in the same hierarchy.
Has anyone one explanation or solution?
May be a bug of the ADB T75 settop box?
Thanks in advance for your comments
Liga0068Problem solved. This was posted by Pretorius_594 on Feb 27, 2004.
Sorry for bothering.
The problem was due to that I was doing a cast to the original object (MyObject). That is:
remoteObject = lookup(...)
MyObject importedobject = (MyObject)remoteObject.
I saw such an example in the Morris and Smith-Chaigneau book, but, definetively, that code seems not to work (at least in the ADB receiver)
Th right solution is to extend the Remote interface (MyRemote) and to cast the importedobject to that type. That is:
public interface MyRemote extends Remote ...
remoteObject = lookup(...)
MyRemote importedobject = (MyRemote)remoteObject.
Liga0068 -
Problems with RMI tutorials using Tomcat 4.1.24
Hi
I have some problem when I try the rmi Hello example tutorial (http://java.sun.com/j2se/1.4.2/docs/guide/rmi/getstart.doc.html)
When I start rmi server as follows:
java -Djava.rmi.server.useCodebaseOnly=true -Djava.security.policy=file:E:\Rmi\Hello\mysrc\bin\policy.policy -Djav
a.rmi.server.codebase=http://127.0.0.1/classes/ examples.hello.HelloImpl
I got the following errors:
HelloImpl err: access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve)
java.security.AccessControlException: access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:270)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:542)
at java.lang.SecurityManager.checkConnect(SecurityManager.java:1044)
at java.net.Socket.connect(Socket.java:420)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
at java.rmi.Naming.rebind(Naming.java:160)
at examples.hello.HelloImpl.main(HelloImpl.java:67)
I have granted all permission in the policy file. I have put all the classes in a subfolder call classes just after the Root directoy Can someone enlighten me. Thanks.i don't know if it helps but i had the following problem:
an rmi-component software plus a servlet contacting the system.
and rmi from the servlet in tomcat did not seem to work ...
java.rmi.MarshalException: error marshalling arguments; nested exception is:
java.net.SocketException: Software caused connection abort: socket write error
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at net.metamagix.essence.Agents.DataAgentI_Stub.storeObjects(Unknown Source)
at net.metamagix.essence.CAgents.ParameterSaviour.save(ParameterSaviour.java:1556)
finaly i changed back to tomcat 4.0.x but it still was not any better, when i found out that most of the problems resulted from pathnames...
tomcat 4.1.24 had a problem with pathnames getting too long (2k on win 2000) and tomcat 4.0 produced errors because of the blank in it's path name "Tomcat 4.0" so i made a new installation with C:\Tomcat4 as home directory and - what a surprise - things turned out fine and rmi worked. -
Hello,
i have installed Tomcat in a path with whitespaces. Our Application use RMI (as server componend) to communicate with other Applications.
when I start Tomcat i get an Exception like this:
(by the way: no protocol: Audit -> Audit is a part of the path with whitespaces and it is nessessary that the tool runs with whitespaces in the path e.g. Program Files)
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested excep
tion is:
java.net.MalformedURLException: no protocol: Audit
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:352
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:207)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
i have write a system parameter with -djava lfor rmi.server.codebase ike this and qoute the whitespaces with %20 but it doesn' t work.
file://d:/test/Tool%20Audit/
Please help me, its urgent.
Best regards
ChrisHi Chris,
the Exception java.net.MalformedURLException: no protocol: Audit means that your path is incorrect, try
<protocol>://<path>/
for Example
http://.../Audit
ftp:/.../Audit
file://../Audit -
Problem using CORBA clients with RMI/EJB servers..!!!???
Hi,
I have a question on using EJB / or RMI servers with CORBA clients using
RMI-IIOP transport, which in theory should work, but in practice has few
glitches.
Basically, I have implemented a very simple server, StockTreader, which
looks up for a symbol and returns a 'Stock' object. In the first example, I
simplified the 'Stock' object to be a mere java.lang.String, so that lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case 1) and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA and RMI-to-RMI.
But the problem arises when I tried using the RMI server (via IIOP) with the
CORBA client, when the client tries to narrow the object ref obtained from
the naming service into the CORBA idl defined type (StockTrader) it ends up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a PortableRemoteObject derived
class, to make it IIOP compliant), and then the server to register the stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming =NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ": " +obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to register the RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref name (with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the naming
service, the operation StockTraderHelper.narrow() fails in the segment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registered in a CORBA
server (as opposed to an RMI server), but works correctly with no casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hariOn the contrary... all that is being said is that we needed to provide clearer examples/documentation in the 5.1.0 release. There will be no difference between the product as found in the service pack and the product found in the 5.1.1. That is, the only substantive will be that 5.1.1 will also
include the examples.
"<=one way=>" wrote:
With reference to your and other messages, it appears that one should not
expect that WLS RMI-IIOP will work in a complex real-life system, at least
not now. In other words, support for real-life CORBA clients is not an
option in the current release of WLS.
TIA
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
We currently publish an IDL example, even though the IDL programmingmodel in Java is completely non-functional, in anticipation of the support
needs for uses who need to use IDL to talk to the Weblogic server,
generically. This example illustrates the simplest connectivity; it does not
address how
to integrate CORBA and EJB, a broad topic, fraught with peril, imo. I'llnote in passing that, to my knowledge, none of the other vendors attempt
this topic either, a point which is telling if all the less happy to hear.
For the record then, what is missing from our distribution wrt RMI-IIOPare a RMI-IIOP example, an EJB-IIOP example, an EJB-C++. In this you are
correct; better examples are forth coming.
Still, I would not call our RMI-IIOP implementation fragile. I would saythat customers have an understandably hard time accepting that the IDL
programming model is busted; busted in the sense that there are no C++
libraries to support the EJB model, and busted in the sense that there is
simply no
support in Java for an IDL interface to an EJB. Weblogic has nothing to doit being busted, although we are trying to help our customers deal with it
in productive ways.
For the moment, what there is is a RMI (over IIOP) programming model, aninherently Java to Java programming model, and true to that, we accept and
dispatch IIOP request into RMI server objects. The way I look at it is this:
it's just a protocol, like HTTP, or JRMP; it's not IDL and it has
practically nothing to do with CORBA.
ST wrote:
Eduardo,
Can you give us more details about the comment below:
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult ot
use an idl client in java to work.It seems to me that Weblogic's RMI-IIOP is a very fragile
implementation. We
don't need a "HelloWorld" example, we need a concrete serious example(fully
tested and seriously documented) that works so that we can get a betteridea
on how to integrate CORBA and EJB.
Thanks,
Said
"Eduardo Ceballos" <[email protected]> wrote in message
news:[email protected]...
Please post request to the news group...
As I said, you must separate the idl related classes (class files and
java
files) from the rmi classes... in the rmic step, you must set a newtarget
(as you did), emit the java files into that directory (it's not clearyou
did this), then remove all the rmi class files from the class path... ifyou
need to compile more classes at that point, copy the java files to theidl
directly is you must, but you can not share the types in any way.
I fear that as soon as the call to narrow succeeds, the remainingapplication will fail to work correctly because it is too difficult otuse
an idl client in java to work.
Harindra Rajapakshe wrote:
Hi Eduardo,
Thanks for the help. That is the way I compiled my CORBA client, by
separating the IDL-generated stubs from the RMI ones, but still I
get a
CORBA.BAD_PARAM upon narrowing the client proxy to the interfacetype.
Here's what I did;
+ Define the RMI interfaces, in this case a StockTrader interface.
+ Implement RMI interface by extendingjavax.rmi.PortableRemoteObject
making
it IIOP compliant
+ Implemnnt an RMI server, and compile using JDK1.2.2
+ use the RMI implementation to generate CORBA idl, using RMI-IIOPplugin
utility rmic;
rmic -idl -noValueMethods -always -d idl stock.StockTraderImpl
+ generate Java mappings to the IDL generated above, using RMI-IIOPplugin
util,
idlj -v -fclient -emitAll -tf src stocks\StockTrader.idl
This creates source for the package stock and also
org.omg.CORBA.*
package, presumably IIOP type marshalling
+ compile all classes generated above using JDK1.2.2
+ Implement client (CORBA) using the classes generated above, NOTthe
RMI
proxies.
+ start RMI server, with stockTrader server obj
+ start tnameserv
+ start CORBA client
Then the client errors when trying to narrow the obj ref from the
naming
service, into the CORBA IDL defined interface using,
org.omg.CORBA.Object obj =naming.resolve(nn);
StockTrader trader =StockTraderHelper.narrow(obj); // THIS
ERRORS..!!!
throwing a CORBA.BAD_PARAM exception.
any ideas..?
Thanks in advance,
-hari
----- Original Message -----
From: Eduardo Ceballos <[email protected]>
Newsgroups: weblogic.developer.interest.rmi-iiop
To: Hari Rajapakshe <[email protected]>
Sent: Wednesday, July 26, 2000 4:38 AM
Subject: Re: problem using CORBA clients with RMI/EJBservers..!!!???
Please see the post on june 26, re Errors compiling... somewherein
there,
I suspect, you are referring to the rmi class file when you are
obliged
to
completely segregate these from the idl class files.
Hari Rajapakshe wrote:
Hi,
I have a question on using EJB / or RMI servers with CORBA
clients
using
RMI-IIOP transport, which in theory should work, but in practice
has
few
glitches.
Basically, I have implemented a very simple server,
StockTreader,
which
looks up for a symbol and returns a 'Stock' object. In the firstexample, I
simplified the 'Stock' object to be a mere java.lang.String, so
that
lookup
would simply return the 'synbol'.
Then I have implemented the above, as an RMI-IIOP server (case
1)
and a
CORBA server (case 2) with respective clients, and the pair of
client-servers work fine as long as they are CORBA-to-CORBA andRMI-to-RMI.
But the problem arises when I tried using the RMI server (via
IIOP)
with
the
CORBA client, when the client tries to narrow the object ref
obtained
from
the naming service into the CORBA idl defined type (StockTrader)
it
ends
up
with a class cast exception.
This is what I did to achieve the above results:
[1] Define an RMI interface StockTrader.java (extending
java.rmi.Remote)
with the method,
public String lookup( String symbol) throws RMIException;
[2] Implement the StorckTrader interface (on a
PortableRemoteObject
derived
class, to make it IIOP compliant), and then the server to
register
the
stock
trader with COS Naming service as follows:
String homeName =....
StockTraderImpl trader =new StockTraderImpl();
System.out.println("binding obj <" homeName ">...");
java.util.Hashtable ht =new java.util.Hashtable();
ht.put("java.naming.factory.initial", args[2]);
ht.put("java.naming.provider.url", args[3]);
Context ctx =new InitialContext(ht);
ctx.rebind(homeName, trader);
[3] Generate the RMI-IIOP skeletons for the Implementation
class,
rmic -iiop stock.StockTraderImpl
[4] generate the IDL for the RMI interface,
rmic -idl stock.StockTraderImpl
[5] Generate IDL stubs for the CORBA client,
idlj -v -fclient -emitAll StockTraderImpl.idl
[6] Write the client to use the IDL-defined stock trader,
String serverName =args[0];
String symList =args[1];
StockClient client =new StockClient();
System.out.println("init orb...");
ORB orb =ORB.init(args, null);
System.out.println("resolve init name service...");
org.omg.CORBA.Object objRef
=orb.resolve_initial_references("NameService");
NamingContext naming=NamingContextHelper.narrow(objRef);
... define a naming component etc...
org.omg.CORBA.Object obj =naming.resolve(...);
System.out.println("narrow objRef: " obj.getClass() ":"
+obj);
StockTrader trader =StockTraderHelper.narrow(obj);
[7] Compile all the classes using Java 1.2.2
[8] start tnameserv (naming service), then the server to
register
the
RMI
server obj
[9] Run the CORBA client, passing it the COSNaming service ref
name
(with
which the server obj is registered)
The CORBA client successfully finds the server obj ref in the
naming
service, the operation StockTraderHelper.narrow() fails in thesegment
below, with a class cast exception:
org.omg.CORBA.Object obj =naming.resolve(...);
StockTrader trader =StockTraderHelper.narrow(obj);
The <obj> returned by naming service turns out to be of the
type;
class com.sun.rmi.iiop.CDRInputStream$1
This is of the same type when stock trader object is registeredin a
CORBA
server (as opposed to an RMI server), but works correctly with
no
casting
excpetions..
Any ideas / hints very welcome.
thanks in advance,
-hari -
Problem in Rmi in machine with two IP local & internet
I am having problem in Rmi in machine with two interfaces local & internet
i.e..
if I set property java.rmi.server.hostname+ to the one with internet ip address using System.setProperty()
I can not access Rmi through local LAN
if I do not set the property Everything works fine in LAN but I can not access the RMI from Internet
Pls tell me the solutionConsider the code Here and if you can suggest in this code what changes I have to make ,I will be thankful to you
// Class MyHelloServer
package rmi.server;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.net.Inet4Address;
import java.net.InetAddress;
import java.net.MalformedURLException;
import java.net.NetworkInterface;
import java.net.SocketException;
import java.rmi.*;
import java.rmi.server.ServerNotActiveException;
import java.util.ArrayList;
import java.util.Enumeration;
import javax.swing.JOptionPane;
import rmi.bl.HelloImpl;
public class MyHelloServer
static public ArrayList hostList = new ArrayList();
static String hostname=null;
static String SERVER_PORT="9999";
static String MULTIPLE_BIND="true";
static{
startTest();
public static void startTest(){
try {
Enumeration enum1= NetworkInterface.getNetworkInterfaces();
while(enum1.hasMoreElements()){
NetworkInterface networkInterface = (NetworkInterface)enum1.nextElement();
Enumeration enum2 = networkInterface.getInetAddresses();
while(enum2.hasMoreElements()){
Object obj = enum2.nextElement();
if(obj instanceof Inet4Address){
if(!hostList.contains(((Inet4Address)obj).getHostAddress())){
hostList.add(((Inet4Address)obj).getHostAddress());
if(networkInterface.isPointToPoint()){
hostname=((Inet4Address)obj).getHostAddress();
}catch (SocketException e) {
e.printStackTrace();
if(hostname!=null){
System.setProperty("java.rmi.server.hostname", hostname);
System.out.println(System.getProperty("java.rmi.server.hostname")+"<<<<<< New");
public static void main(String args[])
try
HelloImpl storeServer = new HelloImpl();
int port=Integer.parseInt(SERVER_PORT);
String host=InetAddress.getLocalHost().getHostAddress();
java.rmi.registry.LocateRegistry.createRegistry(port);
if(MULTIPLE_BIND.equals("true")){
for (int i = 0; i < hostList.size(); i++) {
System.out.println(hostList.get(i).toString() + " <<<<IP" + i);
Naming.rebind("//"+hostList.get(i).toString()+":"+port+"/STORESERVER", storeServer);
}else{
Naming.rebind("//"+host+":"+port+"/"+"STORESERVER", storeServer);
MyHelloServer.MyThread thread= new MyThread(":"+port+"/"+"STORESERVER", storeServer);
System.out.println("Remote Server started.....");
catch (java.net.MalformedURLException me)
System.out.println("Malformed URL: " + me.toString());
System.exit(0);
catch (RemoteException re)
System.out.println("Remote exception: " + re.toString());
System.exit(0);
catch (Exception e)
System.out.println("Error: " + e.toString());
System.exit(0);
static class MyThread extends javax.swing.JPanel implements ActionListener{
String str="";
HelloImpl impl;
public MyThread(String text,HelloImpl storeServer){
this.impl=storeServer;
str=text;
int timetoWaitForCheck=15000;
javax.swing.Timer timer = new javax.swing.Timer(timetoWaitForCheck, this);
timer.start();
public void actionPerformed(ActionEvent ae)
startTest();
// Rebind
for (int i = 0; i < hostList.size(); i++) {
try {
Naming.rebind("//"+hostList.get(i).toString()+str, impl);
} catch (RemoteException e) {
e.printStackTrace();
} catch (MalformedURLException e) {
e.printStackTrace();
} -
RMI Problems with WL 6 and JDK1.3
I have been working on converting an existing RMI Service- Client
Application to use Weblogic 6.0. All the rmi services run in an
external VM seperate from the WL server. This setup works fine with
plain RMI, I have converted this to WL and JNDI. I get the following
error after a few connections to the service have been made. It always
happens.
<Feb 18, 2001 10:53:39 PM EST> <Error> <ConnectionManager> <Closing:
'weblogic.r
jvm.t3.T3JVMConnection@91cee' because of: 'Client received a routed
message from
an unknown JVM: '-5623439693736234706C:24.185.83.208''>
I have taken the Stock Applet example from WL5.1 and it also exhibits
the same problems. Since there are no examples with RMI and JNDI in
WL6 maybe I am missing something. I create an initial an IntialContext
and I can list and see any objects. But I will always wind up getting
these errors that Peer has shutdown because a message has been
received from an unknown VM. I have dumped out the info of and the
message is coming from a "known" VM but the weblogic rmi subsystem
seems to have lost the information. Any ideas or help would be
grateful.
Thanks
Alex JeannopoulosI have been working on converting an existing RMI Service- Client
Application to use Weblogic 6.0. All the rmi services run in an
external VM seperate from the WL server. This setup works fine with
plain RMI, I have converted this to WL and JNDI. I get the following
error after a few connections to the service have been made. It always
happens.
<Feb 18, 2001 10:53:39 PM EST> <Error> <ConnectionManager> <Closing:
'weblogic.r
jvm.t3.T3JVMConnection@91cee' because of: 'Client received a routed
message from
an unknown JVM: '-5623439693736234706C:24.185.83.208''>
I have taken the Stock Applet example from WL5.1 and it also exhibits
the same problems. Since there are no examples with RMI and JNDI in
WL6 maybe I am missing something. I create an initial an IntialContext
and I can list and see any objects. But I will always wind up getting
these errors that Peer has shutdown because a message has been
received from an unknown VM. I have dumped out the info of and the
message is coming from a "known" VM but the weblogic rmi subsystem
seems to have lost the information. Any ideas or help would be
grateful.
Thanks
Alex Jeannopoulos -
Hi,
I have written a simple Ping program, to exercise me with RMI, this program worked fine with jdk1.3, now I have downloaded j2sdk1.4 and I have installed it, I runned the RMI program but now I have a run-time error message.
Could you explain me what can be happened?
Thanks a lotThe error message + stacktrace would help...
did you also compile with jdk1.4 or just execute with the jre shipped with 1.4? -
Remote Delta link setup problem with Bean / Access Service
Hello,
I am trying to setup Remote Delta Link (RDL) between two portals. (Both portals same version - EP 7.0 EHP1 SP 05 - are in the same domain)
I already have the Remote Role Assignment working without any issues.
The following have been done successfully:
1. Same user repository has been setup for both the portals
2. Setup trust between producer and consumer (SSO working fine)
3. Producer added and registered succesfully on consumer
4. Permissions setup on producer and consumer
4. pcd_service user with required UME actions setup
I am able to see all the remote content in the Consumer portal.
When I try to copy the remote content and paste it as local content, I am getting the following error:
Could not create remote delta link to object 'page id'. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly.
After increasing the log severity, I am able to see the following in Default Trace:
com.sap.portal.fpn.transport.Trying to lookup access service (P4-RMI) for connecting to producer 'ess_int' with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
com.sap.portal.fpn.transport.Unable to lookup access service (P4-RMI) with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
AbstractAdvancedOperation.handleDirOperationException
[EXCEPTION]
com.sap.portal.pcm.admin.exceptions.DirOperationFailedException: Could not retrieve the bean / access service to connect with producer
Could not retrieve the bean / access service to connect with producer
Like you can see above, there is some bean / access service which is not retrieved successfully. I am not sure if this is a permission problem on the consumer.
I have checked that the P4 ports are configured correctly (standard - not changed) and I am able to telnet from producer to consumer (and vice versa) on the P4 port.
I am stuck at this point and am not able to find any information on this.
I would really appreciate if some one can point me in the right direction.
Thank you for reading.
- RajHi Raj,
Please check your config of the P4 port on the producer. Is it really 50004 (check SystemInfo of the producer)?
I do think there's a problem with the P4 communication since RDL requires P4 connection.
Do you have load balanced consumer-producer connection? Please refer to this blog for further details
Little known ways to create a load balanced Consumer Producer connection in a FPN scenario
Regards,
Dao -
Problem with setting oracle type parameter in viewobject query
Hi There,
I am facing a problem with JDev1013. I have a view that has JDBC positional parameters that are supposed to be in parameters for function like:
SELECT x.day, x.special_exact_period_only
FROM (
SELECT x.day, x.special_exact_period_only
FROM (
SELECT
x.day,
rb.special_exact_period_only
FROM TABLE (
RentabilityPkg.findMarkerSlots(
'start',
? /* dchannel */,
NULL,
? /* resorts */,
'special',
NULL,
? /* code */,
NULL,
TRUNC(SYSDATE),
TRUNC(SYSDATE + 365 * 2),
NULL
) x
JOIN resourcebase rb USING (rentabilitymanager_id)
UNION
SELECT
x.day,
rb.special_exact_period_only
FROM TABLE (
RentabilityPkg.findMarkerSlots(
'start',
? /* dchannel */,
NULL,
? /* resorts */,
'composition',
NULL,
? /* code */,
NULL,
TRUNC(SYSDATE),
TRUNC(SYSDATE + 365 * 2),
NULL
) x
JOIN resourcebase rb USING (rentabilitymanager_id)
)x
ORDER BY x.day
) x
WHERE ROWNUM <= 30now the JDBC positional parameters take our custom defined list type defined as:
CREATE TYPE NumberList AS TABLE OF NUMBER;
we are setting the parameter in the views with the help of oracle.sql.ARRAY class like:
* Set parameters.
public void setParams(Integer dchannelId, Integer[] resorts, String specialCode)
try {
System.out.println(this.getClass() + ".setParams()");
ARRAY arrParam1 = ((NWSApplicationModule)getApplicationModule()).toSQLNumberList(Arrays.asList(resorts));
ARRAY arrParam2 = ((NWSApplicationModule)getApplicationModule()).toSQLNumberList(Arrays.asList(resorts));
System.out.println("arrParam1 - " + arrParam1);
System.out.println("arrParam1 - " + arrParam1);
System.out.println(this.getClass() + " ARRAY - " + arrParam1.getArray());
System.out.println(this.getClass() + " -- " + arrParam1.length());
System.out.println("arrParam2 - " + arrParam2);
System.out.println("arrParam2 - " + arrParam2);
System.out.println(this.getClass() + " ARRAY - " + arrParam2.getArray());
System.out.println(this.getClass() + " -- " + arrParam2.length());
Object[] params =
{ dchannelId,
arrParam1,
specialCode,
dchannelId,
arrParam2,
specialCode
setWhereClauseParams(params);
System.out.println("DONE WITH " + this.getClass() + ".setParams()");
catch(Exception ex)
ex.printStackTrace(System.out);
}the toSQLNumberList() method is defined in our App module baseclass as follows:
public ARRAY toSQLNumberList(Collection coll)
debug("toSQLNumberList()");
DBTransaction txn = (DBTransaction)getTransaction();
debug("txn - " + txn + " : " + txn.getClass());
return NWSUtil.toSQLNumberList(coll, getConnection(txn));
public static ARRAY toSQLNumberList(Collection c, Connection connection)
//printTrace();
debug("toSQLNumberList()");
try
ArrayDescriptor numberList = ArrayDescriptor.createDescriptor("NUMBERLIST", connection);
NUMBER[] elements = new NUMBER[c == null ? 0 : c.size()];
if (elements.length > 0 )
Iterator iter = c.iterator();
for (int i = 0; iter.hasNext(); i++)
elements[i] = new NUMBER(iter.next().toString());
return new ARRAY(numberList, connection, elements);
catch (Exception ex)
ex.printStackTrace();
return null;
protected Connection getConnection(DBTransaction dbTransaction)
//return null;
debug("Inside getConnection()");
CallableStatement s = null;
try
* Getting Conenction in BC4J is dirty but its better
* as otherwise we might end up coding with connections
* and the Transaction Integrety will be
s = dbTransaction.createCallableStatement("BEGIN NULL; END;", 0);
debug("DOING s.getConnection()...");
Connection conn = s.getConnection();
debug("DONE WITH s.getConnection()...");
/*try
throw new Exception("TEST");
catch (Exception ex)
ex.printStackTrace(System.out);
debug("conn CLASS - " + conn.getClass());
return conn;
catch (Exception ex)
ex.printStackTrace();
return null;
finally
try { s.close(); }
catch (Exception ex) {}
}Whenever we try setting the parameters in view using setParams() and use this view to set the model of a java control it thorws the following exception :
[2006-10-10 12:34:48,797 AWT-EventQueue-0 ERROR] JBO-28302: Piggyback write error
oracle.jbo.PiggybackException: JBO-28302: Piggyback write error
at oracle.jbo.common.PiggybackOutput.getPiggybackStream(PiggybackOutput.java:185)
at oracle.jbo.common.JboServiceMessage.marshalRefs(JboServiceMessage.java:267)
at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:343)
at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:316)
at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processMessage(AbstractRemoteApplicationModuleImpl.java:2283)
at oracle.jbo.server.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:7509)
at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.sync(AbstractRemoteApplicationModuleImpl.java:2221)
at oracle.jbo.server.remote.ejb.ServerApplicationModuleImpl.doMessage(ServerApplicationModuleImpl.java:79)
at oracle.jbo.server.ejb.SessionBeanImpl.doMessage(SessionBeanImpl.java:474)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteAMReservation_StatefulSessionBeanWrapper906.doMessage(RemoteAMReservation_StatefulSessionBeanWrapper906.java:286)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
## Detail 0 ##
java.io.NotSerializableException: oracle.jdbc.driver.T4CConnection
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
at oracle.jbo.common.SvcMsgResponseValues.writeObject(SvcMsgResponseValues.java:116)
at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:890)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1333)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
at oracle.jbo.common.PiggybackOutput.getPiggybackStream(PiggybackOutput.java:173)
at oracle.jbo.common.JboServiceMessage.marshalRefs(JboServiceMessage.java:267)
at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:343)
at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:316)
at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processMessage(AbstractRemoteApplicationModuleImpl.java:2283)
at oracle.jbo.server.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:7509)
at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.sync(AbstractRemoteApplicationModuleImpl.java:2221)
at oracle.jbo.server.remote.ejb.ServerApplicationModuleImpl.doMessage(ServerApplicationModuleImpl.java:79)
at oracle.jbo.server.ejb.SessionBeanImpl.doMessage(SessionBeanImpl.java:474)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteAMReservation_StatefulSessionBeanWrapper906.doMessage(RemoteAMReservation_StatefulSessionBeanWrapper906.java:286)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)This is a typical interaction between 2 server-side components (view-object and app module). Now the question is why is this exception thrown? Any answers?
This application is one that we have migrated from 904 to 1013 and are trying to get it running in 3-tier.
Regards,
AnupamSorry I missed out some semicolons, the script follws:
-- The following TABLE was created to simulate the issue
CREATE TABLE TEST_OBJECT
ASSET_ID NUMBER,
OBJECT_ID NUMBER,
NAME VARCHAR2(50)
INSERT INTO TEST_OBJECT VALUES(1,1,'AAA');
INSERT INTO TEST_OBJECT VALUES(2,2,'BBB');
INSERT INTO TEST_OBJECT VALUES(3,3,'CCC');
COMMIT;
SELECT * FROM TEST_OBJECT;
-- The following TYPES was created to simulate the issue
CREATE OR REPLACE
TYPE DUTYRESULTOBJECTTAB AS TABLE OF DUTYRESULTOBJECT;
CREATE OR REPLACE
type DutyResultObject as object
( ASSET_ID number,
OBJECT_ID number,
NAME varchar2(150)
-- The following PACKAGE N FUNCTION was created to simulate the issue
CREATE OR REPLACE PACKAGE TESTOBJECTPKG
IS
FUNCTION OBJECTSEARCH(P_RESOURCE IN NUMBERLIST) RETURN DUTYRESULTOBJECTTAB;
END;
CREATE OR REPLACE PACKAGE BODY TESTOBJECTPKG
IS
FUNCTION OBJECTSEARCH(P_RESOURCE IN NUMBERLIST) RETURN DUTYRESULTOBJECTTAB
IS
BULKDUTYRESULTOBJECTTAB DUTYRESULTOBJECTTAB;
BEGIN
SELECT DUTYRESULTOBJECT(ASSET_ID, OBJECT_ID, NAME)
BULK COLLECT INTO BULKDUTYRESULTOBJECTTAB
FROM TEST_OBJECT;
RETURN BULKDUTYRESULTOBJECTTAB;
END;
END;
[\code] -
Problem with Application server
Hi All,
I'm facing problem with Application Server. When I installed the appserver and started it.. It started with the message " server has been started and some services will run at back". But when I tried stopping it using the stop default server i got the message that there is no server running but when i saw in the task manager i cud see two process running 1) appserver.exe and 2) imqbroker(something).exe so eventually I had to kill it.
Now when I'm trying to start the application server again its giving me this message "CLI156 Could not start the domain domain1" and below is the log file attached if its of any help
[#|2005-08-31T23:37:57.000+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-08-31T23:37:57.015+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\bin].|#]
[#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-08-31T23:38:15.796+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-08-31T23:38:16.484+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-09-01T00:48:45.484+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-09-01T00:48:45.531+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-09-04T04:12:39.281+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-09-04T04:12:39.343+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\var\instances|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-09-04T04:13:50.453+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:176)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:101)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:281)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1894)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:712)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:293)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
... 3 more
Caused by: java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:156)
... 21 more
|#]
[#|2005-09-04T04:13:50.484+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:376)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
Thanks in advance
AjayThe VERY FIRST message in the server log gives you a hint as to what the problem might be. The server thinks you have spaces in your PATH to the application server. Therefore, the solution is to kill the server however you need to (task manager, whatever) and then reinstall it in a path that doesn't contain spaces. That's the low-hanging fruit here; if that doesn't work, well, then we will have to find some other solution.
-
Oracle 8.1.7 driver limit causes problems with CMP
The information below is from Oracle's site and has been noted by a few
people on various message groups. We had upgraded to 8.1.7 but hadn't put
the latest classes12.zip (June 2001) in our classpath. When we do, we get
the following error from the driver/generated code. We believe this is
because we are hitting the limit cited below. I don't know why the Oracle
driver has this limit, but since WL generates this code for the EB, I don't
see an easy way for us to avoid it.
Anyone have any comments on this? Is my interpretation of the stacktrace
correct? If we go back to the old classes12.zip (June 2000) then we don't
have this problem. But in addition to wanting to run the matching zip file
with the version of the DB, we also want to use some of the functionality in
the 8.1.7 zip. Does BEA have a workaround for CMP?
java.rmi.UnexpectedException: Unexpected exception in
sync.server.system.SystemSessionDataBean.setSessionData():
java.sql.SQLException: ORA-01483: invalid length for DATE or NUMBER bind
variable
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1610
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1535)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:2053)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:398)
at
weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:
47)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.update(SystemSessio
nDataPSWebLogic_CMP_RDBMS.java:318)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.store(SystemSession
DataPSWebLogic_CMP_RDBMS.java:284)
at weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:192)
at
weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.jav
a:227)
at
weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.jav
a:355)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:865)
Using Streams to Avoid Limits on setBytes() and setString()
There is a limit on the maximum size of the array which can be bound using
the PreparedStatement class setBytes() method, and on the size of the string
which can be bound using the setString() method.
Above the limits, which depend on the version of the server you use, you
should use setBinaryStream() or setCharacterStream() instead.
When connecting to an Oracle8 database, the limit for setBytes() is 2000
bytes (the maximum size of a RAW in Oracle8) and the limit for setString()
is 4000 bytes (the maximum size of a VARCHAR2 in Oracle8).
When connecting to an Oracle7 database, the limit for setBytes() is 255
bytes (the maximum size of a RAW in Oracle7) and the limit for setString()
is 2000 bytes (the maximum size of a VARCHAR2 in Oracle7).
The 8.1.6 Oracle JDBC drivers may not raise an error if you exceed the limit
when using setBytes() or setString(), but you may receive the following
error:
ORA-17070: Data size bigger than max size for this type
Future versions of the Oracle drivers will raise an error if the length
exceeds these limits.Joe Herbers wrote:
>
I added some debug output to verify that this problem is definitely caused
by the WL generated code/Oracle driver. To do this, I used
the -keepgenerated code on ejbc. Then I modified the generated code to
print the length of the byte array before calling setBytes. I compiled the
class and put an updated version in my bean jar.
When I run our test suite, I see hundreds of calls to setBytes with sizes
such as 315, 368, 1988, 2020. And then occasionally there are sizes of
41932 or 19409. These larger sizes are always followed by the ORA-01483
exceptions.
This appears to be certain confirmation that the problem is caused by the
8.1.7 driver's enforcement of the 4k limit on the methods that the
WL-generated code is using to map our Java byte[] to our Long Raw/BLOB field
in Oracle. Any suggestions for workarounds?Actually, it indicates the driver's being caught by the limitation that
Oracle itself imposes with setBytes(). This is a known issue I believe, and
you should ask support for a patch to ejbc that generates calls to setBinaryStream()
rather than setBytes().
Joe Weinstein
>
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
We use WL 5.1, SP10. I've noticed that sp11 is now out, but it doesn'tseem
to have any fixes for this problem (it mentions Oracle 8.1.6, but not8.1.7,
which seems to be the release in which Oracle started enforcing thislimit).
We're kind of stuck at the moment, I'm surprised no one else hasencountered
this problem with WebLogic (I have seen postings elsewhere about it with
other AppServers)
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Joe,
From your CMP DD it's clear that you use WL 5.1. Which service pack
do you use?
AFAIR this problem was fixed in WL 6.1, though I'm not sure about
5.1. Could you use ejbc with -keepgenerated option and look at
SystemSessionDataPSWebLogic_CMP_RDBMS.java, particularly
how bind variable related to you LONG RAW? Is setBytes used? Or
it's something like setBinaryStream?
Regards,
Slava Imeshev
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
The table has only three fields: two IDs (Number(18)) and a Long Raw
that
we
are storing a Hashtable in. The field seems to be filled fine most of
the
time. With the old driver, it always works. As soon as we switch thenew
driver in, certain operations fail consistently. I haven't verifiedthat
the size is indeed > 4k in these cases, but our error matches whatothers
have seen. Here's the CMP DD but I doubt that helps...
<weblogic-rdbms-bean>
<pool-name>oracle</pool-name>
<table-name>scc_sm_sys_sess_data</table-name>
<attribute-map>
<object-link>
<bean-field>mlSystemSessionDataID</bean-field>
<dbms-column>sys_sess_data_id</dbms-column>
</object-link>
<object-link>
<bean-field>mlSystemSessionID</bean-field>
<dbms-column>sys_sess_id</dbms-column>
</object-link>
<object-link>
<bean-field>mBSessionData</bean-field>
<dbms-column>sys_sess_data</dbms-column>
</object-link>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Joe,
This limit defines limit written to oracle strings, raws, blobs and
clobs
when setBytes is used. It has nothing to do with the exception
you're
getting.
Could you show us your CMP deployment descriptor(s)?
Regards,
Slava Imeshev
"Joe Herbers" <[email protected]> wrote in message
news:[email protected]...
The information below is from Oracle's site and has been noted by
a
few
people on various message groups. We had upgraded to 8.1.7 but
hadn't
put
the latest classes12.zip (June 2001) in our classpath. When we
do,
we
get
the following error from the driver/generated code. We believe th
is
is
because we are hitting the limit cited below. I don't know why
the
Oracle
driver has this limit, but since WL generates this code for the
EB,
I
don't
see an easy way for us to avoid it.
Anyone have any comments on this? Is my interpretation of the
stacktrace
correct? If we go back to the old classes12.zip (June 2000) then
we
don't
have this problem. But in addition to wanting to run the matching
zip
file
with the version of the DB, we also want to use some of the
functionality
in
the 8.1.7 zip. Does BEA have a workaround for CMP?
java.rmi.UnexpectedException: Unexpected exception in
sync.server.system.SystemSessionDataBean.setSessionData():
java.sql.SQLException: ORA-01483: invalid length for DATE or
NUMBER
bind
variable
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
atoracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1610
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1535)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:2053)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:398)
at
weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:
47)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.update(SystemSessio
nDataPSWebLogic_CMP_RDBMS.java:318)
at
sync.server.system.SystemSessionDataPSWebLogic_CMP_RDBMS.store(SystemSession
DataPSWebLogic_CMP_RDBMS.java:284)
atweblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:192)
at
weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.jav
a:227)
at
weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.jav
a:355)
atweblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:865)
Using Streams to Avoid Limits on setBytes() and setString()
There is a limit on the maximum size of the array which can be
bound
using
the PreparedStatement class setBytes() method, and on the size of
the
string
which can be bound using the setString() method.
Above the limits, which depend on the version of the server you
use,
you
should use setBinaryStream() or setCharacterStream() instead.
When connecting to an Oracle8 database, the limit for setBytes()
is
2000
bytes (the maximum size of a RAW in Oracle8) and the limit forsetString()
is 4000 bytes (the maximum size of a VARCHAR2 in Oracle8).
When connecting to an Oracle7 database, the limit for setBytes()
is
255
bytes (the maximum size of a RAW in Oracle7) and the limit forsetString()
is 2000 bytes (the maximum size of a VARCHAR2 in Oracle7).
The 8.1.6 Oracle JDBC drivers may not raise an error if you exceed
the
limit
when using setBytes() or setString(), but you may receive the
following
error:
ORA-17070: Data size bigger than max size for this type
Future versions of the Oracle drivers will raise an error if thelength
exceeds these limits.
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX -
Problem with the NodeManager in Weblogic 10.0 MP1
Hi,
I have a problem starting the Nodemanager successfully. I have currently installed BEA Weblogic 10.0 MP1. The admin server is getting started successfully. When, I start the Nodemanager with the command:
startnodemanager -machine <hostname>, it neither gives the success message nor the error message. It comes to a stand still. Please see the below text, which appears on the Command prompt, when I run the nodemanager command.
Machine PUNITP128166D.ad.infosys.com
Listen Address: PUNITP128166D.ad.infosys.com
Listen Port: 8097
PID for D:\Ariba9r1\shared/bin/startNodeManager.cmd: 5980
D:\Ariba9r1\BuyerDev9r1\Server\bin>
D:\Ariba9r1\BuyerDev9r1\Server>set CLASSPATH=D:\BEA10\wlserver_10.0\server\lib\A
ribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib\tools.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;
D:\Ariba9r1\BuyerDev9r1\Server>chdir /d "D:\Ariba9r1\shared\nodemanager"
D:\Ariba9r1\shared\nodemanager>"D:\BEA10\jdk150_11\bin\java.exe" -client -Xms32m
-Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Xverify:none -classpath "D:\BE
A10\wlserver_10.0\server\lib\AribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib
\tools.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic.jar;" -Dbea.home=D:\BEA10 -Djava.security.policy=D:\BEA1
0\wlserver_10.0\server\lib\weblogic.policy -DSavedLogsDirectory=D:\Ariba9r1\shar
ed\nodemanager\logs -DJavaHome=D:\BEA10\jdk150_11 -DTrustedHosts=D:\BEA10\wlserv
er_10.0\common\nodemanager\config\nodemanager.hosts -DListenAddress=PUNITP128166
D.ad.infosys.com -DListenPort=8097 -DReverseDnsEnabled=true -DLogToStderr=true -
DLogFile=D:\Ariba9r1\shared\nodemanager\nodemanager.log -DNodeManagerHome=D:\Ari
ba9r1\shared\nodemanager weblogic.NodeManager
After this, when I check the nodemanager status in Console, then the status appears as REACHABLE. Assuming, this to be the successfully message, I try to start the managed servers associated with the Machine/Server. But, it fails and there appears a message on the console with the status as 'Force Shutting Down' for this server.
When I check the logs, there seems to be some problem with the Nulll exception. Please see the below logs as it appears, its only a part of the logs
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040306> <JMS service is active now.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281003> <SAF Service has been initialized.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281002> <SAF Service has been started.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226120> <BEA-101128> <Initializing HTTP services.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101135> <buyerserver1 is the default Web server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101052> <[HttpServer (defaultWebserver) name: buyerserver1] Initialized>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101129> <Initializing the Web application container.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226198> <BEA-180046> <INFO: Logging service enabled.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC license service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Task Manager instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC security service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Transaction service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <JMX> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226604> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://PUNITP128166D.ad.infosys.com:8050/jndi/weblogic.management.mbeanservers.runtime .>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226651> <BEA-000287> <Invoking startup class: ariba.j2ee.appserver.weblogic.Startup.startup(directory=D:\Ariba9r1\BuyerDev9r1\Server)>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227229> <BEA-000288> <ariba.j2ee.appserver.weblogic.Startup reports: Changed directory to D:\Ariba9r1\BuyerDev9r1\Server>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <Management> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227244> <BEA-141187> <Java system properties are defined as follows:
ariba.server.home = D:\Ariba9r1\BuyerDev9r1\Server
awt.toolkit = sun.awt.windows.WToolkit
bea.home = D:\BEA10
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBOracleJDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBDB2JDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBMssqlJDBC.zip;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes;D:\Ariba9r1\BuyerDev9r1\Server\classes\AribaJ2EE.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions;D:\BEA10\wlserver_10.0\server\lib\wls-api.jar
java.class.version = 49.0
java.endorsed.dirs = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed
java.ext.dirs = D:\BEA10\jdk150_11\jre\lib\ext
java.home = D:\BEA10\jdk150_11\jre
java.io.tmpdir = C:\DOCUME~1\suram_vishal\Local Settings\Temp\
java.library.path = D:\BEA10\jdk150_11\bin;.;C:\SYSROOT\system32;C:\SYSROOT;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\jdk150_11\bin;D:\BEA10\patch_wlw1001\profiles\default\native;D:\BEA10\patch_wls1001\profiles\default\native;D:\BEA10\wlserver_10.0\server\native\win\32;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\modules\org.apache.ant_1.6.5\bin;D:\BEA10\jdk150_11\jre\bin;D:\BEA10\jdk150_11\bin;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:/Ariba9r1/BuyerDev9r1/Server/bin/Win32;D:/Ariba9r1/BuyerDev9r1/Server/bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\Program Files\Java\jre1.5.0_06;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;D:\BEA10\wlserver_10.0\server\native\win\32\oci920_8;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\lib\Win32;D:\Ariba9r1\BuyerDev9r1\Server\internal\lib\Win32
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net
java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version = 1.5.0_11-b03
java.security.policy = D:\BEA10\wlserver_10.0\server\lib\weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.5
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.5.0_11
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.5.0_11-b03
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser
org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
os.arch = x86
os.name = Windows 2003
os.version = 5.2
path.separator = ;
sun.arch.data.model = 32
sun.boot.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\serializer.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xalan.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xercesImpl.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xml-apis.jar;D:\BEA10\jdk150_11\jre\lib\rt.jar;D:\BEA10\jdk150_11\jre\lib\i18n.jar;D:\BEA10\jdk150_11\jre\lib\sunrsasign.jar;D:\BEA10\jdk150_11\jre\lib\jsse.jar;D:\BEA10\jdk150_11\jre\lib\jce.jar;D:\BEA10\jdk150_11\jre\lib\charsets.jar;D:\BEA10\jdk150_11\jre\classes
sun.boot.library.path = D:\BEA10\jdk150_11\jre\bin
sun.cpu.endian = little
sun.desktop = windows
sun.io.unicode.encoding = UnicodeLittle
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot Client Compiler
sun.os.patch.level = Service Pack 2
user.country = US
user.dir = D:\Ariba9r1\BuyerDev9r1\Server
user.home = C:\Documents and Settings\suram_vishal
user.language = en
user.name = suram_vishal
user.timezone = Asia/Calcutta
vde.home = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\ldap
weblogic.Name = buyerserver1
weblogic.ReverseDNSAllowed = false
weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
weblogic.management.server = http://PUNITP128166D.ad.infosys.com:8099
weblogic.net.http.URLStreamHandlerFactory = ariba.util.net.URLStreamHandlerFactory
weblogic.nodemanager.ServiceEnabled = true
weblogic.security.SSL.ignoreHostnameVerification = true
weblogic.security.TrustKeyStore = DemoTrust
weblogic.system.BootIdentityFile = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\nodemanager\boot.properties
>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229510> <BEA-000365> <Server state changed to STANDBY>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229525> <BEA-000365> <Server state changed to STARTING>
####<Jun 28, 2010 4:20:29 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722229572> <BEA-149209> <Resuming.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230182> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Warning> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-101162> <User defined listener ariba.server.ormsserver.ServletContextListener failed: java.lang.NullPointerException.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)
at ariba.j2ee.core.J2EEServer.initialize(J2EEServer.java:77)
at ariba.j2ee.core.AribaServletContextListener.contextInitialized(AribaServletContextListener.java:25)
at ariba.server.ormsserver.ServletContextListener.contextInitialized(ServletContextListener.java:26)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jun 28, 2010 4:20:35 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_ADMIN to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Jun 28, 2010 4:20:35 PM IST> <Alert> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Kindly help me in getting this resolved.
Thanks,
Vishal.The error appears to come from the ariba code. I suggest asking them.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53) -
Problems with async callback with the BPEL Java API (Urgent- pls help)
Hi,
I have an async BPEL process and I invoke it form a JSP page using BPEL java API.
I have followed the tutorials and docs at:
$SOA_HOME/bpel\samples\tutorials\102.InvokingProcesses\rmi\com\otn\samples\async
I can inititiate successfully the process, but when I try to get the result using getResult() or getField(String fieldName) methods I get the error:
Oct 2, 2007 2:35:16 PM oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNING: Exception returned by remote server: {0}
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.evermind.io.ClassLoaderObjectInputStream.resolveClass(ClassLoaderObjectInputStream.java:33)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1538)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
at com.evermind.server.rmi.RMIClientConnection.handleMethodInvocationResponse(RMIClientConnection.java:856)
at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:287)
at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:242)
at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:224)
at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:152)
at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:127)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:107)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.util.MissingResourceException: Can't find bundle for base name com.collaxa.cube.i18n.exception_cube, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:836)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:805)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:699)
at com.collaxa.cube.CubeException.getResourceBundle(CubeException.java:142)
at com.collaxa.cube.CubeException.<clinit>(CubeException.java:82)
... 17 more
07/10/02 14:35:16 java.lang.ClassCastException: java.util.MissingResourceException
07/10/02 14:35:16 at com.oracle.bpel.client.delivery.ext.async.thread.AsyncInstanceWatchdog.run(AsyncInstanceWatchdog.java:152)
I check for the result only after I have checked that the instance is closed (completed or faulted) by using IInstanceHandle:getState() and InstanceHandle.STATE_CLOSED_COMPLETED, or IInstanceHandle.STATE_CLOSED_FAULTED
I would like to add that so far I had no problems with invocation and geting result of sync BPEL processes. I do not what is missing for async processes.
Any kind of help is appreciable.
Thanks and best regards,
EvanelaHi again,
i managed to solve the problem:) Totally stupid.. the process variable name was not specified correctly..., but more stupid sounds the error message:))))
Best Regards,
Evanela -
Remote JDBC Problem with Oracle BPM Studio
Hi all, i am facing the Remote JDBC Problem with Oracle BPM Studio.
When i configure a Remote JDBC Connection for SQL in BPM Studio, it prompt me an error.
The SQL Connection is configured as following :
External Resource:
Name : MyDS
Type : SQL Database
Supported Types : Remote JDBC
Details:
Database Type : BPM's Oracle Driver Version:10, 11
J2EE : WLS
Lookup Name : MyAppDS
Configuration for "WLS"
Name : WLS
Type : J2EE Application Server
Supported Types : GENERIC_J2EE
Details:
Initial Context Factory : weblogic.jndi.WLInitialContextFactory
URL : t3://localhost:7001
But, when i try to connect to the Database by using this configuration, I will get an Exception.
An exception occurred while getting a resource from a connector.
Detail:The connector [[ MyDS : SQL : REMOTE_JDBC ]] caused an exception when getting a resource.
Caused by: An exception occurred while getting a resource from a connector.
Detail:The connector [[ WLS : J2EE : J2EE ]] caused an exception when getting a resource.
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [[ Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory ]]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at fuego.jndi.FaultTolerantContext.createContext(FaultTolerantContext.java:726)
at fuego.jndi.FaultTolerantContext.<init>(FaultTolerantContext.java:79)
at fuego.connector.impl.GenericJ2EEConnector.createInitialContext(GenericJ2EEConnector.java:177)
at fuego.connector.impl.GenericJ2EEConnector.createStandaloneContext(GenericJ2EEConnector.java:98)
at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:92)
at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:76)
at fuego.connector.J2EEHelper.getReadOnlyContext(J2EEHelper.java:86)
... 12 more
Edited by: user2262377 on Jun 22, 2009 4:01 PMI guess the weblogic.jar is not included in the studio.
So, i added weblogic.jar (Weblogic 10.3) and wlclient.jar (Weblogic 10.3)
It is working in my simple java code. But, still not working in BPM Studio.
The error logs:
An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
Caused by: java.lang.Object cannot be cast to java.io.Serializable
fuego.connector.ConnectorException: An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:88)
at fuego.connector.JDBCHelper.getReadOnlyConnection(JDBCHelper.java:93)
at fuego.sqlintrospector.BrowserPanel.connect(BrowserPanel.java:395)
at fuego.sqlintrospector.BrowserPanel.populateTree(BrowserPanel.java:200)
at fuego.ui.wizards.ui.CheckTreeBrowser$1.construct(CheckTreeBrowser.java:63)
at fuego.ui.SwingWorker$2.run(SwingWorker.java:39)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: java.lang.Object cannot be cast to java.io.Serializable
at weblogic.iiop.IIOPOutputStream.writeAny(IIOPOutputStream.java:1588)
at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2231)
at weblogic.utils.io.ObjectStreamClass.writeFields(ObjectStreamClass.java:413)
at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:235)
at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:225)
at weblogic.corba.utils.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:182)
at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:1963)
at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:2001)
at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2266)
at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Maybe you are looking for
-
I am new to MDM 7.1 & Multiple Main Tables. I have a very basic questionu2019 My Requirement is that I have to keep Two Main Tables, 1. Manufacturer Parts Master Table and the key is Manufacturer Name + Manufacturer Part No (Two fields) 2.
-
How do I move iTunes library to an external hard drive to use less space?
How do I move iTunes library to an external hard drive to use less space?
-
HT4623 What is the latest os for my iPad 1
How do I upgrade my os on iPad 1 think it's on 5.1.1 can it go to 6 or 7 as required for some of latest apps
-
IDSM should protect serverfarm on FWSM form outside/inside threats
Hi all, We have 6509 with FWSM and IDSM.All vlans (servers,voice,users etc) are homed directly on the FWSM.We need to protect the serverfarm vlan from attacks originating from both inside and outside. All traffic comming from outside and headed for t
-
the following is the result of exporting motion preset to xml. <Motion duration="1" xmlns="fl.motion.*" xmlns:geom="flash.geom.*" xmlns:filters="flash.filters.*"> <source> <Source frameRate="24" x="449.5" y="138.55" scaleX="1" scaleY="1" rotation="