Madhumita Banerjee

Greenhorn
+ Follow
since May 02, 2001
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Madhumita Banerjee

Hi,
I have a Web Project that uses struts. The project needs to access a common java project containing a class that serves as an error handler (ErrorHandler.java).
The ErrorHandler class is instantiated from an Action class in the web project. The ErrorHandler has a method getErrors() which returns an ActionErrors object.
I have placed struts.jar in WEB-INF/lib of the web project and included struts.jar in the classpath for the Java project containing ErrorHandler.java. I have also linked the Java project to the web application.
Though the ErrorHandler class compiles correctly, a 'java.lang.NoClassDefFoundError: org/apache/struts/action/ActionErrors' is thrown at runtime when the getErrors() method is called.
If ErrorHandler.java is made part of the web project it works fine. The 'NoClassDef found' error occurs only when it is moved out into a separate Java Project.
Is there a specific configuration in WSAD5 that can help me run my application when the ErrorHandler is moved out into a separate Java Project?
Thanks.
17 years ago
Hi,
We are using WebSphere Application Server v 4.0.2 on AIX. We are using a cloned environment (both horizontal as well as vertical), with 4 application servers on 2 WebSphere instances. Our database is on a separate AIX box. This box, is however, shared by many other oracle applications (non Web).
We have been having a problem with the Oracle Datasource since our application was launched some time back.
All of the database connections seem to get stuck in a 'Hung' state. The Resource analyzer tells us that connections that were allocated to clients are not getting returned. The strange part is that the problem does not appear at all times, or at regular intervals. It happens all of a sudden. Sometimes the application works well for a week, and then suddenly the problem appears. Restarting the application server solves the problem.
Following is a list of some typical behaviours that we have observed -
1. This problem develops within 5 to 10 minutes (can be less). I.e. the system would be running well at one point of time, and then suddenly, within 5 to 10 minutes, it would die (or the number of database connections start increasing dramatically).
2. Connections are allocated to clients by WebSphere. But these connections seem to get locked up. They are never returned back to the connection pool. Hence the rise in the number of connections in the pool.
3. This cannot be attributed to the code because - The same code runs correctly at all other times. Problem happens only once or twice a week.
4. Generally, it results in the total number of connections in the pool to max out.

5. Eventually, all the processes in the HTTP Server get stuck in the 'Wait' state.
6. Restart of the App Server generally destroys all the connections. Hence the problem gets resolved. This is because the problem generally happens in one instance of time. After the App Server is restarted, it starts behaving normally (on most occasions).
Initially, we felt that the memory of the machine hosting the database was the problem. The memory was then increased, and the problem did not appear again for some time. However, after one week, the problem re-appeared.
Can anyone help?
thanks,
Madhu
18 years ago
Hi,
We are using WebSphere 4.0.2 on AIX. Our application is very session intensive. The back end used is CICS with CTG 3.1 as the transaction gateway. Our application involves getting request parameters from a user login page and passing this information to CICS to retrieve information specific to that user. All the information is then stored in a session and displayed to the user.
However, in some cases the response received does not match the information requested for i.e. information retrieved is that of a different user, though the request parameters passed to CICS are correct.
We are using VAJ 4.0 to generate the java classes used to interact with CICS. We use ECI to communicate with CICS progs. As far as I know, the mode of communication with the CTG is Synchronous ( We are using default settings -Interaction Verb=1 - specified in VAJ). However, is it possible that the responses are being treated as generic asynchronous because of which the application receives whichever response is queued on the CTG? If so how can this be solved? Is some configuration required for the CTG to ensure Synchronous responses?
Also, the mixup with responses seems to occur most frequently at times when the CICS regions were down/CTG was throwing errors and there were simultaneous requests made. If anybody had encountered similar problems and can help out, it would be great.
Madhu
[ July 09, 2002: Message edited by: Madhumita Banerjee ]
[ July 09, 2002: Message edited by: Madhumita Banerjee ]
18 years ago
Hi,
I am using WebSphere App Server v 3.5 on AIX 4.3.3, and IBM HTTPServer as the web server. Everything is running fine, except for the messages that keep coming in the trace.log.ibmhttp.* log files. The error message says- "ERROR: In do_service_time_request, enter_callback_mode failed". Another error entry is "Error - sysmgmt_queue_for_uri : Error returned from sysmgmt_vhost_for_aliasport rc=9". Does anyone have any idea on what this message means....
Thanks,
Madhu
19 years ago
Hi,
I am working with websphere Advanced edition v3.5 and IBM HTTP Server on AIX. the problem I am facing is that - though the websphere Application server is starting up and running fine, the HTTP Server cannot be started. If the LoadModule(mod_ibm_app_server.so), AddModule(mod_app_server.c), Alias(bootstrap.properties) lines are commented out in the httpd.conf file the http server starts up. Also, if i try to start the http server with the above mentioned lines uncommented, I get a core-dumped error.
Any suggestions/ reasons for this ?
Thanks.
19 years ago
Hi,
I have used the jetace tool provided with websphere to create the deployable JAR file. This tool creates a ser file. The steps I followed are:
a) I created a JAR file containing the class files of the remote, home interface and the session bean (i.e. HelloHome.class, Hello.class, HelloEJB.class).
b) I launched the jetace tool and selected this JAR file to be read by jetace.
c) The jetace tool created a ser file. I then saved the deployable JAR file. The files present in the deployable JAR file created by jetace are :
1. Home interface class file
2. Remote interface class file.
3. session bean class file.
4. ser file.
5. comments.dep
6. comments.env
7. meta-inf/manifest.mf
So, u see, the jetace tool creates a ser file. The deployable JAR file is given as input to WebSphere.
(i.e. after i selected create->EJB Bean option, I browsed to the location of the deployable JAR file).
On double-clicking the JAR file, the ser file created by jetace is seen. On selecting this, a message box appears where I select the "deploy only" option.
At the time of deployment (when WebSphere tries to generate stubs and tie classes), I get the error mentioned in my first mail.
Madhu


