Tuxedo Client in EJB method + Test Client
Hi,
Currently, the Tuxedo client-side logic is wrapped and exposed as a remote EJB method.
Have the following deployment questions:
(a) How can I set up my WebLogic container to point to a remote Tuxedo domain (e.g. domain name/IP/port). Are there any steps to refer to?
(b) Is it possible to write a Tuxedo client so that the InitialContext object contains the domain name/IP/port etc so that it will bypass the container and test the remote Tuxedo APIs directly? What are the settings I should put in the Properties object?
Any advice?
Thanks.
To clear your first two questions. The password needs to be encrypted before it can be stored in a plaintext file such as config.xml, so the key is used for this purpose. The assumption is your Tuxedo /Domain is configured with SECURITY=DM_PW, and your WTC is configured with SECURITY="DM_PW" for your local access point. Am I correct? If not correct then you either have to correct your configuration or not needed to configure DM_PW.
You need clear password pair from your Tuxedo Application Domain. You use "weblogic.wtc.gwt.genpasswd" to generate encrypted passwords information and use those information to cut/paste to the WLS console. The generated information such as "Local Password" and "Local Password IV" are needed. The "Key" should be the same for all the password, and should be entered as part of your java option "weblogic.wtc.PasswordKey".
For instance,
Your Tuxedo configured a GWTDOMAIN gateway with id TDOM, and a remote access point id WDOM. And in your WTC you configured a local access point with id WDOM, and a remote access point with TDOM.
Your Tuxedo TDOMAIN you configured a password pair for TDomain session (TDOM, WDOM), the password pair looks like (TdomPassword, WdomPassword).
You use "helloworld" for your passowrd key. Then you do the following
java weblogic.wtc.gwt.genpasswd helloworld WdomPassword localLocal Password : cu/008NA4gWgmmJa193PgReSLmQ6Kk08in2fnN9mE0U=
Local Password IV: bat/6QcWm54=
java weblogic.wtc.gwt.genpasswd helloworld TdomPassword remoteRemote Password : T6aC069iqDjZE+O/p5vhalRdBuonClnGJH+WQ/L1MNw=
Remote Password IV: aMtSUUbEDjg=
On you console you have to enter
cu/008NA4gWgmmJa193PgReSLmQ6Kk08in2fnN9mE0U=
for your local password
bat/6QcWm54=
for your local password IV
do the same for your remote password information
and in your WLS command line java options you do
java -Dweblogic.wtc.PasswordKey=helloworld weblogic.Server
Similar Messages
-
EJB Websphere with Universal Test Client
Hi,
I developed an ejb application using WSAD. I developed a universal test client in WSAD. The business logic method which i have written is argumented. When i am testing ejb applicatin with Universal test client, i should see text box to enter value for that arguments. But i am not getting that provision.
The method definition is like this:
private long [] employeeIDs = { 10010, 10023, 10045, 10051, 10061 };
private String [] employees = {"Frank", "Sam", "Maddy", "Jack", "Lorette" };
public String getEmployeeName( long employeeID )
throws javax.ejb.CreateException, java.rmi.RemoteException
for ( int i=0; i < employees.length; i++ )
if ( employeeIDs[ i ] == employeeID )
return employees[ i ];
return "ramesh";
Please help me. Thanks in advanceIs this the first time you are using the Universal Test Client? You first have to get to the EJB via either a create (for a Session Bean) or a create or finder method for an entity bean. Once you have the EJB, it should show you all the available methods and when you select one, it should give you the text box to enter the parameters. How far are you getting in the process? By the way, methods have to be defined in the remote or local interface for the UTC to show them.
This has nothing to do with the UTC but why is your getEmployeeName method throwing a CreateException? -
Urgent Please help: Error Testing EJB in Universal Test Client
Hi,
I have to get this working by tommrow guys - can you please help.
I wonder if someone can assist. I am new to WSAD 5.1 and am trying to test an EJB I have created with both local and remote interfaces.
The bean has been created OK and ithe stub files have created for the bean via Generate->Deploy and RMIC code.
The RJB project has been defind in my WAS server correctly. The JNDI name in the EJB is \ejb\MyEJBHome
I start the Universal Test client (UTC) via the options on my WAS Server and then click on the JNDI explorer icon option and see my local EJB Folder and an ejb folder (plus others). If I go to the local EJB folder the stub for my local home inteface appears , I am able to click on it and consumme the bean.
However if I go to the ejb folder I see my home stub for the remote inteface , I do indded need to click on this to get at the remote inteface for my bean. However on clicking it I get a WAS error "null reference found".
It does not appear to be able to get at the MyBeanHome stub (no reference to it).
Ok what am I doing wrong! The project build with no errors and I can see all the stubs in the ejbModule folder. Now is the UTC expecting these stubs to be sitting in a particular directory? if so where?Hi Problem is with
public class MyEJBBean extends AbstractStatelessSessionBean {
private javax.ejb.SessionContext mySessionCtx;
extends AbstractStatelessSessionBean causes a problem in UTC.
Regards. -
Test web service proxy using EJB session bean client...
Hello!
I am following this blog /people/abdelmorhit.elrhazi/blog/2009/10/30/how-to-consume-an-inbound-backend-web-service-in-nwdsjboss-environment to create a EJB session bean client to access the web service proxy...
The blog is not very clear. Where should I be deploying the web service proxy and the EJB session bean (web service client) ? on the PI 7.1 ?
How to find out the URL for the wsdl ?
Thanks> The blog is not very clear. Where should I be deploying the web service proxy and the EJB session bean (web service client) ? on the PI 7.1 ?
"To deploy your web service proxy and session bean, right click on your JBoss server in the Servers view, and click on Add Remove Projects, add you ear file and click finish."
You need a JBoss server. -
Error while running EJB from java client on JBOSS
Hi
As i am new to EJB i have created a helloworld application in ejb which is working fine when i try to call it from servlet but when i try to invoke the same ejb from java client (i.e from diff jvm) on jboss i got the following error:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1399)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.gl.TestClient.main(TestClient.java:39)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:228)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:266)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
... 5 more
Following is my code:
Home Interface:
package com.gl;
import javax.ejb.CreateException;
public interface testHome extends EJBHome {
String JNDI_NAME = "testBean";
public test create()
throws java.rmi.RemoteException,CreateException;
Remote Interface:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBObject;
public interface test extends EJBObject {
public String welcomeMessage() throws RemoteException;
Bean:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
public class testbean implements SessionBean {
public void ejbActivate() throws EJBException, RemoteException {
// TODO Auto-generated method stub
public void ejbPassivate() throws EJBException, RemoteException {
// TODO Auto-generated method stub
public void ejbRemove() throws EJBException, RemoteException {
// TODO Auto-generated method stub
public void setSessionContext(SessionContext arg0) throws EJBException,
RemoteException {
// TODO Auto-generated method stub
public void ejbCreate(){}
public String welcomeMessage(){
return "Welcome to the World of EJB";
ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>testBean</ejb-name>
<home>com.gl.testHome</home>
<remote>com.gl.test</remote>
<ejb-class>com.gl.testbean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
jboss.xml:
<?xml version='1.0' ?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
<jboss>
<enterprise-beans>
<entity>
<ejb-name>testBean</ejb-name>
<jndi-name>testBean</jndi-name>
</entity>
</enterprise-beans>
</jboss>
Client code:
package com.gl;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
public class TestClient {
public static void main(String[] args) throws Exception{
try{
/* Properties props=new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
props.put(Context.PROVIDER_URL, "jnp://localhost:1099");
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL, "localhost:1099");
System.out.println("Properties ok");
//env.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
//env.put(Context.PROVIDER_URL,"http://localhost:8080");
//env.put(Context.SECURITY_PRINCIPAL, "");
//env.put(Context.SECURITY_CREDENTIALS, "");
Context ctx=new InitialContext(props);
System.out.println("context ok");
//testHome home = (testHome)ctx.lookup("testBean");
Object obj = ctx.lookup ("testBean");
System.out.println("ojb = " + obj);
testHome ejbHome = (testHome)PortableRemoteObject.narrow(obj,testHome.class);
test ejbObject = ejbHome.create();
String message = ejbObject.welcomeMessage();
System.out.println("home ok");
System.out.println("remote ok");
System.out.println(message);
catch(Exception e){e.printStackTrace();}
I am able to successfully deployed my ejb on JBOSS but i m getting above error when i am trying to invoke ejb from java client.
kindly suggest me something to solve this issue.
Regards
Gagan
Edited by: Gagan2914 on Aug 26, 2008 3:28 AMIs it a remote lookup? Then maybe this will help:
[http://wiki.jboss.org/wiki/JBoss42FAQ]
- Roy -
[b]EJB Hotel RA Client Error - HELP[/b]
1. Travel schema installed fine
2. Web Client can successfully be run and all the buttons
work fine
3. The only file I modified was in config properties.
Provider_Url = ormi://localhost:8888/OneEJBHotel
4. in oc4j directory: principals file:
user id is "admin", and password was given as
"admin"
4. deployment from jdeveloper is fine as follows:
---- Deployment started. ---- Jan 24, 2003 6:24:08 PM
Wrote EJB JAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel.jar
Wrote WAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.war
Wrote EAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.ear
Invoking OC4J admin tool...
C:\jdeveloper\jdk\jre\bin\javaw.exe -jar C:\jdeveloper\j2ee\home\admin.jar ormi://DLEE/ admin **** -deploy -file C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.ear -deploymentName OneEJBHotel
Auto-unpacking C:\oc4j\j2ee\home\applications\OneEJBHotel-Web.ear... done.
Auto-unpacking C:\oc4j\j2ee\home\applications\OneEJBHotel-Web\OneEJBHotel-Web.war... done.
Copying default deployment descriptor from archive at C:\oc4j\j2ee\home\applications\OneEJBHotel-Web/META-INF/orion-application.xml to deployment directory C:\oc4j\j2ee\home\application-deployments\OneEJBHotel...
Auto-deploying OneEJBHotel (New server version detected)...
Exit status of OC4J admin tool (-deploy): 0
C:\jdeveloper\jdk\jre\bin\javaw.exe -jar C:\jdeveloper\j2ee\home\admin.jar ormi://DLEE/ admin **** -bindWebApp OneEJBHotel OneEJBHotel-Web http-web-site /OneEJBHotel
Exit status of OC4J admin tool (-bindWebApp): 0
Use the following context root(s) to test your web application(s):
http://DLEE:8888/OneEJBHotel
Elapsed time for deployment: 14 seconds
---- Deployment finished. ---- Jan 24, 2003 6:24:22 PM
5. System Configuation
jdeveloper: 9.0.3.1035
DB: oracle 92010
oc4j: 9.0.3.0.0
6. When run from jdeveloper client: run Client.jpr
the following errors were generated:
Process exited with exit code 0.
C:\jdeveloper\jdk\bin\javaw.exe -ojvm -classpath C:\oc4j\samples\ejb\OneEJBHotel\src\classes;C:\oc4j\samples\ejb\OneEJBHotel\config;C:\oc4j\samples\ejb\OneEJBHotel;C:\oc4j\samples\ejb\OneEJBHotel\src\web;C:\jdeveloper\jdev\lib\jdev-rt.jar;C:\jdeveloper\j2ee\home\lib\activation.jar;C:\jdeveloper\j2ee\home\lib\ejb.jar;C:\jdeveloper\j2ee\home\lib\jaas.jar;C:\jdeveloper\j2ee\home\lib\jaxp.jar;C:\jdeveloper\j2ee\home\lib\jcert.jar;C:\jdeveloper\j2ee\home\lib\jdbc.jar;C:\jdeveloper\j2ee\home\lib\jms.jar;C:\jdeveloper\j2ee\home\lib\jndi.jar;C:\jdeveloper\j2ee\home\lib\jnet.jar;C:\jdeveloper\j2ee\home\lib\jsse.jar;C:\jdeveloper\j2ee\home\lib\jta.jar;C:\jdeveloper\j2ee\home\lib\mail.jar;C:\jdeveloper\j2ee\home\oc4j.jar oracle.otnsamples.OneEJBHotel.client.EJBHotelSample
javax.naming.NamingException: Lookup error: java.io.IOException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791; nested exception is:
java.io.IOException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
RMIContext.java:134
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
InitialContext.java:350
void oracle.otnsamples.OneEJBHotel.client.EJBHotelSample.getHotelSystemBean()
EJBHotelSample.java:132
void oracle.otnsamples.OneEJBHotel.client.EJBHotelSample.main(java.lang.String[])
EJBHotelSample.java:147
Process exited with exit code 0.
Thanks for help!
DavidDavid,
config.properties is used only by the client.jpr. Not by the Web.jpr
config.properties file has been provided for looking up resources[EJB, Datasources] from JNDI tree of OC4J.
Since servlet and other resources are in the same container[Single JVM] there is no need to specify the username, password, Provdier_URL at the time of lookup.
Look at the init method of EJBHotelServlet.java :
Context ctx = new InitialContext();
// Acquire the home interface handle and call the create
//method on it
homeInterface = (HotelSystemHome)ctx.lookup("OneEJBHotel");
Here servlet looks up EJB without any authentication information, as servlet and EJB are in the same container.
Whereas Stand alone client is running outside the OC4J.
So the stand alone client need to authentcate itself for looking up the resources from JNDI tree.
Look at the getHotelSystemBean method of EJBHotelSample.java :
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, prop.getProperty("Initial_Context_Factory"));
env.put(Context.SECURITY_PRINCIPAL, prop.getProperty("Principal"));
env.put(Context.SECURITY_CREDENTIALS, prop.getProperty("Credential"));
env.put(Context.PROVIDER_URL, prop.getProperty("Provider_Url") );
// Associate the properties with the context
Context ctx = new InitialContext(env);
// Acquire the home interface handle and call the create
//method on it
homeInterface = (HotelSystemHome)ctx.lookup("OneEJBHotel");
Here stand alone client looks up EJB by specifying the authentication information, as stand alone client and EJB are running in different JVM's.
Hope this helps...
Cheers
--Venky -
Error after using Test Client (HomeFactory Problem)
All,
I am a newbie with websphere and I try to develop a sample EJB app.
My attempts to test my method of my stateless Session bean were not successful.
I got the following messaage:
[18.07.05 00:02:51:752 CEST] 31c7edd5 WebGroup I SRVE0180I: [bpesoapclient] [bpesoapclient] [Servlet.LOG]: InvokerServlet: init
[18.07.05 00:02:52:003 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: BPERemoteDeploy
[18.07.05 00:02:52:023 CEST] 31c7edd5 ApplicationMg A WSVR0200I: Die Anwendung wird gestartet: query
[18.07.05 00:02:52:083 CEST] 31c7edd5 EJBContainerI I WSVR0207I: Der Start des EJB-JAR wird vorbereitet: querybean.jar
[18.07.05 00:02:52:333 CEST] 31c7edd5 EJBContainerI I WSVR0037I: EJB-JAR-Datei wird gestartet: querybean.jar
[18.07.05 00:02:52:524 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: query
[18.07.05 00:02:52:534 CEST] 31c7edd5 ApplicationMg A WSVR0200I: Die Anwendung wird gestartet: TestDmProjectEAR
[18.07.05 00:02:52:644 CEST] 31c7edd5 EJBContainerI I WSVR0207I: Der Start des EJB-JAR wird vorbereitet: TestDmProject.jar
[18.07.05 00:02:57:671 CEST] 31c7edd5 EJBContainerI I WSVR0037I: EJB-JAR-Datei wird gestartet: TestDmProject.jar
[18.07.05 00:03:01:266 CEST] 31c7edd5 ApplicationMg A WSVR0221I: Die Anwendung wurde gestartet: TestDmProjectEAR
[18.07.05 00:03:01:496 CEST] 31c7edd5 StaffServiceI I STFF0032I: Der Staff Service wurde ordnungsgem葹 gestartet.
[18.07.05 00:03:02:899 CEST] 31c7edd5 HttpTransport A SRVE0171I: Der Transport http ist empfangsbereit an Port 9.080.
[18.07.05 00:03:06:003 CEST] 31c7edd5 HttpTransport A SRVE0171I: Der Transport https ist empfangsbereit an Port 9.443.
[18.07.05 00:03:06:043 CEST] 31c7edd5 SchedulerServ I SCHD0031I: Der Scheduler Service wird gestartet.
[18.07.05 00:03:12:733 CEST] 31c7edd5 SchedulerServ I SCHD0032I: Die Scheduler-Instanz BPEScheduler wird gestartet.
[18.07.05 00:03:17:309 CEST] 31c7edd5 SchedulerDaem I SCHD0038I: Der Scheduler-D舂on f・ die Instanz BPEScheduler wurde gestartet.
[18.07.05 00:03:17:500 CEST] 31c7edd5 SchedulerServ I SCHD0033I: Die Scheduler-Instanz BPEScheduler wurde gestartet.
[18.07.05 00:03:17:520 CEST] 31c7edd5 SchedulerServ I SCHD0001I: Der Scheduler Service wurde gestartet.
[18.07.05 00:03:19:012 CEST] 31c7edd5 RMIConnectorC A ADMC0026I: Der RMI-Connector ist an Port 2809 verf・bar.
[18.07.05 00:03:19:542 CEST] 31c7edd5 WsServer A WSVR0001I: Der Server server1 ist f・ e-business bereit.
[18.07.05 00:03:27:013 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: jndiLookupServlet: init
[18.07.05 00:03:29:517 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /index.jsp: init
[18.07.05 00:03:29:827 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/ejbFrame.jsp: init
[18.07.05 00:03:29:837 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/toolbar/global_nav.jsp: init
[18.07.05 00:03:30:458 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/referencePage.jsp: init
[18.07.05 00:03:30:468 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/parameterPage.jsp: init
[18.07.05 00:03:30:939 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/toolbar/toolbar.jsp: init
[18.07.05 00:03:30:959 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/reference.jsp: init
[18.07.05 00:03:31:520 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: /html/ejbPage/parameter.jsp: init
[18.07.05 00:03:36:457 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: treeExpansionServlet: init
[18.07.05 00:03:39:932 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: selectMemberServlet: init
[18.07.05 00:03:42:145 CEST] 46da2dd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: invokeServlet: init
[18.07.05 00:03:44:388 CEST] 4d94edd7 WebGroup I SRVE0180I: [IBM Universal Test Client] [UTC] [Servlet.LOG]: addObjectServlet: init
[18.07.05 00:03:55:504 CEST] 46da2dd7 SystemOut O class=class com.mbusa.TestDm._EJSRemoteCMPStatusHome_ce727769_Stub
[18.07.05 00:03:55:504 CEST] 46da2dd7 SystemOut O ejbRef ejb/com/mbusa/TestDm/StatusHome is a remote reference.
[18.07.05 00:03:56:105 CEST] 46da2dd7 ExceptionUtil E CNTR0019E: Bei der Verarbeitung der Methode "setStatus" ist eine nicht auf die Anwendung zur・kzuf・rende Ausnahme eingetreten. Ausnahmedaten: com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException
at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:151)
at com.ibm.ejs.container.CMStatelessBeanO.<init>(CMStatelessBeanO.java:53)
at com.ibm.ejs.container.CMStatelessBeanOFactory.create(CMStatelessBeanOFactory.java:40)
at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:668)
at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:755)
at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:78)
at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:516)
at com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContainer.java:2762)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2487)
at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2472)
at com.mbusa.TestDm.EJSRemoteStatelessTestDmSession_3f7076e7.setStatus(EJSRemoteStatelessTestDmSession_3f7076e7.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.rmi.util.ProxyUtil$4.run(ProxyUtil.java:726)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java:351)
at com.ibm.rmi.util.ProxyUtil.invokeWithClassLoaders(ProxyUtil.java:724)
at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:1121)
at $Proxy5.setStatus(Unknown Source)
at com.mbusa.TestDm._TestDmSession_Stub.setStatus(_TestDmSession_Stub.java:266)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.etools.utc.model.ReflectionMethodModel.invoke(ReflectionMethodModel.java:68)
at com.ibm.etools.utc.servlet.InvokeServlet.invoke(InvokeServlet.java:110)
at com.ibm.etools.utc.servlet.InvokeServlet.doPost(InvokeServlet.java:366)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1019)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:592)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:204)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:615)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:144)
... 51 more
Caused by: java.lang.ClassCastException: com.mbusa.TestDm._EJSRemoteCMPStatusHome_ce727769_Stub
at com.mbusa.TestDm.TestDmSessionBean.getHomes(TestDmSessionBean.java:71)
at com.mbusa.TestDm.TestDmSessionBean.ejbCreate(TestDmSessionBean.java:39)
... 57 more
The code looks as follows:
package com.mbusa.vrm;
* Bean implementation class for Enterprise Bean: VrmSession
import javax.ejb.*;
import javax.naming.*;
import java.rmi.RemoteException;
import java.sql.Date;
import com.test.dm.homeFactory.*;
public class TestDmSessionBean implements javax.ejb.SessionBean {
private javax.ejb.SessionContext mySessionCtx;
protected StatusLocalHome statusHome = null;
* getSessionContext
public javax.ejb.SessionContext getSessionContext() {
return mySessionCtx;
* setSessionContext
public void setSessionContext(javax.ejb.SessionContext ctx) {
mySessionCtx = ctx;
* ejbCreate
public void ejbCreate() throws javax.ejb.CreateException {
getHomes();
* ejbActivate
public void ejbActivate() {
getHomes();
* ejbPassivate
public void ejbPassivate() {
statusHome = null;
* ejbRemove
public void ejbRemove() {
protected void getHomes() {
try {
statusHome = (StatusLocalHome) HomeFactory.singleton().getHome("ejb/com/test/dm/StatusHome");
} catch (NamingException ex) {
ex.printStackTrace();
throw new EJBException("Error looking up homes: "+ex.getMessage());
public void setStatus(int statusId, String description) throws FinderException, CreateException {
try {
StatusLocal status = statusHome.create(statusId);
status.setDescription(description);
} catch (EJBException ex) {
throw new EJBException("Status setStatus failed for "+ statusId);
public String getStatusDEscription(int statusId) throws FinderException, CreateException {
try {
StatusLocal status = statusHome.findByPrimaryKey(new StatusKey(statusId));
return status.getDescription();
} catch (EJBException ex) {
throw new EJBException("Status setStatus failed for "+ statusId);
I appreciate any help!!!
Cheers
GregHi,
I am using the Universal test client to test my methods.
Thank you very much for your help!!!
Greg -
Test client pinned to single node in production
WL 6.1 sp2, Solaris 2.8
Currently we have a bunch of SLSBs deployed in cluster out in production and
a web tier that usually gets and invokes a single SLSB, and they're running
happily. But everyone once in a while, we get an asymmetrical exception,
where one node in the cluster is giving us bad results. What I like to do
is write some simple test clients that can pin to a particular node and
diagnose just that node while the regular client (web tier) still
round-robins in production.
Our SLSBs do not have <stateless-clustering> elemements at all in
weblogic-ejb-jar.xml, so <stateless-bean-is-clusterable> defaults to true.
My understanding is this means WL will round robin at 3 different levels:
jndi Context, EJBHome and EJBObject, unless server-client is co-located in
which WL will always pick the local object.
What I have tried to do is to write the test client with a single url in
PROVIDER_URL
and PIN_TO_PRIMARY_SERVER set to true in InitialContext construction. This
does not seem to work; by the time I get the EJBHome, create the EJBObject
and invoke a test method, I see round-robin occuring. I can understand a
reason FOR this behavior, and a counter-argument AGAINST this behavior. The
reason why WL is still round-robining is because only the Context is pinned
to the primary server; subsequent EJBHome and EJBObject are cluster-aware,
and hence will round-robin, which in fact it is doing. But then the reason
against this observation is that once I retrieve InitialContext, the
subsequent EJBHome and EJBObject are all available locally. So shouldn't WL
do co-location optimization and hence never round-robin???
Here are some alternative framework I've thought up so I can write a test
client that pins to a specific ejb server:
1) Create a second set of DD's in weblogic-ejb-jar.xml, this time setting
stateless-bean-is-clusterable to false, and have the test client us this for
pinning.
2) Expose a co-located servlet that will accept ejb invocation (via SOAP or
customized RPC). Servlet invocation will always be ip-specific, and
hopefully co-location of web and ejb tier will
Problem with #1 is 2 sets of DD's, hence 2 sets of EJBHomes/Objects that
behave slightly differently.
Problem with #2 is the complexity of a new web tier just for pinning, which
then also means the test client doesn't exactly replicate my actual web
client calls.
Is there a simple solution to isolate and diagnose a single node in a
production cluster? Am I missing something? Much appreciated!
Gene
WL 6.1 sp2, Solaris 2.8
Currently we have a bunch of SLSBs deployed in cluster out in production and
a web tier that usually gets and invokes a single SLSB, and they're running
happily. But everyone once in a while, we get an asymmetrical exception,
where one node in the cluster is giving us bad results. What I like to do
is write some simple test clients that can pin to a particular node and
diagnose just that node while the regular client (web tier) still
round-robins in production.
Our SLSBs do not have <stateless-clustering> elemements at all in
weblogic-ejb-jar.xml, so <stateless-bean-is-clusterable> defaults to true.
My understanding is this means WL will round robin at 3 different levels:
jndi Context, EJBHome and EJBObject, unless server-client is co-located in
which WL will always pick the local object.
What I have tried to do is to write the test client with a single url in
PROVIDER_URL
and PIN_TO_PRIMARY_SERVER set to true in InitialContext construction. This
does not seem to work; by the time I get the EJBHome, create the EJBObject
and invoke a test method, I see round-robin occuring. I can understand a
reason FOR this behavior, and a counter-argument AGAINST this behavior. The
reason why WL is still round-robining is because only the Context is pinned
to the primary server; subsequent EJBHome and EJBObject are cluster-aware,
and hence will round-robin, which in fact it is doing. But then the reason
against this observation is that once I retrieve InitialContext, the
subsequent EJBHome and EJBObject are all available locally. So shouldn't WL
do co-location optimization and hence never round-robin???
Here are some alternative framework I've thought up so I can write a test
client that pins to a specific ejb server:
1) Create a second set of DD's in weblogic-ejb-jar.xml, this time setting
stateless-bean-is-clusterable to false, and have the test client us this for
pinning.
2) Expose a co-located servlet that will accept ejb invocation (via SOAP or
customized RPC). Servlet invocation will always be ip-specific, and
hopefully co-location of web and ejb tier will
Problem with #1 is 2 sets of DD's, hence 2 sets of EJBHomes/Objects that
behave slightly differently.
Problem with #2 is the complexity of a new web tier just for pinning, which
then also means the test client doesn't exactly replicate my actual web
client calls.
Is there a simple solution to isolate and diagnose a single node in a
production cluster? Am I missing something? Much appreciated!
Gene
-
Client calling EJB + No object bound eror
Hi,
I am a newbie to oc4j. I have tried to get a client to call a stateless ejb using a bat file outside the server, with no luck. I get NamingException: No object bound for java:comp/env/EmployeeBean when doing a jndi lookup. I have read the doc's, tried the answers in the forum and I even used the example code provided from oracle, but I still get the same error message every time.
Has anyone come across this issue when calling an ejb from a client??
Any help would be greatly appreciated. Its driving me crazy.
Thanks
DavidHi,
I will check out the link, thank you. I am a newbie to java and oracle, so any help would be great. i wasnt sure which bits of code would be really helpfull, so i just put most of it in, sorry if it is too much info.
i am using oracle9ias release 1.0.2.2a (i dont know if this would make any difference). I deploy all my ears using the enterprise manager. The client-jar is within the ear. i use a bat to run the Client code.
I can get a servlet to call the same ejbs and that works fine.
#batfile
========
i set the classpath which including refernces to oc4j.jar and oc4jclient.jar and my ejb-jar
and then i use
set BigD=-Dorg.omg.CORBA.ORBInitialHost=localhost -Duser.timezone=ECT
java.exe %BigD% -classpath "%classpath%" com.test.client.Client
//Client Code
=============
public class Client {
public static void main(String[] args) {
System.out.println("Client started again...");
try {
Context context = new InitialContext();
System.out.println("got context");
Object homeObject = context.lookup("java:comp/env/ejb/ConsumerRequestSession");
ConsumerRequestSessionHome home = (ConsumerRequestSessionHome) PortableRemoteObject.narrow(homeObject, ConsumerRequestSessionHome.class);
System.out.println("got home");
ConsumerRequestSession remote = (ConsumerRequestSession) PortableRemoteObject.narrow(home.create(), ConsumerRequestSession.class);
System.out.println("got remote");
String retValue = remote.getString();
System.out.println("The retValue from client is : " + retValue);
}catch(Exception e) {
e.printStackTrace();
System.out.println("ERROR in try block of client when creating jndi :" + e.getMessage());
#jndi
====
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
java.naming.provider.url=ormi://localhost/test
java.naming.security.principal=admin
java.naming.security.credentials=welcome
#application-client.xml
=======================
<application-client>
<display-name>ejb/ConsumerRequestSession</display-name>
<ejb-ref>
<ejb-ref-name>ejb/ConsumerRequestSession</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.test.ejb.ConsumerRequestSessionHome</home>
<remote>com.test.ejb.ConsumerRequestSession</remote>
</ejb-ref>
<!-- <display-name>EmployeeBean</display-name>
<ejb-ref>
<ejb-ref-name>EmployeeBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>employee.EmployeeHome</home>
<remote>employee.Employee</remote>
</ejb-ref>
-->
</application-client>
#orion-application-client.xml
=============================
<orion-application-client>
<ejb-ref-mapping location="com/test/ejb/ConsumerRequestSession" name="ejb/ConsumerRequestSession"/>
<!--<ejb-ref-mapping name="EmployeeBean" location="employee/EmployeeBean" />
<ejb-ref-mapping name="EmployeeBean" location="employee/EmployeeBean" />-->
</orion-application-client>
#ejb-jar.xml
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>ejb/ConsumerRequestSession</ejb-name>
<home>com.test.ejb.ConsumerRequestSessionHome</home>
<remote>com.test.ejb.ConsumerRequestSession</remote>
<ejb-class>com.test.ejb.ConsumerRequestSessionEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>ejb/ConsumerRequestSession</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
#orion-ejb-jar.xml
==================
<orion-ejb-jar>
<enterprise-beans>
<session-deployment location="com/test/ejb/ConsumerRequestSession" name="ejb/ConsumerRequestSession"/>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>" impliesAll="true"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
thank you for your help
david. -
WebLogic Test Client, throws java.lang.NoSuchMethodException
In weblogic server 10.3, the WebLogic Test Client, throws java.lang.NoSuchMethodException for “any” soap fault message from the web service.
In Detail:
Our web services uses JAX-WS spec and are deployed in WebLogic server 10.3.The web service ear file is generated using standard ant utility. We are using “WebLogic Test Client” available through WebLogic server administration console .The issue is, for “any” soap fault message from the web service, the test client generates “java.lang.NoSuchMethodException:” . The key point is we are creating this class. We are not using our own client. WebLogic Test Client 's service response section has the following stack trace.
S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</faultstring>
<detail>
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="com.sun.xml.ws.encoding.soap.SerializationException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="328" method="createDetailFromUserDefinedException" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
<ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
</ns2:stackTrace>
<ns2:cause class="java.lang.NoSuchMethodException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
<ns2:stackTrace>
<ns2:frame class="java.lang.Class" file="Class.java" line="1605" method="getMethod" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="323" method="createDetailFromUserDefinedException" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
<ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
</ns2:stackTrace>
</ns2:cause>
</ns2:exception>
</detail>
</S:Fault>
</S:Body>
</S:Envelope>Thanks for your assistance. Here is the log from weblogic. You may find "xxx" and "yyy" terms. these are given to our specific project oriented names. If you need any further info please let me know. Again a brief about the issue. when the service returns a fault soap message, the server trying to set the error code in a class generated by it's own where the method is not avilable. this happens for all fault soap message. In case of right response from the service no issues. all are working fine.
Note: Max 3000 characters are allowed to post. so truncating initial stack trace.
Thanks, ganesh.
<xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2e0bd8e
Bound datums[Lxxx.sql.STRUCT;@1b2d059
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1aa0f36
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@191d9ba
Bound datums[Lxxx.sql.STRUCT;@1dc70ec
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1def11c
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2683f76
Bound datums[Lxxx.sql.STRUCT;@197400e
Caused by: our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy188.findxxxxxx(Unknown Source)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
... 30 more
Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
... 56 more
Nov 21, 2008 9:38:27 AM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
INFO: Service Provider API did not return any object back.
our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy188.findxxxxxx(Unknown Source)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:71)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
... 56 more
com.sun.xml.ws.encoding.soap.SerializationException: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:328)
at com.sun.xml.ws.fault.SOAPFaultBuilder.getFaultDetail(SOAPFaultBuilder.java:306)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:170)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:265)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
at java.lang.Class.getMethod(Class.java:1605)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:323)
... 30 more -
Runtime Error in Test Client after Transport
Hello SDNers,
I did enhancements to standard SAP component ICCMP_BP_SEARCH in developement system in client XXX of system SSS.
I wanted to test the functionality in client YYY so used SCC1 transaction to transport from client XXX to client YYY.
But when i tried to test the application, it resulted in runtime error.
I had kinda identified the problem while debugging, in the class CL_CHTMLB_CONFIG_UTILITY method CREATE_UI_ELEMENT, it is not taking my Z class references rather it still referring to starndard classes.
My Z classes are created for IMPL class, CTXT class and CN00 class.
If any one has suggestions your help would be appreciated
Thanks in advance.
Best Regards,
SrikanthSrikanth,
Is the definition of the enhancement set defined properly for your test client. This table does not transport and you have to maintain it manually in each client. The view is BSPWDV_EHSET_ASG for SM30. Client is not the first field in the table, so you have to edit this view in each client.
Take care,
Stephen -
Webservice is not working on browser test client
Hi,
I am using Weblogic 9.2 server, and have deployed a webservice application. While accessing the Websevice browser test client (which is a https url) it renders all the available Web Service methods of that service.
When i click on any of the methods the request goes to http and it says page not found. when i change the http to https it renders the method attributes correctly.
I am able to access the web service from some test clients (like SoapUI) without any issues. So the problem is only with the browser based weblogic test client which uses http request internally.
Anybody have idea what could be the reason for this.
Regards,
ChandranHi,
I am using Weblogic 9.2 server, and have deployed a webservice application. While accessing the Websevice browser test client (which is a https url) it renders all the available Web Service methods of that service.
When i click on any of the methods the request goes to http and it says page not found. when i change the http to https it renders the method attributes correctly.
I am able to access the web service from some test clients (like SoapUI) without any issues. So the problem is only with the browser based weblogic test client which uses http request internally.
Anybody have idea what could be the reason for this.
Regards,
Chandran -
Writing a Standalone Client for EJB 3.0 Bean For Weblogic 10
Steps for Writing a Standalone Client
Client Code
package com.client;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import com.StatelessService;
public class StatelessClient {
public static void main(String [] args){
Context ctx = null;
try {
ctx = getInitialContext("t3://localhost:7001/protossbservice","weblogic","weblogic");
Object ref = ctx.lookup("StatelessService#"+StatelessService.class.getName());
StatelessService service = (StatelessService)PortableRemoteObject.narrow(ref,StatelessService.class);
System.out.println("StatelessClient.getMessage() ++");
String message = service.getMessage();
System.out.println("StatelessClient.getMessage --");
System.out.println("Message from Bean "+message);
} catch (NamingException e) {
e.printStackTrace();
private static Context getInitialContext(String url, String user, String password) throws NamingException {
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
h.put(Context.SECURITY_PRINCIPAL, user);
h.put(Context.SECURITY_CREDENTIALS, password);
return new InitialContext(h);
Business Interface
package com;
public interface StatelessService {
public String getMessage();
Stateless Session Bean
package com;
import javax.annotation.PostConstruct;
import javax.ejb.Remote;
import javax.ejb.Stateless;
* Test Stateless Session Bean
@Stateless(mappedName="StatelessService")
@Remote(StatelessService.class)
public class StatelessServiceBean implements StatelessService {
public String getMessage(){
return "I am invoked";emekaco wrote:
Hi,
I am a trainee although with a good background in java.
I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss
Here's a good free e-book but without Netbean. It covers everything you would need to know about EJBs.
>
Again, is container managed bean good for a big project?
The question is too vague to be answered. It's a design decision that needs more details. -
Client copy error in test mode
Dear all,
I am doing a client copy in test mode. Following log is generated. Please tell me solution for it.
Log File:
devdemo\sapmnt\trans\log\CC000007.RBD
Client copy from 25.08.2008 15:43:29
System ID............................ RBD
Target client........................ 120
R/3 Release.......................... 700
Basis Support Package...............SAPKB70012
Host................................. devdemo
Start in background............. .....
User................................. SAP*
Parameter
Source destination......................PRD_300
Source system.........................PRD
Client in source system..............300
Users in source system..............RBASIS
Basis Support Package...............SAPKB70012
Copier profile:.......................SAP_ALL
Table selection
Customizing data .....................X
With application data................ X
Initialize and recreate......... X
/ | Change documents are not copied |
Test mode (without database update).. X
3S3T | Start analysis of system 15:43:29 |
/GC1/CC_EXIT_CLIENT_DELETION executed 0( 0) entries copied
Exit program /GC1/CC_EXIT_CLIENT_DELETION successfully executed 15:43:44
Table /SAPCND/CONDINDX is deleted, not copied
Table /SAPCND/CONDREF is deleted, not copied
Table /SAPCND/CONDRECS is deleted, not copied
/SAPCND/CC_EXCLUDE_TABLES executed 3( 0) entries copied
Exit program /SAPCND/CC_EXCLUDE_TABLES successfully executed 15:43:44
Unknown message with
/SAPCND/CC_GROUP_WS_AA executed 0( 0) entries copied
Runtime 0 seconds
Exit program /SAPCND/CC_GROUP_WS_AA successfully executed 15:43:45
ADDR_CLIENTCOPY_SELECT_TABLES executed 26( 0) entries copied
Runtime 1 seconds
Exit program ADDR_CLIENTCOPY_SELECT_TABLES successfully executed 15:43:47
EFG_FORM_CC_EXIT_BEFORE executed 0( 0) entries copied
Runtime 0 seconds
Exit program EFG_FORM_CC_EXIT_BEFORE successfully executed 15:43:48
Start of deletion methods for client 120
Start the deletion method for object FINB-TR-DERIVATION
End of deletion method of object FINB-TR-DERIVATION
Start the deletion method for object UCM003
End of deletion method of object UCM003
Start the deletion method for object /EACC/ARCHIVING
End of deletion method of object /EACC/ARCHIVING
Start the deletion method for object /EACC/JOURNALCC
End of deletion method of object /EACC/JOURNALCC
Start the deletion method for object /EACC/DERIVATION-1
End of deletion method of object /EACC/DERIVATION-1
Start the deletion method for object FINB-PERSIST
End of deletion method of object FINB-PERSIST
Start the deletion method for object FINB_GENERATOR
Deletion log for client 120, application 10
0 objects registered for deletion
No errors found in simulation mode
Deletion log for client 120, application EA
0 objects registered for deletion
No errors found in simulation mode
Deletion log for client 120, application UG
0 objects registered for deletion
No errors found in simulation mode
End of deletion method of object FINB_GENERATOR
Start the deletion method for object FINB_SBU_DUMMY
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area AS deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area AS deleted on server devdemo_RBD_00
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area XP deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area XP deleted on server devdemo_RBD_00
Buffer FINB_S_KF_CHARS_BUFFER_KEY, area HA deleted on server devdemo
Buffer FINB_S_KF_CHARS_BUFFER_KEY, area HA deleted on server devdemo_RBD_00
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area GN deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area GN deleted on server devdemo_RBD_00
End of deletion method of object FINB_SBU_DUMMY
FINB_TR_CC_EXIT executed 0( 0) entries copied
Runtime 1 seconds
Exit program FINB_TR_CC_EXIT successfully executed 15:43:50
TPM_TRG_CCEXIT_REMOTE executed 0( 0) entries copied
Runtime 0 seconds
Exit program TPM_TRG_CCEXIT_REMOTE successfully executed 15:43:56
CLIENTCOPY_SELECT_TEXTTAB executed 3( 0) entries copied
Runtime 0 seconds
Exit program CLIENTCOPY_SELECT_TEXTTAB successfully executed 15:43:56
Table KX9RABA0000108 is deleted, not copied
Table TABADRH is deleted, not copied
Table TABADRS is deleted, not copied
Table TABADRSF is deleted, not copied
Table TABADRST is deleted, not copied
Table UCF001C is deleted, not copied
Table UCF001G is deleted, not copied
Table UCF001T is deleted, not copied
Table UCF0020 is deleted, not copied
Table UCF0021 is deleted, not copied
Table UCF0022 is deleted, not copied
Table UCF0023 is deleted, not copied
Table UCF002C is deleted, not copied
Table UCF002T is deleted, not copied
Table UCF0032 is deleted, not copied
Table UCF003C is deleted, not copied
Table UCF003G is deleted, not copied
Table UCF003T is deleted, not copied
Table UCF0040 is deleted, not copied
Table UCF0041 is deleted, not copied
Table UCF0042 is deleted, not copied
Table UCF0043 is deleted, not copied
Table UCF004C is deleted, not copied
Table UCF004T is deleted, not copied
Table UCF1000 is deleted, not copied
Table UCF1001 is deleted, not copied
Table UCF1002 is deleted, not copied
Table UCF2300 is deleted, not copied
Table UCF2301 is deleted, not copied
Table UCF2310 is deleted, not copied
Table UCF2311 is deleted, not copied
Table UCF3000 is deleted, not copied
Table UCF3001 is deleted, not copied
Table UCF3010 is deleted, not copied
Table UCF4000 is deleted, not copied
Table UCF4001 is deleted, not copied
Table UCF4002 is deleted, not copied
Table UCF5000 is deleted, not copied
Table UCF5001 is deleted, not copied
Table UCF5002 is deleted, not copied
Table UCF5010 is deleted, not copied
Table UCF600C is deleted, not copied
Table UCF6010 is deleted, not copied
Table UCF6020 is deleted, not copied
Table UCF6030 is deleted, not copied
Table UCF6050 is deleted, not copied
Table UCF6100 is deleted, not copied
Table UCF6110 is deleted, not copied
Table UCF6120 is deleted, not copied
Table UCF6130 is deleted, not copied
Table UCF6140 is deleted, not copied
Table UCF6150 is deleted, not copied
Table UCF6160 is deleted, not copied
Table UCF6170 is deleted, not copied
Table UCF6180 is deleted, not copied
Table UCF6200 is deleted, not copied
Table UCF620C is deleted, not copied
Table UCF620T is deleted, not copied
Table UCF6210 is deleted, not copied
Table UCF6300 is deleted, not copied
Table UCF6310 is deleted, not copied
Table UCF7100 is deleted, not copied
Table UCF7101 is deleted, not copied
Table UCF7102 is deleted, not copied
Table UCF7110 is deleted, not copied
Table UCF7300 is deleted, not copied
Table UCF7400 is deleted, not copied
Table UCF7410 is deleted, not copied
Table UCF7500 is deleted, not copied
Table UCF900C is deleted, not copied
Table UCF9010 is deleted, not copied
Table UCFE01T is deleted, not copied
Table UCFE020 is deleted, not copied
Table UCFE02T is deleted, not copied
Table UCFE03G is deleted, not copied
Table UCFE03T is deleted, not copied
Table UCFE04G is deleted, not copied
Table UCFE04T is deleted, not copied
Table UCFE050 is deleted, not copied
Table UCFE05G is deleted, not copied
Table UCFE05T is deleted, not copied
Table UCFE060 is deleted, not copied
Table UCFE06G is deleted, not copied
Table UCFE06T is deleted, not copied
Table UCFE070 is deleted, not copied
Table UCFE080 is deleted, not copied
Table UCFE081 is deleted, not copied
Table UCFI00C is deleted, not copied
Table UCFI10T is deleted, not copied
Table UCFI200 is deleted, not copied
Table UCFI210 is deleted, not copied
Table UCFT000 is deleted, not copied
Table UCFT001 is deleted, not copied
Table UCFT002 is deleted, not copied
Table UCFV000 is deleted, not copied
Table UCFV200 is deleted, not copied
Table UCFV201 is deleted, not copied
Table UCFV202 is deleted, not copied
Table UCFV20G is deleted, not copied
Table UCFV21G is deleted, not copied
Table UCFV21T is deleted, not copied
Table UCFV220 is deleted, not copied
Table UCFV22T is deleted, not copied
Table UCI1101 is deleted, not copied
Table UCI1201 is deleted, not copied
Table UCI2100 is deleted, not copied
Table UCL2011 is deleted, not copied
Table UCL201G is deleted, not copied
Table UCL201T is deleted, not copied
Table UCM0010 is deleted, not copied
Table UCM0011 is deleted, not copied
Table UCM0012 is deleted, not copied
Table UCM0013 is deleted, not copied
Table UCM0014 is deleted, not copied
Table UCM0015 is deleted, not copied
Table UCM0016 is deleted, not copied
Table UCM001T is deleted, not copied
Table UCM002C is deleted, not copied
Table UCM002T is deleted, not copied
Table UCM0030 is deleted, not copied
Table UCM0031 is deleted, not copied
Table UCM0032 is deleted, not copied
Table UCM0033 is deleted, not copied
Table UCM003C is deleted, not copied
Table UCM003T is deleted, not copied
Table UCM1000 is deleted, not copied
Table UCM1001 is deleted, not copied
Table UCM100G is deleted, not copied
Table UCM100T is deleted, not copied
Table UCM600C is deleted, not copied
Table UCM600T is deleted, not copied
Table UCMA100 is deleted, not copied
Table UCMA101 is deleted, not copied
Table UCMA10C is deleted, not copied
Table UCMA10T is deleted, not copied
Table UCMI100 is deleted, not copied
Table UCMI10C is deleted, not copied
Table UCMI10T is deleted, not copied
Table UCMI200 is deleted, not copied
Table UCMI210 is deleted, not copied
Table UCMI220 is deleted, not copied
Table UCMT010 is deleted, not copied
Table UCMT01C is deleted, not copied
Table UCMT01T is deleted, not copied
Table UCMT100 is deleted, not copied
Table UCMT10C is deleted, not copied
Table UCMT10T is deleted, not copied
Table UCMV01T is deleted, not copied
Table UCRX01C is deleted, not copied
Table UCRX02G is deleted, not copied
Table UCS0100 is deleted, not copied
Table UCS0102 is deleted, not copied
Table UCS0103 is deleted, not copied
Table UCS0104 is deleted, not copied
Table UCS0105 is deleted, not copied
Table UCS0106 is deleted, not copied
Table UCS0107 is deleted, not copied
Table UCS0108 is deleted, not copied
Table UCS010T is deleted, not copied
Table UCS0110 is deleted, not copied
Table UCS01A0 is deleted, not copied
Table UCS01A1 is deleted, not copied
Table UCS01A2 is deleted, not copied
Table UCS01A3 is deleted, not copied
Table UCS020T is deleted, not copied
Table UCT100G is deleted, not copied
Table UCT100T is deleted, not copied
Table UCT101C is deleted, not copied
Table UCT101T is deleted, not copied
Table UCT2001 is deleted, not copied
Table UCT200G is deleted, not copied
Table UCT200T is deleted, not copied
Table UCT2010 is deleted, not copied
Table UCT2011 is deleted, not copied
Table UCT2012 is deleted, not copied
Table UCT2013 is deleted, not copied
Table UCT2014 is deleted, not copied
Table UCT2015 is deleted, not copied
Table UCT2016 is deleted, not copied
Table UCT3000 is deleted, not copied
Table UCT300G is deleted, not copied
Table UCT4000 is deleted, not copied
Table UCT400G is deleted, not copied
Table UCT8000 is deleted, not copied
Table UCT800G is deleted, not copied
Table UCT8010 is deleted, not copied
Table UCT8011 is deleted, not copied
Table UCT8012 is deleted, not copied
Table UCT8013 is deleted, not copied
Table UCT8014 is deleted, not copied
Table UCT8015 is deleted, not copied
Table UCT8016 is deleted, not copied
Table UCT801G is deleted, not copied
Table UCT801T is deleted, not copied
Table /ISDFPS/CS_EXLST is convertible to the RFC system, field missing locally
Table /ISDFPS/CS_EXLST is deleted, not copied
Table AD01DLI is convertible to the RFC system, field missing locally
Table AD01DLI is deleted, not copied
Table ADRC is convertible to the RFC system, field missing locally
Table ADRC is deleted, not copied
Table AFFW is convertible to the RFC system, field missing locally
Table AFFW is deleted, not copied
Table AFIH is convertible to the RFC system, field missing locally
Table AFIH is deleted, not copied
Table AFKO is convertible to the RFC system, field missing locally
Table AFKO is deleted, not copied
Table AFPO is convertible to the RFC system, field missing locally
Table AFPO is deleted, not copied
Table AFRU is convertible to the RFC system, field missing locally
Table AFRU is deleted, not copied
Table AFRV is convertible to the RFC system, field missing locally
Table AFRV is deleted, not copied
Table AFVC is convertible to the RFC system, field missing locally
Table AFVC is deleted, not copied
Table ASMD is convertible to the RFC system, field missing locally
Table ASMD is deleted, not copied
Table AUFK is convertible to the RFC system, field missing locally
Table AUFK is deleted, not copied
Table AUFM is convertible to the RFC system, field missing locally
Table AUFM is deleted, not copied
Table CEZP is convertible to the RFC system, field missing locally
Table CEZP is deleted, not copied
Table CHVW is convertible to the RFC system, field missing locally
Table CHVW is deleted, not copied
Table CHVW_INC is convertible to the RFC system, field missing locally
Table CHVW_INC is deleted, not copied
Table CKIS is convertible to the RFC system, field missing locally
Table CKIS is deleted, not copied
Table CPZP is convertible to the RFC system, field missing locally
Table CPZP is deleted, not copied
Table CRFH is convertible to the RFC system, field missing locally
Table CRFH is deleted, not copied
Table EBAN is convertible to the RFC system, field missing locally
Table EBAN is deleted, not copied
Table EKBE is convertible to the RFC system, field missing locally
Table EKBE is deleted, not copied
Table EKBEH is convertible to the RFC system, field missing locally
Table EKBEH is deleted, not copied
Table EKEK is convertible to the RFC system, field missing locally
Table EKEK is deleted, not copied
Table EKES is convertible to the RFC system, field missing locally
Table EKES is deleted, not copied
Table EKET is convertible to the RFC system, field missing locally
Table EKET is deleted, not copied
Table EKKO is convertible to the RFC system, field missing locally
Table EKKO is deleted, not copied
Table EKPO is convertible to the RFC system, field missing locally
Table EKPO is deleted, not copied
Table EKRS is convertible to the RFC system, field missing locally
Table EKRS is deleted, not copied
Table EQBS is convertible to the RFC system, field missing locally
Table EQBS is deleted, not copied
Table EQUI is convertible to the RFC system, field missing locally
Table EQUI is deleted, not copied
Table EQUZ is convertible to the RFC system, field mWell.. those don't look like errors to me... depending on what copy profile you use SAP chooses what tables to copy and what tables to delete... so basically is just letting you know which tables are not to be copied across...
Read
http://help.sap.com/saphelp_nw04s/helpdata/en/99/0a2a8e7e2511d2a6250000e82deaaa/content.htm
Regards
Juan -
NullPointer when GUI calls method in Client
Hi, I'm relatively new to Java programming and this conference.
I hope the following is not too long winded.
I'm trying to programme a FTP Client which is controlled by a GUI.
My JBuilder project has three classes:
ClientGUI.java and ClientFrame.java (produced with JBUilder's New Application option)
plus AClient.java (this is the 'engine' of the project).
ClientGUI constructs an instance 'frame' of ClientFrame which in turn constructs an instance 'client' of AClient.
The call to the AClient constructor has to be in a try/catch statement,
and takes a JTextArea as a parameter from ClientFrame to allow 'client' to display messges in my GUI.
The AClient constructor opens the Socket connection to a simple server on the same computer.
This part works.
However, when I attempt to use events generated by buttons in my GUI ('frame')to call methods in 'client', I get the following null-pointer exception:-
java.lang.NullPointerException
at ClientFrame.jButton1_actionPerformed(ClientFrame.java:219)
at ClientFrame_jButton1_actionAdapter.actionPerformed(ClientFrame.java:274)
etc...
etc...
These refer to code blocks:-
if ( client.isAlive() ) { /*line 219*/
System.out.println("client alive");
}where isAlive() is a simple test method that returns true,
and
public void actionPerformed(ActionEvent e) {
adaptee.jButton1_actionPerformed(e); /*line 274*/
}'client' is listed as a public field in ClientFrame and is instanciated, so why do I have this problem?
Enclosing the call in a try/catch statement doesn't help.
Thanks in advance. LaurenceThe NullPointer means that the client was not instantiated, though you may think it has been.
Make sure that you are instantiating the correct variable, for instance, if you have a class-level field called client you would do something like this:
public class WhateverClass {
private AClient client;
//other stuff
public WhateverClass(...) {
client = //assignment either
//with new AClient(...)
//or something else
}You would NOT do:
public class WhateverClass {
private AClient client;
//other stuff
public WhateverClass(...) {
AClient client = //assignment either
//with new AClient(...)
//or something else
}Since this would create a second variable of name client that only has scope within the constructor.
Also, if the client is being assigned through a parameter in the constructor, check to make sure that that you are not passing a null value along... Do a System.out.println(client) after the assignement and see what you get. Then you know if the problem occurs in this class or in the class that creates the AClient reference to begin with...
Maybe you are looking for
-
How can I record a QuickTime video clip of in-game action?
I've seen video reviews of games from time to time that show actual video clips of a game being played. The ability to record video clips of a game would come in very handy for me, because I'm experiencing a bug in the graphics of Call of Duty 2 that
-
Java.io.IOException: Not enough space - Weblogic 8.1 on Solaris 8
Hi, We get "java.io.Exception: Not enough space" sometimes when trying to access JSPs hosted on Weblogic 8.1 on Solaris 8. It looks like a problem because of increased swap space usage. What should we do to get rid of this issue Compilation of '.....
-
Trailing space (encode base64) dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW
If there is a space at the end of DN, the dn will become encode base64. The DN is looked like this dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW Put an "-e" option on the ldapsearch can make the "dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW" becomes vis
-
I have been having issues with the iMac and so decided to Erase/Install from scratch after first carrying out a Time Machine backup (which I checked had worked) Once installed I tried to mount the USB drive and it didn't show. I checked all the usual
-
I was able to view gallery before the move. What am I looking for now to post and view photos?