ejbFindByCustomerId Table not found: CUSTOMER_ACCOUNT_XREF

[sysuser1]

Hi!

I downloaded the Getting Started documentation and source, ran all the commands with jboss-build.xml as it is described. Everything reported "BUILD SUCCESSFUL".
Then, when I go to http://localhost:8080/bank/main and login with id 200 and password j2ee, it shows the following:

Server Error
Your request cannot be completed. The server got the following error:
null

And on server side I see exception:

14:55:52,668 ERROR [LogInterceptor] EJBException:
javax.ejb.EJBException: ejbFindByCustomerId Table not found: CUSTOMER_ACCOUNT_XREF in statement [select account_id from customer_account_xref where customer_id = '200' ]
at com.sun.ebank.ejb.account.AccountBean.ejbFindByCustomerId(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.ejb.plugins.BMPPersistenceManager.callFinderMethod(BMPPersistenceManager.java:585)
at org.jboss.ejb.plugins.BMPPersistenceManager.findEntities(BMPPersistenceManager.java:316)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInter
ceptor.java:322)
.....

Using HSQL Database Manager, I can see CUSTOMER_ACCOUNT_XREF table and I checked the request, mentioned in exception message, - it works.


Can somebody help?

[sysuser1]

"jonlee" wrote:

"jonlee" wrote:
This is a known Sun Java RMI problem. Usually on Unices, the recommended solution is to ensure that the /etc/hosts is properly configured for resolution of the hostname.

However, this becomes a problem if you have DHCP on your primary interface. In this case, you may need to revert to using the -D:java.rmi.server.hostname=xxx.xxx.xxx.xxx type substitution or if you have a secondary interface, changing the hostname resolution in /etc/hosts to the secondary interface. You may have network-related side-effects with the latter.

If you must bind to the DHCP interface, you can put in some scripting substitutions to substitute the current assigned IP address. The problem will be that if the IP address changes during the lifetime of the server runtime instance, you will need to restart JBoss.

We've also had problems on Windows when dialled up to a client. If you start up JBoss when connected, the primary interface is the PPP. After disconnection, JBoss fails because the RMI interface was the PPP which has now gone - so you need to restart JBoss for things to work again.

[luke_t]

Please see my last post in this thread

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=44130

and let me know if it fixes your problem.

Luke.