Does Mule community edition v3.3.0 support shutdownTimeout feature?
The documentation at http://www.mulesoft.org/documentation/display/current/Global+Settings+Configuration+Reference suggests that the shutdowntimeout feature is supported from v2.2.0 but I am not able to get that shutdownTimeout feature to work?
Does anybody has implemented that shutdown feature in Mule v3.3.0 CE? Please help me in configuring that and get that feature to work.
Is this feature available only for EE or it is available in CE too?
the attribute is present and taken into account in 3.3.0.
In order to use it you should add a configuration tag in your config file and set a value for that attribute:
<mule>
...
<configuration shutdownTimeout="60000" />
...
However, as reported in https://www.mulesoft.org/jira/browse/MULE-6816 depending on the message processors present in your flow, the shutdown process could fail, if that's the case you could review the code changes in the fix and apply them.
What problem are you facing?
Regards,
Marcos
Related
I was following a tutorial for setting up a WebSphere Liberty Server Here and didn't really know what a part of the tutorial did. I completed the tutorial and it works fine.
On step 3 it has me modify the server.xml with these two lines and I dont really know what they do.
<applicationMonitor updateTrigger="mbean" />
<feature>localConnector-1.0</feature>
I Found the documentation for localConnector-1.0 but its a little over my head
https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.liberty.autogen.nd.doc/ae/rwlp_feature_localConnector-1.0.html
I think localConnector allows IntelliJ to run the server somehow but i dont know what updateTrigger="mbean" does.
If anyone has an explanation that would be great. Thanks!
The localConnector-1.0 feature enables the local JMX connector on Liberty so that the JMX Client (IntelliJ) can connect to and administer Liberty.
You can find more documentation on the feature here: https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/twlp_admin_localconnector.html
updateTrigger="mbean" is setting the application updates to only occur when trigger by an mbean call (whereas the default is to poll for changes).
You can find more documentation here:
https://www.ibm.com/support/knowledgecenter/SSAW57_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_setup_dyn_upd.html
people! I am migrating to mule 4 Kernel version.
I'm stuck in this moment: requirement is to read file from FTP and then process it. In old version it was like a few components:
1. quartz,
2. transformer
3. transformer
4. queue
Can somebody help me to migrate it to mule 4 kernel?
How to do this? How to put file content as string into queue like it was in older version? It would be nice if we could talking about Mule Kernel version. I'm new member of this community and of Mule developers, to pls dont hate me.
In next step I'm gonna split this file (splitter) but I know in Kernel there is not splitters anymore, so I have to use for each, right?
Now I've got
1. http listener (but it should be job. For my own tests It is http listener, I'm gonna to change this).
2. FTP read with FTP connector
3. ????
<flow>
<quartz
with cronExpression
and with conector to FTP>
</quartz>
<gzip-uncompress-transformer encoding="UTF-8"></gzip-uncompress-transformer>
<byte-array-to-string-transformer encoding="UTF-8"></byte-array-to-string-transformer>
<jms:outbound-endpoint queue="xxx" ></jms:outbound-endpoint>
</flow>
You should first try to read the migration guide and try to migrate each component to its equivalent in Mule 4: https://docs.mulesoft.com/mule-runtime/4.2/index-migration
For the example you mentioned it should very straightforward.
Quar
tz: it was already deprecated in Mule 3 by the Poll element. Its
replacement in Mule 4 is the Scheduler:
https://docs.mulesoft.com/mule-runtime/4.2/migration-core-poll
FTP:
there is a new FTP connector, which works in operations rather than
inbound/output:
https://docs.mulesoft.com/mule-runtime/4.2/migration-connectors-ftp-sftp
gzip uncompress: this isn't mentioned in the migration guide but just a search shows that there is a replacement: https://docs.mulesoft.com/connectors/compression/compression-module#gzip-decompressor-strategy
jms outbount: https://docs.mulesoft.com/mule-runtime/4.2/migration-connectors-jms#SendingMessages
: this kind of low level transformation is usually not needed anymore in Mule 4. (https://docs.mulesoft.com/mule-runtime/4.2/migration-core)
Most of the information is already in the documentation.
Another suggestion is try to use the latest available version of Mule and connectors.
Does anyone know how to configure NServiceBus (v6.2) using the AzureServiceBusTransport to not attempt to create namespaces?
I'd like to configure NServiceBus the use a connection string which only has permissions to send (the queue's should already be there and if not an error is more appropriate than creation) but whenever I configure it this way I get the following error:
Pre start-up check failed: Configured to create topology, but have no manage rights for the following namespace(s): xxxxxxxxxxxxxx
This error message suggests the functionality is configurable but having looked through the code and the documentation for the mechanism I can't find it.
Many thanks
Adam
Looks like I answered my own question - a bug was raised against the AzureServiceBusTransport and subsequently fixed a little while ago:
https://github.com/Particular/NServiceBus.AzureServiceBus/issues/528
As the bug says upgrading to version 7.1.8 or 7.2.3 and not enabling installers fixes the issue.
Good evening all, does any one know anything about this error
JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
it always appears when i start deploying mysql jar and my application fails to start on the sever HTTP Status 404 i suffered a lot from that and can't have any solution, please help me.
Note: i used mysql-connector-java-5.1.24.jar
That message gets printed because the MySQL driver is not JDBC compliant. That may seem a bit weird, but it's a long-standing known issue:
http://bugs.mysql.com/bug.php?id=62038
The problem is that to be fully JDBC compliant, the driver has to have SQL support conforming to the entry level of the SQL92 standard, but MySQL doesn't support features that are required by that. You read that right: MySQL doesn't support the most basic level of a twenty-year-old standard. Probably the most prominent example of a missing feature is check constraints. Therefore, the driver is non-compliant, and JBoss logs a message saying so.
However, this does not prevent the driver deploying correctly. As the message says, JBoss deploys it.
If your app is not working, the problem lies somewhere else.
Try using these instructions to deploy mysql driver to JBoss AS. With connector 5.1.22 as found in fedora18 I've never had a problem. Here is the module.xml
I am trying to connect to GlassFish 3's JMS service from a standalone remote client. However I am getting a java.lang.ClassNotFoundException: com.sun.messaging.jms.ra.ResourceAdapter. Any ideas on how to fix this?
Here's my setup so far:
Glassfish 3 JMS Service in LOCAL mode (I am assuming that EMBEDED mode will not work in this case because it bypasses the network stack)
JNDI properties are specified as follows:
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
java.naming.factory.url.pkgs=com.sun.enterprise.naming
java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl
gf-client-module.jar (in GLASSFISH_HOME/modules) added to the standalone application's classpath. Also tried adding other jars present in the modules directory (such as jms-core.jar), but still getting the same ClassNotFoundException.
Any help would be much appreciated.
Instead of using all of the individual Glassfish jar files that you might need (such as gf-client-module.jar, imqjmsra.jar, and imqbroker.jar), the preferred method is to use the gf-client.jar file. It can be found at $GLASSFISH_HOME/lib.
There is more information at http://glassfish.java.net/javaee5/ejb/EJB_FAQ.html#StandaloneRemoteEJB. That document pertains to using EJBs in standalone clients, but the solution is the same for using JMS.
Ok. I found a solution. See here for details, but the short answer is that I needed to add two jars to the classpath: imqjmsra.jar and imqbroker.jar. These were available inside a rar called imqjmsra.rar which can be found under glassfish's mq directory. I had to extract the two jars from this rar!
This is the complete list of client jars for glassfish 3 :
auto-depends.jar
deployment-common.jar
glassfish-corba-internal-api.jar
internal-api.jar
management-api.jar
bean-validator.jar
dol.jar
glassfish-corba-newtimer.jar
javax.ejb.jar
orb-connector.jar
common-util.jar
ejb-container.jar
glassfish-corba-omgapi.jar
javax.jms.jar
orb-iiop.jar
config-api.jar
ejb.security.jar
glassfish-corba-orb.jar
javax.resource.jar
security.jar
config-types.jar
glassfish-api.jar
glassfish-corba-orbgeneric.jar
javax.servlet.jar
ssl-impl.jar
config.jar
glassfish-corba-asm.jar
glassfish-naming.jar
javax.transaction.jar
transaction-internal-api.jar
connectors-internal-api.jar
glassfish-corba-codegen.jar
gmbal.jar
jta.jar
container-common.jar
glassfish-corba-csiv2-idl.jar
hk2-core.jar
kernel.jar
As mentioned in the Ivan A Krizsan's notes for the EJB certification, and depending on the Glassfish version, this should be enough:
GlassFish 3 (and GlassFish 4 too, I've just tested it): $GLASSFISH_HOME/lib/gf-client.jar
GlassFish 2: $GLASSFISH_HOME/lib/appserv-rt.jar and $APS_HOME/lib/javaee.jar