https status codes

100     Continue

101     Switching protocols

200     OK

201     Created

202     Accepted

203     Non-authoritative information

204     No content

205     Reset content

206     Partial content

300     Multiple choices

301     Moved permanently

302     Moved temporarily

303     See other

304     Not modified

305     Use proxy

400     Bad request

401     Unauthorized

402     Payment required

403     Forbidden

404     Not found

405     Method not allowed

406     Not acceptable

407     Proxy authentication required

408     Request timeout

409     Conflict

410     Gone

411     Length required

412     Precondition failed

413     Request entity too large

414     Request-URI too long

415     Unsupported media type

500     Internal server error

501     Not implemented

502     Bad gateway

503     Service unavailable

504     Gateway timeout

505     HTTP version not supported

Adding new fonts for all users in Linux

Adding new fonts for all users

To install fonts for all users you need to login as root and create a directory under /usr/share/fonts/ for example /usr/share/fonts/custom. Copy the fonts you wish to add into the directory you created and run: fc-cache -f /usr/share/fonts/
All existing and new users should now be able to use the installed fonts.

WildFly 8 access log configuration

WildFly 8 configuration

WildFly open method and JBoss access_log 7 are similar, but also to find the web container corresponding to add configuration can be, but the container two use is not the same, but WildFly must be specified directory log.

 <subsystem xmlns="urn:jboss:domain:undertow:1.0">
            <buffer-caches>
                <buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/>
            </buffer-caches>
            <server name="default-server">
                <http-listener name="default" socket-binding="http"/>
                <host name="default-host" alias="localhost">
                    <location name="/" handler="welcome-content"/>
                    <filter-ref name="server-header"/>
                    <filter-ref name="x-powered-by-header"/>
                    <access-log pattern="common" directory="${jboss.home.dir}/standalone/log" prefix="access" />
                </host>
            </server>
            <servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only">
                <jsp-config/>
            </servlet-container>
            <handlers>
                <file name="welcome-content" path="${jboss.home.dir}/welcome-content" directory-listing="true"/>
            </handlers>
            <filters>
                <response-header name="server-header" header-name="Server" header-value="Wildfly 8"/>
                <response-header name="x-powered-by-header" header-name="X-Powered-By" header-value="Undertow 1"/>
            </filters>
        </subsystem>

As above, add the red line, you can open the WildFly 8 access_log function, restart the server, access to ip:8080 can be generated access.log in the JBOSS_HOME/standalone/log directory.

Among them

Prefix specifies the prefix log file name or file name

Pattern specifies the format of the log

Pattern can be set to two ways, the first is "common pattern=", the second is pattern="combined"

As can be seen, the second format of the log output relative to the concrete, and the actual development of opening which format in the access_log process according to demand to determine it.

Conclusion

Opening the access_log configuration to the end, if you have any questions, please refer to the following information, or to contact us, thank you！

ERROR [stderr] (HouseKeeper) Exception in thread "HouseKeeper" java.lang.OutOfMemoryError:

 ERROR [stderr] (HouseKeeper) Exception in thread "HouseKeeper" java.lang.OutOfMemoryError: Java heap space

 ERROR [stderr] (default task-6) Exception in thread "default task-6" java.lang.OutOfMemoryError: Java heap space

 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014612: Operation ("read-resource") failed - address: : java.lang.OutOfMemoryError: Java heap space

Task Scheduler: This task requires that the user account specified has Log on as batch job rights.

When I save a Task in Windows 2003 or 2008 R2, I get the following notification
Task Scheduler: This task requires that the user account specified has Log on as batch job rights.
To set this up you need to do the following
1. Start -> Run
2. Type in secpol.msc /s
3. Select "Local Policies" in MSC snap in
4. Select "User Rights Assignment"
5. Right click on "Log on as batch job" and select Properties
6. Click "Add User or Group", and include the relevant user.
7. OK out of dialogs

UT000047: The number of parameters exceeded the maximum of 1000

Issue:-

: java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000
2015-05-28 10:23:17,946 ERROR [io.undertow.request] (default task-54) UT005023: Exception handling request to /.do : java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000        at io.undertow.server.handlers.form.FormData.add(FormData.java:77) [undertow-core-1.1.0.Final.jar:1.1.0.Final]        at io.undertow.server.handlers.form.FormData.add(FormData.java:67) [undertow-core-1.1.0.Final.jar:1.1.0.Final]        at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.doParse(FormEncodedDataDefinition. We need to like below max-parameters need to add in standalone.xml Solution:- <ajp-listener name="default.ajp" socket-binding="ajp" max-parameters="200000"/>   <http-listener name="default" socket-binding="http" max-parameters="200000"/>

How to enable AJP protocal in WildFly8x to connect Apache server step by steps

WildFly  AJP settings It will update the configuration file of standalone.xml.   WILDFLY_HOME / standalone / configuration / standalone.xml   Please check the AJP port . When I default , it has become a 8009 .
1) Go to WILDFLY_HOME / standalone / configuration / standalone.xml You can see below info in standalone.xml<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:8090}"/>    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:8090}"/>    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>    <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>    <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>    <socket-binding name="http" port="${jboss.http.port:8080}"/>    <socket-binding name="http" port="${jboss.http.port:8080}"/>    <socket-binding name="https" port="${jboss.https.port:8443}"/>    <socket-binding name="https" port="${jboss.https.port:8443}"/>    <socket-binding name="txn-recovery-environment" port="4712"/>    <socket-binding name="txn-recovery-environment" port="4712"/>    <socket-binding name="txn-status-manager" port="4713"/>    <socket-binding name="txn-status-manager" port="4713"/>    <outbound-socket-binding name="mail-smtp">    <outbound-socket-binding name="mail-smtp">        <remote-destination host="localhost" port="25"/>        <remote-destination host="localhost" port="25"/>    </outbound-socket-binding>    </outbound-socket-binding> </socket-binding-group

2)You need to add below line under <server name="default-server"> and save 

<ajp-listener name="ajpListner" scheme="http" socket-binding="ajp"/>

After save restart of WildFly to Setting of AJP WildFly is complete .Then test AJP protocol listing or not using this command. netstat -a | grep 8009