Announcement

**leeyuiwah** · 14 Jun 2013, 11:37

I have two strange observations.

1. If I saved the dynamically generated XML string into a file under war/ds/, and then use DataSourceManager to load it, I could get the DataSource instance working (responding to fetch() operation correctly).

Code:

String dynDsHandle = "dynDs314784014";
// first store the dynamically generated XML string
// into a *.ds.xml file, and then
DataSource ds = DataSourceManager.get(dynDsHandle)
List list = ds.fetch(null); // okay

2. Furthermore, and this is really strange, even if I just copied the generated DataSource instance (via the fromXML()) IN MEMORY (not file I/O), I could also get the instance working.

Code:

Map<String, DataSource> map = new HashMap<String, DataSource>();
String dynDsHandle = "dynDs314784014";

DataSource ds = DataSource.fromXML(xmlString);

map.put(dynDsHandle, ds); // these two lines are line dummy, but they actually changed the result !
DataSource ds2 = map.get(dynDsHandle);

ds2.fetch(); // Also okay! Very strange

**Isomorphic** · 15 Jun 2013, 00:37

Take a look at the QuickStart, Server Framework chapter - the correct approach for server-side dynamic DataSources is to use DynamicDSGenerator, and not the approach you've attempted here. Details of usage are in the server-side JavaDoc.

**leeyuiwah** · 17 Jun 2013, 14:22

Hi,

I am following the suggestion by "Isomorphic" (probably one of your colleagues) from this post:

http://forums.smartclient.com/showpost.php?p=61795&postcount=8

Anyway, I have got my problem solved by writing the XML string to a file (*.ds.xml) first and then load it using DataSourceManager.

I don't understand why I need to do that but it works. (Could it be a bug with the DataSource.fromXML() method?)

**Isomorphic** · 17 Jun 2013, 18:38

That's an obsolete approach which only works for limited features, which is why we've given the correct approach prominent placement (right in the QuickStart Guide).

You should switch over to the correct approach soon, so that you aren't relying on a hack of writing new files (doesn't work in a variety of environments).

**jay.l.fisher** · 19 Jun 2013, 15:22

We are using the DynamicDSGenerator and have been successfully for some time. But after installing SmartClient Version: v8.3p_2013-06-16/PowerEdition Deployment (built 2013-06-16) we are seeing this message too.

In our case it is intermittent and the datasource name is auto-generated. For example, one time the message might say "Can't find dataSource: isc_DataSource_610 - please make sure that you have a isc_DataSource_610.ds.xml file for it in [webRoot]/shared/ds" but the next time it might say "Can't find dataSource: isc_DataSource_614 ..."

**Isomorphic** · 20 Jun 2013, 09:07

To help us focus in, can you let us know what release you were using before 2013-06-16?

**jay.l.fisher** · 20 Jun 2013, 09:29

We took the 6/13 update a few days prior but not sure if it started showing up before we took the 6.16 build. Before that we were running the 3/13 build.

**Isomorphic** · 21 Jun 2013, 06:43

We see no changes since March 13th that would obviously have an effect on Dynamic DataSources. We're going to need a repro case or at least some more information around the circumstances of these failures to get any further.

That message is badly-worded, by the way - it has been around since before the introduction of DynamicDSGenerator, when the only explanation for a DataSource not being loadable was, there was no .ds.xml file. In your case, it probably means that your DynamicDSGenerator is returning null, and there is no file called isc_DataSource_610.ds.xml.

Finally, those names look like they have been auto-generated by client-side code - is that the case? If so, it implies that the names are meaningless in themselves, in which case how does your DynamicDSGenerator know what DS to generate?

**jay.l.fisher** · 21 Jun 2013, 07:37

The auto-generated name is confusing us too. We have a few places in the app where we create a new DataSource() client side, but it is only used client side.

Since it is intermittent we haven't been able to tell exactly where the problem is, but given the point at which it occurs, it could be related to some initial demo screens that we created a few years ago and haven't touched since.

Does anything look wrong here?

Code:

DataSource newsDataSource = new DataSource();
newsDataSource
		.setDataURL("http://risnews.edgl.com/rss/RssLatestRetailNews");
newsDataSource.setRecordXPath("//item");
DataSourceTextField newsTitleField = new DataSourceTextField("title",
		"Title");
DataSourceLinkField newsLinkField = new DataSourceLinkField("link", "Link");
newsDataSource.setFields(newsTitleField, newsLinkField);
ListGrid newsGrid = new ListGrid();
newsGrid.setAutoFetchData(true);
newsGrid.setShowHeader(false);
newsGrid.setDataSource(newsDataSource);
newsGrid.setFields(new ListGridField("link"));
newsGrid.setLinkTextProperty("title");

// Sample company calendar
DataSource eventDS = new DataSource();
DataSourceSequenceField eventIdField = new DataSourceSequenceField(
		"eventId");
eventIdField.setPrimaryKey(true);
DataSourceTextField nameField = new DataSourceTextField("name");
DataSourceTextField descField = new DataSourceTextField("description");
DataSourceDateTimeField startDateField = new DataSourceDateTimeField(
		"startDate");
