I´m using WSO2 Governance Registry 4.5.1.
I want to use UDDI, I download the version WSO2 Governance Registry 4.5.1 and I followed de instruction here http://docs.wso2.org/wiki/display/Governance450/Support+for+UDDI but I get the next error:
[2012-12-06 17:11:13,635] INFO {org.wso2.carbon.core.deployment.DeploymentInter
ceptor} - Deploying Axis2 service: UDDIReplicationService {super-tenant}
[2012-12-06 17:11:16,220] **ERROR {org.wso2.carbon.registry.uddi.servlet.JUDDIRegi
stryServlet} - jUDDI registry could not be started.java.lang.ArrayIndexOutOfBou
ndsException: 0**
org.apache.commons.configuration.ConfigurationException: java.lang.ArrayIndexOut
OfBoundsException: 0
at org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:122)
at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:95)
at org.apache.juddi.config.AppConfig.<init>(AppConfig.java:62)
at org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:183)
at org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:205)
at org.apache.juddi.Registry.start(Registry.java:55)
at org.wso2.carbon.registry.uddi.servlet.JUDDIRegistryServlet.init(JUDDI
RegistryServlet.java:25)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.init(Se
rvletRegistration.java:64)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.registerServle
t(ProxyServlet.java:142)
at org.eclipse.equinox.http.servlet.internal.HttpServiceImpl.registerSer
vlet(HttpServiceImpl.java:59)
at org.wso2.carbon.registry.servlet.internal.RegistryAtomServiceComponen
t.registerJUDDIServlet(RegistryAtomServiceComponent.java:96)
at org.wso2.carbon.registry.servlet.internal.RegistryAtomServiceComponen
t.setJUDDIRegistryServlet(RegistryAtomServiceComponent.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Do I forget any step?
Any suggestion???
Thank you very much.
Please try using Governance Registry 4.5.3 instead. 4.5.1 version did have some limitations which is probably why you are seeing this. However, even in 4.5.3, there are a few known issues which would impact certain UDDI operations, but most of the UDDI functionality is working in 4.5.3.
Thanks,
Senaka.
Related
Vulnerable JS Library jquery-3.4.1.js reported in Wso2 identity server 5.11.0.
I recently installed wso2 identity server 5.11.0 on my linux server and intregrated my application with it.
During ZAP scan below vulnerbaility is reported:
Vulnerable JS Library jquery-3.4.1.js reported in Wso2 identity server 5.11.0
Reported URL :
https://myapplicationurl.com/authenticationendpoint/libs/jquery_3.4.1/jquery-3.4.1.js
Does WSO2 provide any fix for this. It seems the authenticationendpoint application of wso2 uses this js and I am not sure of the impact if I just replace it with higher version of jquery.
Please refer to the WSO2 Security reporting process
at https://wso2.com/security. WSO2 discourages discussing security issues in public forums.
Nevertheless, most of the reported vulnerabilities of JQuery are not a threat to WSO2IS when it comes to their usage. Because those vulnerabilities reside in specific functions of JQuery and those functions are not used at all or not used in a vulnerable way.
this is my first question in Stackoverflow and i'm new in WSO2 ESB. I installed the 4.9.0 version of ESB and also installed Application Server feature on it. WSO2 ESB can not manage HttpSession. Can u help me please to solve this problem?
I already tried to change this parameter to true or false:
<session-config>
<session-timeout>30</session-timeout>
<cookie-config>
<secure>false</secure>
</cookie-config>
</session-config>
in ESB_HOME\repository\conf\tomcat\web.xml
Application server feature installed well i think. I can start my app and its working till i trying to use httpsession to manage users session and authentication.
Somebody had the same problem?
Using WSO2 API Manager 1.3 and WSO2 BAM 2.0.
I followed the instructions found in the README.txt in /statistics.
I am getting the following error when starting API Manager:
TID: [0] [AM] [2013-05-02 11:42:44,239] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Any suggestions on where to start looking for the issue?
It looks like you have not properly configured WSO2 API Manager 1.3 to work with WSO2 BAM.
For proper configuration follow the official docs[1]
This issue might also occur When you set an offset to BAM by 1 as described in the README.txt, as it needs its Cassandra DB configurations to be changed for the offset by 1 at BAM_HOME/repository/conf/etc/cassandra-component.xml. Therefore follow the like provided[1] where we change the API Manager's offset.
Suho
[1]http://docs.wso2.org/wiki/display/AM130/Monitoring+and+Statistics
I got the following error when runnning WSO2 API Manager 1.3.1 to use the WSO2 BAM Server 2.0.1.
TID: [0] [AM] [2013-05-02 18:58:40,609] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Both API Manager and BAM are running on the same machine and I changed offset to 1 in /home/jtao/api/wso2bam-2.0.1/repository/conf/carbon.xml based on Monetization of API Usage.
I also checked that BAM_HOME/repository/conf/etc/cassandra-component.xml doesn't exist in BAM 2.0.1. as someone suggested in the answer of another question "Configuring WSO2 API Manager to use the WSO2 BAM Server"
Any ideas?
I ran the same scenario described in guide and it works without any error. May be your have missed a part in the configuration guide? Make sure BAM_HOME is set correctly and BAM server is started before the AM server.
The following guide too can be used to integrate AM 1.3.1 with BAM 2.0.1
http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
Ishara
Having linked an instance of ESB v4.6.0 to a G-Reg v4.5.3 as per
http://docs.wso2.org/wiki/display/ESB460/Remote+Registry+Instance+Configuration#RemoteRegistryInstanceConfiguration-Atom-BasedRemoteInstanceConfiguration
When the ESB starts it throws several errors like:
[Framework Event Dispatcher] ERROR AbstractTransportService Error while checking the transport availability
java.lang.NullPointerException
Despite that, I can browse the Registry in both ends but when I create a BAM Profile in ESB while it's successfully saved in the Registry, the ESB starts to fail with:
[http-nio-9443-exec-37] ERROR RPCMessageReceiver Exception occurred while trying to invoke service method getResourceString
java.lang.reflect.InvocationTargetException
and the BAM Profile can't be read in the ESB end neither through the Registry Browser (empty resource) nor the BAM Profile management page (Exceptions). But can be read in the Governance Registry browser.
I set the permissions wide open when I create the shared collection, and the artifacts can be read, write, etc. by everyone.
I can't find information about what can be wrong with the connection, to allow to browse and write, but prevents ESB to read.
Any help would be much appreciated.
I'll respond my own question, to help out somebody else facing the same issue.
Atom-based registry sharing is deprecated "de-facto" in newer versions of WSO2.
Use JDBC-based registry sharing from now on.
Regards
i don't think its deprecated, im pretty sure its a bug, present in 4.5.1/2/3
wso2esb wso2 governance registry