[This message has been edited by Madhumita Banerjee (edited May 03, 2001).]
19 years ago
Hi,
I have been trying to deploy a stateless session bean in the trial version of Websphere App Server, Advanced Edition (V3.5) on AIX.
I created an initial JAR file containing the bean, home and remote intrface class files. I then created a deployable JAR file using jetace.
When i tried to deploy the Jar file in WebSphere I received the following error.....
EJBDeploy:generateTies(): Generating ties for implementation classes...
rmic command line:
rmic -classpath
/usr/WebSphere/AppServer/deployedEJBs/HelloEJBDepWorkingDir/__ejbjar:/usr/WebSphere/AppServer/lib/ibmwebas.jar:/usr/WebSphere/AppServer/properties:/usr/WebSphere/AppServer/lib/serv let.jar:/usr/WebSphere/AppServer/lib/webtlsrn.jar:/usr/WebSphere/AppServer/lib/lotusxsl.jar:/usr/WebSphere/AppServer/lib/compat.jar:/usr/WebSphere/AppServer/lib/xalan.jar:/usr/WebS phere/AppServer/lib/ns.jar:/usr/WebSphere/AppServer/lib/ejs.jar:/usr/WebSphere/AppServer/lib/ujc.jar:/usr/WebSphere/AppServer//lib/idb.jar:/usr/WebSphere/AppServer/lib/repository.j ar:/usr/WebSphere/AppServer/lib/admin.jar:/usr/WebSphere/AppServer/lib/swingall.jar:/usr/WebSphere/AppServer/lib/console.jar:/usr/WebSphere/AppServer/lib/was20cm.jar:/usr/WebSphere /AppServer/lib/tasks.jar:/usr/WebSphere/AppServer/lib/xml4j.jar:/usr/WebSphere/AppServer/lib/vaprt.jar:/usr/WebSphere/AppServer/lib/sslight.jar:/usr/WebSphere/AppServer/lib/ibmjndi .jar:/usr/WebSphere/AppServer/lib/deployTool.jar:/usr/WebSphere/AppServer/lib/databeans.jar:/usr/WebSphere/AppServer/classes:/usr/WebSphere/AppServer/lib/tools.jar:/usr/WebSphere/A ppServer/lib/bsf.jar:/usr/WebSphere/AppServer/lib/dertrjrt.jar:/usr/WebSphere/AppServer/lib/derdbpw.jar:/usr/WebSphere/AppServer/lib/ivjejb35.jar:/usr/WebSphere/AppServer/lib/js.ja r -keep -iiop -d
/usr/WebSphere/AppServer/deployedEJBs/HelloEJBDepWorkingDir/__ejbjar .EJSRemoteHome
rmic return code = 1
com.ibm.ejs.sm.exception.DeploymentException: Deployment[createEJSJar] failed.
IVJ0805E: There were errors during generation of stubs/ties for the interface classes.
I checked the "__ejbjar" folder and found that the EJSRemoteHome file was not being created.
Can you please let me know what the reason for this error could be and how I can work-around this error ?
Is there any specific setting in WebSphere/jetace environment that I may have overlooked?
i had tried to deploy the EJB in an Application server that I had created. Though I encountered an error while deploying this EJB,i was able to deploy an EJB (jar file) that was provided with the WebSphere example files.
The EJB classes that I created have been included below, for your reference.
Thanks,
Madhu
The EJB classes that I created .........
Home interface -HelloHome.java Remote Interface - Hello.java
Session Bean - HelloEJB.java
The code for each is given below:
HelloHome.java
import javax.ejb.*;
import java.rmi.*;
public interface HelloHome extends EJBHome {
Hello create()
throws RemoteException, CreateException;
}
Hello.java
import javax.ejb.*;
import java.rmi.*;
public interface Hello extends EJBObject {
String sayHello() throws RemoteException;
}
HelloEJB.java
import javax.ejb.*;
import java.rmi.*;
public class HelloEJB implements SessionBean {
String str="Hello";
public void ejbCreate() {
}

public String sayHello() throws RemoteException {
return str;
}
public void setSessionContext(SessionContext sc){}
public void ejbRemove() throws RemoteException {}
public void ejbActivate() throws RemoteException {}
public void ejbPassivate() throws RemoteException {}
}

[This message has been edited by Madhumita Banerjee (edited May 02, 2001).]
[This message has been edited by Madhumita Banerjee (edited May 02, 2001).]
19 years ago