DataSourceDateTimeField endDateField = new DataSourceDateTimeField(
		"endDate");
eventDS.setFields(eventIdField, nameField, descField, startDateField,
		endDateField);
eventDS.setClientOnly(true);
eventDS.setTestData(CalendarData.getRecords());
Calendar calendar = new Calendar();
calendar.setDataSource(eventDS);
calendar.setShowAddEventButton(true);
calendar.setAutoFetchData(true);
calendar.setCurrentViewName(ViewName.MONTH);
calendar.setHeight100();
calendar.setWidth100();
calendar.setTitle("Company Calendar");

**jay.l.fisher** · 21 Jun 2013, 08:01

We've discovered the pattern that causes the problem. In our app, we first present a login screen and then load all of our datasources using information from the login screen in our DynamicDSGenerator.

If the user logs out and back in without closing the browser window, when the datasources are loaded again we see a message for each in the SC dev console. Here are a couple of examples.

Code:

10:45:37.542:XRP4:WARN:Log:Specified ID: DailyOrderActivity collides with the ID for an existing SmartGWT component or object. The existing object will be destroyed and the ID bound to the new object.
10:45:37.543:XRP4:WARN:Log:Specified ID: OrdersInProcess collides with the ID for an existing SmartGWT component or object. The existing object will be destroyed and the ID bound to the new object.

We've seen those messages for a long time and it makes sense that the old ds objects are destroyed and this has never been a problem.

But now, after those messages show up in the console we see these messages.

Code:

10:45:37.976:XRP7:WARN:RPCManager:Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/dsundefined - response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 59,
httpResponseCode: 200,
httpResponseText: "//isc_RPCResponseStart-->[{data:"Can't f..."[258],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -1,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Can't find dataSource: isc_DataSource_61..."[137],
invalidateCache: false,
isDSResponse: true,
queueStatus: -1}
10:45:37.995:XRP9:WARN:RPCManager:Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/dsundefined - response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 60,
httpResponseCode: 200,
httpResponseText: "//isc_RPCResponseStart-->[{data:"Can't f..."[258],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -1,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Can't find dataSource: isc_DataSource_61..."[137],
invalidateCache: false,
isDSResponse: true,
queueStatus: -1}
10:45:38.090:XRP3:WARN:RPCManager:Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/dsundefined - response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 61,
httpResponseCode: 200,
httpResponseText: "//isc_RPCResponseStart-->[{data:"Can't f..."[258],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -1,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Can't find dataSource: isc_DataSource_61..."[137],
invalidateCache: false,
isDSResponse: true,
queueStatus: -1}
10:45:38.107:XRP6:WARN:RPCManager:Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/dsundefined - response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 62,
httpResponseCode: 200,
httpResponseText: "//isc_RPCResponseStart-->[{data:"Can't f..."[258],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -1,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Can't find dataSource: isc_DataSource_61..."[137],
invalidateCache: false,
isDSResponse: true,
queueStatus: -1}
10:45:38.312:XRP2:WARN:RPCManager:Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/dsundefined - response: {operationId: "custom",
clientContext: undef,
context: Obj,
transactionNum: 71,
httpResponseCode: 200,
httpResponseText: "//isc_RPCResponseStart-->[{data:"Can't f..."[258],
xmlHttpRequest: [object XMLHttpRequest],
transport: "xmlHttpRequest",
status: -1,
clientOnly: undef,
httpHeaders: Obj,
isStructured: true,
callbackArgs: null,
results: Obj,
data: "Can't find dataSource: isc_DataSource_61..."[137],
invalidateCache: false,
isDSResponse: true,
queueStatus: -1}

On the server side console we get this stack trace.

Code:

java.lang.Exception: Can't find dataSource: isc_DataSource_614 - please make sure that you have a isc_DataSource_614.ds.xml file for it in [webRoot]/shared/ds
	at com.isomorphic.application.AppBase.executeDefaultDSOperation(AppBase.java:672)
	at com.isomorphic.application.AppBase.executeAppOperation(AppBase.java:658)
	at com.isomorphic.application.AppBase.execute(AppBase.java:491)
	at com.isomorphic.datasource.DSRequest.execute(DSRequest.java:2033)
	at com.isomorphic.servlet.IDACall.handleDSRequest(IDACall.java:216)
	at com.islandpacific.gui.server.customDataSource.IpIDACall.handleDSRequest(IpIDACall.java:83)
	at com.isomorphic.servlet.IDACall.processRPCTransaction(IDACall.java:173)
	at com.islandpacific.gui.server.customDataSource.IpIDACall.processRPCTransaction(IpIDACall.java:54)
	at com.isomorphic.servlet.IDACall.processRequest(IDACall.java:138)
	at com.isomorphic.servlet.IDACall.doPost(IDACall.java:74)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at com.isomorphic.servlet.BaseServlet.service(BaseServlet.java:152)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1097)
	at com.islandpacific.gui.server.GWTCacheControlFilter.doFilter(GWTCacheControlFilter.java:44)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1088)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:343)
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:97)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:100)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:35)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:188)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:79)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at com.islandpacific.gui.security.IpConcurrentSessionFilter.doFilter(IpConcurrentSessionFilter.java:55)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:355)
	at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:149)
	at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
	at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1088)
	at com.isomorphic.servlet.CompressionFilter.doFilter(CompressionFilter.java:259)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1088)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:843)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

