[JBoss JIRA] Created: (JBESB-1100) Wrong Juddi-DB initialisation script for Sybase
by Mikhail Kolesnikov (JIRA)
Wrong Juddi-DB initialisation script for Sybase
-----------------------------------------------
Key: JBESB-1100
URL: http://jira.jboss.com/jira/browse/JBESB-1100
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration, Deployment, Registry and Repository
Affects Versions: 4.2
Environment: JBoss 4.2, MsSQL 9.0 as a BackEnd
Reporter: Mikhail Kolesnikov
Assigned To: Mark Little
Fix For: 4.2.1, 4.2
For initializing JUDDI data source on MsSQL I have used script for Sybase and there is an error occured in server log:
com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated
Perform some debugging I had find a root cause - wrong DB structure
This script exists in ESB distribution:
CREATE TABLE BINDING_TEMPLATE
(
SERVICE_KEY VARCHAR(41) NOT NULL,
BINDING_KEY VARCHAR(41) NOT NULL,
ACCESS_POINT_TYPE VARCHAR(20) NULL,
ACCESS_POINT_URL VARCHAR(255) NULL,
HOSTING_REDIRECTOR VARCHAR(255) NULL,
LAST_UPDATE DATETIME NOT NULL,
PRIMARY KEY (BINDING_KEY),
FOREIGN KEY (SERVICE_KEY)
REFERENCES BUSINESS_SERVICE (SERVICE_KEY)
)
But we need in that one:
CREATE TABLE BINDING_TEMPLATE
(
SERVICE_KEY VARCHAR(41) NOT NULL,
BINDING_KEY VARCHAR(41) NOT NULL,
ACCESS_POINT_TYPE VARCHAR(20) NULL,
ACCESS_POINT_URL TEXT NULL, -- HERE MUST BE 'TEXT'
HOSTING_REDIRECTOR VARCHAR(255) NULL,
LAST_UPDATE DATETIME NOT NULL,
PRIMARY KEY (BINDING_KEY),
FOREIGN KEY (SERVICE_KEY)
REFERENCES BUSINESS_SERVICE (SERVICE_KEY)
)
Best regards...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1071) SqlTableGatewayListener code supports 'where' clause, but it is missing in jbossesb-1.0.1.xsd
by Bernhard Gass (JIRA)
SqlTableGatewayListener code supports 'where' clause, but it is missing in jbossesb-1.0.1.xsd
---------------------------------------------------------------------------------------------
Key: JBESB-1071
URL: http://jira.jboss.com/jira/browse/JBESB-1071
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2, 4.2.1
Environment: OSX-10.4.10
Dual 2GHz PowerPC G5, 3GB
Reporter: Bernhard Gass
Assigned To: Mark Little
SqlTableGatewayListener auto created a prepared sql statement from the information given in the *-esb.xml file defining your services. A where condition is supported in the code
SqlTableGatewayListener - Line 344
ListenerTagNames - Line 111
but 'whereCondition' or 'where-condition' is not supported in jbossesb-1.0.1.xsd.
Asessment:
If my understanding is correct the generated prepared statement is called for every pull, but only one message is processed.
Every fetch loads ALL messages from the DB every cycle which leads to a problem specially when the source database has many rows. A static where clause can solve some of the above, but most likeley a parameterized 'where clause' is desireable (which leads to the question where the parameters come from).
Additional considerations:
- Processing speed can be improved considerably by fetching several rows and deliver them for processing one by one or better process them in batches all together (given the business case allows that).
- Some mechanism is needed to parameterize the fetching mechanism. A rudimentary mechanism can be realized using a plain 'where' clause
- In a production scenario additional issues play a role.
- Messages most of the times have a sequence they need to be processed in.
- A specific business case might or might not allow gaps in the sequence of transaction id's. A sequence of transaction id's without gaps often is used to assure no messages are missing.
- Even using something like an Oracle sequence is not a guaranty for a sequence witout gaps (sequence gaps can e.g. occure after a Oracle CPU flush).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBESB-704) business_rules_service QS does not function properly after redeployment
by Kevin Conner (JIRA)
business_rules_service QS does not function properly after redeployment
-----------------------------------------------------------------------
Key: JBESB-704
URL: http://jira.jboss.com/jira/browse/JBESB-704
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Content Based Routing
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Mark Little
The business_rules_service does not function correctly after a redeployment.
The first time the QS is executed you will receive output similar to the following
10:31:12,355 INFO [STDOUT] Customer Status: 60
10:31:12,355 INFO [STDOUT] Order Total: 44.92
10:31:12,355 INFO [STDOUT] { ================ After Order Priority
10:31:12,356 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60
10:31:12,356 INFO [STDOUT] Order Priority: 1
10:31:12,356 INFO [STDOUT] Order Discount: 0.0
10:31:12,356 INFO [STDOUT] Order Total: 44.92
10:31:12,356 INFO [STDOUT] } ================ After Order Priority
10:31:12,357 INFO [STDOUT] Customer Status: 60
10:31:12,358 INFO [STDOUT] Order Total: 44.92
10:31:12,358 INFO [STDOUT] { ================ After Order Discount
10:31:12,358 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60
10:31:12,358 INFO [STDOUT] Order Priority: 1
10:31:12,358 INFO [STDOUT] Order Discount: 0.0
10:31:12,358 INFO [STDOUT] Order Total: 44.92
10:31:12,358 INFO [STDOUT] } ================ After Order Discount
10:31:12,360 INFO [STDOUT] Low Priority
10:31:12,426 INFO [STDOUT] { ================ Shipping
10:31:12,426 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60
10:31:12,426 INFO [STDOUT] Order Priority: 1
10:31:12,426 INFO [STDOUT] Order Discount: 0.0
10:31:12,426 INFO [STDOUT] Order Total: 44.92
10:31:12,427 INFO [STDOUT] } ================ Shipping
If you then redeploy the QS the output changes to the following
10:32:06,353 INFO [STDOUT] { ================ After Order Priority
10:32:06,354 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60
10:32:06,354 INFO [STDOUT] Order Priority: 1
10:32:06,354 INFO [STDOUT] Order Discount: 0.0
10:32:06,354 INFO [STDOUT] Order Total: 44.92
10:32:06,354 INFO [STDOUT] } ================ After Order Priority
10:32:06,356 INFO [STDOUT] { ================ After Order Discount
10:32:06,356 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60
10:32:06,356 INFO [STDOUT] Order Priority: 1
10:32:06,356 INFO [STDOUT] Order Discount: 0.0
10:32:06,357 INFO [STDOUT] Order Total: 44.92
10:32:06,357 INFO [STDOUT] } ================ After Order Discount
This appears to be the output from the ReviewMessage actions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1051) jUDDI error in a transacted environment.
by Kevin Conner (JIRA)
jUDDI error in a transacted environment.
----------------------------------------
Key: JBESB-1051
URL: http://jira.jboss.com/jira/browse/JBESB-1051
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Blocker
Fix For: 4.2.1
Running jUDDI within a transacted environment results in the following exception being raised.
ERROR [STDERR] Caused by: java.lang.Exception: faultCode=null, faultString=You cannot commit during a managed transaction!, faultActor=null, errno=null, errCode=null, errText=null
ERROR [STDERR] at org.apache.juddi.registry.local.AbstractService.handleRequest(AbstractService.java:269)
ERROR [STDERR] at org.apache.juddi.registry.local.InquiryService.inquire(InquiryService.java:77)
The exception is raised when jUDDI attempts to issues commits on connections which are controlled by the encompassing transaction.
One path leading to this is FindTModelFunction->JDBCDataStore->Transaction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1059) JmsGatewayListener doesn't support JMS Topics
by Tom Cunningham (JIRA)
JmsGatewayListener doesn't support JMS Topics
---------------------------------------------
Key: JBESB-1059
URL: http://jira.jboss.com/jira/browse/JBESB-1059
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Message Store
Affects Versions: 4.2
Reporter: Tom Cunningham
Assigned To: Mark Little
Fix For: 4.2.1
Attachments: topic.tar.gz
It doesn't seem like JmsGatewayListener supports JMS Topics. Both bus and message filter support topics, but those don't seem to have any value if there's no listener.
Attached a small example program which can be run from within product/samples/quickstarts.
Here's the Exception that I get when trying to listen to a Topic :
11:07:55,607 INFO [quickstart_helloworld_Request_gw] Unbinding JNDI name: topic/quickstart_helloworld_Request_gw
11:07:55,611 INFO [quickstart_helloworld_Request_esb] Unbinding JNDI name: topic/quickstart_helloworld_Request_esb
11:07:55,710 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld.esb
11:07:55,732 INFO [quickstart_helloworld_Request_esb] Bound to JNDI name: topic/quickstart_helloworld_Request_esb
11:07:55,736 INFO [quickstart_helloworld_Request_gw] Bound to JNDI name: topic/quickstart_helloworld_Request_gw
11:07:55,894 INFO [JDBCDataStore] Generated token 'authToken:EF81D3B0-65F8-11DC-AA81-C454965D6D9A' for user: 'jbossesb/JBoss ESB User'
11:07:56,202 WARN [AbstractManagedLifecycle] Unexpected exception caught while initialisation
java.lang.ClassCastException: org.jboss.mq.SpyTopic
at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:367)
at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:102)
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:160)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:79)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:79)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
11:07:56,203 WARN [CourierFactory] Calling cleanup on existing couriers for identity LifecycleIdentity:16
11:07:56,207 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_helloworld.esb
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: java.lang.ClassCastException: org.jboss.mq.SpyTopic
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:145)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:160)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:79)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:79)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: java.lang.ClassCastException: org.jboss.mq.SpyTopic
at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:367)
at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:102)
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
... 51 more
11:07:56,246 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb
State: FAILED
Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: java.lang.ClassCastException: org.jboss.mq.SpyTopic
I Depend On:
jboss.esb.quickstart.destination:service=Topic,name=quickstart_helloworld_Request_esb
jboss.esb.quickstart.destination:service=Topic,name=quickstart_helloworld_Request_gw
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb
State: FAILED
Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: java.lang.ClassCastException: org.jboss.mq.SpyTopic
I Depend On:
jboss.esb.quickstart.destination:service=Topic,name=quickstart_helloworld_Request_esb
jboss.esb.quickstart.destination:service=Topic,name=quickstart_helloworld_Request_gw
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month