WebSphere Issues


Asynchronous request dispatching

Filed under: Java, WAS — Ishtiaque @ 12:58 pm

Allow Asynchronous Request Dispatching will enable enable the asynchronous request dispatcher (ARD), which enables servlets and JSP pages to make standard include calls concurrently on separate threads. Additionally, the initiation and the insertion of the include contents can be separated so that the include has more time to execute before it needs to be written to the response. ARD requires aggregation of the include contents with the original response. The application server can aggregate the contents in memory or the client browser can aggregate the contents through AJAX. Aggregation type is configurable at the application level.”

We were getting following exception while calling a web service method via AJAX.

8/22/13 17:42:07:437 PKT] 00000064 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: An exception was thrown by one of the service methods of the servlet [JAX-RS Servlet] in application. Exception created : [javax.xml.ws.soap.SOAPFaultException: java.net.ConnectException: Connection refused: no further information
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1052)
at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMinimalMethodMarshaller.demarshalFaultResponse(DocLitBareMinimalMethodMarshaller.java:440)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:597)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:537)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:403)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:188)

We managed to resolve this issue by checking Allow Asynchronous Request Dispatching.

1. Navigate to Servers > Server Types > WebSphere application servers > server_name > Web Container Settings > Web container > Asynchronous request dispatching

2. Check Allow Asynchronous Request Dispatching and restart the server



DSRA9350E: Operation Connection.commit is not allowed during a global transaction

Filed under: Eclipse, Oracle, websphere, WebSphere Application Server — Ishtiaque @ 12:44 pm

I was getting this exception while code was trying to commit the transaction in a EJB web service.

Exception [EclipseLink-4002] (Eclipse Persistence Services – 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: DSRA9350E: Operation Connection.commit is not allowed during a global transaction.
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:421)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:386)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:404)
at org.eclipse.persistence.internal.sessions.AbstractSession.basicCommitTransaction(AbstractSession.java:503)
at org.eclipse.persistence.sessions.server.ClientSession.basicCommitTransaction(ClientSession.java:155)
at org.eclipse.persistence.internal.sessions.AbstractSession.commitTransaction(AbstractSession.java:685)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransaction(UnitOfWorkImpl.java:1572)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1441)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1518)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3171)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3152)

We managed to resolve this issue by checking Non-transactional data source property in WAS.

1. Navigate to
Resources > JDBC > JDBC providers > JDBC_provider > Data sources > data_source > WebSphere Application Server data source properties

2. Check Non-transactional data source property.

Here’s the exception stack trace:

Credit goes my colleague Saqib who help to resolve this issue.




Copy Eclipse Workbench Layout and Working Set from a workspace into another workspace

Filed under: Eclipse, RAD — Ishtiaque @ 12:28 pm

1. MENU -> File -> Switch workspace -> Other -> Copy Settings of
Workbench Layout
Working Sets

2. Copy/backup and replace following folder to new created Workspace.





IBM Rational Clear Case (UCM) basic concepts

Filed under: Java, programming, Rational — Tags: , , , — Ishtiaque @ 12:53 pm
  • SCM : Software Configuration Management is about managing change to software
  • UCM Unified Change Management is IBM’s solution for managing change across the development lifecycle using Rational brand tools. UCM integrates a project’s activities with the software artifacts being changed through a defined, repeatable process.
  • ClearCase : It’s a robust software artifact management tool that provides automated parallel development.
  • ClearQuest : It’s is a flexible, customizable defect and change-tracking application.
  • Activity : An activity represents a unit of work in your UCM project, for example: Defect Fix, New Feature or Enhancement Request.
  • Element : An element is an artifact under source control; it can be a file, or a directory element. For example html, xml, .java, .sql etc
  • Version: Each revision of an element is called a version. An element encompasses the entire set of versions of the artifact.
  • Component: UCM manages the large number of artifacts by collecting related files and directories into a component, an entity that can be managed as a whole.
  • Baseline: A baseline is a stable configuration of one or more components. At the beginning of a project, a configuration manager creates an initial baseline. It identifies one version of each element to be used by developers as a starting point for their development.
  • Project: An object that contains configurations and policies relating to a development effort to create a Product, Group of products, Subset of a product’s functionality
  • VOB: ClearCase stores element versions and components in a repository called a Versioned Object Base (VOB).
  • PVOB: ClearCase stores objects associated with the project in a repository called a Project VOB (PVOB)
  • Development Stream: The development stream contains activities and a baseline that configure which versions of elements appear in the development view. The stream does not necessarily select versions of all elements. Development streams isolate a developer’s changes until the changes are ready to be integrated. Development streams enable parallel development to occur.
  • Development View: Contains the versions appropriate for implementing your activities. Selects zero or one version of each element. Is configured to look at a single stream.
  • Integration Stream:  The main shared stream of a UCM project, typically created and maintained by the project manager. Its primary functions are to: Enable access to versions of the project’s shared elements, Share the results of each developer’s completed activities, Maintain baselines created at various points in time during the development effort.
  • Integration View: Each developer has an integration view that is associated with the project’s integration stream. The developer uses this view to build and test the latest versions of a project’s shared elements.
  • Activity: Changes to artifacts stored in ClearCase are linked to UCM activities. The activity keeps track of: Which artifacts are created or modified as you work on the activity, The stream in which the activity is located, Whether the activity is currently set in any view.
  • Rebase: It brings changes in a baseline from the integration stream to your development stream. Deliver brings activities from your development stream to the integration stream. Before you start a rebase operation, check in all files and directories in your development view. You cannot start a rebase operation from a view that contains checkouts.
  • Deliver: Deliver brings activities from your development stream to the integration stream.
  • Hijacked File: A hijacked file is a file loaded in your view that has been modified without first being checked out. You can hijack a file by disabling the read-only attribute in File Properties or by a explicit command in ClearCase Remote Client.



Blog at WordPress.com.