**Isomorphic** · 21 Jun 2013, 10:42

OK, we have a suspicion about a possible cause for this, but it's pretty deep so a way to reproduce it ourselves would be helpful. Can you post the code that re-loads the DataSources?

**jay.l.fisher** · 21 Jun 2013, 11:34

I've narrowed it down to a fetch to a particular datasource that is done after the datasources have been loaded. Now that I can recreate it I stopped in debug after the datasources are evalulated. The next thing that happens is a series of fetches to this datasource.

Code:

<DataSource ID="AS400Command" dataFormat="iscServer"
	webServiceOperations="fetch" dbName="as400"
	serverConstructor="com.islandpacific.gui.server.customDataSource.AS400CommandDS">
	<!-- An interface for the client to request the execution of an AS400 command. -->
	<fields>
		<field name="Command" title="Command" type="text" primaryKey="true"/>
		<field name="Success" title="Completed successfully" type="boolean"/>
	</fields>
</DataSource>

The fetch request is made in this method.

Code:

	/**
	 * Call an AS/400 command.
	 * @param commandText
	 * @param callback IpBooleanCallback When complete, calls onTrue if the command completed successfully or onFalse if the Command failed
	 */
	public static void executeAS400Command(String commandText, final IpBooleanCallback callback) {
		DSRequest request = new DSRequest();
		Criteria criteria = new Criteria("Command", commandText);
		myAs400CommandDS.fetchData(criteria, new DSCallback() {
			@Override
			public void execute(DSResponse response, Object rawData,
					DSRequest request) {
				Record values = (Record) response.getData()[0];
				boolean commandSuccessful = values.getAttributeAsBoolean("Success");
				if (commandSuccessful) {
					callback.onTrue();
				}
				else {
					callback.onFalse();
				}
			}
		}, request);
	}

This is the serverConstructor class that satisfies the fetch request using a utility class to execute a server command string passed in the Command field as critieria.

Code:

package com.islandpacific.gui.server.customDataSource;

import java.util.HashMap;
import java.util.Map;

import com.isomorphic.datasource.BasicDataSource;
import com.isomorphic.datasource.DSRequest;
import com.isomorphic.datasource.DSResponse;

public class AS400CommandDS extends BasicDataSource {

	
	@SuppressWarnings("unchecked")
	@Override
	public DSResponse execute(DSRequest req) throws Exception {
		
		DSResponse response = new DSResponse();

		if (req.getOperationType().equals("fetch")
				|| req.getOperationType().equals("custom")) {
			Map criteria = req.getCriteria();
			if (criteria == null) {
				response.setData("Criteria not set for AS400 Command.");
				response.setFailure();
				return response;
			}
			if (!criteria.containsKey("Command")) {
				response.setData("Criteria not complete for AS400 Command.");
				response.setFailure();
				return response;
			}
			String command = (String)criteria.get("Command");
			
			Map responseData = new HashMap();
			responseData.put("Command", command);
			boolean success = AS400Utilities.executeAS400Command(command);
			responseData.put("Success", success);
			response.setData(responseData);
			return response;
		}

		response.setData("Invalid request type for AS400Command");
		response.setFailure();
		return response;

	}
}

**Isomorphic** · 24 Jun 2013, 18:13

It looks like there are some missing pieces to your sample code. The execute() function in AS400CommandDS calls a single-argument function AS400Utilities.executeAS400Command() which expects a boolean return value. However, the snippet of AS400Utilities that you included instead defines a two-argument executeAS400Command() function with a void return value. In addition, you've nowhere defined IpBooleanCallback.

Can you provide a complete reproducing sample, ideally as a set of attached files rather than various snippets of things?

**godonnell_ip** · 25 Jun 2013, 06:05

Thank you for your responses so far. Jay is out of pocket this week and has asked me to pick up where he left off with you.

That being the case, it will take a little time to prepare the test case for which you asked, so in the meantime I thought I'd post the following snippet which shows the server-side definition for executeAS400Command(). The prior snippet that you correctly stated was mismatched with the remainder of the supplied code is actually the client-side implementation.

We will be working on putting together a test case until and unless you are able to discern the issue by examining this latest snippet.

Thanks again.

Code:

	/**
	 * Execute a command on the AS400
	 * @return true if the command succeeds
	 */
	public static boolean executeAS400Command(String commandText) {
		AS400 as400 = getAS400();
		if (as400 == null) {
			return false;
		}
		CommandCall command = new CommandCall(as400);
		log.info("Executing AS/400 command: " + commandText);
		boolean response = false;
		try {
			response = command.run(commandText);
		} catch (Exception e) {
			response = false;
		}
		log.info("AS/400 command completion: " + response);
		AS400Utilities.returnAS400(as400);
		return response;
	}

Announcement

Dynamic DataSource on Server: Error: Can't find dataSource

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment