I've been playing with the jHipster yeoman generator for the past week and I'm trying to get my application working with atomikos for JTA/XA transactions and I'm running into a number of problems, which is to be expected since I'm new to spring boot and a number of the other components in the jHipster stack.
I have been using the example found here as my starting point for configuring atomikos. I've implemented everything described there, replacing HikariCP entirely.
At the moment I have eliminated Metrics and liquibase from my configuration as they were giving me problems and I wanted to get the basics working and then add them back in. However, I'm now hitting a Hibernate issue.
Hibernate is complaining that second-level cache is used but hibernate.cache.region.factory_class is not given. The factory_class setting is specified in the configuration and I'm not able to figure out what I'm missing.
Has anyone managed to get atomikos (or maybe bitronix) working with this stack?
I've managed to get this working. For some reason I had to explicitly set hibernate.cache.use_second_level_cache to false. Not sure why it would require this given that I am not setting any second level cache flags anywhere that I can see.
Never the less. It's working now.
Related
We have to migrate several node.js applications from Loopback3 to Loopback4.
So the first step we want to do is a basic migration following guidelines (1 and 2), and then complete it by manually upgrade methods and logic, and completely remove lb3 application.
Unfortunately, at the end of the migration steps in the guide, when trying to start the app (node -r source-map-support/register .), we receive the following error:
...
Swagger: skipping unknown type "Document".
Cannot start the application. { S2OError: Could not resolve reference #/definitions/Document
...
Any help would be appreciated.
OK,
I had also opened an issue on loopback-next repo on github, at the same time of this question.
So this problem has been solved on that thread.
Here the solution:
I've temporarily changed this return type to Object, and it runs successfully and migration goes fine. So I've solved in this way as my scope is to rewrite this specific method.
Anyway I have to say the lb3 application runs fine, even though this type is not defined in it.
I hope this may help someone.
I updated my open source forum app to ASP.NET Core 1.1, and after battling deployment weirdness (it broke for reasons I don't totally understand, but believe it has something to do with the changing tooling), now I find that routing is broken. When I say it's broken, I mean it continues display links with tag and HtmlHelpers, but they don't match the "clean" routing that they used to. They work correctly locally, but not in an Azure app service.
For example, the correct URL should be:
https://popforumsdev.azurewebsites.net/Forums/first-test-forum
But it's resolving as:
https://popforumsdev.azurewebsites.net/Forums/Forum?urlName=first-test-forum
I get the tooling changing, but this has me totally stumped. Same code, working differently locally and in Azure, and it didn't break until I updated to v1.1. (It doesn't instill a lot of confidence for what I assume will be relatively frequent framework updates, either.)
I don't imagine this has anything to do with it, because it works as expected locally, and it didn't change for v1.1, but here's the routing code:
https://github.com/POPWorldMedia/POPForums/blob/master/src/PopForums.Web/Areas/Forums/Extensions/RouteBuilders.cs
Well, after redeploying twice, this resolved itself. That's even more concerning, that routing would break like that, and that it didn't.
I'm using solr 5.2.1 with jetty.In my logs(solr.log) there's an error with
"org.apache.solr.core.CoreContainer; Error creating core [dosweb]: Could not load conf for core project : Error loading solr config from solrconfig.xml" title
,and I understand it's because of misconfigured in solr version,and it is showing me this exception:Caused by: java.lang.IllegalArgumentException: Illegal parameter 'termIndexInterval'
,what I should do to fix it.
thanks alot.
Not enough data.
It seems like your core is misconfigured for 5.2.1
I'd suggest that you try first with a reference configuration core, or a reference empty core, make sure that works, and then merge the config from the dosWeb core to the newly created core in steps.
This way you will find the part of the configuration that causes the issue.
EDIT -
After you added information (still not enough - a snippet of the offending configuration would have been good) I've been able to track down the bug that refers to the issue you get.
https://issues.apache.org/jira/browse/SOLR-6560
Essentially - the configuration for termIndexInterval is now not only deprecated, but can't be done in a standard way at all. From what I understand from the bug, It's also not needed anymore.
I have an XPages application that has been running quite happily for the last couple of years.
The application uses some Java classes as converters that are used to convert data entry on certain fields to upper case, proper case, etc. This functionality has been present and working since the app was first deployed.
Today I was asked to make a change to one of the pages, adding a new field. The change was made in a test copy of the database, the app rebuilt and tested and all was fine.
The same change was then promoted into the live database, but after being rebuilt the error
Can't instantiate class: 'Cannot find class uk.co.xxx.beans.UpperCase in NSF'.
is being returned.
I have tried rebuilding the app and cleaning the project numerous times without success. I have also tried amending the code in the Java class and rebuilding.
If I remove all references to the UpperCase class it then complains about the ProperCase class. It appears as if the app has lost its reference to the Java classes and rebuilding isn't fixing the problem.
As an interim solution I have removed all uses of these classes so that users can at least display the page - but this is obviously not a long term solution. As soon as I reinstate one instance and rebuild, the error returns.
The only change in the app has been the addition of the new field. Removing it makes no difference.
Can you suggest anything else I can try and what may be causing the problem?
Open production db in designer and using Navigator view open WebContent/WEB-INF and delete classes folder. Then rebuild the app or refresh it from template again.
Sometimes classes are not updated correctly. I've seen it few times.
I have seen this too (domino 8.5.3). I recompile until it eventually works. With a restart of the http task thrown in for good measure. How are you deploying the classes within the db or as jar files in lib/ext?
I ran into similar issues with 8.53 FP2 with the same "can't instantiate errors" if accessed by a designer client. I even put a PRD in at IBM for it.
In order to fix this problem we had to update to the server and clients to FP5. We had a work around before we could update the FP5. We had to modify how the application was rolled out. Once the database was updated from a template we had to do a clean then a build while use our Application ID used for signing applications.
http://www-01.ibm.com/support/docview.wss?uid=swg21639571
JDAE8ZV2CX
XPage With Java Design Element Breaks When Domino Designer opens after applying 8.5.3 Fix Pack 2 interim fix of any 853 Fix Pack 2/Fix Pack 3 hotfix
I'm building an application with (smart)gwt, hibernate (actually gilead, or hibernate4gwt) and Spring Security.
I'm pretty new to all of these, by the way.
Everything worked fine until now, but I've recently added Spring security functionality, in order to implement an authentication system. Seems there are multiple ways of making this work, I looked at a few tutorials.
I liked this simple idea here: http://blog.maxmatveev.com/2011/06/gwt-and-spring-security-integration-as.html?showComment=1328698687249#c4823182825437196300
I also tried this one (a lot of dummy classes and such, but oh well): http://seewah.blogspot.com/2009/02/gwt-and-spring-security.html
In both cases I have the same problem, I get this error in the applicationContext.xml:
Error occured processing XML 'org/springframework/security/access/intercept/aopalliance/MethodSecurityInterceptor'
In the first link it occurs at line:
<security:global-method-security secured-annotations="enabled" mode="aspectj"/>
In the second link it occurs at line:
<security:global-method-security secured-annotations="enabled" jsr250-annotations="disabled" />
I googled the problem, but I didn't find an answer..
PS1: using Eclipse 3.6, and I have installed plugins for Spring framework and aspectJ.
PS2: I didn't write all the code here, instead I liked to the tutorials i used (would have been too much code).
Maybe someone can help me out.
Thank you in advance.
It may be a problem with version of Spring/Spring Security.
Make sure you are updated to recent version (to handle attribute mode="aspectj" of element security:global-method-security) e.g. Spring-Security 3.1.