I'm getting the following error when I start up a Java server process (WildFly application server):
Caused by: java.net.UnknownHostException: proxy01.phx2.fedoraproject.org: Name or service not known
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
at java.net.InetAddress.getLocalHost(InetAddress.java:1501)
The server is not harmed by this error, but it bothers me to have this error in the logs. It is something related with my environment. Indeed, the problem happens no matter which version of the server and on any location of my file system.
I have checked in /etc/hosts and /etc/resolv.conf but I really don't have idea where the "proxy01.phx2.fedoraproject.org" comes from.
Any idea?
Thanks
Related
I am receiving an error when starting application server. I am getting this error only specific server, the other starting perfectly fine. We are using WebSphere 8.0.0.9 version. I have shared the log below. I am not familiar with WebSphere system so if you need anything else beside this log, I will try to share it.
Exception Log:
class load: org.eclipse.osgi.service.debug.DebugTrace from: file:/opt/IBM/WebSphere/AppServer/plugins/org.eclipse.osgi_.jar
class load: org.osgi.framework.InvalidSyntaxException from: file:/opt/IBM/WebSphere/AppServer/plugins/org.eclipse.osgi_.jar
java.lang.NullPointerException
at java.security.SecureRandom.nextBytes(SecureRandom.java:292)
at java.security.SecureRandom.next(SecureRandom.java:311)
at java.util.Random.nextLong(Random.java:252)
at java.io.File.generateFile(File.java:1693)
at java.io.File.createTempFile0(File.java:1736)
at java.io.File.createTempFile(File.java:1814)
at org.eclipse.osgi.internal.baseadaptor.AdaptorUtil.canWrite(AdaptorUtil.java:208)
at org.eclipse.core.runtime.adaptor.LocationManager.canWrite(LocationManager.java:276)
at org.eclipse.core.runtime.adaptor.LocationManager.buildLocation(LocationManager.java:204)
at org.eclipse.core.runtime.adaptor.LocationManager.initializeLocations(LocationManager.java:150)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:275)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:394)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:157)
class load: java/text/MessageFormat
class load: java/text/FieldPosition
class load: java/util/Date
See this IBM technote for directions on adding the IBM JVM specific security service classes to theserver configuration, in particular the java.ext.dirs JVM property definition. The technote is for the IBM i platform, and based on the file location of the native_stderr.log you pasted above, I believe you're on a Linux platform, but the technote should still apply.
I have webservices deployed on WAS that use Clearquest jars to connect to Clearquest. At runtime, I get the following errors.
java.lang.Exception: Cannot parse the output since it has an error. Error = ReasonCode = conflictCRVAP0049E (internal-error): Cannot instantiate protocol provider: cqjnilinuxproxy (Not found in java.library.path)
...java.lang.reflect.InvocationTargetException:
at com.ibm.rational.stp.cs.internal.util.StpExceptionImpl.realException(StpExceptionImpl.java:493)
at com.ibm.rational.stp.cs.internal.util.StpExceptionImpl.<init>(StpExceptionImpl.java:572)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
at com.ibm.rational.stp.client.internal.core.ProtocolSubprovider.setProtocolProvider(ProtocolSubprovider.java:614)
... 57 more
Caused by: java.lang.UnsatisfiedLinkError: cqjnilinuxproxy (Not found in java.library.path)
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1090)
at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:1054)
at java.lang.System.loadLibrary(System.java:510)
at com.rational.clearquest.cqjni.CQJNIBaseObj.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:202)
at com.ibm.rational.stp.client.internal.cqjni.CqJniProtocol.<init>(CqJniProtocol.java:2343)
... 62 more
I followed the technote https://www-304.ibm.com/support/docview.wss?uid=swg21515079 - "An exception occurs on 64-bit WebSphere servers when running reports from ClearQuest data sources that require the Java Native Interface (JNI).
As suggested, WAS 32-bit was installed instead on 64 bit. But the error still occurs. Can you please let me know where this library is or what is going wrong?
Thanks,
Aarthi
The ClearQuest libraries and jars need to be placed on the path so WebSphere can pick them up. Did you source cq_setup.csh prior to starting the WebSphere profile? You would need to source cq_setup.csh and then start the profile in the same shell.
When I tried jbosseap6.3 install as service. I got below error. Anyone have any idea on the below error. Any one shed light means it is very helpful for me.
java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE"
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:119)
at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:338)
at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:291)
at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:300)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:542)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
at org.jboss.as.logging.logmanager.ConfigurationPersistence.configure(ConfigurationPersistence.java:149)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262)
at java.util.logging.LogManager$3.run(LogManager.java:399)
at java.util.logging.LogManager$3.run(LogManager.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
at java.util.logging.LogManager.access$800(LogManager.java:145)
at java.util.logging.LogManager$2.run(LogManager.java:345)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
at java.util.logging.LogManager.getLogManager(LogManager.java:378)
at org.jboss.modules.Main.main(Main.java:443)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:117)
... 18 more
Caused by: java.io.FileNotFoundException: C:\jboss-eap-6.3\standalone\log\server.log (The process cannot access the file because it is being used by another process)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:154)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setFile(PeriodicRotatingFileHandler.java:105)
at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:192)
at org.jboss.logmanager.handlers.FileHandler.<init>(FileHandler.java:122)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.<init>(PeriodicRotatingFileHandler.java:73)
... 23 more
Shutdown JBossEAP6.3.0 service [2015-05-29 09:58:27]
Try to start jBoss server as administrator by pressing right mouse key, it will permit jboss to create all folders and files .
Right click the installation directory of Jboss EA (mine is C:\program files\EAP6.1, then Properties, Security tab. Given everyone permissions on this folder (all users you can see just give full control). This should then be able to create logs etc files within the required folder.
This is just a workaround though only works for local installs.
I had the same issue, it worked after running it on root, maybe you are running it without the proper rights.
I had resolved this issue by creating log directory in the
C:\jboss-eap-6.3\standalone\
it's a problem due to permissions, the solution that worked for me is that i removed the home directory of jboss wildfly from C:\programmes to C:\
Starting Wildfly/Jboss from the administrator cmd worked!!
You are most likely getting this error because you either have the log file open in a text editor or you're already running that instance of JBoss.
I got the same exception
Try changing the path from c to another destination, that solved my issue and I am able to start the server
I am getting repeatedly below error while running java application on IBM - WebSphere Application Server.
[ 00000024 TCP E org.jgroups.protocols.TP$IncomingPacket run failed handling incoming message
java.io.IOException: failed reading header
at org.jgroups.Message.readHeader(Message.java:757)
at org.jgroups.Message.readFrom(Message.java:643)
at org.jgroups.protocols.TP.readMessage(TP.java:1502)
at org.jgroups.protocols.TP.access$700(TP.java:49)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1804)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:773)
Caused by: java.io.EOFException
at java.io.DataInputStream.readShort(DataInputStream.java:309)
at org.jgroups.Message.readHeader(Message.java:734)
... 7 more
java.io.IOException: failed reading header
at org.jgroups.Message.readHeader(Message.java:757)
at org.jgroups.Message.readFrom(Message.java:643)
at org.jgroups.protocols.TP.readMessage(TP.java:1502)
at org.jgroups.protocols.TP.access$700(TP.java:49)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1804)
at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1763)
at org.jgroups.util.ShutdownRejectedExecutionHandler.rejectedExecution(ShutdownRejectedExecutionHandler.java:39)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:779)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:667)
at org.jgroups.protocols.TP.dispatchToThreadPool(TP.java:1354)
at org.jgroups.protocols.TP.receive(TP.java:1321)
at org.jgroups.protocols.BasicTCP.receive(BasicTCP.java:258)
at org.jgroups.blocks.BasicConnectionTable.receive(BasicConnectionTable.java:239)
at org.jgroups.blocks.BasicConnectionTable$Connection.run(BasicConnectionTable.java:664)
at java.lang.Thread.run(Thread.java:773)
Caused by: java.io.EOFException
at java.io.DataInputStream.readShort(DataInputStream.java:309)
at org.jgroups.Message.readHeader(Message.java:734)
... 14 more
Application has file export operation. Somehow files are deleted from specified location and whenever I try to run application through above exception continuously. I tried killing java but that too do not help.
Please suggest how to resolve.
Stop IBM Webservice application already started services from services.msc :)
I have a really strange problem. I can successfully start my Eclipse internal JBoss Server (7.0.2). I can access the website and everything is fine. But after restarting or shutting down and starting again I always receive the following error out of nowhere:
Exception in thread "main" java.lang.NoClassDefFoundError: /Users/path/Coding/JBoss
Caused by: java.lang.ClassNotFoundException: .Users.robin.Coding.JBoss
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
I googled and looked in the JBoss forums. Some ppl had a problem with using the JRE Version instead of the JDK. I checked I am using the JDK 1.6..
Here some other informations:
Eclipse Indigo (3.7.1)
JBoss (jboss-as-web-7.0.2.Final) also tested with the newer version 7.1
JBoss Tools (3.3.x)
Java version "1.6.0_29"
Mac Os X 10.7.3 (Lion)
After deleting the internal Server in Eclipse and recreating I can again start it successfully the first time. The path to the external JBoss directory is correct.
Did anyone have the same problem or any idea what it could be?
Thanks for your help!
I found the solution. It's very strange but somehow after executing the Server a second time it's crashing because of the space in the path:
/Users/robin/Coding/JBoss Servers/..'
After removing the space I could also run the Server several times without crashing. Thanks to Perception, his comment was leading me to the solution.