War file generated in WinXPPro gives runtime error in Win2003Server

Question

Hi,
I'm using Netbeans4.1 to compile my jsp application war file in windowsXP Pro environment.
But when I try to deploy the war file to production server that is running Win2003Server, it gives the following error. At the end, I install NetBeans4.1 on the server and compile the war file in the win2003Server environment and everything works fine.
So, I wonder if war file is depended on the OS environment. Anyone face this issue before? If yes, would appreciate your comments.
Cannot create PoolableConnectionFactory (Server connection failure during transaction. Due to underlying exception: 'java.net.ConnectException: Connection timed out: connect'.
** BEGIN NESTED EXCEPTION **
java.net.ConnectException
MESSAGE: Connection timed out: connect
STACKTRACE:
java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.SocksSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:124)
     at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:225)
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1899)
     at com.mysql.jdbc.Connection.<init>(Connection.java:450)
     at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
     at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
     at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
     at my.com.snt.util.DBUtil.getConnection(DBUtil.java:44)
     at org.apache.jsp.sysSignInTop_jsp._jspService(org.apache.jsp.sysSignInTop_jsp:71)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)
** END NESTED EXCEPTION **
Attempted reconnect 3 times. Giving up.)

Answer 1

Hey Evert-Jan,
A small (but long :-)) question : I am facing the same issue with JHeadstart 10.1.3.3.85 (latest release I believe?).
Current situation :
A master - detail structure, where each detail is a tab page on the same page as the master table. 2 of the tab pages have a master-detail structure themselves. The contents of the tab pages were generated to regions, because otherwise the jspx would become too large. The 2 tab pages with a master-detail contained 2 regions, one for the master, and one for the detail group.
My first problem (with JHS 10.1.3.3.53) with the 2 master detail tab pages was the following : when changing the master record on the tab, the detail record did not refresh, although the refresh condition was set to "Always". After a long search, I finally found that the partialTriggers were not set correctly by the JAG:
<!-- Pseudo code for content of one tab page -->
<!-- Region with master table (id : masterTableId) in it -->
<region id="masterRegionId" .../>
<!-- Region with detail table in it -->
<panelGroup partialTriggers="masterTableId" ...>
<region id="detailRegionId" .../>
</panelGroup>
Here, the partialTrigger of the detail panelGroup should ofcourse be "masterRegionId:masterTableId".
After upgrading to version 10.1.3.3.85, this was resolved (partialTriggers were generated correctly), but then I was unable to switch tabs. I kept getting the Exception of the thread starter. For now, I solved this issue by disabling the "Generate Group In Region file" property for the 2 tabs that have a master detail on them, which works. But it would be a lot cleaner to be able to separate all tabs in a separate region.
There are a few templates that I redefined, but none of them were changed in the upgrade from .53 to .85 I think. Could you tell me what template was changed to fix this? And if the fix was implemented in version .85?
Thanks in advance!!
Chris