When Oracle acquired BEa they began moving all the bea and weblogic sites into the oracle.com domain.
Problem of course is that a lot of good articles are referenced on the web to their old original Bea urls.
This page lists where the equivilent sections exist on the oracle site
Overview of migration -> http://wiki.oracle.com/page/Dev2Dev+%2F+Arch2Arch+Status+and+Migration+Update?t=anon
Dev2dev and arch2arch -> http://www.oracle.com/technology/pub/articles/dev2arch/index.html
Friday, April 10, 2009
Weblogic JMS rollback
I was getting the following error in a Weblogic 9.2 deployment.
####<10-apr-2009> <info> <ejb> <vmmiddleware11> <mwalsb11> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1239355884374> <bea-010213> <message-driven xid="BEA1-23F28F44E9B311BE176F(110581804),Status="Rolled" reason="weblogic.transaction.internal.AppSetRollbackOnlyException],numRepliesOwedMe="0,numRepliesOwedOthers="0,seconds" begin="0,seconds" left="60,XAServerResourceInfo[WLStore_MWALSBDomain_JDBCStore_MWALSB11]="(ServerResourceInfo[WLStore_MWALSBDomain_JDBCStore_MWALSB11]="(state="rolledback,assigned="MWALSB11),xar="WLStore_MWALSBDomain_JDBCStore_MWALSB1146900074,re-Registered" state="rolledback),OwnerTransactionManager="ServerTM[ServerCoordinatorDescriptor="(CoordinatorURL="MWALSB11+vmmiddleware11:7011+MWALSBDomain+t3+," xaresources="{WLStore_MWALSBDomain_JDBCStore_MWALSB11," nonxaresources="{})],CoordinatorURL="MWALSB11+vmmiddleware11:7011+MWALSBDomain+t3+).">
First steps are to get more informative error messages by enabling debugging for JTA
This is done by adding the following switches to weblogic on startup
-Dweblogic.debug.DebugJDBCJTA=true
-Dweblogic.log.StdoutSeverity="Debug"
This article give a list of other possible switches available on Weblogic
http://www.questtech.co.uk/index.php?option=com_content&view=article&id=163&Itemid=40
####<10-apr-2009> <info> <ejb> <vmmiddleware11> <mwalsb11> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1239355884374> <bea-010213> <message-driven xid="BEA1-23F28F44E9B311BE176F(110581804),Status="Rolled" reason="weblogic.transaction.internal.AppSetRollbackOnlyException],numRepliesOwedMe="0,numRepliesOwedOthers="0,seconds" begin="0,seconds" left="60,XAServerResourceInfo[WLStore_MWALSBDomain_JDBCStore_MWALSB11]="(ServerResourceInfo[WLStore_MWALSBDomain_JDBCStore_MWALSB11]="(state="rolledback,assigned="MWALSB11),xar="WLStore_MWALSBDomain_JDBCStore_MWALSB1146900074,re-Registered" state="rolledback),OwnerTransactionManager="ServerTM[ServerCoordinatorDescriptor="(CoordinatorURL="MWALSB11+vmmiddleware11:7011+MWALSBDomain+t3+," xaresources="{WLStore_MWALSBDomain_JDBCStore_MWALSB11," nonxaresources="{})],CoordinatorURL="MWALSB11+vmmiddleware11:7011+MWALSBDomain+t3+).">
First steps are to get more informative error messages by enabling debugging for JTA
This is done by adding the following switches to weblogic on startup
-Dweblogic.debug.DebugJDBCJTA=true
-Dweblogic.log.StdoutSeverity="Debug"
This article give a list of other possible switches available on Weblogic
http://www.questtech.co.uk/index.php?option=com_content&view=article&id=163&Itemid=40
Sunday, March 29, 2009
Google Map getting latitude and longitude
Simple.
Search for wanted address. This will centre the location in the map.
Run the following command from the address bar
javascript:void(prompt('',gApplication.getMap().getCenter()));
Magic
Search for wanted address. This will centre the location in the map.
Run the following command from the address bar
javascript:void(prompt('',gApplication.getMap().getCenter()));
Magic
Thursday, January 08, 2009
ssh tunnels that stay alive
Don't have time for an explanation but heres a command to setup a ssh tunnel. (linux)
This will keep the tunnel alive after you logout, and also send keepAlive pings in order to stop any other proceses from deciding that its a dead link and shutting it down.
ssh -2 -x -L <localport>:<remotehost>:<remoteport> <remotelogin>@<remotehost> -N -n –f
This will keep the tunnel alive after you logout, and also send keepAlive pings in order to stop any other proceses from deciding that its a dead link and shutting it down.
ssh -2 -x -L <localport>:<remotehost>:<remoteport> <remotelogin>@<remotehost> -N -n –f
Tuesday, December 23, 2008
Eclipse and Maven
This one is really stupid, but it had me scratching my head for a long time, so ... in it goes.
I develop mainly on a powerful desktop machine in work. Recently however I was transferring some work to my laptop, so I could potentially work on some problems from home.
When I imported the project I was working on onto the same version of eclipse on my laptop it was producing errors.
We use mvn for our builds, so I did the usual thing, of running
mvn eclipse:clean eclipse:eclipse
Still no luck.
After much head scratching te problem was that I had never initialized my M2_REPO variable within my laptops version of eclipse. Therefore all the M2_REPO based libs that mvn eclipse:eclipse generates, were not pointing to anything.
Very annoying.
I develop mainly on a powerful desktop machine in work. Recently however I was transferring some work to my laptop, so I could potentially work on some problems from home.
When I imported the project I was working on onto the same version of eclipse on my laptop it was producing errors.
We use mvn for our builds, so I did the usual thing, of running
mvn eclipse:clean eclipse:eclipse
Still no luck.
After much head scratching te problem was that I had never initialized my M2_REPO variable within my laptops version of eclipse. Therefore all the M2_REPO based libs that mvn eclipse:eclipse generates, were not pointing to anything.
Very annoying.
Sunday, December 14, 2008
Tuesday, December 09, 2008
Weblogic states
WE had a question on our weblogic status recently. SOme libraries were listed as been in the "Installed" state, as opposed to the usual "Active" state.
Heres a breakdown on the various states in Bea Weblogic:
1. There is no valid deployment state as "Installed".
2.. The deployment state is stored in "weblogic.management.runtime.AppRuntimeStateRuntimeMBean". As per the documentation these are the states:
STATE_ACTIVE, STATE_ADMIN, STATE_FAILED, STATE_NEW, STATE_PREPARED, STATE_RETIRED, STATE_UPDATE_PENDING
This is the link to documentation: http://e-docs.bea.com/wls/docs90/javadocs_mhome/weblogic/management/runtime/AppRuntimeStateRuntimeMBean.html
3. You can also check this runtime MBean on the MBean Reference: http://e-docs.bea.com/wls/docs92/wlsmbeanref/core/index.html
4. I got some known issues where it is stated that "Installed" is a console text string that indicates the LibraryMBean is present in the configuration.The Installed state can be changed by rebooting the domain. The problem can happen unexpectedly. Also the library works fine with Installed state as well.
5. It may be possible that the console is picking up a wrong state for the deployment.
6. We can verify this by using WLST to reach the AppRuntimeStateRuntimeMBean and then get the status.
i) First access the DomainRuntimeMBean using the following link: http://e-docs.bea.com/wls/docs92/config_scripting/nav_edit.html#wp1001225
ii) The DomainRuntimeMBean has the handle to AppRuntimeStateRuntimeMBean. Please check the API docs for the method getAppRuntimeStateRuntime(): http://e-docs.bea.com/wls/docs92/javadocs_mhome/weblogic/management/runtime/DomainRuntimeMBean.html
iii) Then get the module IDs and then access the status using AppRuntimeStateRuntimeMBean.getCurrentState(..).
Please let me know what are the results of this test.
Moreover this seems to be a non-reproduceable issue as we can see this occurs only in Production but not in Test.
Please let me know whether the provided information is sufficient. Also let me know if you face any problems in testing the deployment status using WLST.
Heres a breakdown on the various states in Bea Weblogic:
1. There is no valid deployment state as "Installed".
2.. The deployment state is stored in "weblogic.management.runtime.AppRuntimeStateRuntimeMBean". As per the documentation these are the states:
STATE_ACTIVE, STATE_ADMIN, STATE_FAILED, STATE_NEW, STATE_PREPARED, STATE_RETIRED, STATE_UPDATE_PENDING
This is the link to documentation: http://e-docs.bea.com/wls/docs90/javadocs_mhome/weblogic/management/runtime/AppRuntimeStateRuntimeMBean.html
3. You can also check this runtime MBean on the MBean Reference: http://e-docs.bea.com/wls/docs92/wlsmbeanref/core/index.html
4. I got some known issues where it is stated that "Installed" is a console text string that indicates the LibraryMBean is present in the configuration.The Installed state can be changed by rebooting the domain. The problem can happen unexpectedly. Also the library works fine with Installed state as well.
5. It may be possible that the console is picking up a wrong state for the deployment.
6. We can verify this by using WLST to reach the AppRuntimeStateRuntimeMBean and then get the status.
i) First access the DomainRuntimeMBean using the following link: http://e-docs.bea.com/wls/docs92/config_scripting/nav_edit.html#wp1001225
ii) The DomainRuntimeMBean has the handle to AppRuntimeStateRuntimeMBean. Please check the API docs for the method getAppRuntimeStateRuntime(): http://e-docs.bea.com/wls/docs92/javadocs_mhome/weblogic/management/runtime/DomainRuntimeMBean.html
iii) Then get the module IDs and then access the status using AppRuntimeStateRuntimeMBean.getCurrentState(..).
Please let me know what are the results of this test.
Moreover this seems to be a non-reproduceable issue as we can see this occurs only in Production but not in Test.
Please let me know whether the provided information is sufficient. Also let me know if you face any problems in testing the deployment status using WLST.
Monday, December 01, 2008
svn externals
It often useful to link to an external resource within a svn project.
for instance you may store Wsdl and Xsd files in one location, but your implementation code may need to access it. You don't want to copy and paste it since you will end up with 2 copies to maintain.
for these cases you can use svn externals to link to an external svn directory (note only directories can be linked to, not individual files)
e.g. (I set svn:externals via eclipse)
Use Team> Set Property > [select svn:externals]
Enter the name of the directory link you want, (a revision number if required, e.g. -r123), followed by the remote directory to link to.
xsd [-r rev] http://svnHost/repos/trunk/MyProject/myDir1/xsd
SVN Ignore
Svn can be instructed to ignore certain files etc.
For example when working with eclipse projects you will want to specify that .classpath, and .project files will not be included in svn, checkin's or diff's.
Ignores can be setup globally or per directory.
Global
This can be done via eclipse (in the windows/ preferences/ Team control),
or find your subversion config file. e.g. ~/.subversion/config then edit the following line, e.g.
global-ignores = .project .claspath *.o *.lo *.la #*# .*.rej *.tmproj
Local
cd to project directory,
svn propset svn:ignore "target/*
This should ignore the target directory (e.g. for maven builds)
for instance you may store Wsdl and Xsd files in one location, but your implementation code may need to access it. You don't want to copy and paste it since you will end up with 2 copies to maintain.
for these cases you can use svn externals to link to an external svn directory (note only directories can be linked to, not individual files)
e.g. (I set svn:externals via eclipse)
Use Team> Set Property > [select svn:externals]
Enter the name of the directory link you want, (a revision number if required, e.g. -r123), followed by the remote directory to link to.
wsdl [-r rev] http://svnHost/repos/trunk/MyProject/myDir1/wsdl
xsd [-r rev] http://svnHost/repos/trunk/MyProject/myDir1/xsd
SVN Ignore
Svn can be instructed to ignore certain files etc.
For example when working with eclipse projects you will want to specify that .classpath, and .project files will not be included in svn, checkin's or diff's.
Ignores can be setup globally or per directory.
Global
This can be done via eclipse (in the windows/ preferences/ Team control),
or find your subversion config file. e.g. ~/.subversion/config then edit the following line, e.g.
global-ignores = .project .claspath *.o *.lo *.la #*# .*.rej *.tmproj
Local
cd to project directory,
svn propset svn:ignore "target/*
This should ignore the target directory (e.g. for maven builds)
Wednesday, November 19, 2008
ALSB install problems
On of our servers was throwing up an exception, while trying to start the Adminserver
####<19-Nov-2008 16:17:22 o'clock GMT> <Critical> <WebLogicServer> <vmmiddleware06> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1227111442502> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
The solution appears to be
"This usually happens if your machine is running low on space and WebLogic Server corrupted a file in the embedded LDAP.
To fix this problem you can delete the file /servers//data/ldap/config/replicas.prop or add 'replica.num=0' to replicas.prop file. "
Thanks to the following link
http://satya-ghattu.blogspot.com/2008/10/number-format-exception-while-starting.html
####<19-Nov-2008 16:17:22 o'clock GMT> <Critical> <WebLogicServer> <vmmiddleware06> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1227111442502> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
The solution appears to be
"This usually happens if your machine is running low on space and WebLogic Server corrupted a file in the embedded LDAP.
To fix this problem you can delete the file /servers//data/ldap/config/replicas.prop or add 'replica.num=0' to replicas.prop file. "
Thanks to the following link
http://satya-ghattu.blogspot.com/2008/10/number-format-exception-while-starting.html
Thursday, September 25, 2008
Search jar files for class
Heres a handy little command for searching classes withen jar files (for example when searching all the jars in a war file)
find <dirs> -name '*.jar' -exec jar tvf {} \; > outputfile
THis will produce a list of all files in the jar files outputted to outputfile.
This script below will print out the filename of each jar, and each associated file within.
find <dirs> -name '*.jar' -exec jar tvf {} \; > outputfile
THis will produce a list of all files in the jar files outputted to outputfile.
This script below will print out the filename of each jar, and each associated file within.
list=$(find /apps/bea -print | grep .jar)
for el in $list; do
printf "Searching in %s\n" "$el";
case $el in
jar -tf $el | grep com.bea.console.utils.ConsoleRequestListener
;;
esac
done
Thursday, August 07, 2008
Jaxb Multiple namespace definitions
I was mildly concerned about the number of namespace definitions that Jaxb was printing every time it marshaleld an Xml document.
I'm using Spring-ws with jaxb bindings. In my definition of the Spring Marshaller I declare the jaxb packages which this marshaller will marshall. Each of these is turned into a namespace definiton on the resulting xml doc.
Results in
This was mildly irritating.
After a bit of searching I find its a 'performance feature' in Jaxb2
https://jaxb.dev.java.net/issues/show_bug.cgi?id=103
So they won't be fixing it.
The alternative from my point of view is to declare multiple marshallers, and use them where appropriate.
I'm using Spring-ws with jaxb bindings. In my definition of the Spring Marshaller I declare the jaxb packages which this marshaller will marshall. Each of these is turned into a namespace definiton on the resulting xml doc.
<bean id="jaxb2Marshaller" class="org.springframework.oxm.jaxb.Jaxb2Marshaller">
<property name="contextPath" value="com.company.package1:com.company.package2:com.company.package3:com.company.package4">
</property>
</bean>
Results in
<ns1:request ns1="http://www.company.com/Package1" ns2="http://www.company.com/Package2" ns3="http://www.company.com/Package3" ns4="http://www.company.com/Package4">
<ns1:data>text
</ns1:data>
</request>
This was mildly irritating.
After a bit of searching I find its a 'performance feature' in Jaxb2
https://jaxb.dev.java.net/issues/show_bug.cgi?id=103
So they won't be fixing it.
The alternative from my point of view is to declare multiple marshallers, and use them where appropriate.
<bean id="jaxb2Marshaller1" class="org.springframework.oxm.jaxb.Jaxb2Marshaller">
<property name="contextPath" value="com.company.package1">
</property>
</bean>
<bean id="jaxb2Marshaller2" class="org.springframework.oxm.jaxb.Jaxb2Marshaller">
<property name="contextPath" value="com.company.package2">
</property>
</bean>
..etc..
Tuesday, August 05, 2008
Python gotcha
This Seemingly innocuous indentation error in python was annoying me.
Problem invoking WLST - Traceback (innermost last):
(no code object) at line 0
File "C:\apps\installWls.py", line 249
toDeploy = sys.argv[3]
^
SyntaxError: inconsistent dedent
Looking at my code (wlst code to auto deploy application into weblogic server), it was all indented correctly.
Well of course the computer was right. It wasn't indented correctly, but it was no obvious.
The issue was some copy and paste code I took from the internet.
It was indented using spaces, whereas I was using tabs.
Replacing the space indentation with tabs fixed the issue (but its not obvious uinless you set your editor to display non visible characters.
Problem invoking WLST - Traceback (innermost last):
(no code object) at line 0
File "C:\apps\installWls.py", line 249
toDeploy = sys.argv[3]
^
SyntaxError: inconsistent dedent
Looking at my code (wlst code to auto deploy application into weblogic server), it was all indented correctly.
Well of course the computer was right. It wasn't indented correctly, but it was no obvious.
The issue was some copy and paste code I took from the internet.
It was indented using spaces, whereas I was using tabs.
Replacing the space indentation with tabs fixed the issue (but its not obvious uinless you set your editor to display non visible characters.
Tuesday, July 29, 2008
StackoverFlow using spring-ws on weblogic 9.2
We finally got our spring-ws application deployed.
Or so we thought. The next day when we arrived int he code was crashing, and the JMS queue was not been read....
The img to the right shows the non-heap memory growth. Something is not clearing.
Below is the stack trace we get
Edit
Two things to check that might help: (I have not been able to test this now, as I no longer work on this project or for this client.)
* Make sure that you haven't somehow configured a foreign JNDI or foreign JMS server that is self referencing.
* Make sure that you haven't specified a URL when there's no need to specify a URL. (Server side applications and configuration should never specify a URL for a resource unless the resource is in a different cluster. When a resource is located in the same cluster, JNDI lookups should simply be made directly in the cluster's JNDI name-space. The way to ensure that the lookup is direct is simply to use initial contexts that were created without an URL.)
http://forums.oracle.com/forums/message.jspa?messageID=2675334#2675334
10:12:31 INFO [org.springframework.jms.listener.DefaultMessageListenerContainer
] - Successfully refreshed JMS Connection
10:12:31 DEBUG [org.springframework.jndi.JndiTemplate] - Looking up JNDI object
with name [java:comp/env/jms.queue.provisioning.request]
10:12:36 INFO [org.springframework.jms.listener.DefaultMessageListenerContainer
] - Setup of JMS message listener invoker failed - trying to recover
java.lang.StackOverflowError
at java.lang.String.indexOf(String.java:1564)
at java.lang.String.indexOf(String.java:1546)
at weblogic.jndi.internal.AbstractURLContext.removeURL(AbstractURLContext.java:24)
at weblogic.jndi.factories.java.javaURLContextFactory$JavaURLContext.rem
oveURL(javaURLContextFactory.java:130)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.j
ava:130)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyCo
ntextWrapper.java:45)
....
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.j
ava:130)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyCo
ntextWrapper.java:45)
It appears that the first exception thrown is
2008-07-26 00:14:08,679 DEBUG org.springframework.jms.listener.DefaultMessageListenerContainer - Consumer [weblogic.jms.client.WLConsumerImpl@14f7bad] of session [weblogic.jms.client.WLSessionImpl@15015db] did not receive a message
2008-07-26 00:14:08,696 INFO org.springframework.jms.listener.DefaultMessageListenerContainer - Setup of JMS message listener invoker failed - trying to recover
weblogic.jms.common.TransactionRolledBackException: Attempt to resume an inactive transaction: BEA1-11D22EBAEF18F82704CC:error resuming transacted session's internal transaction
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.receiveMessage(JMSSession.java:797)
at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:579)
at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:167)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:404)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:285)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:260)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:944)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:874)
at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:259)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.jms.common.TransactionRolledBackException: Attempt to resume an inactive transaction: BEA1-11D22EBAEF18F82704CC:error resuming transacted session's internal transaction
at weblogic.jms.frontend.FESession.transactedException(FESession.java:2024)
at weblogic.jms.frontend.FESession.throwTransactedException(FESession.java:2039)
at weblogic.jms.frontend.FESession.transactedInfect(FESession.java:2140)
at weblogic.jms.frontend.FEConsumer.receive(FEConsumer.java:527)
at weblogic.jms.frontend.FEConsumer.invoke(FEConsumer.java:780)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:36)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:113)
... 2 more
Caused by: javax.transaction.InvalidTransactionException: Attempt to resume an inactive transaction: BEA1-11D22EBAEF18F82704CC
at weblogic.transaction.internal.TransactionManagerImpl.resume(TransactionManagerImpl.java:360)
at weblogic.transaction.internal.ServerTransactionManagerImpl.resume(ServerTransactionManagerImpl.java:356)
at weblogic.jms.frontend.FESession.transactedInfect(FESession.java:2085)
... 9 more
2008-07-26 00:14:08,709 INFO org.springframework.jms.listener.DefaultMessageListenerContainer - Successfully refreshed JMS Connection
2008-07-26 00:14:08,713 DEBUG org.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/meteor.jms.queue.provisioning.request]
2008-07-26 00:14:13,758 INFO org.springframework.jms.listener.DefaultMessageListenerContainer - Setup of JMS message listener invoker failed - trying to recover
java.lang.StackOverflowError
at java.lang.String.indexOf(Ljava.lang.String;I)I(Unknown Source)
at java.lang.String.indexOf(Ljava.lang.String;)I(Unknown Source)
at weblogic.jndi.internal.AbstractURLContext.removeURL(AbstractURLContext.java:24)
Wednesday, June 18, 2008
Spring-ws and weblogic incompatibilities
I wrote about incompatible versions of spring before resulting in cryptic error messages.
Well my solution there wasn't the full picture, if you are running xml /web servicse on weblogic. (Though at least this time I recognised the error as incompatible jars)
I was getting various different non-intuitive errors when trying to run a spring-ws application on weblogic 9.2.1.
e.g.
<User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webServiceTemplateProxy' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'webServiceTemplate' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean withname 'webServiceTemplate' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'messageFactory' while setting bean property 'messageFactory'; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'messageFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception is java.lang.NoSuchMethodError: org.springframework.aop.support.AopUtils.getTargetClass(Ljava/lang/Object;)Ljava/lang/Class;.org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webServiceTemplateProxy' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'webServiceTemplate' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creatingbean with name 'webServiceTemplate' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'messageFactory' while setting bean property 'messageFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception isjava.lang.NoSuchMethodError: org.springframework.aop.support.AopUtils.getTargetClass(Ljava/lang/Object;)Ljava/lang/Class;
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1244)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1008)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:470)
Truncated. see log file for complete stacktrace
or
java.lang.NoClassDefFoundError: org/apache/axiom/soap/SOAPFactory
After a lot of effort and with help from various postings (namely here, and here ), I managed to track down the various xml jars I needed to override weblogics internal jars.
These include the following taken from my maven pom.xml file. (Note I can't guarantee that this is the full list, or that this list does not contain jars that are in fact not needed. All I can say is that this list worked for me). BTW some of these I had to manually install in my maven repository myself, as I couldn't find them on remote repositories.
<dependency>
<groupId>org.springframework.ws</groupId>
<artifactId>spring-ws</artifactId>
<version>1.5.2</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-api</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-dom</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-impl</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-impl</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>stax</groupId>
<artifactId>stax-api</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>apache-xerces</groupId>
<artifactId>xercesImpl</artifactId>
<version>2.9.1</version>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.3.03</version>
</dependency>
<dependency>
<groupId>org.codehaus.woodstox</groupId>
<artifactId>wstx-asl</artifactId>
<version>3.2.6</version>
</dependency>
The problem is with weblogic (various versions, 9.2, 9.2.1, 8.1, and I believe 10) and spring-ws. Weblogic comes with various xml libraries, most of which have been superseded by newer versions. Spring-ws requires some of these newer jars (e.g. saaj, and axiom), which in turn refer to newer versions of base xml libraries. Thus you have an incompatibility.
Also from Arjens post you need to update your weblogic.xml file, adding the following, to instruct weblogic to take the supplied files before already installed files int he weblogic system
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
BTW I was only able to finally fix the problem by firstly deploying it on Tomcat.
The above example works much easier in Tomcat, since it doesn't have any conflicting xml libraries causing grief. By actually getting the application running in tomcat, I was able to (relatively) quickly find out which jars I needed.
Tomcat would throw a NoClassDefFound exception when it came across a jar it didn't have. This doesn't happen in weblogic since it has xml jars, just the wrong versions. Once I had the application running in tomcat, I knew I had found all the required jars. When I moved it back to weblgoic the problem was solved.
Note: unlike Ajens post, I required saaj1.3 in my WEB-INF/lib folder
Actually I wasn't quite there yet, (see next post), but I this had finally sorted out this problem
Well my solution there wasn't the full picture, if you are running xml /web servicse on weblogic. (Though at least this time I recognised the error as incompatible jars)
I was getting various different non-intuitive errors when trying to run a spring-ws application on weblogic 9.2.1.
e.g.
<User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webServiceTemplateProxy' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'webServiceTemplate' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean withname 'webServiceTemplate' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'messageFactory' while setting bean property 'messageFactory'; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'messageFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception is java.lang.NoSuchMethodError: org.springframework.aop.support.AopUtils.getTargetClass(Ljava/lang/Object;)Ljava/lang/Class;.org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webServiceTemplateProxy' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'webServiceTemplate' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creatingbean with name 'webServiceTemplate' defined in class path resource [com/meteor/provisioning/servicecategory/serviceBeansSpringConfig.xml]: Cannot resolve reference to bean 'messageFactory' while setting bean property 'messageFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception isjava.lang.NoSuchMethodError: org.springframework.aop.support.AopUtils.getTargetClass(Ljava/lang/Object;)Ljava/lang/Class;
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1244)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1008)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:470)
Truncated. see log file for complete stacktrace
or
java.lang.NoClassDefFoundError: org/apache/axiom/soap/SOAPFactory
After a lot of effort and with help from various postings (namely here, and here ), I managed to track down the various xml jars I needed to override weblogics internal jars.
These include the following taken from my maven pom.xml file. (Note I can't guarantee that this is the full list, or that this list does not contain jars that are in fact not needed. All I can say is that this list worked for me). BTW some of these I had to manually install in my maven repository myself, as I couldn't find them on remote repositories.
<dependency>
<groupId>org.springframework.ws</groupId>
<artifactId>spring-ws</artifactId>
<version>1.5.2</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-api</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-dom</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-impl</artifactId>
<version>1.2.6</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-impl</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>stax</groupId>
<artifactId>stax-api</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>apache-xerces</groupId>
<artifactId>xercesImpl</artifactId>
<version>2.9.1</version>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.3.03</version>
</dependency>
<dependency>
<groupId>org.codehaus.woodstox</groupId>
<artifactId>wstx-asl</artifactId>
<version>3.2.6</version>
</dependency>
The problem is with weblogic (various versions, 9.2, 9.2.1, 8.1, and I believe 10) and spring-ws. Weblogic comes with various xml libraries, most of which have been superseded by newer versions. Spring-ws requires some of these newer jars (e.g. saaj, and axiom), which in turn refer to newer versions of base xml libraries. Thus you have an incompatibility.
Also from Arjens post you need to update your weblogic.xml file, adding the following, to instruct weblogic to take the supplied files before already installed files int he weblogic system
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
BTW I was only able to finally fix the problem by firstly deploying it on Tomcat.
The above example works much easier in Tomcat, since it doesn't have any conflicting xml libraries causing grief. By actually getting the application running in tomcat, I was able to (relatively) quickly find out which jars I needed.
Tomcat would throw a NoClassDefFound exception when it came across a jar it didn't have. This doesn't happen in weblogic since it has xml jars, just the wrong versions. Once I had the application running in tomcat, I knew I had found all the required jars. When I moved it back to weblgoic the problem was solved.
Note: unlike Ajens post, I required saaj1.3 in my WEB-INF/lib folder
Actually I wasn't quite there yet, (see next post), but I this had finally sorted out this problem
Failure executing javac
There's nothing quite so deflating as seeing a message like the following
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.5.0_06). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
com.sun.tools.javac.code.Symbol$CompletionFailure: file javax\xml\ws\WebServiceClient.class not found
You really begin to wonder if you're doing something very wrong.
Fortunately you're not, and there is a quick and easy workaround.
This it turns out is a bug with javac on windows
My quick solution. Compile using cygwin. (If you haven't got cygwin, simply download setup.exe, and install)
This worked fine. My details was using jdk 1.5.0_06 (the bug has been reported on 1.5.0_04, and seen on 1.6 as well), on windows xp building using maven 2.0.8. Running my maven script in a cygwin bash window worked fine.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.5.0_06). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
com.sun.tools.javac.code.Symbol$CompletionFailure: file javax\xml\ws\WebServiceClient.class not found
You really begin to wonder if you're doing something very wrong.
Fortunately you're not, and there is a quick and easy workaround.
This it turns out is a bug with javac on windows
My quick solution. Compile using cygwin. (If you haven't got cygwin, simply download setup.exe, and install)
This worked fine. My details was using jdk 1.5.0_06 (the bug has been reported on 1.5.0_04, and seen on 1.6 as well), on windows xp building using maven 2.0.8. Running my maven script in a cygwin bash window worked fine.
Tuesday, June 10, 2008
spring versions
Beware of mixing tools with different Spring versions.
I was using spring ws 1.5.3, and getting the following error
java.lang.NoSuchMethodError: org.springframework.util.ResourceUtils.toURI(Ljava/net/URL;)Ljava/net/URI;
....
Problem is that I had spring 2.0.x on my path, but spring-ws requires spring 2.5.x
Once I updated to using spring 2.5.x the problem was solved.
Could be a nasty problem, since the error message could easily lead you on a wild goose chase
I was using spring ws 1.5.3, and getting the following error
java.lang.NoSuchMethodError: org.springframework.util.ResourceUtils.toURI(Ljava/net/URL;)Ljava/net/URI;
....
Problem is that I had spring 2.0.x on my path, but spring-ws requires spring 2.5.x
Once I updated to using spring 2.5.x the problem was solved.
Could be a nasty problem, since the error message could easily lead you on a wild goose chase
Friday, June 06, 2008
GSM Codes
GSM codes.
These can be saved in you phonebook/ contacts list for fast access.Most are obviously selectable by going through your phones menu, but these are much quicker, and I can never find some of them, like call waiting and call hold
Call Divert (all call types)
All
Set: **21*destination#[SEND]
Cancel: ##21#[SEND]
Query: *#21#[SEND]
No Answer
Delay nn seconds: max 30 seconds, in 5 second increments
Set: **61*destination*nn#[SEND]
Cancel: ##61#[SEND]
Query: *#61#[SEND]
Unreachable
Set: **62*destination#[SEND]
Cancel: #62#[SEND]
Query: *#62#[SEND]
Busy
Set: **67*destination#[SEND]
Cancel: ##67#[SEND]
Query: *#67#[SEND]
Cancel All
##002#[SEND]
Divert Voice Calls
All
Set: **21*destination*11#[SEND]
Cancel: ##21*11#[SEND]
Query: *#21*11#[SEND]
No Answer
Delay nn seconds: max 30 seconds, in 5 second increments
Set: **61*destination*11*nn#[SEND]
Cancel: ##61*11#[SEND]
Query: *#61*11#[SEND]
Unreachable
Set: **62*destination*11#[SEND]
Cancel: ##62*11#[SEND]
Query: *#62*11#[SEND]
Busy
Set: **67*destination*11#[SEND]
Cancel: ##67*11#[SEND]
Query: *#67*11#[SEND]
Divert Data Calls
All
Set: **21*destination*25#[SEND]
Cancel: ##21*25 [SEND]
Query: *#21*25#[SEND]
No Answer
Delay nn seconds: max 30 seconds, in 5 second increments
Set: **61*destination*25*nn#[SEND]
Cancel: ##61*25#[SEND]
Query: *#61*25#[SEND]
Unreachable
Set: **62*destination*25#[SEND]
Cancel: ##62*25#[SEND]
Query: *#62*25#[SEND]
Busy
Set: **67*destination*25#[SEND]
Cancel: ##67*25#[SEND]
Query: *#67*25#[SEND]
Divert Fax Calls
All
Set: **21*destination*13#[SEND]
Cancel: ##21*13#[SEND]
Query: *#21*13#[SEND]
No Answer
Delay nn seconds: max 30 seconds, in 5 second increments
Set: **61*destination*13*nn#[SEND]
Cancel: #61*13#[SEND]
Query: *#61*13#[SEND]
Unreachable
Set: **62*destination*13#[SEND]
Cancel: #62*13#[SEND]
Query: *#62*13#[SEND]
Busy
Set: **67*destination*13#[SEND]
Cancel: ##67*13#[SEND]
Query: *#67*13#[SEND]
Divert Line 2 Calls
All
Set: **21*destination*89#[SEND]
Cancel: #21*89#[SEND]
Query: *#21*89#[SEND]
No Answer
Delay nn seconds: max 30 seconds, in 5 second increments
Set: **61*destination*89*nn#[SEND]
Cancel: ##61*89#[SEND]
Query: *#61*89#[SEND]
Unreachable
Set: **62*destination*89#[SEND]
Cancel: ##62*89#[SEND]
Query: *#62*89#[SEND]
Busy
Set: **67*destination*89#[SEND]
Cancel: ##67*89#[SEND]
Query: *#67*89#[SEND]
Call Barring
You use call barring to control what calls can be made or received by your account.
The barring code is specific to the network. Ask your service provider.
Note that Call Barring can't work if call diverts are active, even the autodivert set by the network.
All calls
Set: **330*barring code#[SEND]
Cancel: ##330*barring code#[SEND]
Query: *#330#[SEND]
Outgoing calls
Set: **333*barring code#[SEND]
Cancel: ##333*barring code#[SEND]
Query: *#333#[SEND]
Incoming calls
Set: **35*barring code#[SEND]
Cancel: ##35*barring code#[SEND]
Query: *#35#[SEND]
Outgoing international calls
Set: **331*barring code#[SEND]
Cancel: ##331*barring code#[SEND]
Query: *#331#[SEND]
Outgoing international calls except to home country
Set: **332*barring code#[SEND]
Cancel: ##332*barring code#[SEND]
Query: *#332#[SEND]
Incoming calls when outside home country
Set: *351*barring code#[SEND]
Cancel: #351*barring code#[SEND]
Query: *#351#[SEND]
Cancel All Call Barring
#330*barring code#[SEND]
SMS
There is no provision in the GSM specification for diverting SMS messages
Bar incoming SMS messages
Set: *35*barring code*16#[SEND]
Cancel: #35*barring code*16#[SEND]
Call waiting
Set: *43#[SEND]
Cancel: #43#[SEND]
Query: *#43#[SEND]
Incoming call waiting
Reject: 0 [SEND]
Drop current call and answer: 1 [SEND]
Hold current call and answer: 2 [SEND]
Calling line identity
Outgoing CLI Release (recipient sees your number)
Release: *31# destination [SEND]
Withhold: #31# destination [SEND]
Query default: *#31#[SEND]
Incoming CLI Presentation (you see the caller's number)
Allow: *30#[SEND]
Prevent: #30#[SEND]
Query default: *#30#[SEND]
Dial number from memory
Where nnn is the memory location number
nnn#[SEND]
Change PIN codes
Change Call Barring pin code
**03*oldpin*newpin*newpin#
Change SIM pin code
**04*oldpin*newpin*newpin#
Change SIM pin2 code
**042*oldpin*newpin*newpin#
Unblock SIM pin code
**05*PUK*newpin*newpin#
Unblock SIM pin code
**06*PUK2*newpin*newpin#
Wednesday, May 14, 2008
Maven multiple source directories
By default with maven you can only specify a single source directory. Not very flexible. The following pluggin expands this, allowing you to specify many src dirs.
Heres a sample from the pom.xml
<build>
Heres a sample from the pom.xml
<build>
<build>
<!-- Replaced with build-helper-maven-plugin below to allow for multiple source directories
<sourceDirectory>${basedir}/src/main/java</sourceDirectory>
-->
<testSourceDirectory>
${basedir}/src/test/java
</testSourceDirectory>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
<debug>false</debug>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<id>add-source</id>
<phase>generate-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>
${basedir}/src/main/java
</source>
<source>
${basedir}/src/types/java
</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Tuesday, May 06, 2008
Why spring rocks in a nuthell
http://www.jroller.com/kdonald/entry/the_essence_of_spring
Injecting enums in Spring beans
Found this while searching for how to insert enums into Spring beans from the xml config file (basically you just put the enum value directly in the xml file, http://www.jroller.com/kdonald/entry/spring_hidden_gem_support_for)
Injecting enums in Spring beans
Found this while searching for how to insert enums into Spring beans from the xml config file (basically you just put the enum value directly in the xml file, http://www.jroller.com/kdonald/entry/spring_hidden_gem_support_for)
Friday, May 02, 2008
PropertyPlaceholderConfigurer doesn't work with XmlBeanFactory
SImple gotcha.
I was using Spring and the PropertyPlaceholderConfigurer. This simply allows you to populate your spring config file with values from a properties file at runtime. For me the properties file is loaded from the classpath (using the classpath: prefix). this is then stored in a seperate config folder whihc is shared between all projects, thus allowing us to update the config file with needing to redploy the complete application again.
e.g.
I write a simple class to instantiate this from a Unit test.
It didn't work. The PropertyPlaceholderConfigurer, wasn't updating the internal spring file with values from the jms.properties. The jmsTemplate value was been returned as ${jms.receiveTimeout}
Turns out that only ApplicationContext files do the replacement. A quick update to
public static ApplicationContext getApplicationContext() {
springConfigFile = System.getProperty("SpringConfig", springConfigFile);
if (_beanFactory == null) {
_beanFactory = new ClassPathXmlApplicationContext(springConfigFile);
}
return _beanFactory;
}
fixed the problem. Thanks also to http://francisoud.blogspot.com/2007/06/spring-property-placeholder.html
I was using Spring and the PropertyPlaceholderConfigurer. This simply allows you to populate your spring config file with values from a properties file at runtime. For me the properties file is loaded from the classpath (using the classpath: prefix). this is then stored in a seperate config folder whihc is shared between all projects, thus allowing us to update the config file with needing to redploy the complete application again.
e.g.
<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<list>
<value>jms.properties</value>
<ref bean="getNetworkServicePropertyFile" />
</list>
</property>
</bean>
<bean id="test" class="com.meteor.provisioning.Test">
<property name="jmsTemplate" value="${jms.receiveTimeout}" />
</bean>
I write a simple class to instantiate this from a Unit test.
public static BeanFactory getSpringContext() {
springConfigFile = System.getProperty("SpringConfig", springConfigFile);
if (_beanFactory == null) {
Resource resource = new ClassPathResource(springConfigFile);
//_beanFactory = new XmlBeanFactory(resource);
}
return _beanFactory;
}
public static Object getBean(String bean){
return getApplicationContext().getBean(bean);
}
and finally a test case
public class Test {
private String jmsTemplate;
public void setJmsTemplate(String jmsTemplate) {
this.jmsTemplate = jmsTemplate;
System.out.println("jmsTemplate = "+jmsTemplate);
}
@org.junit.Test
public void doTest(){
Utils.getBean("test");
}
}
It didn't work. The PropertyPlaceholderConfigurer, wasn't updating the internal spring file with values from the jms.properties. The jmsTemplate value was been returned as ${jms.receiveTimeout}
Turns out that only ApplicationContext files do the replacement. A quick update to
public static ApplicationContext getApplicationContext() {
springConfigFile = System.getProperty("SpringConfig", springConfigFile);
if (_beanFactory == null) {
_beanFactory = new ClassPathXmlApplicationContext(springConfigFile);
}
return _beanFactory;
}
fixed the problem. Thanks also to http://francisoud.blogspot.com/2007/06/spring-property-placeholder.html
Subscribe to:
Posts (Atom)