Github Pull Request Builder - Cannot trigger build and cannot set build status on github commit - github

I'm using GitHub pull request builder plugin to setup a build per pull request.
However, this build is not triggered for any new pull request or new commit on a pull request. There are few exception on the Jenkins log. I have no clue what's wrong according to those logs.
Thanks in advance.
Sep 22, 2014 12:10:52 AM SEVERE org.jenkinsci.plugins.ghprb.GhprbTrigger getBuilds
The ghprb trigger for keeper-pull-request wasn't properly started - helper is null
Sep 22, 2014 12:10:52 AM WARNING hudson.model.listeners.RunListener report
RunListener failed
java.lang.NullPointerException
at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onStarted(GhprbBuildListener.java:19)
at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onStarted(GhprbBuildListener.java:12)
at hudson.model.listeners.RunListener.fireStarted(RunListener.java:213)
at hudson.model.Run.execute(Run.java:1702)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Sep 22, 2014 12:10:54 AM INFO jenkins.plugin.assembla.AssemblaProjectProperty$DescriptorImpl getSites
Called getSites size=0
Sep 22, 2014 12:11:00 AM WARNING hudson.triggers.Trigger checkTriggers
org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for hudson.model.FreeStyleProject#17c57009[keeper-pull-request]
java.lang.NullPointerException
at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:140)
at hudson.triggers.Trigger.checkTriggers(Trigger.java:266)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)

Finally, the problem is I haven't set Github project field in job configuration.
After configed that field, everything works well.

Related

Alfresco 5.2.4 in weblogic server

I am getting the following error when trying to install Alfresco 5.2.4 in weblogic 12. I am using all the supported technology stack as per the alfresco documentation. Any help would be greatly appreciated.
<Nov 28, 2018 10:13:21,313 PM CST> <Error> <javax.faces> <BEA-000000> <Unable
to call #PreDestroy annotated methods because no InjectionProvider can be
found. Does this container implement the Mojarra Injection SPI?>
<Nov 28, 2018 10:13:21,313 PM CST> <Error>
<javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Critical
error during deployment:
com.sun.faces.config.ConfigurationException: Factory
'javax.faces.lifecycle.ClientWindowFactory' was not configured properly.
I have faced similar issue recently. The following Work Around should fix this error:
Uncomment following lines in /META-INF/weblogic-application.xml
<package-name>javax.faces.*</package-name>
<package-name>javax.faces.application.*</package-name>
<package-name>javax.faces.component.*</package-name>
<package-name>javax.faces.context.*</package-name>
<package-name>javax.faces.convert.*</package-name>
<package-name>javax.faces.el.*</package-name>
<package-name>javax.faces.event.*</package-name>
<package-name>javax.faces.lifecycle.*</package-name>
<package-name>javax.faces.model.*</package-name>
<package-name>javax.faces.render.*</package-name>
<package-name>javax.faces.validator.*</package-name>
<package-name>javax.faces.webapp.*</package-name>

Exception while starting oim_server1 in Oracle Identity Manager

