[JBoss JIRA] Created: (JBESB-2979) Override juddi sequence name
by Kevin Conner (JIRA)
Override juddi sequence name
----------------------------
Key: JBESB-2979
URL: https://jira.jboss.org/jira/browse/JBESB-2979
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.6
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7
The juddi v3 hibernate configuration is using hibernate_sequence as the name of its sequence and this clashes with the jBPM setup.
We have also discovered an issue where this sequence is not always created but this is related to the database configuration.
Depending on the startup sequence the following outcomes are possible
- no errors are seen and everything works
- complaint during juddi initialisation that the hibernate_sequence does not exist
- complaint during the jBPM initialisation that the hibernate_sequence already exists.
Changing the name of the sequence removes the conflict between the jBPM and juddi configurations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2978) Juddi v3 errors running on Oracle
by Kevin Conner (JIRA)
Juddi v3 errors running on Oracle
---------------------------------
Key: JBESB-2978
URL: https://jira.jboss.org/jira/browse/JBESB-2978
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.6
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7
Tom Cunningham investigate this and provided the following comment
"Earlier today, Julian found an issue during ESB startup with Oracle and jUDDI :
(10:09:42 AM) jdc: 2009-11-12 15:01:41,758 ERROR [org.hibernate.util.JDBCExceptionReporter] (pool-8-thread-6) ORA-01400: cannot insert NULL into ("SOA"."J3_ADDRESS_LINE"."LINE")
This also happens on one other table - J3_BINDING_DESCR on the DESCR column later in the startup.
>From what I can see, the issue here is that Oracle treats empty strings as NULLs, and if a column has a NULL constraint on it and you try and insert an empty string, it treats it as a null and throws an error. We didn't see this in our jUDDI testing because it requires the combination of ESB and jUDDIV3 on Oracle (we used MySQL and Postgres during testing). Other databases treat empty strings as empty strings, so we didn't see this until now in our testing.
Fixing these two issues would require a change to JAXRRegistryImpl.java in the ESB project and a change to Scout. I've aspectized the Scout change in the ESB project and I'm sending Kevin/Julian/Trevor the diffs.
This issue can also be easily worked around for testing with a small manual change. If you let the server startup and fail, the tables will be created. Then stop the server, and go in and modify the J3_ADDRESS_LINE.LINE column and the J3_BINDING_DESCR.DESCR columns to be NULLABLE. Then startup again and everything will succeed."
I have his changes and am going to apply the workarounds to our codebase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2976) Null pointer exception in JOPR plugin (plus fix?)
by Kevin Conner (JIRA)
Null pointer exception in JOPR plugin (plus fix?)
-------------------------------------------------
Key: JBESB-2976
URL: https://jira.jboss.org/jira/browse/JBESB-2976
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.6
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7
Hi,
I deployed the BPM orchestration 2 quickstart and then went to:
JBoss ESB Statistics
JBoss ESB Deployments
Quickstart_bpm_orchestration2.esb JBoss ESB Statistics
JBoss ESB Services
ResultsService Service
JBoss ESB Listeners
ESB-Listener - BPM_Orchestration2_Service1 Listener Configuration
in the admin console. I saw:
15:58:15,811 ERROR [MeasurementManager] Could not get measurement values
java.lang.NullPointerException
at org.jbosson.plugins.jbossesb.ListenerComponent.getValues(ListenerComponent.java:64)
Is the attached the correct fix (it hides the exception and is similar to the
other clauses)?
Thanks,
J
Index: product/tools/jonplugin/src/main/java/org/jbosson/plugins/jbossesb/ListenerComponent.java
===================================================================
--- product/tools/jonplugin/src/main/java/org/jbosson/plugins/jbossesb/ListenerComponent.java (revision 30085)
+++ product/tools/jonplugin/src/main/java/org/jbosson/plugins/jbossesb/ListenerComponent.java (working copy)
@@ -61,8 +61,10 @@
String metricName = request.getName();
if (metricName.equals(MEP)) {
EmsAttribute attribute = getEmsBean().getAttribute(MEP);
- String processed = (String) attribute.refresh();
- report.addData(new MeasurementDataTrait(request, processed));
+ if (attribute != null) {
+ String processed = (String) attribute.refresh();
+ report.addData(new MeasurementDataTrait(request, processed));
+ }
} else if (metricName.equals(LIFECYCLE_STATE)) {
EmsAttribute attribute = getEmsBean().getAttribute(LIFECYCLE_STATE);
String processed = new String();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2975) hsql db related test failures
by Kevin Conner (JIRA)
hsql db related test failures
-----------------------------
Key: JBESB-2975
URL: https://jira.jboss.org/jira/browse/JBESB-2975
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.7
Reporter: Kevin Conner
Fix For: 4.8
Having changed the way in which hsql is being used within our tests, we are now seeing two different types of failure.
The first is a deadlock in hsql, caused by the shutdown method sleeping while holding a lock on the server.
java.lang.Thread.State: TIMED_WAITING (sleeping)
[java] [junit] at java.lang.Thread.sleep(Native Method)
[java] [junit] at org.hsqldb.Server.shutdown(Unknown Source)
[java] [junit] - locked <0xae4bec58> (a org.hsqldb.Server)
[java] [junit] at org.hsqldb.Server.shutdown(Unknown Source)
[java] [junit] at org.jboss.soa.esb.testutils.HsqldbUtil.stopHsqldb(HsqldbUtil.java:99)
[java] [junit] at org.jboss.soa.esb.persistence.tests.ScheduledRedeliveryUnitTest.runAfterAllTests(ScheduledRedeliveryUnitTest.java:198)
[java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
The second is being seen on windows only, exhibited as follows
[java] [junit] [Server@750159]: [Thread[HSQLDB Server @750159,5,main]]: Database [index=0db=file:E:\hudson\data\jobs\JBoss_ESB\workspace\trunk\product\build\testdb/persistUnitTestDB, alias=persistunittestdb] did not open: org.hsqldb.HsqlException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@57a1a0db[file =E:\hudson\data\jobs\JBoss_ESB\workspace\trunk\product\build\testdb\persistUnitTestDB.lck, exists=true, locked=false, valid=false, fl =null]: java.lang.Exception: checkHeartbeat(): lock file [E:\hudson\data\jobs\JBoss_ESB\workspace\trunk\product\build\testdb\persistUnitTestDB.lck] is presumably locked by another process.
[java] [junit] [Server@750159]: [Thread[HSQLDB Server @750159,5,main]]: Shutting down because there are no open databases
Updating the hsql version to the latest download (hsqldb_1_8_1_1.zip) fixes the first and appears to fix the second.
I have successfully executed a full CI run on windows and have verified the code changes for the deadlock.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2906) JuddiRMIService: avax.naming.ServiceUnavailableException when using the binding manager
by Daniel Bevenius (JIRA)
JuddiRMIService: avax.naming.ServiceUnavailableException when using the binding manager
---------------------------------------------------------------------------------------
Key: JBESB-2906
URL: https://jira.jboss.org/jira/browse/JBESB-2906
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Priority: Critical
Fix For: 4.7
I ran into this issue when trying the twoservers quickstart on AS 5.1 and starting the server like described in readme.txt:
./run.sh -c first -Djboss.service.binding.set=ports-01
Stacktrace:
17:03:49,877 INFO [JuddiRMIService] starting juddi RMI service
17:03:49,897 INFO [JuddiRMIService] ProviderURL : + jnp://localhost:1099
17:03:49,897 INFO [JuddiRMIService] InitialContextFactory : org.jnp.interfaces.NamingContextFactory
17:03:49,897 INFO [JuddiRMIService] InitialContextFactoryPgks : org.jboss.naming
17:03:54,957 ERROR [STDERR] javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]]
17:03:54,959 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
17:03:54,961 ERROR [STDERR] at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:547)
17:03:54,961 ERROR [STDERR] at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:540)
17:03:54,961 ERROR [STDERR] at javax.naming.InitialContext.rebind(InitialContext.java:367)
17:03:54,961 ERROR [STDERR] at org.apache.juddi.registry.rmi.JNDIRegistration.register(JNDIRegistration.java:95)
17:03:54,961 ERROR [STDERR] at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:138)
17:03:54,962 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
17:03:54,962 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
17:03:54,962 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
17:03:54,962 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
17:03:54,962 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
17:03:54,963 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
17:03:54,963 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
17:03:54,963 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
17:03:54,963 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
17:03:54,963 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
17:03:54,963 ERROR [STDERR] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
17:03:54,964 ERROR [STDERR] at $Proxy38.start(Unknown Source)
17:03:54,964 ERROR [STDERR] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
17:03:54,964 ERROR [STDERR] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
17:03:54,964 ERROR [STDERR] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
17:03:54,964 ERROR [STDERR] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
17:03:54,965 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
17:03:54,965 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
17:03:54,965 ERROR [STDERR] at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
17:03:54,965 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
17:03:54,965 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
17:03:54,965 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
17:03:54,966 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
17:03:54,966 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
17:03:54,966 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
17:03:54,966 ERROR [STDERR] at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
17:03:54,966 ERROR [STDERR] at org.jboss.system.ServiceController.start(ServiceController.java:460)
17:03:54,967 ERROR [STDERR] at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
17:03:54,967 ERROR [STDERR] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
17:03:54,967 ERROR [STDERR] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
17:03:54,967 ERROR [STDERR] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
17:03:54,967 ERROR [STDERR] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
17:03:54,968 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
17:03:54,968 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
17:03:54,968 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
17:03:54,968 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
17:03:54,968 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
17:03:54,968 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
17:03:54,969 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
17:03:54,969 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
17:03:54,969 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
17:03:54,969 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
17:03:54,969 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
17:03:54,970 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
17:03:54,970 ERROR [STDERR] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
17:03:54,970 ERROR [STDERR] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
17:03:54,970 ERROR [STDERR] at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
17:03:54,970 ERROR [STDERR] at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
17:03:54,970 ERROR [STDERR] at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
17:03:54,971 ERROR [STDERR] at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
17:03:54,971 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
17:03:54,971 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
17:03:54,971 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
17:03:54,971 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
17:03:54,971 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
17:03:54,972 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
17:03:54,972 ERROR [STDERR] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
17:03:54,972 ERROR [STDERR] at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
17:03:54,972 ERROR [STDERR] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
17:03:54,972 ERROR [STDERR] at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
17:03:54,973 ERROR [STDERR] at org.jboss.Main.boot(Main.java:221)
17:03:54,973 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:556)
17:03:54,973 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
17:03:54,974 ERROR [STDERR] Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]
17:03:54,974 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
17:03:54,974 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
17:03:54,975 ERROR [STDERR] ... 68 more
17:03:54,976 ERROR [STDERR] Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]
17:03:55,009 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
17:03:55,010 ERROR [STDERR] ... 69 more
17:03:55,011 ERROR [STDERR] Caused by: java.net.ConnectException: Connection refused
17:03:55,011 ERROR [STDERR] at java.net.PlainSocketImpl.socketConnect(Native Method)
17:03:55,011 ERROR [STDERR] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
17:03:55,011 ERROR [STDERR] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
17:03:55,012 ERROR [STDERR] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
17:03:55,012 ERROR [STDERR] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
17:03:55,012 ERROR [STDERR] at java.net.Socket.connect(Socket.java:520)
17:03:55,012 ERROR [STDERR] at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
17:03:55,012 ERROR [STDERR] at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
17:03:55,013 ERROR [STDERR] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
17:03:55,013 ERROR [STDERR] ... 69 more
Troubleshooting:
I think this might have to do with the removal of the system properties related to java.naming. Previously we set these in JuddiRMIService but this overwrote them for the entire JVM.
Now this is the only thing we do in startService()
System.setProperty("juddi.propertiesFile", juddiPropertyFile.getAbsolutePath());
System.setProperty("javax.xml.registry.ConnectionFactoryClass","org.apache.ws.scout.registry.ConnectionFactoryImpl");
JNDIRegistration.register();
Now, JNDIRegistraion.register() (http://ws.apache.org/juddi/xref/org/apache/juddi/registry/rmi/JNDIRegistr...) first checks the system properties and if they don't exist will default to ones specified in it's configuration. I thought that that would be the properties that we specify with "juddi.propertiesFile" above but they do not seem to get set.
I tried setting them explicitly like this:
Config.setStringProperty(RegistryEngine.PROPNAME_JAVA_NAMING_PROVIDER_URL, xmlProperties.getProperty("java.naming.provider.url"));
Config.setStringProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_INITIAL, xmlProperties.getProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_INITIAL));
Config.setStringProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_URL_PKGS, xmlProperties.getProperty(RegistryEngine.PROPNAME_JAVA_NAMING_FACTORY_URL_PKGS));
And this worked for me but I we should look into this to see if there are other options availabe. But hopefully this will help with investigating this issue.
I'll attach a modified (debug statements) of JuddiRMIService to this jira.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months