[jira] Updated: (GERONIMO-4257) Problem with processing and delivery jms messages
[ https://issues.apache.org/jira/browse/GERONIMO-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-4257: --- Priority: Critical (was: Major) Problem with processing and delivery jms messages - Key: GERONIMO-4257 URL: https://issues.apache.org/jira/browse/GERONIMO-4257 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, OpenEJB, transaction manager Affects Versions: 2.1.1, 2.1.2 Environment: Windows XPPro SP2, JDK 6 Reporter: Tomasz Mazan Priority: Critical I've found strange Geronimo 2.1.2 behaviour with using JMS. 1) When message is waiting for delivery to MDB i cannot undeploy module with this MDB from command line. I have to stop module via G-console and then undeploy 2) If messages are waiting for delivery and I shutdown server (geronimo stop) and the run it again none of messages are delivered to listener 3) When MDB onMessage method throws i.e. NullPointerException, the transaction is rolledback but a) message is not being redelivered anymore, b) module couldn't be restarted == application stops working :( Geronimo 2.1 hadn't these features. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-206) Error while deploying EAR to running server Geronimo 2.0.1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588972#action_12588972 ] Tomasz Mazan commented on GERONIMODEVTOOLS-206: --- Tim, I've just go back from short holidays. I'm able to retest it in a few days. Please, write if it's satisfying - if not, I'll close this issue with hope that's not present. Error while deploying EAR to running server Geronimo 2.0.1 -- Key: GERONIMODEVTOOLS-206 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 WTP 2.0 + GEP 2.0 Reporter: Tomasz Mazan Assignee: Tim McConnell Priority: Critical Fix For: 2.1.x Exception on deploy Distribution of configuration failed. See log for details. java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) org.apache.geronimo.common.DeploymentException: java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:121) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at org.apache.geronimo.deployment.util.DeploymentUtil.copyFile(DeploymentUtil.java:92) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:118) ... 34
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean delivery problem
[
https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525
]
beniamin edited comment on GERONIMO-3783 at 2/4/08 1:02 PM:
I've edited deployment plan and finally have RAs like below:
{noformat}
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageReceiversMDB/resourceadapter-name
config-property-setting
name=UseInboundSessiontrue/config-property-setting
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMRConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
/xa-transaction
single-pool
max-size20/max-size
blocking-timeout-milliseconds5000/blocking-timeout-milliseconds
select-one-assume-match/
/single-pool
/connectionmanager
/connectiondefinition-instance
/connection-definition
/outbound-resourceadapter
/resourceadapter
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageSender/resourceadapter-name
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMSConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
/xa-transaction
single-pool
max-size20/max-size
blocking-timeout-milliseconds5000/blocking-timeout-milliseconds
select-one-assume-match/
/single-pool
/connectionmanager
/connectiondefinition-instance
/connection-definition
/outbound-resourceadapter
/resourceadapter
{noformat}
It's not working if {{maxSessions}} not equals {{maxMessagesPerSessions}}
was (Author: beniamin):
I've edited deployment plan and finally have RAs like below:
pre
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageReceiversMDB/resourceadapter-name
config-property-setting
name=UseInboundSessiontrue/config-property-setting
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMRConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525 ] Tomasz Mazan commented on GERONIMO-3783: I've edited deployment plan and finally have RAs like below: resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter resourceadapter resourceadapter-instance resourceadapter-nameMessageSender/resourceadapter-name nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMSConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter It's not working if codemaxSessions/code not equals codemaxMessagesPerSessions/code MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525 ] beniamin edited comment on GERONIMO-3783 at 2/4/08 1:00 PM: I've edited deployment plan and finally have RAs like below: pre resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter resourceadapter resourceadapter-instance resourceadapter-nameMessageSender/resourceadapter-name nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMSConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter /pre It's not working if codemaxSessions/code not equals codemaxMessagesPerSessions/code was (Author: beniamin): I've edited deployment plan and finally have RAs like below: resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563136#action_12563136 ] Tomasz Mazan commented on GERONIMO-3783: I got exception when I try to set ThreadPool's attribute ipoolSize/i. I want to emphasize I use Geronimo 2.1-SNAPSHOT 14:06:48,968 WARN [ConfigurationUtil] Could not load gbean org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/jar?J2EEApplicatio n=null,ResourceAdapterModule=org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/jar,j2eeType=GBean,name=MRConnectorThreadPool org.apache.geronimo.gbean.InvalidConfigurationException: Could not inject configuration data into the GBean org.apache.geronimo.test.mdb/Mes sageReceiversDestinations/1.0/jar?J2EEApplication=null,ResourceAdapterModule=org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/j ar,j2eeType=GBean,name=MRConnectorThreadPool at org.apache.geronimo.gbean.runtime.GBeanInstance.init(GBeanInstance.java:375) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:433) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:515) 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:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor133.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalStateException: Attribute is not
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563154#action_12563154 ] Tomasz Mazan commented on GERONIMO-3783: Nonetheless exception above Setting maxSessions == maxMessagesPerSessions could avoid stop in processing messages MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562990#action_12562990 ] Tomasz Mazan commented on GERONIMO-3783: Thanks for your advice. I'll check that way ASAP. Please, give me the instruction how to provide enough threads to RA. How can I manage them ? MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562155#action_12562155 ] beniamin edited comment on GERONIMO-3783 at 1/25/08 2:25 PM: - Example to show my problem. Requirements: 1. installed Geronimo 2.1-snapshot 2. Ant 1.7.0 3. not to have Junit 3 on the classpath You need to: - edit build.properties file - run targets: - deploy - test / test-with-report was (Author: beniamin): Example to show my problem. Requirements: 1. installed Geronimo 2.1-snapshot You need to: - edit build.properties file - run targets: - deploy - test / test-with-report MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3783) MessageDrivenBean delivery problem
MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3783: --- Description: MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html was: MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3783: --- Attachment: mdb-issue.zip Example to show my problem. Requirements: 1. installed Geronimo 2.1-snapshot You need to: - edit build.properties file - run targets: - deploy - test / test-with-report MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3673) MessageDrivenBean injection issue
[ https://issues.apache.org/jira/browse/GERONIMO-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3673: --- Attachment: ejb-jar.xml MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3673) MessageDrivenBean injection issue
[ https://issues.apache.org/jira/browse/GERONIMO-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3673: --- Attachment: JmsRequestFeedbackBean.java MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3673) MessageDrivenBean injection issue
[ https://issues.apache.org/jira/browse/GERONIMO-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3673: --- Attachment: openejb-jar.xml MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3673) MessageDrivenBean injection issue
[ https://issues.apache.org/jira/browse/GERONIMO-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMO-3673: --- Attachment: metadata-complete-dd.xml MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3673) MessageDrivenBean injection issue
MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3673) MessageDrivenBean injection issue
[ https://issues.apache.org/jira/browse/GERONIMO-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548749 ] Tomasz Mazan commented on GERONIMO-3673: It looks like Geronimo-Eclipse integration issue. Eclipse: If I starts Geronimo (using Eclipse's run) with deployed application all is working fine. The problem appears if I redeploy (or undeploy + deploy) application. What could be important - I deploy EAR application containing JAR. If then I shutdown server and start it again, all is working Ant: If I deploy/undeploy/redeploy ejb.jar using ant task that uses geronimo deployer.jar all works fine. regards Beniamin MessageDrivenBean injection issue - Key: GERONIMO-3673 URL: https://issues.apache.org/jira/browse/GERONIMO-3673 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2 Reporter: Tomasz Mazan Attachments: ejb-jar.xml, JmsRequestFeedbackBean.java, metadata-complete-dd.xml, openejb-jar.xml I found problem with injecting Jms ConnectionFactory to my MDB, which needs it to send message to queue different to that it's listening to. During deployment I get only WARN in my logs: iWARN [OpenEJB] Injection data not found in enc: jndiName='DispatcherJmsXAConnectionFactory', target=class myapp.dispatcher.feedback.JmsRequestFeedbackBean/jmsConnFactory/i and during application's work NullPointerException when I try to access this jmsConnFactory property. With David Jenks we investingated strange form of metadata complete deployment descriptor. It indicates a kind of bug with deploying application regards Beniamin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Mazan resolved GERONIMO-3462.
Resolution: Invalid
It's not a bug. It's a feature ;-)
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
Assignee: Jarek Gawor
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean
encountered a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533777
]
Tomasz Mazan commented on GERONIMO-3462:
Sorry Jarek, but I haven't testet it yet. I will do it in a few days - I'm
overworked.
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
Assignee: Jarek Gawor
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean
encountered a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3503) DBPool wizzard creates plans only for local-transactions
DBPool wizzard creates plans only for local-transactions Key: GERONIMO-3503 URL: https://issues.apache.org/jira/browse/GERONIMO-3503 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Reporter: Tomasz Mazan Fix For: 2.0.2 I use DatabasePool Wizzard to deploy Pools for PostgresQL. In both cases - I choosed PostgreAQL XA or PostgreSQL Local - wizzard generated plan with model connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3504) Exception while generating WSDL
Exception while generating WSDL --- Key: GERONIMO-3504 URL: https://issues.apache.org/jira/browse/GERONIMO-3504 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: webservices Affects Versions: 2.0.2 Reporter: Tomasz Mazan I try to use jaxws-tools.bat wsgen to generate WSDL file from my web service (I've succesfully generated using com.sun.tools.ws.ant.WsGen included in Geronimo 2.0.1, but now I got exception [exec] Using GERONIMO_BASE: D:\SERVER\geronimo-tomcat [exec] Using GERONIMO_HOME: D:\SERVER\geronimo-tomcat [exec] Using GERONIMO_TMPDIR: var\temp [exec] Using JRE_HOME:C:\DEV\SDK\jdk1.5.0_09\jre [exec] Problem encountered during annotation processing; [exec] see stacktrace below for more information. [exec] java.lang.NullPointerException [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.isSubtype(WebServiceAP.java:416) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.isRemote(WebServiceAP.java:411) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalType(WebServiceVisitor.java:811) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalMethod(WebServiceVisitor.java:642) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.methodsAreLegal(WebServiceVisitor.java:622) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalImplementation(WebServiceVisitor.java:540) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.shouldProcessWebService(WebServiceVisitor.java:350) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitClassDeclaration(WebServiceVisitor.java:143) [exec] at com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.accept(ClassDeclarationImpl.java:95) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.buildModel(WebServiceAP.java:345) [exec] at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.process(WebServiceAP.java:230) [exec] at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:60) [exec] at com.sun.tools.apt.comp.Apt.main(Apt.java:454) [exec] at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:448) [exec] at com.sun.tools.apt.main.Main.compile(Main.java:1075) [exec] at com.sun.tools.apt.main.Main.compile(Main.java:938) [exec] at com.sun.tools.apt.Main.processing(Main.java:95) [exec] at com.sun.tools.apt.Main.process(Main.java:85) [exec] at com.sun.tools.apt.Main.process(Main.java:67) [exec] at com.sun.tools.ws.wscompile.CompileTool.buildModel(CompileTool.java:603) [exec] at com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:536) [exec] at com.sun.tools.ws.util.ToolBase.run(ToolBase.java:54) [exec] at com.sun.tools.ws.util.WSToolsObjectFactoryImpl.wsgen(WSToolsObjectFactoryImpl.java:42) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [exec] error: compilation failed, errors should have been reported [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:585) [exec] at org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:190) [exec] at org.apache.geronimo.jaxws.builder.JAXWSTools.invoke(JAXWSTools.java:174) [exec] at org.apache.geronimo.jaxws.builder.JAXWSTools.invokeWsgen(JAXWSTools.java:161) [exec] at org.apache.geronimo.jaxws.builder.JAXWSToolsCLI.main(JAXWSToolsCLI.java:64) [exec] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-223) J2EE module dependencies losting
J2EE module dependencies losting Key: GERONIMODEVTOOLS-223 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-223 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.1 Environment: Eclipse 3.3 + GEP (win32) Reporter: Tomasz Mazan I got J2EE project + 2 EJB projects. J2EE project has defined module dependencies - uses both of my ejb projects. From time to time it losts one of dependency and I have to set it again using project properties. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: testEJB.zip Attachment with project source, and build jar, which is successfully deployed on Geronimo 2.0.1 Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: (was: project views.jpg) Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: project view.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: deployed jar view.jpg Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: deployed jar view.jpg, deploying view.jpg, geronimo console view.jpg, project view.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: deploying view.jpg Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: deployed jar view.jpg, deploying view.jpg, geronimo console view.jpg, project view.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: geronimo console view.jpg Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: deployed jar view.jpg, deploying view.jpg, geronimo console view.jpg, project view.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Mazan updated GERONIMODEVTOOLS-214: -- Attachment: screenshot-1.jpg Project development view Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: screenshot-1.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529532 ] Tomasz Mazan commented on GERONIMODEVTOOLS-214: --- Kan, The same exepcion got my workmate - using eclipse for Linux (I use win32 version). But - as I understand - it indicates, that Eclipse has sent application to Geronimo. In my environment there's no any visibile activity. Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan Assignee: Tim McConnell Attachments: deployed jar view.jpg, deploying view.jpg, geronimo console view.jpg, project view.jpg, testEJB.zip When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-215) Does not work right-clik's option Remove to remove project from Server (Servers View)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528679 ] Tomasz Mazan commented on GERONIMODEVTOOLS-215: --- Tim, thanks for your reply. Steps are quite simplier: 1. Deploy ejb.jar xor app.ear 2. Try to click on module and remove - no effect 3. Click on server - Add and remove projects - and here Remove - working Does not work right-clik's option Remove to remove project from Server (Servers View) - Key: GERONIMODEVTOOLS-215 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan Assignee: Tim McConnell Hi Tomasz, Sorry to be so dense but I'm missing something obvious. Are you able/willing to provide the artifacts that is causing the failure for you ?? If not, are these the correct steps that is causing the failure (so I can try to reproduce) ?? 1. Deploy your first ejb.jar 2. Deploy your ear, which contains other ejb.jar files 3. Then I assume you're attempting to undeploy the ear that was deployed in Step 2 ?? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-215) Does not work right-clik's option Remove to remove project from Server (Servers View)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528698 ] Tomasz Mazan commented on GERONIMODEVTOOLS-215: --- I would have to create the new one. I can't publish our bisness application ;-) I hope you understand Does not work right-clik's option Remove to remove project from Server (Servers View) - Key: GERONIMODEVTOOLS-215 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan Assignee: Tim McConnell Hi Tomasz, Sorry to be so dense but I'm missing something obvious. Are you able/willing to provide the artifacts that is causing the failure for you ?? If not, are these the correct steps that is causing the failure (so I can try to reproduce) ?? 1. Deploy your first ejb.jar 2. Deploy your ear, which contains other ejb.jar files 3. Then I assume you're attempting to undeploy the ear that was deployed in Step 2 ?? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-215) Does not work right-clik's option Remove to remove project from Server (Servers View)
Does not work right-clik's option Remove to remove project from Server (Servers View) - Key: GERONIMODEVTOOLS-215 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-215) Does not work right-clik's option Remove to remove project from Server (Servers View)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528367 ] Tomasz Mazan commented on GERONIMODEVTOOLS-215: --- It concerns running: ear-application (that contains ejb-jars) and ejb.jar module (deployed independently) Does not work right-clik's option Remove to remove project from Server (Servers View) - Key: GERONIMODEVTOOLS-215 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-215 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-214) Fictional deployment of EJB-JAR
Fictional deployment of EJB-JAR --- Key: GERONIMODEVTOOLS-214 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-214 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Geronimo 2.0.1 Reporter: Tomasz Mazan When I'm deploying my EJB project, Server Views shows it as deployed, but there no any activity trail on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-206) Error while deploying EAR to running server Geronimo 2.0.1
Error while deploying EAR to running server Geronimo 2.0.1 -- Key: GERONIMODEVTOOLS-206 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Geronimo 2.0.1 WTP 2.0 + GEP 2.0 Reporter: Tomasz Mazan Exception on deploy Distribution of configuration failed. See log for details. java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) org.apache.geronimo.common.DeploymentException: java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:121) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.FileNotFoundException: C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip (File not found) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at org.apache.geronimo.deployment.util.DeploymentUtil.copyFile(DeploymentUtil.java:92) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:118) ... 34 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-200) javax.xml.soap not included in geronimo runtime library
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526716 ] Tomasz Mazan commented on GERONIMODEVTOOLS-200: --- Thanks for quick patch. Works fine. javax.xml.soap not included in geronimo runtime library --- Key: GERONIMODEVTOOLS-200 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-200 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan Assignee: Tim McConnell Fix For: 2.0 javax.xml.soap not included in geronimo runtime library by default. User have to import single jar to project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526626
]
Tomasz Mazan commented on GERONIMO-3462:
Jarek
Thanks for your instruction. I'll try to implement your advices and reply with
test's result.
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
Assignee: Jarek Gawor
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean
encountered a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-199) javax.xml.bind is not included in server runtime library
javax.xml.bind is not included in server runtime library Key: GERONIMODEVTOOLS-199 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-199 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan JAX-B classes/annotation are not included in default Geronimo's server runtime so user must include single jar to use i.e. XmlElement to annotate classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-200) javax.xml.soap not included in geronimo runtime library
javax.xml.soap not included in geronimo runtime library --- Key: GERONIMODEVTOOLS-200 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-200 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Tomasz Mazan javax.xml.soap not included in geronimo runtime library by default. User have to import single jar to project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
Problem with throwing SOAPFaultException within WebService based on SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
I create SOAPFaultException using code below:
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
and my WebMethod returns this exception in case internal exception:
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
and client catches fault with attributes:
[faultstring]=
string(298) java.rmi.RemoteException: The bean encountered a non-application
exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean
encountered a non-application exception.; nested exception i
s:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]=
string(11) soap:Server
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Mazan updated GERONIMO-3462:
---
Description:
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean encountered
a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
was:
I create SOAPFaultException using code below:
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
and my WebMethod returns this exception in case internal exception:
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
and client catches fault with attributes:
[faultstring]=
string(298) java.rmi.RemoteException: The bean encountered a non-application
exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean
encountered a non-application exception.; nested exception i
s:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]=
string(11) soap:Server
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new
[jira] Commented: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526265
]
Tomasz Mazan commented on GERONIMO-3462:
Jarek
1) According to jax-ws spec (JSR-000224) point 10.2.2.3 faultcode is correct.
Faultstring is wrapped in exception classname etc. - opposite to my
expectations.
3) My client is a php script so I'm wondering why there's
java.rmi.RemoteException
Thanks
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
Assignee: Jarek Gawor
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean
encountered a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3462) Problem with throwing SOAPFaultException within WebService based on SessionBean
[
https://issues.apache.org/jira/browse/GERONIMO-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526288
]
Tomasz Mazan commented on GERONIMO-3462:
PHP script calls my function
part of wsdl:
{noformat}
wsdl:operation name=createCustomer
wsdl:input message=ns1:createCustomer name=createCustomer
/wsdl:input
wsdl:output message=ns1:createCustomerResponse
name=createCustomerResponse
/wsdl:output
wsdl:fault message=ns1:SOAPFaultException name=SOAPFaultException
/wsdl:fault
/wsdl:operation
xs:complexType name=SOAPFaultException
xs:sequence
xs:element name=faultcode nillable=true type=xs:QName/
xs:element name=faultstring nillable=true type=xs:string/
xs:element name=faultactor nillable=true type=xs:string/
xs:element name=message nillable=true type=xs:string/
/xs:sequence
/xs:complexType
{noformat}
and php code looks like
{noformat}
$soapClient = new
SoapClient(http://localhost:8080/MyApp/MyService?wsdl;, array(exceptions =
true));
$temp = $soapClient - createCustomer(array(identifier =
$argv[1]))-return;
{noformat}
Problem with throwing SOAPFaultException within WebService based on
SessionBean
Key: GERONIMO-3462
URL: https://issues.apache.org/jira/browse/GERONIMO-3462
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0.1
Environment: ApacheCXF as service provider
Reporter: Tomasz Mazan
Assignee: Jarek Gawor
I create SOAPFaultException using code below:
{noformat}
public SOAPFaultException createFault(String errorCode, String
errorString) {
SOAPFault fault = null;
try {
fault = SOAPFactory.newInstance().createFault();
fault.setFaultCode(new QName(foo, bar, abc));
fault.setFaultString(errorString);
fault.setFaultActor(ACTOR);
} catch (SOAPException ex) {
return new SOAPFaultException(null);
}
return new SOAPFaultException(fault);
}
{noformat}
and my WebMethod returns this exception in case internal exception:
{noformat}
@WebService(serviceName = MyService, portName = CustomerServices)
@Stateless(name = MyCustomerService)
public class MyCustomerService {
@EJB
private CoreManager coreManager = null;
public MyCustomerService() {
}
@WebMethod(operationName = createCustomer)
public Customer createCustomer(@WebParam(name = identifier) String
identifier) throws SOAPFaultException {
try {
return this.coreManager.createCustomer(identifier);
} catch (ServiceException e) {
throw this.faultService.createFault(FAULT CODE,
FAULT STRING);
}
}
}
{noformat}
and client catches fault with attributes:
{noformat}
[faultstring]= string(298) java.rmi.RemoteException: The bean
encountered a non-application exception.; nested exception is:
javax.xml.ws.soap.SOAPFaultException: FAULT STRING: The bean encountered a
non-application exception.; nested exception i
s: javax.xml.ws.soap.SOAPFaultException: FAULT STRING
[faultcode]= string(11) soap:Server
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