In my project, I am using Oracle Identity and Access Management-12.2.1.3.0. I did installation of weblogic (fmw_12.2.1.3.0_infrastructure.jar), Oracle SOA Suite 12c (fmw_12.2.1.3.0_soa_quickstart.jar), Oracle Identity Governance (OIM 12c) 12.2.1.3.0 (fmw_12.2.1.3.0_idm.jar). Executed RCU for schema creation and did weblogic domain configuration also.
In weblogic domain configuration, I gave username - "weblogic" and passoword - "Welcome1" for keystore, OIMSchemaPassword, sysadmin and WeblogicAdminKey in at credentials step.
Node manager, weblogic server and soa_server1 are starting smoothly but when I am starting oim_server1, I am getting exception -
<Dec 15, 2017 6:13:41,431 PM IST> <Info> <oracle.iam.OIMPostConfigManager> <BEA-000000> < task failed :ENCRYPT_CONFIGURATION>
<Dec 15, 2017 6:13:41,433 PM IST> <Error> <oracle.iam.OIMPostConfigManager> <BEA-000000> <Task failed.::ENCRYPT_CONFIGURATION>
<Dec 15, 2017 6:13:41,433 PM IST> <Error> <oracle.iam.OIMPostConfigManager> <BEA-000000> <Task failed.::ENCRYPT_CONFIGURATION>
<Dec 15, 2017 6:13:42,000 PM IST> <Info> <oracle.iam.OIMPostConfigManager> <BEA-000000> <updating feature:ENCRYPT_CONFIGURATIONwith state :FAILEDwith executionTimeNot Applicable>
<Dec 15, 2017 6:13:42,046 PM IST> <Error> <oracle.iam.OIMPostConfigManager> <BEA-000000> <Shutting down the BootStrap Process. Please fix the problem and start the OIM Managed server again to complete OIM BootStrap. OR, If you want to skip the feature which has failed, mark the feature as complete using sql 'update oimbootstate set state='COMPLETE' where featurename='FAILED_FEATURE_NAME' and start the Managed Server again. In the latter case, you will have to manually perform the task being done by the failed feature. Refer to the Install documentations for the same>
<Dec 15, 2017 6:13:42,046 PM IST> <Error> <oracle.iam.OIMPostConfigManager> <BEA-000000> <Shutting down the BootStrap Process. Please fix the problem and start the OIM Managed server again to complete OIM BootStrap. OR, If you want to skip the feature which has failed, mark the feature as complete using sql 'update oimbootstate set state='COMPLETE' where featurename='FAILED_FEATURE_NAME' and start the Managed Server again. In the latter case, you will have to manually perform the task being done by the failed feature. Refer to the Install documentations for the same>
java.lang.Exception: Exception occured while encrypting the configuration
at oracle.iam.OIMPostConfigManager.config.util.EncryptConfigurationAndDB.encryptConfiguration(EncryptConfigurationAndDB.java:181)
at oracle.iam.OIMPostConfigManager.config.OIMConfigManager.encryptConfiguration(OIMConfigManager.java:5319)
at oracle.iam.OIMPostConfigManager.config.OIMConfigManager.executeAndRegisterTask(OIMConfigManager.java:1634)
at oracle.iam.OIMPostConfigManager.config.OIMConfigManager.configureOIM(OIMConfigManager.java:1556)
at oracle.iam.OIMPostConfigManager.config.OIMConfigManager.doExecute(OIMConfigManager.java:1175)
at oracle.iam.OIMPostConfigManager.appListener.BootStrapListener.preStart(BootStrapListener.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.run(BaseLifecycleFlow.java:240)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.application.internal.ApplicationContextImpl$WLSSecurityProvider.invokePrivilegedAction(ApplicationContextImpl.java:1594)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:201)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:245)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:729)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:241)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:66)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:65)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:166)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:41)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:193)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments$2.doItem(ConfiguredDeployments.java:741)
at weblogic.management.deploy.internal.parallel.BucketInvoker.invoke(BucketInvoker.java:138)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionAppsParallel(ConfiguredDeployments.java:749)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:363)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:219)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:133)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1287)
at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:333)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:375)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:116)
at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:698)
at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:78)
at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:212)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:235)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:116)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:90)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1237)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1168)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$UpOneLevel.run(CurrentTaskFuture.java:786)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
Caused by: java.lang.Exception: Exception occurred during generation of keystores.
at oracle.iam.OIMPostConfigManager.config.util.EncryptConfigurationAndDB.encryptConfiguration(EncryptConfigurationAndDB.java:161)
... 66 more`enter code here`
I am starting soa_server1 and oim_server1 using command startManagedWebLogic.cmd soa_server1 and startManagedWebLogic.cmd oim_server1 respectively.
I finally found the answer to this problem:
Try to check if you have password to /app/oracle/product/ofm/user_projects/domains/IAM_domain/config/fmwconfig/default-keystore.jks by running following command
$JAVA_HOME/bin/keytool -list -keystore /app/oracle/product/ofm/user_projects/domains/IAM_domain/config/fmwconfig/default-keystore.jks -storepass PASSWORD_OF_THE_DEFAULT_KEYSTORE
If the KeyStore entries are displayed, at least this much can be sure that the KeyStore is not corrupt or tampered with. As your password is correct, it may be possible that in the Credential store, somehow password may be incorrect.
So, log in the Enterprise Manager console (http://hostname:7001/em), Weblogic Domain --> IAM_Domain --> Right Click --> Security --> Credentials --> oim.
Then edit the password of default-keystore.jks in EM And then restart the servers.
With the incorrect password, you will receive:
keytool error: java.io.IOException:` Keystore was tampered with, or password was incorrect
As you do not know the password to default-keystore.jks; take backup of this file, delete it and create new at the same location with same name and alias as orakey
$JAVA_HOME/bin/keytool -genkeypair -keyalg RSA -alias orakey -keypass <NEWPASS> -keystore default-keystore.jks -storepass <NEWPASS> -validity 3600

javax.mail.MessagingException in servlet

In Eclipse, I created a class EmailSender.java to send an email using the javax.mail library.
In a tester class, Tester.java, I am able to create a EmailSender object and send an email
Tester.java
EmailSender emailS=new EmailSender();
emailS.eSend(emailTo,msg);
And it's working..emailTo receives msg as email.
But inside a servlet, FaireOffre.java, creating an EmailSender object is giving me errors..
exception trace
Apr 17, 2015 9:41:08 PM org.apache.catalina.core.ApplicationContext log
INFO: Marking servlet faireOffre as unavailable
Apr 17, 2015 9:41:08 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet faireOffre
java.lang.ClassNotFoundException: javax.mail.MessagingException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at com.hp.servlets.FaireOffre.<init>(FaireOffre.java:30)
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 java.lang.Class.newInstance(Class.java:433)
...
Note that my Tester.java class, EmailSender.java class and FaireOffre.java (servlet) are in different packages.
How can I resolve these exceptions ?
This solved my problem:
Go to "Project properties -> Deployment Assembly page".
I added the javax.mail jars under 'Source'

Why is database medrec not found by the Avitek sample application?

Circumstances: performed a by-the-book developer install using wls1212_dev.zip and wls1212_dev_supplemental.zip. Followed the README.txt and the README_SUPP.txt strictly. Created a sample domain by hand, no issues seen. Executed the run_samples.sh configuration script, no issues seen.
When starting the medrec domain (Avitek sample app) using startWebLogic.sh, the medrec database is not found (specific error below). The Avitek app comes up and display-only pages are navigable, but database touches all fail. The WLS console in the medrec domain works fine. The JDBC data source "MedRecGlobalDataSourceXA" exists in the domain and the fields look ... well, reasonable, to my untrained eye.
For now I am taking the error message at face value and assuming database creation failed within the setup script (run_samples.sh) But I examined all the logs in wlserver/samples after executing the run_samples.sh script, and there was nothing that seemed relevant.
Platform: VirtualBox VM with CentOS 6.5 and JDK1.7.0_45
Other notes: I am aware of the security fix in 1.7.0_51 and higher JDKs that breaks existing Derby database applications. I purposely chose to avoid this issue by installing the 0_45 JDK until I resolve this "database not found" issue.
Grateful for any help.
Error:
<May 25, 2014 8:40:46 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<May 25, 2014 8:40:46 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<May 25, 2014 8:40:47 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application "MedRecGlobalDataSourceXA" due to error weblogic.application.ModuleException: org.apache.derby.client.am.DisconnectException: The connection was refused because the database medrec was not found.
weblogic.application.ModuleException: org.apache.derby.client.am.DisconnectException: The connection was refused because the database medrec was not found.
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:338)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:167)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
Truncated. see log file for complete stacktrace
Caused By: org.apache.derby.client.am.DisconnectException: The connection was refused because the database medrec was not found.
at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
Truncated. see log file for complete stacktrace
In linux unset variable LANG before starting Derby database server.

Akka warning about "Too many HashedWheelTimer instances"

I'm getting the following warning when my Akka 1.2-based application tries to work with more than 500 or so grid nodes:
Jan 05, 2012 1:36:43 PM org.jboss.netty.util.internal.SharedResourceMisuseDetector
WARNING: You are creating too many HashedWheelTimer instances.
HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
I'm going to dig more deeply into the Akka code to find out where the HashedWheelTimer is being used and what I should do to avoid too many of those being created. While I'm doing that, I thought I'd post the warning here in case one of the experts may be able to give me a pointer or two that may narrow and speed up my search, please?
Using Akka 1.3-RC6, I'm getting the following exception:
Jan 12, 2012 1:24:38 PM org.jboss.netty.util.HashedWheelTimer
WARNING: An exception was thrown by TimerTask.
org.jboss.netty.channel.ChannelException: Failed to open a socket.
at org.jboss.netty.channel.socket.nio.NioClientSocketChannel.newSocket(NioClientSocketChannel.java:49)
at org.jboss.netty.channel.socket.nio.NioClientSocketChannel.<init>(NioClientSocketChannel.java:83)
at org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory.newChannel(NioClientSocketChannelFactory.java:139)
at org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory.newChannel(NioClientSocketChannelFactory.java:86)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:218)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:188)
at akka.remote.netty.ActiveRemoteClient.connect(NettyRemoteSupport.scala:470)
at akka.remote.netty.ActiveRemoteClientHandler$$anonfun$channelClosed$1$$anon$4.run(NettyRemoteSupport.scala:599)
at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:519)
at org.jboss.netty.util.HashedWheelTimer$Worker.notifyExpiredTimeouts(HashedWheelTimer.java:440)
at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:379)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.SocketException: Too many open files
at sun.nio.ch.Net.socket0(Native Method)
at sun.nio.ch.Net.socket(Net.java:323)
at sun.nio.ch.Net.socket(Net.java:316)
at sun.nio.ch.SocketChannelImpl.<init>(SocketChannelImpl.java:101)
at sun.nio.ch.SelectorProviderImpl.openSocketChannel(SelectorProviderImpl.java:60)
at java.nio.channels.SocketChannel.open(SocketChannel.java:142)
at org.jboss.netty.channel.socket.nio.NioClientSocketChannel.newSocket(NioClientSocketChannel.java:47)
... 11 more
Has been fixed in Akka 2.0-M1, I've now backported the fix to 1.3 and it will be in the next RC.