java,wildfly,wildfly-8,session-management,undertow
To override default InMemmorySessionManager with another SessionManager following steps should be done: Develop SessionManager which implements io.undertow.server.session.SessionManager Develop SessionManagerFactory which implements io.undertow.servlet.api.SessionManagerFactory Develop startup extension which implements io.undertow.servlet.ServletExtension, and in handleDeployment(Deployment) method change sessionManagerFactory with new SessionManagerFactory. Register new ServletExtension by adding...
The UndertowJaxrsServer is overriding the filehandler of your builder: public UndertowJaxrsServer start(Undertow.Builder builder) { server = builder.setHandler(root).build(); server.start(); return this; } Seems like there is no way to pass another handler to the UndertowJaxrsServer. Possible workarounds might be: Deploy another application with one resource class which simply serves files. Use...
You need to add a driver module dependency to your application in a jboss-deployment-structure.xml as described in Class Loading in WildFly Eg: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <dependencies> <module name="com.mysql" /> </dependencies> </deployment> </jboss-deployment-structure> ...
jsf,session,cdi,wildfly,jboss-weld
It seems we did encounter a Wildfly 8.2 bug, located in Weld. See this jira for more information : https://issues.jboss.org/browse/WFLY-4753 The fix has been to patch Wildfly with this patch : http://sourceforge.net/projects/jboss/files/Weld/2.2.12.Final Thank you all...
You will not be able to use the logger options in the console. The reason is that if you include a log4j config an entirely isolated logging instance is created for that deployment. If you want to use jboss's tools, you must remove your logging config and define in the...
There are a few possibilities what could go wrong. First, you are opening the connection in initParser(), but closing it in finalizeParser(), without using finally. If an exception is thrown, the connection is not closed. It would still be better to use try-with-resources. Another potential problem is that the class...
Okay, now I feel retarded.. I simply had to reload the server configuration. I though it would be enough to just add the resource and you are ready to go! On a single page deep inside Wildfly it said it has to reload the configuration. So I did and now...
This can be achieved by getting the Keycloak AdapterDeploymentContext from the ServletContext: AdapterDeploymentContext deploymentContext = (AdapterDeploymentContext) getServletContext().getAttribute(AdapterDeploymentContext.class.getName()); KeycloakDeployment deployment = deploymentContext.resolveDeployment(null); The deployment can then be queried for getAuthServerBaseUrl() & getRealm(). I got this to work in TomEE 1.7.1 (aka Tomcat 7 with the 1.1.0-Final of Keycloak) I'm sure it...
You can't register two different WAR's under the same context. Since you want to leave the business logic separate from the UI it's probably best to register the WAR with your REST services under a different context.
authentication,jboss,authorization,wildfly
I see 2 problems here. If you want to use your database only to load roles, then use the password-stacking in both login modules. It says to subsequent login modules not to check the credentials and only load roles. The DatabaseCertificate login module should be used together with SSL/TLS and...
xml,wildfly,jboss6.x,wildfly-8
For Http bloacking and Https enabling make changes to standalone-full.xml(i.e for custom server) or standalone.xml as follows 1: In messaging - hornetq-server subsystem connectors change http to https <http-connector name="http-connector" socket-binding="https"> <http-connector name="http-connector-throughput" socket-binding="https"> 2: In undertow subsystem change <http-listener name="default" socket-binding="http"/> to <https-listener name="default-ssl" socket-binding="https" security-realm="UndertowRealm"/> Note:...
I found the answer. We need to create an Undertow ServletExtension (io.undertow.servlet.ServletExtension) in the META-INF/services to register the authentication mechanism . My extension class looks like this: public class NtlmServletExtension implements ServletExtension { @Override public void handleDeployment(DeploymentInfo deploymentInfo, ServletContext servletContext) { deploymentInfo.addAuthenticationMechanism("NTLM", new NtlmAuthenticationMechanism.Factory()); } } Check this for more...
I think you need an additional dependency: <dependencies> <module name="javax.api"/> ... </dependencies> ...
log4j,wildfly,wildfly-8,jboss-logging
How about this one with jboss-cli: /subsystem=logging/custom-handler=LOG4J_SMTP:add( \ class="org.apache.log4j.net.SMTPAppender", \ module="org.apache.log4j", \ formatter="%-5p [%c] (%t) %s%e", \ level=INFO, \ properties={ \ From="[email protected]", \ LocationInfo=true, \ SMTPDebug=true, \ SMTPHost="smtp.gmail.com", \ SMTPPort=465, \ SMTPProtocol="smtps", \ SMTPUsername="[email protected]", \ SMTPPassword="***", \ Subject="error mail subject", \ To="[email protected]", \ BufferSize=256 }) For configuration...
This issue is because typo in filename it is not modules.xml it should be module.xml
batch-file,jboss,server,wildfly
You have started JBoss in standalone mode. There are two scripts to start JBoss, standalone.bat and domain.bat. If you start JBoss using domain.bat then it will start in domain mode. I actually wrote a blog about domain mode just the other day, which you might find useful as background reading:...
The script is almost certainly trying to start WildFly as the debian user wildfly. You will need to create this user and make sure it has correct permissions for your WildFly directories. The most easy way is to run useradd wildfly More detailed instructions can easily be found online...
cluster-computing,jndi,wildfly,hibernate-search,hornetq
When searching for this message Failed to connect to any server. Servers tried: [remote://127.0.0.1 from your stack trace I found this issue here which sounds similar: As remoting port is not enabled anymore in Wildfly Beta1, you will need to use the http-remoting protocol and point to port 8080. https://developer.jboss.org/message/843963#843963...
jboss,clojure,wildfly,undertow,immutant
This is not a solution but it can give you a hint on what's happening. From Immutant/WildFly documentation, it looks like your problem may come from this limitation when deploying and running into WildFly: When running inside WildFly, the :host and :port options to immutant.web/run are silently ignored since your...
hibernate,java-ee,wildfly,wildfly-8
I guess that this answer also answers my question http://stackoverflow.com/a/6263592/39998 It's fine to have the entities inside the lib directory like WEB-INF/lib/entities.jar, but then the persistence.xml file must be inside WEB-INF/lib/entities.jar/META-INF/persistence.xml If the persistence.xml file is inside WEB-INF/classes/META-INF/persistence.xml then the automatic scanning will occurr only inside WEB-INF/classes/* Makes sense. (kind...
java,eclipse,maven,wildfly,wildfly-8
It turns out that the POM was adding a whole bunch of stuff that I thought I needed, but in actuality didn't. I got rid of everything except those I added when the project was't maven based and I added server runtime libraries then everything was cool.
logging,log4j,wildfly,keycloak
You can add a log4j appender as a custom-handler. If you're using a custom log4j appender you'd need to install it as a module first. Example CLI command to add a org.apache.log4j.RollingFileAppender. /subsystem=logging/custom-handler=log4j-file:add(module=org.apache.log4j,class=org.apache.log4j.RollingFileAppender,named-formatter=PATTERN,properties={maxBackupIndex=5,append=true,immediateFlush=true,maxFileSize="10MB",file="${jboss.server.log.dir}/log4j.log"}) ...
http,jboss,jboss7.x,wildfly,wildfly-8
Support for range requests was added to undertow(web server used in WildFly) in version 1.2. Version 1.2 included in WildFly 9. WildFly 9 CR1 is out, with .Final version coming in few days. so in short, upgrade to WildFly 9...
WildFly only allows local connections by default, so if you get remote management connections, it seems you've changed the defaults already. This is the relevant section in standalone.xml <interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:127.0.0.1}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:127.0.0.1}"/> </interface> <interface name="unsecure"> <inet-address...
jboss,classpath,jboss7.x,wildfly,wildfly-8
Run standalone.sh -h to see the valid options. -p is not a valid option. Besides, WildFly uses modular classloading via JBoss Modules. The classpath is almost meaningless in this context, exception for bootstrapping JBoss Modules....
mysql,jdbc,jar,version,wildfly
Yes, of course. Connector/J 5.1.34 is latest version the official JDBC driver for MySQL. See docs http://dev.mysql.com/doc/connector-j/en/connector-j-versions.html Connector/J 5.1 is a Type 4 pure Java JDBC driver, which conforms to the JDBC 3.0 and JDBC 4.0 specifications. It provides compatibility with all the functionality of MySQL, including 4.1, 5.0, 5.1,...
eclipse,web-services,cxf,wildfly,ws-security
I had the same issue while working with the CXF with wildfly8.2 and wildfly8.1. Basically the wildfly server has its own CXF jars , which are by default loaded when you start the server. If you use the maven project then add the below dependancy with scope "provided" <dependency> <groupId>org.apache.cxf</groupId>...
ssl,encryption,wildfly,wildfly-8
You have to add a attribute called "enabled-cipher-suites" to the "https-listener" found at "subsystem undertow" -> "server". An example for this configuration can be found here. Unfortunately this example is wrong when it comes to the value of this attribute. You must not name such things as "ALL:!MD5:!DHA" but instead...
java,web-services,java-ee,wildfly,stateful-session-bean
That's unfortunately not the way web services work. The stateful bean is only stateful for the stateless bean. And not for a client. And that's very dangerous for several reasons: -The stateless bean saves state of a call in its stateful reference. But the next call of the stateless bean...
the problem was an @ID in a subclass. Annoying, that Hibernate does not tell the Entity where it happens. best regards Heiko...
Easier to deploy (only one package instead of multiples). Some server (example Weblogic, but not wildfly) allow shared session for an entire EAR. In general, EAR provide more option to configure with AS. Special folder (APP-INF) that let you define a config file application.xml. If your application would consist...
java,jboss7.x,message,wildfly,persistent-storage
HornetQ, the JMS implementation bundled with WildFly, uses persistent storage by default. This is true at least for 8.2.0.Final, I didn't check earlier releases. "Persistent" and "database" are not synonymous. HornetQ uses the filesystem for persistence, but that shouldn't really make a difference to your application....
hibernate,postgresql,java-ee,jpa,wildfly
I found the solution: I instantiated the DAO class with the "new"-operator in my EJB, instead of injecting it with the @Inject annotation.
Solved using WildFly standalone.xml: ... <logging-profiles> <logging-profile name="Webapp1"> <file-handler name="Webapp1File"> <level name="DEBUG"/> <file relative-to="jboss.server.log.dir" path="webapp1.log"/> </file-handler> <root-logger> <level name="DEBUG"/> <handlers> <handler name="Webapp1File"/> </handlers> </root-logger> </logging-profile> </logging-profiles> And in each War insert a manifest file with: Logging-Profile: Webapp1 ...
java,hibernate,postgresql,wildfly,entitymanager
I've prepared a sample application using JAX-RS, EJB and JPA - https://github.com/aparnachaudhary/prototypes/tree/master/jaxrs-db-access. I used the JMeter script to access the REST endpoint with multiple threads. But I could not reproduce the issue with PostgreSQL 9.3, postgresql-9.3-1103.jdbc41.jar and WildFly 8.1.0.Final.
jsf-2,jsf-2.2,wildfly,picketlink,resource-contracts
I was able to solve my problem with the following security configuration: .forPath("/javax.faces.resource/*.png.xhtml").unprotected() I've seen in my Firefox Inspector that the browser tried to load the image from /MyTestProject/javax.faces.resource/logo-main.png.xhtml?con=TemplateBlue, so trying the above seemed logical and it works!...
json,java-ee,resteasy,wildfly,pojo
Problem was in setter method Before fix: public void setFriends(Set<String> friends) { this.friends = new HashSet<>(friends) } To fix just need to add validation public void setFriends(Set<String> friends) { if (friends != null) { this.friends = new HashSet<>(friends) } } Hopefully this will help to avoid same mistakes for others....
java-ee,authentication,ldap,wildfly
The following step of operation will have to be performed for authenticating your application using LDAP (assuming that LDAP is already setup). Creating a new security domain in standalone.xml file. <security-domain name="LDAPAuth"> <authentication> <login-module code="LdapExtended" flag="required"> <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> <module-option name="java.naming.provider.url" value="ldap://localhost:389"/> <module-option...
You will need to add the certificate to keystore to make an SSL connection.You can refer to the following links. Install SSL Certificate Create KEYSTORE-File from existing SSL-Certificate Then you can create a datasource with a SSL URL as demonstrated in the below sample in standalone.xml file. <datasource jndi-name="java:jboss/datasources/dbname" pool-name="poolname">...
After backup-ing, edit your server config XML file (e.g standalone-full.xml) and add the jmx-management-enabled XML element, as described here for disabling JMX: ....... <subsystem xmlns="urn:jboss:domain:messaging:2.0"> <hornetq-server> <!-- next line is to be added --> <jmx-management-enabled>true</jmx-management-enabled> ........... </hornetq-server> ........... After that restart WildFly....
java,rest,jackson,jax-rs,wildfly
"How can I configure Jackson and its SerializationFeature in Wildfly?" You don't need to configure it in Wildfly, you can configure it in the JAX-RS applciation. Just use a ContextResolver to configure the ObjectMapper (see more here). Something like @Provider public class ObjectMapperContextResolver implements ContextResolver<ObjectMapper> { private final ObjectMapper...
jsp,java-ee,servlets,wildfly,java-ee-7
I had an: @ApplicationPath("/") public class MyApplication extends Application {} that was already bound to the root path so the login.jsp file, also in the root path, was ignored. Changing the above to @ApplicationPath("rest") solved the issue....
java,maven,ejb,wildfly,objectdb
Wow just writing about it here on SO helped me find my error :) I just have to force maven to include all dependencies. This can be done by including the following plugin into the pom.xml: <plugins> ... <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals> <goal>single</goal> </goals> </execution> </executions> <configuration> <descriptorRefs>...
Follow the guide from the Wildfly makers themselves. Below is the link: Glassfish to Wildfly Migration Also a very similar guide over here.Another Glassfish to Wildfly Migration...
What you're seeing in domain mode is the fully qualified name. It is telling you the host name, followed by the node name. If you look in your host-master.xml, you will see the root tag looks like this: <host name="master" xmlns="urn:jboss:domain:2.2"> If you change the host name to something like...
jboss,dependencies,pom.xml,wildfly,wildfly-8
Not all modules used by the server are meant to be used on deployments. There is a list of implicit module dependencies. If you look at the module.xml file for some of these you'll probably see a property <property name="jboss.api" value="private"/>. This essentially just means that the dependency can change...
java,maven,jboss,wildfly,wildfly-8
You must download JDBC driver for PostgreSQL: https://jdbc.postgresql.org/download.html Then configure it like this article: http://dmitrypukhov.pro/configure-jboss-and-postgresql-jdbc-datasource/
You have a few options. If you're leveraging CDI, you can add an observer method for @Observes @Initialized(ApplicationScoped.class) Object o If you're leveraging EJBs, you can have a @javax.ejb.Singleton @javax.ejb.Startup with a @PostConstruct method that does initialization. Here are two example implementations. // using a CDI object @ApplicationScoped public class...
caching,clojure,wildfly,immutant
This was being caused by an error with our deployment scripts. A hack had been done to deploy the same .war twice for an application requirement. The hack stopped the application from shutting down cleanly when a redeployment happened, and was causing the issue with the cache.
java,jboss,wildfly,wildfly-8,keycloak
The XML namespace urn:jboss:domain:web:1.1 is for AS7. The correct namespace in WildFly for web subsystem is urn:jboss:domain:undertow:1.0: <security-realms> ... <security-realm name="SecureRealm"> <server-identities> <ssl> <keystore path="localhost.keystore" relative-to="jboss.server.config.dir" keystore-password="wildfly"/> </ssl> </server-identities> </security-realm> </security-realms> ... <subsystem xmlns="urn:jboss:domain:undertow:1.0"> ... <server...
1.If you have EAR, you need to just set context-root for web module to "/" in your application.xml. <module> <web> <web-uri>webapp.war</web-uri> <context-root>/</context-root> </web> </module> 2.If you have WAR, you need to add jboss-web.xml next to web.xml with content: <jboss-web> <context-root>/</context-root> </jboss-web> (EDIT)3.You can set default-web-module attribute for default-host <subsystem xmlns="urn:jboss:domain:undertow:1.1">...
java,transactions,ejb,wildfly,infinispan
When using NON_XA transactions, failure to commit TX in cache may let the transaction to commit, and you would not get any exception that would tell you that the cache is inconsistent. As for cache.values(), prior to Infinispan 7.0 it returns only local entries, however that should not matter in...
Sooooo, I feel like a bit on a knob. It turns out that when I use chrome and not firefox, I don't get this problem. Firefox was mangling the JSESSIONIDs. This is because I've been too busy working to upgrade my ubuntu and I am using a very out of...
I managed to solve this by editing the standalone.conf file, and adding: JAVA_OPTS="$JAVA_OPTS -Djym.classpath=C:/MUNDO_JAVA/projects/jym/dev/props" I still didn't know why I had to edit that file, and not the standalone.conf.bat since I'm running on Windows, and I've read that the standalone.conf is for Unix....
java,java-ee,network-programming,wildfly
The configuration looks fine, I assume that there is some other Windows /network configuration besides the firewall setting preventing your access. Try telnet hostname port from your client to your server to check if port is accessible (see this SU answer)....
Need to read release notes: http://wildfly.org/news/2015/06/10/WildFly9-CR2-Released/ WildFly 9 CR2 is released! I’m happy to announce the WildFly 9.0.0.CR2 release! This release addresses a number issues discovered during the CR1 cycle, and also includes a major UX update to the console. ...
The real answer is you shouldn't edit the raw XML :) The short answer though is no. It's best to either use the web console or use CLI to manage the profiles. You can use CLI script files as well....
java-ee,wildfly,application-server
The standalone.bat/standalone.sh startup scripts accept a bind parameter so you can bind the application server to specific IP addresses for incoming requests. For example standalone.bat -b 0.0.0.0 will start Wildfly listening on all your IP addresses. Possible parameters: 0.0.0.0 for all IP addresses, 127.0.0.1 to listen just on localhost, 192.168.1.72...
java,hibernate,transactions,ejb,wildfly
org.apache.log4j.JBossAppenderHandler.doPublish(JBossAppenderHandler.java:42) This line was a little bit meaningless for me, but recently i find out the meaning... I had a structure of my project with log4j.xml inside WebContent/META-INF folder and i was using org.jboss.logging.Logger. Unfortunately i didn't get any error but the location of this file was wrong. As documentation...
I figured it out my self. Step 1: Open the openrdf-sesame.war with Total Commander or any file archiver. Go the WEB-INF folder and open the web.xml file. Edit the web.xml file by adding constraints, roles and the login-config tag as in this example : http://www.rivuli-development.com/further-reading/sesame-cookbook/basic-security-with-http-authentication/ Save the edited file within...
The process Controller is a tiny Java process which is in charge to mediate between the Domain controller and the Host controller. You don't have much control over it, as it is spawned when the Host controller is started, except that you can define the local port and address where...
Just in case somebody else stumbles into this Wildfly bug: The root exception for us was a ClassNotFoundError because an entirely unrelated JAR inside the EAR had the wrong version number. So the only thing really helping is, as Mike Robinson said, to double-check everything with a colleague. We also...
ajax,jsf,jsf-2,jsf-2.2,wildfly
This is a bug in Mojarra. I've just reported it as issue 3968. For now, one work around is to pass them as EL method arguments instead. <h:form enctype="multipart/form-data"> <h:commandButton value="Submit" action="#{bean.action(true)}"> <f:ajax execute="@this" render="@this"/> </h:commandButton> </h:form> public void action(boolean myparam) { // ... } ...
jboss,docker,wildfly,dockerfile
As James R. Perkins noted in his comment, I can't access it with localhost, I used docker host IP address and it worked
java,eclipse,jboss,netty,wildfly
This error is due the fact that you are referencing a non-existent connector. By default does not exist a netty-connector, but other such as http-connector. 'Cause you're using standalone-full, I'll consider that org.jboss.as.messaging module is enabled. First, we have to include an acceptor, responsible by accepting connections that will be...
java-ee,wildfly,hornetq,message-driven-bean
I managed to get it working. Some important points: The messaging-remote port in the consuming server configuration should of course point to the same port as in the producing server (5445). A user needs to be created using the bin/add-user.sh tool. The MDB then needs two ActivationConfigProperty's: @ActivationConfigProperty(propertyName = "user",...
jboss,jboss7.x,wildfly,wildfly-8
In standalone it's probably too late to set it in the configuration files. You'll need to add it to the standalone.conf or standalone.conf.bat in the JAVA_OPTS environment variable. A global property like that needs to be set before anything else attempts to use java.util.Arrays.
java-ee,jndi,wildfly,java-ee-7,managedthreadfactory
The standard managed thread factory is available in JNDI using the name java:comp/DefaultManagedThreadFactory. See §EE.5.21 of the Java EE 7 spec for more information....
I'm not a RestAssured used, so I can't answer your question directly, but here are some ideas that may help you out. I don't know what serializer RestAssured uses under the hood, but Resteasy on Wildfly uses Jackson by default. I would get familiar with this library. For less trivial...
In the logs you get on deploy appName='GSServerEAR-0.0.1' but when the exception occurs: appName:GSServerEAR. So I suppose, the runtime of your EAR file (when you deploy it) contains the version, and it should not.
There isn't a way. The web console doesn't generate CLI commands it generates DMR which is a detyped management model similar to JSON. CLI does the same thing. It takes CLI commands and converts them to DMR operations. The CLI does have tab complete which might help you. Some helpful...
You need to look at the JBoss Log Manager not WildFly. WildFly just delegates everything to the log manager. Specifically what you're looking for is this. That said this is a tricky issue. There's not a good reliable way to determine what files should be deleted. With a date suffix...
Have a look at logging profiles. Using a logging profile you can assign different logging configurations to different deployments. It also allows you to use the log view, assuming you use the jboss.server.log.dir relative path, and make changes at runtime. As far as provisioning a new server. There's nothing you...
thanks all for help; If anyone getting the same error than me, maybe this helps: I used managed beans in JSF which are EJB, but I need to use CDI-Beans. As I deleted the Beans from the faces-config.xml everything works fine. Sorry for asking this question....
java,file,properties,jboss,wildfly
Try putting files in WEB-INF/classes . If you put your config in src, than after compile it will be in WEB-INF/classes....
OSGi is no longer part of WildFly distribution. However, community member Arcadiy Ivanov picked up the projected and released compatible version for WildFly 8.2 see http://ivanov.biz/2015/jbosgi-for-wildfly-8-2-released/ for more...
authentication,ldap,jboss7.x,jsf-2.2,wildfly
i presumed that this security realms were meant to authenticate the application server console access You're partially correct there. The name="ManagementRealm" does indeed specify a realm config for accessing admin functions. name="ApplicationRealm" would be the attribute to specify for securing a web application Your current realm config is missing...
java,datasource,wildfly,wildfly-8
It turns out that Hibernate was holding connection and not releasing them to the Pool. Irrespective of the fact that we are using thread local context. But after adding <property name="hibernate.connection.release_mode">after_transaction</property> to the hibernate config. The problem got solved. PS: I still dont understand why we need to define this...
You can consider using JSON based HTTP management API. Sample plugin (Python based) for JBossAS - standalone mode is available here https://github.com/aparnachaudhary/nagios-plugin-jbossas7. This should also work for WildFly. Some details about WildFly HTTP Management API can be found here https://docs.jboss.org/author/display/WFLY9/The+HTTP+management+API...
To get spring 4 to log in wildfly 8, I had to add the following to the logging subsystem config in the standalone.xml file. <add-logging-api-dependencies value="false"/> <use-deployment-logging-config value="false"/> Additionally to get debug logging <logger category="org.springframework"> <level name="DEBUG"/> </logger> Here is the full subsystem config: <subsystem xmlns="urn:jboss:domain:logging:2.0"> <add-logging-api-dependencies value="false"/> <use-deployment-logging-config value="false"/>...
rest,session,cluster-computing,wildfly,weld
I had a similar looking stack trace. But I forgot set the "instance-id" in the undertow section of my wildfly configuration. The problem didn't come up, as long as the server didn't try to replicate the session. So the solution for me was simply setting an instance-id like this: <subsystem...
Found the answer: It was standalone.xml <subsystem xmlns="urn:jboss:domain:keycloak:1.0"> <auth-server name="main-auth-server"> <enabled>true</enabled> <web-context>auth</web-context> </auth-server> </subsystem> This was the problem I had to remove bit inside Keycloak upgraded to new version two days ago and they haven't upgraded their documentation. Hope this helps people trying to integrate new KeyCloak version...
security,java-ee,websocket,wildfly
For this you will have to modify the Websocket handshake. You can do this as below: 1) Modify you websocket endpoint to use custom configurator @ServerEndpoint(value = "/someWSEndpoint", configurator = SomeCustomConfigurationClass.class) public class SomeWSService { ... } 2) Modify WS Handshake similar to public class SomeCustomConfigurationClass extends ServerEndpointConfig.Configurator { @Override...
Used the info from this blog and Red Hat Site for setting up PKCS11-NSS provider and then added below steps to get it working: Add new socket-binding under socket-binding-group. <socket-binding name="https-myapp" port="7443"/> Add https-listener under subsystem/undertow <https-listener name="https-myapp-listener" socket-binding="https-myapp" security-realm="MyAppRealm" enabled-protocols="TLSv1" enabled-cipher-suites="TLS_RSA_WITH_AES_128_CBC_SHA" /> Add security realm under management/security-realms <security-realm...
java-ee,jboss7.x,wildfly,jboss-eap-6
I've discovered that I need to use JMX to obtain this value as its exposed via an MBean to the JVM (verifyable via JConsole....) So answering my own question: try { ObjectName serverMBean = new ObjectName("jboss.as:management-root=server"); MBeanServer server = ManagementFactory.getPlatformMBeanServer(); String serverGroupName = (String) ManagementFactory.getPlatformMBeanServer().getAttribute(serverMBean, "serverGroup"); logger.info("JBoss server group name...
This was a known issue in Alpha1 that was already fixed https://github.com/wildfly-swarm/wildfly-swarm/commit/761cdf1848a8720614b20a2272983bcd4e5f3c60 Best to build it from sources until Alpha2 release is done....
java,java-ee,integration-testing,wildfly,jboss-arquillian
The problem might be that your using ShrinkWrap.createFromZipFile. From my experience with Arquillian it better to create a custom WAR/JAR for each test. The method which creates the deployment usually looks like this: @Deployment public static WebArchive createDeployment() { //Load dependencies from POM final PomEquippedResolveStage pom = Maven .resolver() .loadPomFromFile("pom.xml");...
no need to add custom filter for access log. All you need is to configure access log in subsystem itself. This would be an example: <host name="default-host" > <location name="/" handler="welcome-content"> .... <access-log /> </host> which will by default log in to log folder with prefix access_.log you can also...
java,spring,jboss,spring-security,wildfly
Since this question is a bit tough, I assume you are already familiar with the Spring Security Kerberos samples that show how to configure kerberos auth with a form auth as fallback. I have no evidence that it'll work but I think you should be able to chain your kerberos...
It was because of the final method modifier.
java,ssl,jax-rs,resteasy,wildfly
"Do we have to generate keystores ourselves?" Yes. You need to generate one for the Server and a Trust store (which is just a key store, but we just call it a trust store to differentiate it). See SSL setup guide in the Wildfly documentation. It will show you...
This seems to be a serious issue in the Undertow (web subsystem in the WildFly) - I've reported it in the WildFly issue tracker: WFLY-4595
postgresql,jboss,wildfly,xa,jboss-cli
Use --exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter instead of --exception-sorter-properties=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter.
java,logging,jboss,wildfly,wildfly-8
From the "clean" standalone.xml I do the following: 1) Add a handler to the console: <profile> <subsystem xmlns="urn:jboss:domain:logging:2.0"> ... <console-handler name="CONSOLE_HANDLER"> <level name="DEBUG"/> <formatter> <named-formatter name="ECLIPSE_PATTERN"/> </formatter> </console-handler> ... 2) If you wish a log file: <profile> <subsystem xmlns="urn:jboss:domain:logging:2.0"> ... <periodic-rotating-file-handler name="MI_PROJECT_FILE_HANDLER" autoflush="true">...
dynamic,jboss,credentials,wildfly
One option could be creating a Datasource dynamically using the CLI's Model API. See the following example: public void createDatasource() throws Exception{ ModelNode request = new ModelNode(); request.get(ClientConstants.OP).set(ClientConstants.ADD); request.get(ClientConstants.OP_ADDR).add("subsystem", "datasources"); request.get(ClientConstants.OP_ADDR).add("data-source", "java:jboss/datasources/NewDatasource"); request.get("jndi-name").set("java:jboss/datasources/NewDatasource");...
gradle,spring-boot,war,wildfly
I removed the extentions of SpringBootServletInitializer, my main and co nfigure methods and added this method instead. It now starts up. @Override public void onStartup(ServletContext container) { ApplicationContext context = new ClassPathXmlApplicationContext("/META-INF/spring/applicationContext.xml"); PollableChannel ftpChannel = context.getBean("ftpChannel", PollableChannel.class); Message<?> message = ftpChannel.receive(); System.out.println("Received message: " + message); } ...
No, WAR files are not unpacked by default. ShrinkWrap is now used to parse the archive. If you want to edit these files, I would recommend continuing to create the myapp.war/ folder, which you can do using a maven assembly....