I am trying to get the Pulse data browser set up within our project, but having no luck. I have seen this post where John lays out pretty clear and concise instructions (from what I can tell it's still relevant) but I'm having issues troubleshooting. The version we are using is 1.7.6. Anyone have any suggestions as to what I can check out?
Below is the properties before I took a look at the repo. I saw in recent documentation that "jmx-manager-http-port" is deprecated but I'm unsure if that's the case with 1.7.6.RELEASE
<util:properties id="gemfire-props">
<prop key="log-level">warning</prop>
<prop key="mcast-port">0</prop>
<prop key="jmx-manager-start">true</prop>
<prop key="jmx-manager">true</prop>
<prop key="jmx-manager-http-port">8070</prop>
</util:properties>
Changed to this. I am able to connect to the locators and managers through GFSH no problem, have tried a couple of different ports and still able to connect to the new ones. I am never able to access localhost:[PORT]/pulse however.
<util:properties id="gemfire-props">
<prop key="mcast-port">0</prop>
<prop key="locators">localhost[11235]</prop>
<prop key="log-level">warning</prop>
<prop key="http-service-port">7070</prop>
<prop key="jmx-manager">true</prop>
<prop key="jmx-manager-port">1099</prop>
<prop key="jmx-manager-start">true</prop>
<prop key="start-locator">localhost[11235]</prop>
</util:properties>
Can post more config/information as needed.
See the instructions in the Spring Boot for Apache Geode (and VMware Tanzu GemFire), SBDG, reference documentation:
https://docs.spring.io/spring-boot-data-geode-build/current/reference/html5/index.html#geode-manager-applications
Scroll down to the section, "Additional, optional Manager depdendencies expressed in Gradle".
The Apache Geode (VMware Tanzu GemFire, formerly Pivotal GemFire) Pulse application is a Web application that can either be bootstrapped in a standalone Servlet container such as Tomcat, or bootstrapped as part of the Geode/GemFire server JVM process, which configures and bootstraps an embedded Servlet container (currently, Eclipse Jetty).
When the org.apache.geode:geode-pulse dependency is on your Spring configured/bootstrapped Geode/GemFire server JVM process, and the Manager is enabled, it will locate the Pulse application classes and bootstrap Pulse inside the embedded Geode/GemFire Jetty Servlet container.
You can see more information in the Spring Data for Apache Geode (GemFire), SDG, reference documentation as well:
https://docs.spring.io/spring-data/geode/docs/current/reference/html/#bootstrap-annotation-config-embedded-services
A few housekeeping items:
SDG 1.x has been EOL for sometime. In fact SDG, 2.2.x and older is EOL already. SDG 2.5.4 is the latest version, based on Apache Geode 1.13.x. SDG 2.6 is already in development. SDG 3.0 will be coming next year (2022) when Spring Framework 6 is available. The baseline of SD[G] will be Spring Framework 6 and most likely Java 11, maybe even Java 17. Currently, SDG is based on Spring Framework 5 and Java 8, FYI.
SDG 2.3.x is the last official version with VMware Tanzu GemFire dependencies/support (spring-data-gemfire module (see here) in the spring-data-geode GitHub repository).
This generally should not be a problem since VMware Tanzu GemFire is based on, and effectively is, the commercial version of Apache Geode.
However, GemFire 9.10.9 is the latest release (see here) and is based on Apache Geode 1.12.4. As of SDG 2.4, SDG is based on Apache Geode 1.13.x, which means GemFire is no longer officially compatible at that version and therefore, cannot be included with SDG until a version of GemFire is based on Apache Geode 1.13. I have no idea whether this will ever happen.
Finally, Spring for Geode/GemFire has grown significantly since the SDG 1.x days. Since then, I have created the Spring Session for Apache Geode (SSDG) project, Spring Test for Apache Geode (STDG) project, and Spring Boot for Apache Geode (SBDG) project. In all of Spring, we encourage users to start with Spring Boot first, and that is no different for Apache Geode and VMware Tanzu GemFire. In fact, you can even start projects using Apache Geode on start.spring.io. SBDG really is the best way to get started with Apache Geode or GemFire. See the guided tour for more details.
Please post in the comments if you have more questions.
Related
Looking for help for some solutions on switching out the default data provider for the project from MS SQL to mySQL. Eventually with the intent of deploying the solution to Auruora on AWS.
After installing the nuget package I get something along the lines of :
System.TypeLoadException: Method 'Clone' in type 'MySql.Data.EntityFrameworkCore.Infraestructure.MySQLOptionsExtension' from assembly 'MySql.Data.EntityFrameworkCore, Version=6.10.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' does not have an implementation.
This lead me to believe that there is no .NET 2.0 Entity Framework Core extention that runs for MySQL. Do I have to rollback to a different version?
For EntityFrameworkCore, it's suggested to use Pomelo.EntityFrameworkCore.MySql.
You may refer to their Getting Started documentation.
A fellow member of the community has kindly summarised the essential steps here:
Put Pomelo.EntityFrameworkCore.MySql into the xxx.EntityFrameworkCore project's .csproj file (see step 2 in the Pomelo getting started guide)
In your xxxDbContextConfigurer class put builder.UseMySql(...) rather than builder.UseSqlServer(...)
Change the connection string found in the appsettings.json file in the xxx.Web.Host project
We have an javaee application already running on Wildfly 8.1 and we want to migrate it on JBoss EAP 6 because our customer needs a commercial license.
On Wildfly we have the following configuration
<subsystem xmlns="urn:jboss:domain:ee:1.2">
...
<concurrent>
<context-services>
<context-service name="default" jndi-name="java:jboss/ee/concurrency/context/default" use-transaction-setup-provider="true"/>
</context-services>
<managed-thread-factories>
<managed-thread-factory name="default" jndi-name="java:jboss/ee/concurrency/factory/default" context-service="default"/>
</managed-thread-factories>
<managed-executor-services>
<managed-executor-service name="default" jndi-name="java:jboss/ee/concurrency/executor/default" context-service="default" hung-task-threshold="60000" core-threads="50" max-threads="500" keepalive-time="5000" queue-length="1000"/>
</managed-executor-services>
<managed-scheduled-executor-services>
<managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" core-threads="2" keepalive-time="3000"/>
</managed-scheduled-executor-services>
</concurrent>
<default-bindings context-service="java:jboss/ee/concurrency/context/default" jms-connection-factory="java:jboss/DefaultJMSConnectionFactory" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>
How could we configure it on JBoss EAP? We read the documentation but the "concurrent" tag does not exist and we want to manage the concurrent threads.
Wildfly 8 was the first version towards a Java EE 7 compliant application server. Wildfly 10 is the latest version in that line.
JBoss EAP 7 is the supported version corresponding to WildFly 10. It is now in Beta.
So in short if you want to use the concurrent tag then you need to use JBoss EAP 7.
You're actually downgrading. JBoss EAP 6.2 is based on JBoss Application Server (AS) 7.3.0.Final. See the JBoss EAP component matrix for reference.
As you can see, EAP 7 is not there, as it was not released yet. The page is being updated as the component versions settle. Once it's out there, instead of JBoss AS, there will be WildFly. For EAP 7, it will be WildFly 10.x, as ozOli wrote.
JBoss EAP 7 (not sure about WildFly 10) has a feature which takes your old standalone.xml and converts it to the new configuration - namespaces, subsystems.
Once there was a tool under development called WindRide which aimed at automated configuration migration, but that was cutted off few years back.
In addition to automated server configuration migration, there are tools to assist with automated application migration:
JBoss Windup - pluggable customizable rule-based automated migration tool.
Pretty good*.
*) reference: me - I'm one of developers :)
I have an ASP.NET application that I would like to upload to a host that offers a MySQL database. I am using Visual Studio 2012, .NET 4.5, Entity Framework 5.0, and I have installed MySQL for Visual Studio 1.0.2. I have been trying to connect to a local MySQL server, but I have encountered some problems.
At first I referenced MySql.Data and MySql.Data.Entity at version 6.6.5.0 in my project. But when I tried to do Update-Database in the package manager console, I got the following error:
System.DateTime System.Data.Entity.Migrations.Model.InsertHistoryOperation.get_CreatedOn()
This seems to be a problem with Entity Framework 5.0 and earlier versions of Connector/.Net - the MySQL connector for visual studio. Since the process was one of discovery, I unfortunately can't recall how my project came to reference MySql.Data and MySql.Data.Entity version 6.6.5.0.
I deleted the references, and then downloaded and referenced the same assemblies in version 6.7.4.0, using NuGet. This solved the error I got before, but now Update-Database gives me the following error:
Could not load file or assembly 'MySql.Data, Version=6.6.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I have solved this problem by including a specific DbProviderFactory in my Web.Config file:
<system.data>
<DbProviderFactories>
<remove invariant="MySql.Data.MySqlClient" />
<add name="MySQL Data Provider"
invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.7.4.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />
</DbProviderFactories>
</system.data>
If I leave out the remove tag, I get the error:
Column 'InvariantName' is constrained to be unique. Value 'MySql.Data.MySqlClient' is already present.
I think this means that somehow my project still has a DbProviderFactory that serves version 6.6.5.0 of the MySQL libraries. But when I search the text files of my project, I can't find the string 6.6.5.0 anywhere.
At the moment this solution lets me connect to my local MySQL server, but when I publish the project to my hosting provider and go to the web site in my browser, I just get an error message. I would like to know how to remove the implicit 6.6.5.0-serving DbProviderFactory, both as part of my learning and because I think my workaround could be the reason that my web site doesn't work at my hosting provider.
As a clue in finding a solution, I find it suspicious that when I try to add a reference, I can only see (several versions of) 6.6.5.0:
But when I go to the NuGet manager, I only have version 6.7.4.0 installed:
Hope this helps.
I wrote a blog post on this subject, my project is available for download at the bottom of this paper.
I had to install (as noted in my article) MySqlDataEntity -Pre, which install the beta version 6.7.2 beta, to get good compatibility with EF 5, but I see that now the current version is noted 6.7.4, so I updated my project accordingly, and it works just as well, so I also updated the project to download from my blog.
Hope this can help you to start with EF and MySql.
BTW, in case this is not clear, you have to install, from NuGet, MySql.Data.Entities, which will also install MYSql.Data, as Entities is depending on it.
My Java EE 6 application uses slf4j with logback as logging framework. I have openjpa custom logging which is not working on Weblogic while it was ok on glassfish before (whit openjpa 1.2).
When I add my custom log factory to "openjpa.log" property in persistence.xml, weblogic ignores this and doesn't work.
my custom log factory:
<property name="openjpa.Log" value="com.kishware.core.log.openjpa.CustomSLF4JLogFactory"/>
Here is the weblogic console output when ignores the property:
<Aug 17, 2013 11:29:35 AM GMT+04:30> <Warning> <J2EE> <BEA-160202> <You have specified a openjpa.Log setting in your configuration for persistence unit banco-product#pu-channel-manager. This setting will be ignored and all log messages will be sent to the WebLogic Server logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings in config.xml, or through the WebLogic Server Administration Console.>
I should mention that I'm using JPA 2.1 with Toplink implementation.
I would be happy to get some hints, how this could be solved.
I should mention that I'm using JPA 2.1 with Toplink implementation
Right there is your problem. You're trying to configure Toplink (and I think you mean EclipseLink) with OpenJPA configuration properties.
Can anybody please help me with a link or document to run jbpm-5.2 on tomcat 7 using mysql as database ? Does jbpm deployment to tomcat require some other tool or repository or something else ? I am a complete novice to jbpm... Please help me.
Thanks in advance...
I had same problem and have posted a solution here (there is an ANT script referenced which can be downloaded):
http://ironclaws.wordpress.com/2012/06/18/jbpm-5-2-tomcat-7-mysql-ant-script-18-2/
To summarize what is required in order to install jbpm 5.2 onto tomcat 7 using the final full distribution:
Bitronix Transaction Manager : The distribution does not attempt to deploy / configure this despite the requirement. The above Ant installer will install Bitronix at the Tomcat Server level – advantageous as at this point BTM may be integrated into other projects on the platform.
The jBPM distribution is designed for JBoss AS server and the console / console-server packages include EL (expression language) libraries. These will conflict with those which are installed with Tomcat – the Tomcat EL should be preserved.
There is some confusion with respect to javassist jar in the config / config-server distributions.
The included jars should be dropped – and included into both config / config-server javassist-3.4.GA
The reason for this dependency is that Hibernate 3.4 is deployed as persistence layer in this distribution.
There is a conflicting dom4j library – dom4j-1.6.jar deployed with the console / console-server packages. This should also be removed.
It is not mentioned clearly that the parameter:
-Dreporting.needcontext=true needs to be passed to the Tomcat JVM in order to allow the gtw-server to correctly instantiate the report module loader.
For the ‘Demo’ it is important to configure the human-server persistence correctly, and additionally address the includeantruntime issue during starting of this service.