Using this example as base, my embedded ApacheDS server runs fine the first time, then, when I stop the JBoss server on which my app runs and start again, and re-deploy, the log returns a load of errors starting with:
'(ERROR [stderr] (MSC service thread 1-1) org.apache.directory.api.ldap.model.exception.LdapEntryAlreadyExistsException: ERR_250_ENTRY_ALREADY_EXISTS ou=system already exists!)'
followed by others that have been accurately identified in this Apache JIRA issue
Every time I stop and start JBoss thereafter, the ApacheDS server starts just fine (same as in the JIRA issue)
The JIRA page states that the issue has been fixed with a little workaround, which I have applied
public EmbeddedADSVerTrunkV2(final File workDir) throws Exception
{
if (!workDir.exists())
{
workDir.mkdirs();
this.initDirectoryService(workDir);
this.service.shutdown();
}
this.initDirectoryService(workDir);
}
but the problem remains for me. The second run always fails before succeeding on the third and subsequent runs.
Are there any new workarounds or fixes that I have missed? Many thanks!
This issue was already fixed, please verify if you have the correct version of the jar file(s).
Related
Okay, before making this thread I've read all other threads here related to this error.
"SRVE0200E: Servlet [org.apache.cxf.transport.servlet.CXFServlet]: Could not find required class - org.apache.cxf.transport.servlet.CXFServlet"
The thing is, my problem here is a little unique. Its intermittent. We did not redeploy the application or do any other updates, what we did was just restart the application server at certain times whenever you tweak settings. After restarting, this shows up when accessing the application. Sometimes the application works fine, sometimes it doesn't and it shows this error. The change happens only every after a restart is made in he applications server
working -> restart -> fail -> restart -> working -> restart -> fail
Need your help. what seems to be the problem?
Application Server: Websphere Application Server v 8.5.0.1
Deployed Application: A rest service that uses Apache CXF framework
We already have the parent class loading to LAST.
Without changing something my webapplication refuses to load today.
I am using JBoss 4.0 and am deploying a web application using Inteli J IDE.
Initially I had the application at http://localhost:8080/app
Yesterday everything was working fine.
Today I am trying to run the application and am recieving a blank page.
Below is a screenshot from the debugger:
Update
I noticed that when I deploy 1 out of the 2 war's, I can access some addresses.
I am starting to suspect there is a problem with a Servlet context listener for one of the two war's.
Update 2
I see in the logs the following message:
java.lang.NoClassDefFoundError: org/jboss/cache/aop/PojoCacheMBean
The problem was with the deployed war. It seems if the deployment fails, this error is thrown for that context.
The solution in the specific case was to make a completely new/fresh and clean InteliJ project, and redo everything from the start with a fresh checkout.
I have the following code:
package ejbs;
import javax.annotation.Resource;
import javax.ejb.Singleton;
import javax.ejb.Timeout;
import javax.ejb.Timer;
import javax.ejb.TimerConfig;
import javax.ejb.TimerService;
#Singleton
public class timerbackup {
#Resource
private TimerService timerservice;
#Timeout
public void methodTimeout(Timer timer)
{
System.out.println("timeout");
}
public void settimer(long in)
{
Timer timer=timerservice.createSingleActionTimer(in,new TimerConfig());
}
}
After deploying the application appeared the error message "EJB Timer Service is not available".
To solve the problem i followed these steps:
Access the glash fish admin console (http://localhost:4848)
Go to Configurations->server-config->EJB Container
Select the tab EJB Timer Service
Then fill out Timer Datasource: with your JDBC Resource (i used "jdbc/projecto_final")
Restart the server
As suggested in Set/configure the EJB Timer Service’s DataSource.
This resulted but after sometime the TimerService stopped working. After deploying the application appears the following error messages:
Severe: Exception while loading the app
Severe: Undeployment failed for context /ProjetoEE1
Info: /file:/E:/formacaoJAVA/2moduloJEE/pratica/projecto_final /projfinal2/ProjetoEE1/build/web/WEB-INF/classes/_DEFAULT_PU logout successful
Warning: EJB Timer Service is not available. Timers for application with id 96332697224871936 will not be deleted
The Set/configure the EJB Timer Service’s DataSource also mention this problem, and present a solution in Glassfish DeploymentException: Error in linking security policy for.
The solutions presented in Glassfish DeploymentException: Error in linking security policy for consists basically in delete some files. The answer more voted suggests basically the following:
Stoped the Glassfish server
Deleted all the content from glassfishhome/glassfish/domains/ yourdomainname/generated
Started Glassfish
I have installed the "GlassFish Server 4.1.1", and this doesn´t work.
The second answer more voted suggests the basically the following:
1.All that's needed to fix this problem is delete the entire OSGi cache under $GLASSFISH_HOME/glassfish/domains//osgi-cache
This also doesn´t work.
What i can do? Any help will be very appreciate
Best regards,
Rafael Costa
I have solved the "same" problem in
deleting glassfish/domains/domain-name/generated folder completely
building application again
restarting glassfish application
In my case, I have installed a new version of my application after a Pull/Push operation with GIT and my application has stopped to work. So I know that before this new build my application worked well and that nothing has been changed on Glassfish.
I have found some explanation on another following site
https://dzone.com/articles/solving-ejb-timer-service-not-available-error-in-g-1
The Glassfish application server uses its embedded JAVADB to persist the state of its available EJB timers. Not setting the data resource for the timer service correctly prevents the EJB timers from being restored and eventually from functioning properly. In this case, normally the “EJB timer service not available” error message is returned. This problem prevents any application that uses an EJB timer service from being started or deployed.
There are two procedures available to overcome such blocking situations:
The first solution is to go to JDBC connection pools and double check the health of the Timerpool connection pool by pinging it. If the ping fails then the connection pool needs to be checked or to be redefined.
If pinging the connection pool is successful, then the problem could be the presence of the EJB timer marker file. A marker file is created whenever a problem occurs during the EJB timer service start-up or restore.
Deleting the marker will solve the problem. The marker file "ejb-timer-service-app" located under as-install-parent/glassfish/domains/domain-name/generated/ejb/. Dont forget to restart Glassfish !
Replace
import javax.ejb.Singleton;
With
import javax.inject.Singleton;
It worked for me. I'm using Derby database is it the case for you?
I solved the problem. If i remenber, i created a new JDBC resource and a new JDBC Connection Pool.
The following link explains how to create a JDBC resource and a JDBC Connection Pool.
General Steps for Creating a JDBC Resource
The JDBC resource and the JDBC Connection Pool can be created using the admin console or the asadmin utility.
The following link explains how to use the asadmin utility.Using the asadmin Utility
(I used this utility because in the admin console when i tried to create a JDBC resource and a JDBC Connection Pool appeared an error)
In the admin console, in the created JDBC Resource the field "Pool Name" should equals the name of the created JDBC Connection Pool.
After that i followed these steps:
Configurations->server-config->EJB Container
Select the tab EJB Timer Service
Fill the field Timer Datasource with the name of the JDBC resource.
Restart the server
Any question please feel free.
Best Regards Rafael Santos Costa
Hello I met the same problem if you have glassfish 4.1.1 there is probably an instability in the server with respect to timer.
Solution: update glassfish 4.1 to glassfish 5 and deploy the web application in this new server
We have an application running on WebSphere 6.1 and every couple of days we get the following appearing in the logs:
org.apache.axis.ConfigurationException: No engine configuration file - aborting!
at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:175)
at org.apache.axis.AxisEngine.init(AxisEngine.java:172)
at org.apache.axis.AxisEngine.(AxisEngine.java:156)
at org.apache.axis.client.AxisClient.(AxisClient.java:52)
at org.apache.axis.client.Service.getAxisClient(Service.java:103)
at org.apache.axis.client.Service.(Service.java:112)
If we restart the JVMs we are fine for about 2-3 days before it kicks off again.
I have seen another question on this site which describes a similar issue and the answer for that was:
I solved this by copying the client_config.wsdd file to WEB-INF/classes folder. Axis did not complaint yet :)
However, as far as we know we don't have a specific client_config.wsdd file nor have we ever had to configure one. If something was missing we would always get this error but as I mentioned above it only happens every few days and a stop start of the JVMs resolves it for a bit.
I am a newbie.I am using Weblogic 10.0.0.0..I am getting an validation error in first page(Login Page wit user name and pwd) as "logger is not initialized",while deploying. I do the same thing with tomcat, and the .war is imported and deployed is success. What is the reason? and also ,in weblogic 10.0.0.0 we have two jdk's(jdk 1.6 and Jrockit)...in my system i m having 1.6.0_17..so which one it takes.i forgot which i choose while installing..whether it takes from wblogic jdk or which one?..wher i m going wrong..its a small one i notice..but could not figure out..plz lemme kno??
This is either because you haven't configured your WLS installation correctly. When you first setup your console there is a parameter you have to change in your auth file that if not set with cause this issue.
Or you are selecting logging during deployment from the admin console and you haven't configured log4j in your application.