I am getting a lot of these errors while trying to build gwtp+mgwt app using ant-
Preparing method tabBarMoreImage
[java] [ERROR] An error occurred while trying to write the image bundle.
[java] javax.imageio.IIOException: Can't create output stream!
[java] at javax.imageio.ImageIO.write(ImageIO.java:1560)
...
Preparing method tabBarMostRecentImage
[java] [ERROR] An error occurred while trying to write the image bundle.
[java] javax.imageio.IIOException: Can't create output stream!
...
[java] Caused by: javax.imageio.IIOException: Can't create cache file!
[java] at javax.imageio.ImageIO.createImageOutputStream(ImageIO.java:397)
[java] at javax.imageio.ImageIO.write(ImageIO.java:1558)
[java] ... 33 more
[java] Caused by: java.io.IOException: Too many open files
[java] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[java] at java.io.File.checkAndCreate(File.java:1704)
[java] at java.io.File.createTempFile(File.java:1792)
[java] at javax.imageio.stream.FileCacheImageOutputStream.(FileCacheImageOutputStream.java:71)
[java] at com.sun.imageio.spi.OutputStreamImageOutputStreamSpi.createOutputStreamInstance(OutputStreamImageOutputStreamSpi.java:50)
[java] at javax.imageio.ImageIO.createImageOutputStream(ImageIO.java:393)
[java] ... 34 more
[java] Preparing method getButtonBarArrowDownImage
[java] [ERROR] An error occurred while trying to write the image bundle.
[java] javax.imageio.IIOException: Can't create output stream!
[java] at javax.imageio.ImageIO.write(ImageIO.java:1560)
[java] at com.google.gwt.resources.rg.ImageBundleBuilder.createImageBytes(ImageBundleBuilder.java:558)
[java] at com.google.gwt.resources.rg.ImageBundleBuilder.toPng(ImageBundleBuilder.java:544)
...
The application runs fine in dev mode. Any ideas?
Maybe GWT compiler is leaking file descriptors ( hence the "Too many open files" exception). Maybe you're on environment that has limited the number of open files per user (is this your own machine)?
Check all user limits with ulimit -a.
You can try to increase the open file limit by using ulimit -Hn <number>. This should at least help you diagnose.
Had exactly the same problem (and error message).
Found the solution in this thread on google groups (GWT)
I am using Linux (I don't know if that's your case)
In /etc/security/limits.conf I added
* soft nofile 65535
* hard nofile 65535
To apply the new settings, log out and in again.
Related
I am getting the following error when I tried to Initiate my test.
The test includes a large feeder which loops for 620,000 and has a map of 120 items with in the feeder.
Uncaught exception when running trip_dte: java.lang.OutOfMemoryError: GC overhead limit exceeded
[error] sbt.ForkMain$ForkError: java.lang.OutOfMemoryError: GC overhead limit exceeded
[error] at scala.collection.immutable.HashMap$HashTrieMap.updated0(HashMap.scala:358)
[error] at scala.collection.immutable.HashMap.$plus(HashMap.scala:62)
[error] at scala.collection.immutable.HashMap.$plus(HashMap.scala:36)
[error] at scala.collection.mutable.MapBuilder.$plus$eq(MapBuilder.scala:29)
[error] at scala.collection.mutable.MapBuilder.$plus$eq(MapBuilder.scala:25)
[error] at scala.collection.generic.Growable.$anonfun$$plus$plus$eq$1(Growable.scala:59)
[error] at scala.collection.generic.Growable$$Lambda$44/1950093417.apply(Unknown Source)
[error] at scala.collection.IndexedSeqOptimized.foreach(IndexedSeqOptimized.scala:32)
[error] at scala.collection.IndexedSeqOptimized.foreach$(IndexedSeqOptimized.scala:29)
[error] at scala.collection.mutable.WrappedArray.foreach(WrappedArray.scala:38)
[error] at scala.collection.generic.Growable.$plus$plus$eq(Growable.scala:59)
[error] at scala.collection.generic.Growable.$plus$plus$eq$(Growable.scala:50)
[error] at scala.collection.mutable.MapBuilder.$plus$plus$eq(MapBuilder.scala:25)
[error] at scala.collection.generic.GenMapFactory.apply(GenMapFactory.scala:48)
You don't provide enough information to be able to figure out your issue.
Possible issues:
you're using an eager feeder (large CSV like feeders are lazy in modern Gatling version, but no idea which Gatling version or which kind of feeder you use).
your system under load or your bandwidth can't handle the load you're trying to generate and your virtual users pile up in memory (can't complete their journey and no virtual users keep on arriving).
I am on JBoss EAP 6 and my task is to migrate a server to the Cloud.
I get JBoss to start, but then some queue fails with:
[echo] try to connect to local JBoss...
Checking for listener at 127.0.0.1:17545
Checking for listener at 127.0.0.1:17545
waitfor: condition was met
Property "jboss.not.started" has not been set
[echo] ...connection is available.
[antcall] Exiting /app/project/app/jboss-6.4-inst1/pi-deploy/tools/extension/configure.xml.
[echo] env.JBOSS_HOME=/opt/inet/jboss-6.4
[java] Executing '/opt/dbsinfra/zst/jdk-1.8.0_161/jre/bin/java' with arguments:
[java] '-jar'
[java] '/opt/inet/jboss-6.4/jboss-modules.jar'
[java] '-mp'
[java] '/opt/inet/jboss-6.4/modules'
[java] 'org.jboss.as.cli'
[java] '--file=/app/project/app/jboss-6.4-inst1/pi-deploy/../bin/configure.cli'
[java]
[java] The ' characters around the executable and arguments are
[java] not part of the command.
[java] INFO [org.jboss.modules] JBoss Modules version 1.3.10.Final-redhat-1
[java] INFO [org.xnio] XNIO Version 3.0.16.GA-redhat-1
[java] INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.16.GA-redhat-1
[java] INFO [org.jboss.remoting] JBoss Remoting version 3.3.12.Final-redhat-2
[java] INFO [org.jboss.as.cli.CommandContext] The batch executed successfully
[java] The batch executed successfully
[java] ERROR [org.jboss.as.cli.CommandContext] 'queue-address' is not found among the supported properties: [selector, entries, durable]
[java] 'queue-address' is not found among the supported properties: [selector, entries, durable]
You can see that the server gets configured via command line interface (CLI):
[java] '--file=/app/project/app/jboss-6.4-inst1/pi-deploy/../bin/configure.cli'
The offending part of the configure.cli script is:
#######################################################################
#
# JMS Queues
#
#######################################################################
# JMS Queue for business events
/subsystem=messaging:add()
/subsystem=messaging/hornetq-server=default:add()
/subsystem=messaging/hornetq-server=default/jms-queue=BusinessEventQueue:add(\
entries=["/queue/BusinessEventQueue"],\
queue-address="jms.queue.BusinessEventQueue"\ <------ HERE
)
/subsystem=messaging/hornetq-server=default/in-vm-connector=in-vm:add(server-id="0")
/subsystem=messaging/hornetq-server=default/in-vm-acceptor=in-vm:add(server-id="0")
/subsystem=messaging/hornetq-server=default/pooled-connection-factory=InVmJMSConnectionFactory:add(\
entries=["java:/InVmJMSConnectionFactory"],\
connector={"in-vm" => undefined}\
)
/subsystem=ejb3:write-attribute(name="default-resource-adapter-name", value="InVmJMSConnectionFactory")
/subsystem=ejb3:write-attribute(name=default-mdb-instance-pool, value="mdb-strict-max-pool")
What I don't get here is:
We're moving from JBoss EAP 6.4 to JBoss EAP 6.4 and the old/previous server is running OK.
I have never come in touch with anything JMS-like...
Question:
What is queue-address="jms.queue.BusinessEventQueue" here? Is this some kind of name?
How do you probably fix this? -> replace by name param?
Thanks
PS: the situation is a little more complex as I cannot just change a local file. The files are pulled from an SVN repo, so any attempt involves a commit... etc.
You cannot use queue-address as an attribute for JMS-Queue "add" operation. As it's not a supported operation. Try the below command it should work.
/subsystem=messaging/hornetq-server=default/jms-queue=BusinessEventQueue:add(\
entries=["/queue/BusinessEventQueue"])
When new JMS queue is created queue-address is set to jms.queue.BusinessEventQueue" by default. You can use below CLI command to check the value.
/subsystem=messaging/hornetq-server=default/jms-queue=BusinessEventQueue:read-attribute(name=queue-address)
if you have use queue-address while adding new JMS-queue, you will have use something like below.
jms-queue add --queue-address=BusinessEventQueue --entries=/queue/BusinessEventQueue
jms.queue would be added by default not need to pass that part.
I am getting OutOfMemoryExeption:Permgern space issue when building a Maven project in Jenkins.
At the end of the building process message is showing as "Build Success" .But after that line below error msg is printing.
Fatal Error : Permgern space
Once this exception comes ,every time whole Jenkins is getting hanged i.e no
corresponding page of Jenkins even if dash board is not opening.
Below is the Command Line argument error for Jenkins.
Java HotSpot(TM) 64-bit Server VM Warning : Exception java.lang.OutOfMemoryError
occured dispatching signal unknown to handler - The VM may need to forcibly terminated.
Below is the error details from the console O/P of job-
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building EmployeeInformation 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
**[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.161 s
[INFO] Finished at: 2016-09-11T00:55:52+05:30
[INFO] Final Memory: 5M/76M**
[INFO] ------------------------------------------------------------------------
Parsing POMs
Established TCP socket on 49708
[Employee_Management] $ "C:\Program Files\Java\jdk1.7.0_03/bin/java" -cp "C:\Users\pc\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.7.jar;C:\Program Files\Apache\maven\apache-maven-3.3.9\boot\plexus-classworlds-2.5.2.jar;C:\Program Files\Apache\maven\apache-maven-3.3.9/conf/logging" jenkins.maven3.agent.Maven32Main "C:\Program Files\Apache\maven\apache-maven-3.3.9" C:\Users\pc\.jenkins\war\WEB-INF\lib\remoting-2.62.jar C:\Users\pc\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.7.jar C:\Users\pc\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-**commons-1.7.jar 49708
FATAL: PermGen space
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
FATAL: PermGen space**
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:144)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)
Caused by: java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:365)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:310)
at hudson.remoting.Launcher.main(Launcher.java:530)
at hudson.remoting.Launcher.main(Launcher.java:513)
at hudson.remoting.Launcher.main(Launcher.java:504)
at hudson.remoting.Launcher.main(Launcher.java:500)
... 6 more
Below are some of the possible steps I tried to solve-
(1)In POM.XML below tag added.
attached image link for Changed permgern space configuration in POM.xml
(2)Set JAVA_OPTS in enviroment variable.
attached image link for setting enviromental variables
But,unfortunately none of them working.Still issue is there.
After searching some where,I got to know
-XX:PermSize=256m -XX:MaxPermSize=512m declaration will resolve the issue.But I am not sure Where and How to give the above declaration.
Guys,Plz go through the above links I attached and let me know If any thing I did wrong.
Any help will be appreciated.
BR//
Abinash
Add your options to the _JAVA_OPTIONS environment variable -- this will work for sure.
Otherwise, for customizing the compiler options in your Maven build environment, there's several possibilities. See this question for an overview.
I have a MVC spring application .
I am using this weblogic.xml descriptor (I want to get fid of Session Tracking: the JSESSION parameter that weblogic adds in the URL)
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
<jsp-descriptor>
<precompile>true</precompile>
</jsp-descriptor>
<!-- Added to resolve classpath problems when AOP is involved (hibernate, jcore, ...),
or compatibility problems between JARs provided in WLS as well as in the application.
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
-->
<context-root>ecat</context-root>
<!-- context-root>iot_devices</context-root-->
<!-- weblogic.xml entry -->
<session-descriptor>
<session-param>
<param-name>UrlRewritingEnabled</param-name>
<param-value>false</param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
but surprisingly I have this error:
[java] <23-May-2016 11:38:29 o'clock CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Users\nunito\git\iot-devices\iot-devicesWeb\build\iot-devicesWeb/WEB-INF/weblogic.xml of module null. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
[java] problem: cvc-complex-type.2.4a: Expected elements 'timeout-secs#http://www.bea.com/ns/weblogic/weblogic-web-app invalidation-interval-secs#http://www.bea.com/ns/weblogic/weblogic-web-app debug-enabled#http://www.bea.com/ns/weblogic/weblogic-web-app id-length#http://www.bea.com/ns/weblogic/weblogic-web-app tracking-enabled#http://www.bea.com/ns/weblogic/weblogic-web-app cache-size#http://www.bea.com/ns/weblogic/weblogic-web-app max-in-memory-sessions#http://www.bea.com/ns/weblogic/weblogic-web-app cookies-enabled#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-name#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-path#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-domain#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-comment#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-secure#http://www.bea.com/ns/weblogic/weblogic-web-app cookie-max-age-secs#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-store-type#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-store-cookie-name#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-store-dir#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-store-pool#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-data-source-jndi-name#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-session-flush-interval#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-session-flush-threshold#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-async-queue-timeout#http://www.bea.com/ns/weblogic/weblogic-web-app persistent-store-table#http://www.bea.com/ns/weblogic/weblogic-web-app jdbc-column-name-max-inactive-interval#http://www.bea.com/ns/weblogic/weblogic-web-app jdbc-connection-timeout-secs#http://www.bea.com/ns/weblogic/weblogic-web-app url-rewriting-enabled#http://www.bea.com/ns/weblogic/weblogic-web-app http-proxy-caching-of-cookies#http://www.bea.com/ns/weblogic/weblogic-web-app encode-session-id-in-query-params#http://www.bea.com/ns/weblogic/weblogic-web-app monitoring-attribute-name#http://www.bea.com/ns/weblogic/weblogic-web-app sharing-enabled#http://www.bea.com/ns/weblogic/weblogic-web-app' instead of 'session-param#http://www.bea.com/ns/weblogic/weblogic-web-app' here in element session-descriptor#http://www.bea.com/ns/weblogic/weblogic-web-app:<null>
[java] at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
[java] at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
[java] at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
[java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
[java] at weblogic.servlet.internal.WebAppDescriptor.getWeblogicWebAppBean(WebAppDescriptor.java:170)
[java] at weblogic.servlet.jsp.jspc20.initDescriptors(jspc20.java:504)
[java] at weblogic.servlet.jsp.jspc20.runBody(jspc20.java:235)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.jspc.main(jspc.java:22)
It seems that you're using the old tag structure for WebLogic.
WebLogic 10g,11g: UrlRewritingEnabled
WebLogic 12c: url-rewriting-enabled
So, your section should be something like this:
<session-descriptor>
<session-param>
<param-name>url-rewriting-enabled</param-name>
<param-value>false</param-value>
</session-param>
</session-descriptor>
Also, make sure to set cookie-secure to false if you intent to use url rewriting, since they conflict with each other. Check out the descriptor structure here.
Hope it helps !
I am trying to run jboss.
But I get the following error:
[javac] C:\Program Files\jbpm-5.0-try3\jbpm-installer\build.xml:518: warning
: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[java] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[java] SLF4J: Defaulting to no-operation (NOP) logger implementation
[java] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for fu
rther details.
[java] Task service started correctly !
[java] Task service running ...
as well, it does not run on port:8080.
What could be the problem?
How can I see the log file?
About the log files:
jboss should have the log files in the folder %JBOSS%\server\default\log.
About the port:8080:
I would check whether some other server is configured to listen on 8080 already. Especially if you are doing a lot of experimantal installations you can end up with several Jbosses, Tomcats and Glassfishes listening at the same port, so most of the servers won't receive their requests. At least to me it has happened once (but don't tell anybody).
It ccould be that logging failed to initialize and further errors prevent your application from correct deployment.
Check this first:
Failed to load class org.slf4j.impl.StaticLoggerBinder
This error is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem.
As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation.