[Beginners Corner] - Re: Deployment order and MYSQL Driver class issues
by PeterJ
zparticle wrote : Unforutnately the app is still loading ahead the JNDI data source getting created.
|
That is one of the joys of working with the beta of the next release - you get to put up with all of the bugs and regressions while they get worked out.
The default deployment ordering has been broken ever since the first beta when the deployers were re-written to be microcontainer-based instead of JMX-based. But things have gotten better - more than 1/2 of the deployment ordering issues I saw in beta4 were fixed in CR1, and I expect more will be fixed in CR2.
So what do you do until then? I try to remember to deploy my apps after the server starts. When I forget (which is often), I simply move my app out of the deploy directory, wait 5 seconds (the time interval between hot deploy runs) and move it back in.
Oh, another possibility - for now create a deploy.last directory within the deploy directory and place your war file there (leave the *-ds.xml file in the deploy directory).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172685#4172685
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172685
18 years
[Beginners Corner] - Re: Deployment order and MYSQL Driver class issues
by zparticle
Okay the hang was, of course, caused by a bug in my logic. The JNDI look up is working now. Unforutnately the app is still loading ahead the JNDI data source getting created.
applicationContext.xml
<bean id="photositeDataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
| <property name="jndiName" value="java:photosite"/>
| <property name="resourceRef" value="false"></property>
| </bean>
jboss-web.xml
<resource-ref>
| <res-ref-name>photosite</res-ref-name>
| <jndi-name>photosite</jndi-name>
| <res-type>javax.sql.DataSource</res-type>
| </resource-ref>
|
web.xml
| <resource-ref>
| <description>DB Connection</description>
| <res-ref-name>photosite</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| </resource-ref>
photosite-ds.xml
| <datasources>
| <local-tx-datasource>
| <jndi-name>photosite</jndi-name>
| <connection-url>jdbc:mysql://localhost:3306/photosite</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>zxcbvzxcv</user-name>
| <password>asfgasdfgqsd</password>
| <min-pool-size>1</min-pool-size>
| <max-pool-size>5</max-pool-size>
| </local-tx-datasource>
| </datasources>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172682#4172682
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172682
18 years
[JBossWS] - Re: IllegalStateException Cannot find property
by PeterJ
I looked at the source code.
The 'outbound' property is set to false when the client sends a request to JBossAS and to true when JBossAS responds back. The exception means that property has not been set.
Earlier in the stack trace, in CommonClient.invoke, line 404, we find that someone commited the cardinal sin of exception handling - they dropped the exception on the floor not even bothering to log it. Instead, they called processPivotInternal which eventually threw the exception that you saw.
So that is why the exception makes no sense - the real cause for the problem was thrown away.
Unfortunately, unless someone else has any ideas, the only thing I can think of is for you to patch CommonClient.invoke and log the exception so that you can discover the root cause.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172673#4172673
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172673
18 years