-
Bug
-
Resolution: Answered
-
Low
-
2.10.0, 4.7.0, 4.7.2
-
None
-
Severity 3 - Minor
-
0
-
database settings using LDAP credential:
<database type="oracle"> <connection dialect="org.hibernate.dialect.Oracle10gDialect" driver="oracle.jdbc.OracleDriver" jdbcurl="jdbc:oracle:thin:@ldap://ldap.server.au/cn=OracleContext,cn=NetServiceNames,dc=test,dc=au/jra1prd" password="Sanitized by Support Utility" username="fecru" maxPoolSize="20" minPoolSize="5" driverSource="bundled"/> </database>
Accessing Smart Commits settings will have the following errors:
2013-07-08 09:29:35,817 ERROR [CommitNotifier1 ] com.atlassian.event.internal.LockFreeEventPublisher$Publisher LockFreeEventPublisher$Publisher-dispatch - There was an exception thrown trying to dispatch event 'com.atlassian.fisheye.event.CommitEventImpl[source=BSG]' from the invoker 'com.atlassian.event.internal.SingleParameterMethodListenerInvoker@36b60ce2'. java.lang.RuntimeException: java.lang.reflect.UndeclaredThrowableException at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:50) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:60) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:28) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:56) at com.atlassian.event.internal.LockFreeEventPublisher$Publisher.dispatch(LockFreeEventPublisher.java:228) at com.atlassian.event.internal.LockFreeEventPublisher.publish(LockFreeEventPublisher.java:83) at com.atlassian.fisheye.event.FisheyeEventPublisher.publish(FisheyeEventPublisher.java:29) at com.cenqua.fisheye.rep.CommitNotificationRepositoryListener$CommitEventNotifier.apply(CommitNotificationRepositoryListener.java:208) ... Caused by: java.lang.reflect.UndeclaredThrowableException ... Caused by: java.lang.reflect.InvocationTargetException ... Caused by: java.sql.SQLException: Could not get connnection ... Caused by: com.cenqua.crucible.hibernate.CruDBException: java.sql.SQLException: IO Error: JNDI Package failure javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.ldap.LdapCtxFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory not found from bundle [com.atlassian.fecru.plugin.commithook.fecru-commithooks-plugin]] ... Caused by: java.sql.SQLException: IO Error: JNDI Package failure javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.ldap.LdapCtxFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory not found from bundle [com.atlassian.fecru.plugin.commithook.fecru-commithooks-plugin]] ... Caused by: oracle.net.ns.NetException: JNDI Package failure javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.ldap.LdapCtxFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory not found from bundle [com.atlassian.fecru.plugin.commithook.fecru-commithooks-plugin]]
Other plugins in Crucible will have similar errors too.
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
PLUG-1079 Plugin2 can't access JNDI when using LDAP credentials.
- Done
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page"){kind=icon}
[CRUC-6533] Plugin 2 can't access JNDI classes
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 433095 ] |
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 860153 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 860153 ] |
| Fix Version/s | New: N/A [ 54415 ] |
| Resolution | New: Answered [ 9 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | New: jac-cleanup-phase9 |
| UIS | Original: 4 | New: 0 |
| UIS | Original: 9 | New: 4 |
| Global Rank | New: Ranked higher |
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.
We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details.
If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates.
Kind regards
Marek Parfianowicz
Development Team Lead