Nabble - NetBeans - EntPack

Extend nb6.1 BPEL editor with new activities

2009-07-30T01:04:16Z

Hello,

I received your answer, but I think that it is now what I need. I am
referring to this project:

http://markmail.org/message/2vo6iia4odlhkasv
http://wiki.open-esb.java.net/Wiki.jsp?page=ExtendingNetBeansBPELEditorWithYourNewActivities

I would like to continue with it because I also have to customize the
palette with new activities. That project is still in early state of
develop and I am wondering if there is available some newer version.

I think that doing it with the plug-in is a good idea but I need help to
start.

Thank you,

Gabriel.

Re: Extend NB6.1 BPEL Editor with new activities.

2009-07-21T07:22:03Z

Please take a look at:
http://wikihome.sfbay.sun.com/swi-syseng/Wiki.jsp?page=SoaDev65

Thanks,
Sergey

Juan Gabriel Carrera Otero wrote:

>
> Hello,
>
> I am interested in continuing this project. I need to add customized
> elements to the BPEL palette. If you had a earlier version of the
> sample code, I would like to take a look on it. Are there advances?
>
> Thank you
>
> Gabriel.
>

Extend NB6.1 BPEL Editor with new activities.

2009-07-21T07:08:51Z

Hello,

I am interested in continuing this project. I need to add customized
elements to the BPEL palette. If you had a earlier version of the sample
code, I would like to take a look on it. Are there advances?

Thank you

Gabriel.

Re: BPEL and web services not deploying together

2009-07-08T12:30:10Z

It looks like you do not have enough free memory on the system, please try without changing -XX:MaxPermSize
Only do <jvm-options>-Xmx512m</jvm-options> to <jvm-options>-Xmx1024m</jvm-options>

Regards
Murali

Agrawal, Vikas IN BLR SISL wrote:

Hello All,

I have some web services deployed in Glassfish v2. Now I have created one BPEL with HL7 binding component (BC) in Netbeans 6.5 but not able to deploy the BPEL in the same server (Glassfish v2) but if I undeploy web services and then deploy the BPEL then it works fine. The error I am getting is related to java heap space error.

I have tried with modifying some jvm-options in <domain.xml> file (glassfish\domains\domain1\config) but in this case Glassfish not even able to start. The changes I have tried are –

<jvm-options>-XX:MaxPermSize=192m</jvm-options> to <jvm-options>-XX:MaxPermSize=1024m</jvm-options>
and, <jvm-options>-Xmx512m</jvm-options> to <jvm-options>-Xmx1024m</jvm-options>

Please suggest some solution.

With Best Regards,

Vikas Kumar Agrawal

Siemens IT Solutions & Services (SIS)

CTDC-TEC

#39, #41, #42

Salarpuria Infozone, Block B, Keonics Electronic City

Hosur Road, Bangalore

Ph :- 080-67115884

mailto: vikaskumar.agrawal@...

www.siemens.co.in

Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system.
Thank You.

Re: Regarding BPEL debugger plugin

2009-07-07T06:54:47Z

This depends on whether you're interested in the run time part of it, or the
design
time. If you feel like starting from the design time, start from [1].

[1] bpel.debugger/src/org/netbeans/modules/bpel/debugger/BpelDebuggerImpl.java

Kirill

On 7/5/09 5:06 PM, Denis Weerasiri wrote:
> Hi all,
> I'm interested in the BPEL debugger plug-in implementation. Can anybody
> tell me what base classes I should refer to get an basic idea on how it
> works.
>
> Cheers,
> Denis

BPEL and web services not deploying together

2009-07-07T01:34:45Z

Hello All,

I have some web services deployed in Glassfish v2. Now I have created one BPEL with HL7 binding component (BC) in Netbeans 6.5 but not able to deploy the BPEL in the same server (Glassfish v2) but if I undeploy web services and then deploy the BPEL then it works fine. The error I am getting is related to java heap space error.

I have tried with modifying some jvm-options in <domain.xml> file (glassfish\domains\domain1\config) but in this case Glassfish not even able to start. The changes I have tried are –

<jvm-options>-XX:MaxPermSize=192m</jvm-options> to <jvm-options>-XX:MaxPermSize=1024m</jvm-options>
and, <jvm-options>-Xmx512m</jvm-options> to <jvm-options>-Xmx1024m</jvm-options>

Please suggest some solution.

With Best Regards,

Vikas Kumar Agrawal

Siemens IT Solutions & Services (SIS)

CTDC-TEC

#39, #41, #42

Salarpuria Infozone, Block B, Keonics Electronic City

Hosur Road, Bangalore

Ph :- 080-67115884

mailto: vikaskumar.agrawal@...

www.siemens.co.in

Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system.
Thank You.

Regarding BPEL debugger plugin

2009-07-05T06:06:10Z

Hi all,
I'm interested in the BPEL debugger plug-in implementation. Can anybody tell me what base classes I should refer to get an basic idea on how it works.

Cheers,
Denis

Re: Unit Testing a BPEL via SSL

2009-05-27T08:07:09Z

I'll look into that, thanks. And by the way curl does work also. It's too bad soapUI has trouble, our QA people like to use it.

Jason Baragry-2 wrote:

I did it in the CASA editor.

The WSDL you create for your bpel projects results in two service units
in the CASA editor. One for the BPEL and one for the SOAP binding.

Can u see that part?

rgds
J

jsexton0 wrote:
> Hello - Could you tell me a little more about the solution you used? Did
> you do that by creating a new HTTP listener that forwards? Or by adding a
> non-SSL WSDL to a BPEL?
>
> Thanks
>
>
> Jason Baragry-2 wrote:
>
>> I tried this once and had the same issues. The built in soap unit-tester
>> doesn't support https and I couldn't get soapui to use my certificates.
>>
>> I found two approaches.
>> - use curl which has good certificate support. (I haven't tried it)
>> - add a new HTTP BC SU that does BC to BC communication. It should be
>> configured to accept external http requests and pass https msgs to your
>> HTTP BC SU that provides the https interface for your bpel. This worked
>> for me.
>>
>> rgds
>> J
>>
>> jsexton0 wrote:
>>
>>> Is in possible to create a test in Netbeans for a WSDL accessed via
>>> https?
>>>
>>> I have a working BPEL, to which I added a new WSDL having an https
>>> address
>>> at port 9181. I can retrieve the WSDL with Firefox, and I can create a
>>> new
>>> test in the SA project. However when I run the test, it fails to get
>>> into
>>> the BPEL:
>>>
>>> May 22, 2009 12:40:29 PM
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
>>> SEVERE: SAAJ0009: Message send failed
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl:
>>> java.security.PrivilegedActionException:
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
>>> ...
>>> Caused by: java.security.PrivilegedActionException:
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
>>> ... 3 more
>>> Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send
>>> failed
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
>>> ... 5 more
>>> Caused by: javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>>> find
>>> valid certification path to requested target
>>> at
>>> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
>>>
>>> I tried using SoapUI but there's a simular problem there I guess.
>>>
>>> Is there a way to test the BPEL via https from Netbeans, SoapUI or any
>>> other
>>> tool? Thank you
>>>
>>>
>> --
>> <http://www.java.com> * Jason Baragry *
>> Senior Solution Architect
>> Software Practice
>> *Sun Microsystems, Inc.*
>> Central & Northern Europe
>> Phone x43697/+47-23-369 697
>> Mobile +47 4899 4603
>> Email Jason.Baragry@Sun.COM
>> <http://www.java.com>
>>
>>
>>
>>
>
>

--
<http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@Sun.COM
<http://www.java.com>

Re: Unit Testing a BPEL via SSL

2009-05-27T08:00:27Z

I did it in the CASA editor.

The WSDL you create for your bpel projects results in two service units
in the CASA editor. One for the BPEL and one for the SOAP binding.

Can u see that part?

rgds
J

jsexton0 wrote:

> Hello - Could you tell me a little more about the solution you used? Did
> you do that by creating a new HTTP listener that forwards? Or by adding a
> non-SSL WSDL to a BPEL?
>
> Thanks
>
>
> Jason Baragry-2 wrote:
>
>> I tried this once and had the same issues. The built in soap unit-tester
>> doesn't support https and I couldn't get soapui to use my certificates.
>>
>> I found two approaches.
>> - use curl which has good certificate support. (I haven't tried it)
>> - add a new HTTP BC SU that does BC to BC communication. It should be
>> configured to accept external http requests and pass https msgs to your
>> HTTP BC SU that provides the https interface for your bpel. This worked
>> for me.
>>
>> rgds
>> J
>>
>> jsexton0 wrote:
>>
>>> Is in possible to create a test in Netbeans for a WSDL accessed via
>>> https?
>>>
>>> I have a working BPEL, to which I added a new WSDL having an https
>>> address
>>> at port 9181. I can retrieve the WSDL with Firefox, and I can create a
>>> new
>>> test in the SA project. However when I run the test, it fails to get
>>> into
>>> the BPEL:
>>>
>>> May 22, 2009 12:40:29 PM
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
>>> SEVERE: SAAJ0009: Message send failed
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl:
>>> java.security.PrivilegedActionException:
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
>>> ...
>>> Caused by: java.security.PrivilegedActionException:
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
>>> ... 3 more
>>> Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send
>>> failed
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
>>> at
>>> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
>>> ... 5 more
>>> Caused by: javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>>> find
>>> valid certification path to requested target
>>> at
>>> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
>>>
>>> I tried using SoapUI but there's a simular problem there I guess.
>>>
>>> Is there a way to test the BPEL via https from Netbeans, SoapUI or any
>>> other
>>> tool? Thank you
>>>
>>>
>> --
>> <http://www.java.com> * Jason Baragry *
>> Senior Solution Architect
>> Software Practice
>> *Sun Microsystems, Inc.*
>> Central & Northern Europe
>> Phone x43697/+47-23-369 697
>> Mobile +47 4899 4603
>> Email Jason.Baragry@...
>> <http://www.java.com>
>>
>>
>>
>>
>
>

--
<http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@...
<http://www.java.com>

Re: Unit Testing a BPEL via SSL

2009-05-26T08:11:33Z

Hello - Could you tell me a little more about the solution you used? Did you do that by creating a new HTTP listener that forwards? Or by adding a non-SSL WSDL to a BPEL?

Thanks

Jason Baragry-2 wrote:

I tried this once and had the same issues. The built in soap unit-tester
doesn't support https and I couldn't get soapui to use my certificates.

I found two approaches.
- use curl which has good certificate support. (I haven't tried it)
- add a new HTTP BC SU that does BC to BC communication. It should be
configured to accept external http requests and pass https msgs to your
HTTP BC SU that provides the https interface for your bpel. This worked
for me.

rgds
J

jsexton0 wrote:
> Is in possible to create a test in Netbeans for a WSDL accessed via https?
>
> I have a working BPEL, to which I added a new WSDL having an https address
> at port 9181. I can retrieve the WSDL with Firefox, and I can create a new
> test in the SA project. However when I run the test, it fails to get into
> the BPEL:
>
> May 22, 2009 12:40:29 PM
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
> SEVERE: SAAJ0009: Message send failed
> com.sun.xml.messaging.saaj.SOAPExceptionImpl:
> java.security.PrivilegedActionException:
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
> ...
> Caused by: java.security.PrivilegedActionException:
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at java.security.AccessController.doPrivileged(Native Method)
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
> ... 3 more
> Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
> ... 5 more
> Caused by: javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at
> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
>
> I tried using SoapUI but there's a simular problem there I guess.
>
> Is there a way to test the BPEL via https from Netbeans, SoapUI or any other
> tool? Thank you
>

--
<http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@Sun.COM
<http://www.java.com>

Re: Unit Testing a BPEL via SSL

2009-05-24T02:24:22Z

I tried this once and had the same issues. The built in soap unit-tester
doesn't support https and I couldn't get soapui to use my certificates.

I found two approaches.
- use curl which has good certificate support. (I haven't tried it)
- add a new HTTP BC SU that does BC to BC communication. It should be
configured to accept external http requests and pass https msgs to your
HTTP BC SU that provides the https interface for your bpel. This worked
for me.

rgds
J

jsexton0 wrote:

> Is in possible to create a test in Netbeans for a WSDL accessed via https?
>
> I have a working BPEL, to which I added a new WSDL having an https address
> at port 9181. I can retrieve the WSDL with Firefox, and I can create a new
> test in the SA project. However when I run the test, it fails to get into
> the BPEL:
>
> May 22, 2009 12:40:29 PM
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
> SEVERE: SAAJ0009: Message send failed
> com.sun.xml.messaging.saaj.SOAPExceptionImpl:
> java.security.PrivilegedActionException:
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
> ...
> Caused by: java.security.PrivilegedActionException:
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at java.security.AccessController.doPrivileged(Native Method)
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
> ... 3 more
> Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
> at
> com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
> ... 5 more
> Caused by: javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at
> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
>
> I tried using SoapUI but there's a simular problem there I guess.
>
> Is there a way to test the BPEL via https from Netbeans, SoapUI or any other
> tool? Thank you
>

Unit Testing a BPEL via SSL

2009-05-22T13:25:29Z

Is in possible to create a test in Netbeans for a WSDL accessed via https?

I have a working BPEL, to which I added a new WSDL having an https address at port 9181. I can retrieve the WSDL with Firefox, and I can create a new test in the SA project. However when I run the test, it fails to get into the BPEL:

May 22, 2009 12:40:29 PM com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
SEVERE: SAAJ0009: Message send failed
com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
...
Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
... 3 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
... 5 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)

I tried using SoapUI but there's a simular problem there I guess.

Is there a way to test the BPEL via https from Netbeans, SoapUI or any other tool? Thank you

Unit Testing a BPEL via SSL

2009-05-22T13:16:02Z

Is in possible to create a test in Netbeans for a WSDL accessed via https?

I have a working BPEL, to which I added a new WSDL which has an https address at port 9181. I can retrieve the WSDL with Firefox, and I can create a new test in the SA project. However when I run the test, it fails to hit the BPEL:

May 22, 2009 12:40:29 PM com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
SEVERE: SAAJ0009: Message send failed
com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:146)
...
Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
... 3 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:344)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
... 5 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)

I tried using SoapUI but there's a simular problem there I guess.

Is there a way to test the BPEL via https from Netbeans (or any other tool)? Thank you

Re: SSL Inside a BPEL?

2009-05-22T10:09:56Z

I looked at the casa editor for this assembly and found that the BPEL was not directly connected to the EJB. It looks like it was in fact using, or trying to use, https even though the units were altogether. It also did not like me trying to change those connections. It complained that the types were not correct.

I'm going to just recreate the WSDL and EJB in question, and I suspect it will behave. All I was looking for right now is confirmation that the EJB invocation is not subject to the transport security when invoked through the NMR, and you've answered that question. Thanks!

Jason Baragry-2 wrote:

AFAIK, the EJB should not be enforcing a transport level security option
if the communication is happening over the NMR.
However, as detailed in the 2nd link I sent, the JavaEE Service Engine
isn't like other engines. Its really a bridge between the JBI container
and the Web/EJB containers in Glassfish. That bridge makes use of HTTP
pieces in Glassfish to implement the JAX-WS pieces necessary to provide
and consume webservice interfaces. It may be that those pieces are
enforcing some SSL implementation that it shouldn't be in your scenario.

This is going beyond my knowledge of how the JavaEE SE is implemented. I
suggest you ask on users@openesb so that one of the engineers can comment.

rgds
Jason

--
<http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@Sun.COM
<http://www.java.com>

Re: SSL Inside a BPEL?

2009-05-22T09:55:44Z

AFAIK, the EJB should not be enforcing a transport level security option
if the communication is happening over the NMR.
However, as detailed in the 2nd link I sent, the JavaEE Service Engine
isn't like other engines. Its really a bridge between the JBI container
and the Web/EJB containers in Glassfish. That bridge makes use of HTTP
pieces in Glassfish to implement the JAX-WS pieces necessary to provide
and consume webservice interfaces. It may be that those pieces are
enforcing some SSL implementation that it shouldn't be in your scenario.

This is going beyond my knowledge of how the JavaEE SE is implemented. I
suggest you ask on users@openesb so that one of the engineers can comment.

rgds
Jason

jsexton0 wrote:

> I have seen those posts, and they are helpful, thanks. But that is what lead
> me to ask the question. I get the exception even though the EJB is in the
> same service assemble as the BPEL that call it. I did not expect that.
>
> Thanks
>
>
> Jason Baragry-2 wrote:
>
>> First, I think you will get more answers on the users@openesb mailing
>> list.
>>
>> OpenESB is a JBI compliant infrastructure. That means there is a
>> difference between Service Engines that provide functionality (like the
>> BPEL engine) and Binding Components that provide connectivity (like the
>> SOAP/HTTP BC).
>>
>> In this infrastructure, the BPEL engine does not talk directly to the
>> EJB, the communication goes via a SOAP/HTTP Binding Component. So if you
>> want to use SSL transport between BPEL and an EJB then you need to
>> configure SSL in the SOAP/HTTP BC that BPEL uses to communicate over the
>> wire to the EJB.
>>
>> See:
>> http://wiki.open-esb.java.net/Wiki.jsp?page=CommonUserScenariosForHTTPBindingComponent
>>
>> However, there is another issue you need to consider. If the BPEL
>> component and the EJB are included in the same service assembly
>> (composite application) then the infrastructure routes the communication
>> within the JVM - i.e., it doesn't go over the wire. In this case its not
>> possible to use SSL because there is no over-the-wire transport involved.
>>
>> This is partially described here:
>> http://blogs.sun.com/jason/entry/removing_the_default_soap_binding
>>
>> hth
>> Jason
>>
>> jsexton0 wrote:
>>
>>> Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working
>>> with
>>> a BPEL that includes an invocation of an EJB. The BPEL and the EJB are
>>> deployed in the same SA. I changed the EJB to use HTTPS, which seemed to
>>> work. The invocation of the BPEL is through a normal HTTP SOAP request.
>>> When the BPEL comes to the invoke element to the now secure EJB WSDL, I
>>> get
>>> an exception:
>>>
>>> javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No
>>> Security header in message
>>>
>>> Is this normal? The BPEL can not invoke an EJB through HTTPS even
>>> internally, and even though the EJB is in the same SA?
>>>
>>> Thanks
>>>
>>>
>> --
>> <http://www.java.com> * Jason Baragry *
>> Senior Solution Architect
>> Software Practice
>> *Sun Microsystems, Inc.*
>> Central & Northern Europe
>> Phone x43697/+47-23-369 697
>> Mobile +47 4899 4603
>> Email Jason.Baragry@...
>> <http://www.java.com>
>>
>>
>>
>>
>
>

Re: SSL Inside a BPEL?

2009-05-22T06:57:12Z

I have seen those posts, and they are helpful, thanks. But that is what lead me to ask the question. I get the exception even though the EJB is in the same service assemble as the BPEL that call it. I did not expect that.

Thanks

Jason Baragry-2 wrote:

First, I think you will get more answers on the users@openesb mailing list.

OpenESB is a JBI compliant infrastructure. That means there is a
difference between Service Engines that provide functionality (like the
BPEL engine) and Binding Components that provide connectivity (like the
SOAP/HTTP BC).

In this infrastructure, the BPEL engine does not talk directly to the
EJB, the communication goes via a SOAP/HTTP Binding Component. So if you
want to use SSL transport between BPEL and an EJB then you need to
configure SSL in the SOAP/HTTP BC that BPEL uses to communicate over the
wire to the EJB.

See:
http://wiki.open-esb.java.net/Wiki.jsp?page=CommonUserScenariosForHTTPBindingComponent

However, there is another issue you need to consider. If the BPEL
component and the EJB are included in the same service assembly
(composite application) then the infrastructure routes the communication
within the JVM - i.e., it doesn't go over the wire. In this case its not
possible to use SSL because there is no over-the-wire transport involved.

This is partially described here:
http://blogs.sun.com/jason/entry/removing_the_default_soap_binding

hth
Jason

jsexton0 wrote:
> Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working with
> a BPEL that includes an invocation of an EJB. The BPEL and the EJB are
> deployed in the same SA. I changed the EJB to use HTTPS, which seemed to
> work. The invocation of the BPEL is through a normal HTTP SOAP request.
> When the BPEL comes to the invoke element to the now secure EJB WSDL, I get
> an exception:
>
> javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No
> Security header in message
>
> Is this normal? The BPEL can not invoke an EJB through HTTPS even
> internally, and even though the EJB is in the same SA?
>
> Thanks
>

--
<http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@Sun.COM
<http://www.java.com>

Re: SSL Inside a BPEL?

2009-05-22T05:53:48Z

I appreciate this post (blog) as well.....

http://blogs.sun.com/jason/entry/constraints_on_bpel_correlation_in

However, if you include the Asynchronous Service in the same Service Assembly (aka Composite Application) as the BPEL process, then the process fails to continue executing. In fact, the entire process waits endlessly. To understand why this occurs you need to look a bit deeper at what is happening under the covers in the JBI infrastructure.

Thanks Jason!

On Thu, May 21, 2009 at 4:43 PM, jsexton0 <jsexton0@...> wrote:

Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working with
a BPEL that includes an invocation of an EJB. The BPEL and the EJB are
deployed in the same SA. I changed the EJB to use HTTPS, which seemed to
work. The invocation of the BPEL is through a normal HTTP SOAP request.
When the BPEL comes to the invoke element to the now secure EJB WSDL, I get
an exception:

javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No
Security header in message

Is this normal? The BPEL can not invoke an EJB through HTTPS even
internally, and even though the EJB is in the same SA?

Thanks
--
View this message in context: http://www.nabble.com/SSL-Inside-a-BPEL--tp23660135p23660135.html
Sent from the NetBeans - EntPack mailing list archive at Nabble.com.

looking for accessible name for frame that netbeans created

2009-05-22T05:23:57Z

---------- Forwarded message ----------
From: Ali Asghar Toraby Parizy <aliasghar.toraby@...>
Date: Mon, May 18, 2009 at 10:10 PM
Subject: looking for accessible name for frame that netbeans created
To: nbentpack@...

hi. how can i access to a frame that netbeans GUI builder created?
this is a coded that netbeans generated:

public void run() {
new CelsiusConverterGUI().setVisible(true);
}

i dont know what is the name of frame object!! how can i access to this object?

Re: SSL Inside a BPEL?

2009-05-22T01:36:52Z

First, I think you will get more answers on the users@openesb mailing list.

OpenESB is a JBI compliant infrastructure. That means there is a
difference between Service Engines that provide functionality (like the
BPEL engine) and Binding Components that provide connectivity (like the
SOAP/HTTP BC).

In this infrastructure, the BPEL engine does not talk directly to the
EJB, the communication goes via a SOAP/HTTP Binding Component. So if you
want to use SSL transport between BPEL and an EJB then you need to
configure SSL in the SOAP/HTTP BC that BPEL uses to communicate over the
wire to the EJB.

See:
http://wiki.open-esb.java.net/Wiki.jsp?page=CommonUserScenariosForHTTPBindingComponent

However, there is another issue you need to consider. If the BPEL
component and the EJB are included in the same service assembly
(composite application) then the infrastructure routes the communication
within the JVM - i.e., it doesn't go over the wire. In this case its not
possible to use SSL because there is no over-the-wire transport involved.

This is partially described here:
http://blogs.sun.com/jason/entry/removing_the_default_soap_binding

hth
Jason

jsexton0 wrote:

> Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working with
> a BPEL that includes an invocation of an EJB. The BPEL and the EJB are
> deployed in the same SA. I changed the EJB to use HTTPS, which seemed to
> work. The invocation of the BPEL is through a normal HTTP SOAP request.
> When the BPEL comes to the invoke element to the now secure EJB WSDL, I get
> an exception:
>
> javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No
> Security header in message
>
> Is this normal? The BPEL can not invoke an EJB through HTTPS even
> internally, and even though the EJB is in the same SA?
>
> Thanks
>

SSL Inside a BPEL?

2009-05-21T13:42:58Z

Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working with a BPEL that includes an invocation of an EJB. The BPEL and the EJB are deployed in the same SA. I changed the EJB to use HTTPS, which seemed to work. The invocation of the BPEL is through a normal HTTP SOAP request. When the BPEL comes to the invoke element to the now secure EJB WSDL, I get an exception:

javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No Security header in message

Is this normal? The BPEL can not invoke an EJB through HTTPS even internally, and even though the EJB is in the same SA?

Thanks

Re: BPEL validation from a command line can not find the WSDLs

2009-05-18T10:55:59Z

Not quite it seems. It looks like it does this, but when I removed lines from catalog.xml the build process from the IDE still had no trouble on the two java steps. It only fails later in the process at the end when trying to build the actual dist files. The catalog.xml is indeed used at that later step (and in fact that part also works from outside the IDE).

How those two classes locate the files is a mystery, however, when doing the validation and copying files into the build directory. I could grep no other reference to those location tags anywhere in the project.

Kirill Sorokin wrote:

Well, the build process per se relies heavily on the data found in
catalog.xml, which
is located @ the root of the file hierarchy of the project. It is used, for
example, to turn
these AAA/xxx.wsdl entries into sensible file paths.

On 5/18/09 8:24 AM, jsexton0 wrote:
> There appears to be a great deal of mystery surrounding the build process.
> I'll include here a few more details for other that may be interested, but
> it appears that a headless build is not possible or practical at this time.
>
> First of all, the information found here:
> http://blogs.sun.com/tronds/entry/creating_a_simple_headless_build
> is vital to even getting started with regard to the build environment. That
> setup may be enough for most projects, or at least projects other than BPEL
> projects that refer to WSDLs in other projects.
>
> The nature of the "location" clause of an import in a BPEL file is unknown.
> It is not a file path, nor does using "file://" work. The build process
> somehow knows where to look for "AAA" when the location tag is
> "AAA/BBB.wsdl", even when the target is in some completely different project
> and hierarchy on the machine. I have been unable to determine how this
> happens - ie, how "AAA/BBB.wsdl" is mapped to a physical file.
>
> This magic occurs in at least two classes invoked by the build process:
>
> org.netbeans.modules.bpel.project.anttasks.cli.CliValidateBpelProjectTask
> org.netbeans.modules.bpel.project.anttasks.cli.CliGenerateCatalogTask
>
> Somehow, inside the GUI only, these classes can map the location tags to
> physical files and find thus the WSDLs required. GUI-only builds is a very
> surprising limitation, but there it is. I anyone has anyother information
> on this, I'd very much like to hear about it. It seems we will have to
> replace the build scripts for our projects.
>
>
> jsexton0 wrote:
>> Hello -
>>
>> When a WSDL from a separate project is included in a BPEL, the<import>
>> tag's location cause looks like this:
>>
>> <import namespace="http://myns" location="otherProject/my.wsdl"
>> importType="http://schemas.xmlsoap.org/wsdl/"/>
>>
>> whereas WSDLs from the local BPEL project look like this:
>>
>> <import namespace="http://myns" location="my.wsdl"
>> importType="http://schemas.xmlsoap.org/wsdl/"/>
>>
>> Both forms work when building from inside Netbeans. When building from
>> the command line with ant, the WSDL file pointed to by the location cause
>> for these imported from other projects can not be found.
>>
>> My question is, what is the location clause exactly? A path? It doesn't
>> seem to be if both the above forms work. What do we have to do so the
>> WSDLs in other projects are found when building from the command line?
>> How does the validation/build process search for included WSDL files?
>>
>> Thank you
>>
>

looking for accessible name for frame that netbeans created

2009-05-18T10:40:27Z

hi. how can i access to a frame that netbeans GUI builder created?
this is a coded that netbeans generated:

public void run() {
new CelsiusConverterGUI().setVisible(true);
}

i dont know what is the name of frame object!! how can i access to this object?

Re: BPEL validation from a command line can not find the WSDLs

2009-05-18T09:44:23Z

Well, the build process per se relies heavily on the data found in
catalog.xml, which
is located @ the root of the file hierarchy of the project. It is used, for
example, to turn
these AAA/xxx.wsdl entries into sensible file paths.

On 5/18/09 8:24 AM, jsexton0 wrote:

> There appears to be a great deal of mystery surrounding the build process.
> I'll include here a few more details for other that may be interested, but
> it appears that a headless build is not possible or practical at this time.
>
> First of all, the information found here:
> http://blogs.sun.com/tronds/entry/creating_a_simple_headless_build
> is vital to even getting started with regard to the build environment. That
> setup may be enough for most projects, or at least projects other than BPEL
> projects that refer to WSDLs in other projects.
>
> The nature of the "location" clause of an import in a BPEL file is unknown.
> It is not a file path, nor does using "file://" work. The build process
> somehow knows where to look for "AAA" when the location tag is
> "AAA/BBB.wsdl", even when the target is in some completely different project
> and hierarchy on the machine. I have been unable to determine how this
> happens - ie, how "AAA/BBB.wsdl" is mapped to a physical file.
>
> This magic occurs in at least two classes invoked by the build process:
>
> org.netbeans.modules.bpel.project.anttasks.cli.CliValidateBpelProjectTask
> org.netbeans.modules.bpel.project.anttasks.cli.CliGenerateCatalogTask
>
> Somehow, inside the GUI only, these classes can map the location tags to
> physical files and find thus the WSDLs required. GUI-only builds is a very
> surprising limitation, but there it is. I anyone has anyother information
> on this, I'd very much like to hear about it. It seems we will have to
> replace the build scripts for our projects.
>
>
> jsexton0 wrote:
>> Hello -
>>
>> When a WSDL from a separate project is included in a BPEL, the<import>
>> tag's location cause looks like this:
>>
>> <import namespace="http://myns" location="otherProject/my.wsdl"
>> importType="http://schemas.xmlsoap.org/wsdl/"/>
>>
>> whereas WSDLs from the local BPEL project look like this:
>>
>> <import namespace="http://myns" location="my.wsdl"
>> importType="http://schemas.xmlsoap.org/wsdl/"/>
>>
>> Both forms work when building from inside Netbeans. When building from
>> the command line with ant, the WSDL file pointed to by the location cause
>> for these imported from other projects can not be found.
>>
>> My question is, what is the location clause exactly? A path? It doesn't
>> seem to be if both the above forms work. What do we have to do so the
>> WSDLs in other projects are found when building from the command line?
>> How does the validation/build process search for included WSDL files?
>>
>> Thank you
>>
>

Re: BPEL validation from a command line can not find the WSDLs

2009-05-18T08:24:56Z

There appears to be a great deal of mystery surrounding the build process. I'll include here a few more details for other that may be interested, but it appears that a headless build is not possible or practical at this time.

First of all, the information found here:
http://blogs.sun.com/tronds/entry/creating_a_simple_headless_build
is vital to even getting started with regard to the build environment. That setup may be enough for most projects, or at least projects other than BPEL projects that refer to WSDLs in other projects.

The nature of the "location" clause of an import in a BPEL file is unknown. It is not a file path, nor does using "file://" work. The build process somehow knows where to look for "AAA" when the location tag is "AAA/BBB.wsdl", even when the target is in some completely different project and hierarchy on the machine. I have been unable to determine how this happens - ie, how "AAA/BBB.wsdl" is mapped to a physical file.

This magic occurs in at least two classes invoked by the build process:

org.netbeans.modules.bpel.project.anttasks.cli.CliValidateBpelProjectTask
org.netbeans.modules.bpel.project.anttasks.cli.CliGenerateCatalogTask

Somehow, inside the GUI only, these classes can map the location tags to physical files and find thus the WSDLs required. GUI-only builds is a very surprising limitation, but there it is. I anyone has anyother information on this, I'd very much like to hear about it. It seems we will have to replace the build scripts for our projects.

jsexton0 wrote:

Hello -

When a WSDL from a separate project is included in a BPEL, the <import> tag's location cause looks like this:

<import namespace="http://myns" location="otherProject/my.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>

whereas WSDLs from the local BPEL project look like this:

<import namespace="http://myns" location="my.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>

Both forms work when building from inside Netbeans. When building from the command line with ant, the WSDL file pointed to by the location cause for these imported from other projects can not be found.

My question is, what is the location clause exactly? A path? It doesn't seem to be if both the above forms work. What do we have to do so the WSDLs in other projects are found when building from the command line? How does the validation/build process search for included WSDL files?

Thank you

BPEL validation from a command line can not find the WSDLs

2009-05-15T13:24:42Z

Hello -

When a WSDL from a separate project is included in a BPEL, the <import> tag's location cause looks like this:

<import namespace="http://myns" location="otherProject/my.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>

whereas WSDLs from the local BPEL project look like this:

<import namespace="http://myns" location="my.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>

Both forms work when building from inside Netbeans. When building from the command line with ant, the WSDL file pointed to by the location cause for these imported from other projects can not be found.

My question is, what is the location clause exactly? A path? It doesn't seem to be if both the above forms work. What do we have to do so the WSDLs in other projects are found when building from the command line? How does the validation/build process search for included WSDL files?

Thank you

Re: Unable to Specify an Operation in a WS

2009-05-14T07:53:29Z

I have the same problem (WSDL with soapAction, but HTTP-BC producing HTTP header without it). Is there any solution or workaround?

Version: Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs)
WSDL: http://service.ecocoma.com/shipping/dhl.asmx?WSDL (read http://service.ecocoma.com/shipping_webservice.aspx for more info)

Regards
Gerhard

Murali Pottlapelli wrote:

Some on from http-bc team might be able to help you better. Posting it
to users@open-esb.dev.java.net

Regards
Murali

jsexton0 wrote:
> Hi -
>
> I'm working with a web service I'd like to call from Java code and from a
> BPEL. The WS is implemented as an SA and an SE deployed on the same
> Glassfish instance I want to call it from. A found that Netbeans generated
> tests, from an SA project, could not call the server because they seemed to
> fail to specify the operation (SOAPAction) in the HTTP header.
>
> I went to some stand alone Java code, and it works fine, when I include like
> this:
>
> MimeHeaders header = mySoapRequest.getMimeHeaders();
> header.addHeader("SOAPAction", mySoapOperation);
> Object res = dispatch.invoke(mySoapRequest);
>
> The operation is added to the HTTP header, and everything is fine. (Java
> 1.6 on Windows)
> Then I moved over to a Ubunti 8.10 box with Java 1.6.0.10. On this box, not
> only am I unable to use the service from a BPEL, but no matter what I do, I
> can't seem to get the right service into the HTTP header from Java code
> either. No matter what I do, the HTTP request header includes this:
>
> SOAPAction = ""
>
> Literally, two double quotes. I can add new, bogus, header elements just
> fine, like so:
>
> MimeHeaders header = mySoapRequest.getMimeHeaders();
> header.addHeader("SomeEntry", "NothingSpecial");
>
> But I can not override SOAPAction on the linux setup. I've tried removing
> the headers, putting nonsense in (that should cause an error but doesn't),
> and all sorts of long-hand construction of the message, but the SOAPAction
> remains "" no matter what, on linux. Even attempts to remove the SOAPAction
> item result in the same HTTP mesage.
>
> I can call the operation fine using the SoapUI tool on either Ubuntu or
> Windows, and I checked the HTTP post on these calls, and they are correct.
>
> Something in the dispatch object must be setting the SOAPAction. I ran
> across this:
>
> http://forums.java.net/jive/thread.jspa?threadID=637
>
> It's not directly related, but it sure seems similar. Even if there is a
> work around in Java, I'll need to call these operations from a BPEL also.
> Any ideas?
>
> Thank you
>
>
>

RE: Derby Error Starting Glassfish

2009-05-04T13:08:42Z

Mmmmm,

Well if that fixed it ....

Manfred

> I'm not sure... I certainly have not coded anything that uses that database
> directly. But here's something: I replaced the databases/ejbtimer directory
> entirely with the same directory from another (Windows) machine running the
> same edition of Glassfish/Netbeans. Following this the server I'm working
> with has stopped and restarted flawlessly twice.
>

RE: Derby Error Starting Glassfish

2009-05-04T11:57:37Z

I'm not sure... I certainly have not coded anything that uses that database directly. But here's something: I replaced the databases/ejbtimer directory entirely with the same directory from another (Windows) machine running the same edition of Glassfish/Netbeans. Following this the server I'm working with has stopped and restarted flawlessly twice.

Manfred Riem wrote:

Hi,

So that rules out a problem with the database. So it
must be in one of your applications. Would one of
your applications by accident try to use that resource?

Manfred

RE: Derby Error Starting Glassfish

2009-05-04T11:01:27Z

Hi,

So that rules out a problem with the database. So it
must be in one of your applications. Would one of
your applications by accident try to use that resource?

Manfred

> I'm sorry, my fault. I was leaving off the ';'
> d'oh!
>
> The queries work fine when I'm connected with ij.

RE: Derby Error Starting Glassfish

2009-05-04T10:58:31Z

I'm sorry, my fault. I was leaving off the ';'
d'oh!

The queries work fine when I'm connected with ij.

Hello again...

I got connected using newer scripts in /javadb/bin rather than /frameworks/NewtworkServer/bin.
It's a little show to connect, and "show tables" seems to hang - with Glassfish not running.

jsexton0 wrote:

I get "no suitable driver" on the connect command. What am I missing there?

This does in fact come up if I undeploy a few things, startup Glassfish, and re-deploy after it has finished it's start process. But if, and only if, my full application is loaded when Glassfish start, then the EJB timer service fails to start due to the time-out selecting from Derby.

Thanks

Manfred Riem wrote:

Hi there,

Have you tried executing the query against that database
yourself?

Manfred

> Hello -
>
> I seem to have reached the inescapable conclusion that Derby can not handle
> supporting the EJB timer service in Glassfish after the application reaches
> a certain point. And the only (drastic) choice is to reconfigure Glassfish
> with a different database.
>
> I only have one timer in my application, but a have been steadily adding SAs
> and I have 3 or 4 DB connection pools, so I guess one of those pushes it
> over the edge and prevents a valid start up?
>
> It's hard to believe that something has not been overlooked here, it really
> just doesn't work? Simple as that? Anyone else want to make a suggestion?
>
> Thanks - here is the startup exception again, just in case.
>
> JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
> problems running JDOQL query with params [server, 0]
> com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
> JDBC SQLException while executing the SQL statement:
> SQL statement<select distinct t0."TIMERID", t0."CREATIONTIMERAW",
> t0."LASTEXPIRATIONRAW", t0."CONTAINERID", t0."OWNERID", t0."STATE",
> t0."PKHASHCODE", t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from
> "EJB__TIMER__TBL" t0 where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and
> t0."STATE" = CAST (? AS INTEGER)> with input values:java.lang.String:server,
> java.lang.Integer:0.
> Please examine the SQLException for more information.
> NestedException: java.sql.SQLTransactionRollbackException: A lock could not
> be obtained within the time requested
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlException(SQLStoreManager.java:645)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:479)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> NestedStackTrace:
> java.sql.SQLTransactionRollbackException: A lock could not be obtained
> within the time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(ResultDesc.java:490)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.getResult(SelectQueryPlan.java:1576)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:477)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> Caused by: java.sql.SQLException: A lock could not be obtained within the
> time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 38 more

RE: Derby Error Starting Glassfish

2009-05-04T10:28:50Z

Here is domain.xml, thanks. It's reassuring that you're not seeing issues like this.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE domain PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 9.1 Domain//EN" "http://www.sun.com/software/appserver/dtds/sun-domain_1_3.dtd">



<domain application-root="${com.sun.aas.instanceRoot}/applications" log-root="${com.sun.aas.instanceRoot}/logs">
<applications>
<j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/MEjbApp" name="MEjbApp" object-type="system-all"/>
<j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__ejb_container_timer_app" name="__ejb_container_timer_app" object-type="system-all"/>
<j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__JWSappclients" name="__JWSappclients" object-type="system-all"/>
<j2ee-application availability-enabled="false" directory-deployed="true" enabled="true" java-web-start-enabled="true" location="U:/Public/work/CMS/CMS_TIMER_EA/dist/gfdeploy" name="CMS_TIMER_EA" object-type="user"/>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_PinChange_SA-CMS_PinChange_EJB" name="CMS_PinChange_SA-CMS_PinChange_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_CardHolder_SA-CMS_CardHolder_EJB" name="CMS_CardHolder_SA-CMS_CardHolder_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/MSG_SA-MSG_EJB" name="MSG_SA-MSG_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="true" enabled="true" location="U:/Public/work/CMS/CMS_Custom_EJB/build/jar" name="CMS_Custom_EJB" object-type="user"/>
<ejb-module availability-enabled="false" directory-deployed="true" enabled="true" location="U:/Public/work/CMS/CMS_CATSA_EJB/build/jar" name="CMS_CATSA_EJB" object-type="user"/>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/LST_SA-LST_EJB" name="LST_SA-LST_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_Card_SA-CMS_Card_EJB" name="CMS_Card_SA-CMS_Card_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_Print_SA-CMS_Print_EJB" name="CMS_Print_SA-CMS_Print_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_AuditTrail_SA-CMS_AuditLog_EJB" name="CMS_AuditTrail_SA-CMS_AuditLog_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_CATSA_SA-CMS_CATSA_EJB" name="CMS_CATSA_SA-CMS_CATSA_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/ConfigurationManagerSA-ConfigurationManagerEJB" name="ConfigurationManagerSA-ConfigurationManagerEJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<ejb-module availability-enabled="false" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/CMS_SA-CMS_EJB" name="CMS_SA-CMS_EJB" object-type="user">
<property name="externally-managed" value="true"/>
</ejb-module>
<web-module availability-enabled="false" context-root="/web1" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/adminapp/adminapp_war" name="adminapp" object-type="system-admin">

</web-module>
<web-module availability-enabled="false" context-root="" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/admingui/adminGUI_war" name="admingui" object-type="system-admin">

</web-module>
<web-module availability-enabled="false" context-root="/__wstx-services" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/wstx-services" name="WSTXServices" object-type="system-all"/>
<lifecycle-module class-name="com.sun.jbi.framework.sun.SunASJBIBootstrap" classpath="${com.sun.aas.installRoot}/jbi/lib/jbi_framework.jar" enabled="true" is-failure-fatal="false" name="JBIFramework" object-type="system-all">
<description>"JBI Framework LifecycleModule"</description>
<property name="com.sun.jbi.home" value="${com.sun.aas.installRoot}/jbi"/>
</lifecycle-module>
<lifecycle-module class-name="com.sun.xml.ws.transport.tcp.server.glassfish.WSTCPLifeCycleModule" classpath="${com.sun.aas.installRoot}/lib/webservices-rt.jar" enabled="true" is-failure-fatal="false" name="WSTCPConnectorLCModule" object-type="system-all"/>
<web-module availability-enabled="false" context-root="portletdriver" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/portletdriver" name="portletdriver" object-type="user"/>
<web-module availability-enabled="false" context-root="/cam" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/cam" name="cam" object-type="user"/>
<web-module availability-enabled="false" context-root="/camBpelPlugin" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/camBpelPlugin" name="camBpelPlugin" object-type="user"/>
<web-module availability-enabled="false" context-root="/aspects" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/aspects" name="aspects" object-type="user"/>
<web-module availability-enabled="false" context-root="amserver" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/amserver" name="amserver" object-type="user"/>
</applications>
<resources>
<jdbc-resource enabled="true" jndi-name="jdbc/sample" object-type="user" pool-name="SamplePool"/>
<custom-resource enabled="true" factory-class="com.iwsinc.factory.StringFactory" jndi-name="ConfigurationManagerEncryptionPassword" object-type="user" res-type="java.lang.String">
<property name="string" value="pancakeboots"/>
</custom-resource>
<custom-resource enabled="true" factory-class="com.iwsinc.factory.StringFactory" jndi-name="ConfigurationManagerEncryptionSalt" object-type="user" res-type="java.lang.String">
<property name="string" value="Testingu"/>
</custom-resource>
<custom-resource enabled="true" factory-class="com.iwsinc.factory.StringFactory" jndi-name="ConfigurationManagerFileLocation" object-type="user" res-type="java.lang.String">
<property name="string" value="C:\EPICMS\"/>
</custom-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/__TimerPool" object-type="system-admin" pool-name="__TimerPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/__CallFlowPool" object-type="system-all" pool-name="__CallFlowPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/__defaultDS" object-type="user" pool-name="DerbyPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/__default" object-type="user" pool-name="DerbyPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/__workflow" object-type="user" pool-name="WorkflowPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/iepseDerbyNonXA" object-type="user" pool-name="iepseDerbyPoolNonXA"/>
<jdbc-resource enabled="true" jndi-name="jdbc/iepseDerbyXA" object-type="user" pool-name="iepseDerbyPoolXA"/>
<jdbc-resource enabled="true" jndi-name="jdbc/SQLExpress" object-type="user" pool-name="SQLExpress">
<description>CMS Database</description>
</jdbc-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/MasterDB" object-type="user" pool-name="MasterDB">
<description>CMS Master Database</description>
</jdbc-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/CMSAudit" object-type="user" pool-name="CMSAudit">
<description>CMS Audit</description>
</jdbc-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/CIDDB" object-type="user" pool-name="CIDDB">
<description>CID DB</description>
</jdbc-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/RADDB" object-type="user" pool-name="RADDB">
<description>RAD DB</description>
</jdbc-resource>
<admin-object-resource enabled="true" jndi-name="jms/cmsTopic" object-type="user" res-adapter="jmsra" res-type="javax.jms.Topic">
<description>CMS JMS Topic</description>
<property name="Name" value="CMSTopic"/>
</admin-object-resource>
<connector-resource enabled="true" jndi-name="jms/CMSTopicFactory" object-type="user" pool-name="jms/CMSTopicFactory">
<description>CMS JMS Topic Connection Factory</description>
</connector-resource>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="__CallFlowPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="databaseName" value="${com.sun.aas.instanceRoot}/lib/databases/sun-callflow"/>
<property name="connectionAttributes" value=";create=true"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="2" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="64" max-wait-time-in-millis="240000" name="__TimerPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="10" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="databaseName" value="${com.sun.aas.instanceRoot}/lib/databases/ejbtimer"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="DerbyPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="connectionAttributes" value=";create=true"/>
<property name="serverName" value="localhost"/>
<property name="DatabaseName" value="sample"/>
<property name="PortNumber" value="1527"/>
<property name="User" value="app"/>
<property name="Password" value="app"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="true" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="WorkflowPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="password" value="WORKFLOW"/>
<property name="connectionAttributes" value=";create=true"/>
<property name="databaseName" value="WORKFLOWDB"/>
<property name="user" value="WORKFLOW"/>
<property name="serverName" value="localhost"/>
<property name="portNumber" value="1527"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="true" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="iepseDerbyPoolNonXA" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="connectionAttributes" value=";create=true"/>
<property name="PortNumber" value="1527"/>
<property name="Password" value="iepseDB"/>
<property name="DatabaseName" value="iepseDB"/>
<property name="serverName" value="localhost"/>
<property name="User" value="iepseDB"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="true" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="iepseDerbyPoolXA" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="connectionAttributes" value=";create=true"/>
<property name="PortNumber" value="1527"/>
<property name="Password" value="iepseDB"/>
<property name="DatabaseName" value="iepseDB"/>
<property name="serverName" value="localhost"/>
<property name="User" value="iepseDB"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="64" max-wait-time-in-millis="60000" name="SQLExpress" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-size="2" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>SQL Server Express</description>
<property name="databaseName" value="EpiCms"/>
<property name="serverName" value="localhost\SQLEXPRESS"/>
<property name="User" value="EPICMS"/>
<property name="Password" value="ImageWare1!"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="MasterDB" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-size="1" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>CMS Master DB</description>
<property name="User" value="EPICMS"/>
<property name="databaseName" value="MasterEpiCms"/>
<property name="Password" value="ImageWare1!"/>
<property name="serverName" value="localhost\SQLExpress"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="64" max-wait-time-in-millis="60000" name="CMSAudit" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-size="2" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>CMS Audit JDBC Connection Pool</description>
<property name="user" value="EPICMS"/>
<property name="password" value="ImageWare1!"/>
<property name="databaseName" value="EpiCms"/>
<property name="serverName" value="localhost\SQLEXPRESS"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="CIDDB" non-transactional-connections="true" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-size="1" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>CID DB</description>
<property name="user" value="EPICMS"/>
<property name="password" value="ImageWare1!"/>
<property name="databaseName" value="CID"/>
<property name="serverName" value="localhost\SQLEXPRESS"/>
</jdbc-connection-pool>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="RADDB" non-transactional-connections="true" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-size="1" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>RAD DB</description>
<property name="databaseName" value="RAD"/>
<property name="serverName" value="localhost\SQLEXPRESS"/>
<property name="user" value="EPICMS"/>
<property name="password" value="ImageWare1!"/>
</jdbc-connection-pool>
<connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.TopicConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/CMSTopicFactory" pool-resize-quantity="2" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="SamplePool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<property name="DatabaseName" value="sample"/>
<property name="User" value="app"/>
<property name="Password" value="app"/>
<property name="URL" value="jdbc:derby://localhost:1527/sample"/>
<property name="PortNumber" value="1527"/>
<property name="serverName" value="localhost"/>
</jdbc-connection-pool>
</resources>
<configs>
<config dynamic-reconfiguration-enabled="true" name="server-config">
<http-service>
<access-log format="%client.name% %auth-user-name% %datetime% %request% %status% %response.length%" rotation-enabled="true" rotation-interval-in-minutes="15" rotation-policy="time" rotation-suffix="yyyy-MM-dd"/>
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="8080" security-enabled="false" server-name="" xpowered-by="true">
<property name="proxiedProtocols" value="ws/tcp"/>
</http-listener>
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</http-listener>
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true"/>
<virtual-server hosts="${com.sun.aas.hostName}" http-listeners="http-listener-1,http-listener-2" id="server" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
<property name="sso-enabled" value="true"/>
</virtual-server>
<virtual-server hosts="${com.sun.aas.hostName}" http-listeners="admin-listener" id="__asadmin" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
<property name="sso-enabled" value="true"/>
</virtual-server>
<request-processing header-buffer-length-in-bytes="8192" initial-thread-count="2" request-timeout-in-seconds="30" thread-count="5" thread-increment="1"/>
<keep-alive max-connections="250" thread-count="1" timeout-in-seconds="30"/>
<connection-pool max-pending-count="4096" queue-size-in-bytes="4096" receive-buffer-size-in-bytes="8192" send-buffer-size-in-bytes="8192"/>
<http-protocol default-response-type="AttributeDeprecated" default-type="text/html; charset=iso-8859-1" dns-lookup-enabled="false" forced-response-type="AttributeDeprecated" forced-type="text/html; charset=iso-8859-1" ssl-enabled="true" version="HTTP/1.1"/>
<http-file-cache file-caching-enabled="false" file-transmission-enabled="false" globally-enabled="false" hash-init-size="0" max-age-in-seconds="30" max-files-count="1024" medium-file-size-limit-in-bytes="537600" medium-file-space-in-bytes="10485760" small-file-size-limit-in-bytes="2048" small-file-space-in-bytes="1048576"/>
<property name="accessLoggingEnabled" value="false"/>
</http-service>
<iiop-service client-authentication-required="false">
<orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1"/>
<iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="3700" security-enabled="false"/>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="3820" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="3920" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
</iiop-service>
<admin-service system-jmx-connector-name="system" type="das-and-server">

<jmx-connector accept-all="false" address="0.0.0.0" auth-realm-name="admin-realm" enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</jmx-connector>

<das-config admin-session-timeout-in-minutes="60" autodeploy-dir="${com.sun.aas.instanceRoot}/autodeploy" autodeploy-enabled="true" autodeploy-jsp-precompilation-enabled="false" autodeploy-polling-interval-in-seconds="2" autodeploy-verifier-enabled="false" deploy-xml-validation="full" dynamic-reload-enabled="true" dynamic-reload-poll-interval-in-seconds="2"/>
</admin-service>
<web-container>
<session-config>
<session-manager>
<manager-properties/>
<store-properties/>
</session-manager>
<session-properties/>
</session-config>
</web-container>
<ejb-container cache-idle-timeout-in-seconds="600" cache-resize-quantity="32" commit-option="B" max-cache-size="512" max-pool-size="128" pool-idle-timeout-in-seconds="600" pool-resize-quantity="8" removal-timeout-in-seconds="5400" session-store="${com.sun.aas.instanceRoot}/session-store" steady-pool-size="0" victim-selection-policy="nru">
<ejb-timer-service max-redeliveries="1" minimum-delivery-interval-in-millis="7000" redelivery-interval-internal-in-millis="5000"/>
</ejb-container>
<mdb-container idle-timeout-in-seconds="600" max-pool-size="32" pool-resize-quantity="8" steady-pool-size="0"/>
<jms-service addresslist-behavior="random" addresslist-iterations="3" default-jms-host="default_JMS_host" init-timeout-in-seconds="60" reconnect-attempts="3" reconnect-enabled="true" reconnect-interval-in-seconds="5" type="LOCAL">
<jms-host admin-password="admin" admin-user-name="admin" host="iws03box1.iwsinc.com" name="default_JMS_host" port="7676"/>
</jms-service>
<log-service alarms="false" file="${com.sun.aas.instanceRoot}/logs/server.log" log-rotation-limit-in-bytes="4000000" log-rotation-timelimit-in-minutes="0" log-to-console="false" retain-error-statistics-for-hours="5" use-system-logging="false">
<module-log-levels admin="INFO" classloader="INFO" cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO" corba="INFO" deployment="INFO" ejb-container="INFO" group-management-service="INFO" javamail="INFO" jaxr="INFO" jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO" management-event="INFO" mdb-container="INFO" naming="INFO" node-agent="INFO" resource-adapter="INFO" root="INFO" saaj="INFO" security="INFO" self-management="INFO" server="INFO" synchronization="INFO" util="INFO" verifier="INFO" web-container="INFO">
<property name="com.sun.jbi" value="INFO"/>
<property name="javax.enterprise.resource.webservices.jaxws" value="INFO"/>
<property name="oracle.toplink.essentials" value="INFO"/>
</module-log-levels>
</log-service>
<security-service activate-default-principal-to-role-mapping="false" anonymous-role="AttributeDeprecated" audit-enabled="false" audit-modules="default" default-realm="file" jacc="default">

<auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="admin-realm">
<property name="file" value="${com.sun.aas.instanceRoot}/config/admin-keyfile"/>
<property name="jaas-context" value="fileRealm"/>
</auth-realm>

<auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="file">
<property name="file" value="${com.sun.aas.instanceRoot}/config/keyfile"/>
<property name="jaas-context" value="fileRealm"/>
</auth-realm>
<auth-realm classname="com.sun.enterprise.security.auth.realm.certificate.CertificateRealm" name="certificate">
</auth-realm>
<jacc-provider name="default" policy-configuration-factory-provider="com.sun.enterprise.security.provider.PolicyConfigurationFactoryImpl" policy-provider="com.sun.enterprise.security.provider.PolicyWrapper">
<property name="repository" value="${com.sun.aas.instanceRoot}/generated/policy"/>
</jacc-provider>
<audit-module classname="com.sun.enterprise.security.Audit" name="default">
<property name="auditOn" value="false"/>
</audit-module>
<message-security-config auth-layer="SOAP">

<provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="XWS_ClientProvider" provider-type="client">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="dynamic.username.password" value="false"/>
<property name="debug" value="false"/>
</provider-config>
<provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="ClientProvider" provider-type="client">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="dynamic.username.password" value="false"/>
<property name="debug" value="false"/>
<property name="security.config" value="${com.sun.aas.instanceRoot}/config/wss-server-config-1.0.xml"/>
</provider-config>
<provider-config class-name="com.sun.xml.wss.provider.ServerSecurityAuthModule" provider-id="XWS_ServerProvider" provider-type="server">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="debug" value="false"/>
</provider-config>
<provider-config class-name="com.sun.xml.wss.provider.ServerSecurityAuthModule" provider-id="ServerProvider" provider-type="server">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="debug" value="false"/>
<property name="security.config" value="${com.sun.aas.instanceRoot}/config/wss-server-config-1.0.xml"/>
</provider-config>
</message-security-config>
</security-service>
<transaction-service automatic-recovery="false" heuristic-decision="rollback" keypoint-interval="65536" retry-timeout-in-seconds="600" timeout-in-seconds="0" tx-log-dir="${com.sun.aas.instanceRoot}/logs"/>
<monitoring-service>
<module-monitoring-levels connector-connection-pool="OFF" connector-service="OFF" ejb-container="LOW" http-service="LOW" jdbc-connection-pool="OFF" jms-service="OFF" jvm="OFF" orb="OFF" thread-pool="OFF" transaction-service="OFF" web-container="LOW"/>
</monitoring-service>
<diagnostic-service capture-app-dd="true" capture-hadb-info="true" capture-install-log="true" capture-system-info="true" compute-checksum="true" max-log-entries="500" min-log-level="INFO" verify-config="true"/>
<java-config classpath-suffix="" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="">

<jvm-options>-XX:MaxPermSize=192m</jvm-options>
<jvm-options>-client</jvm-options>
<jvm-options>-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/endorsed</jvm-options>
<jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
<jvm-options>-Djava.security.auth.login.config=${com.sun.aas.instanceRoot}/config/login.conf</jvm-options>
<jvm-options>-Dsun.rmi.dgc.server.gcInterval=3600000</jvm-options>
<jvm-options>-Dsun.rmi.dgc.client.gcInterval=3600000</jvm-options>
<jvm-options>-Xmx512m</jvm-options>
<jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks</jvm-options>
<jvm-options>-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks</jvm-options>
<jvm-options>-Djava.ext.dirs=${com.sun.aas.javaRoot}/lib/ext${path.separator}${com.sun.aas.javaRoot}/jre/lib/ext${path.separator}${com.sun.aas.instanceRoot}/lib/ext${path.separator}${com.sun.aas.derbyRoot}/lib</jvm-options>
<jvm-options>-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver</jvm-options>
<jvm-options>-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder</jvm-options>
<jvm-options>-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory</jvm-options>
<jvm-options>-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar</jvm-options>
<jvm-options>-Dcom.sun.enterprise.taglisteners=jsf-impl.jar</jvm-options>
<jvm-options>-XX:NewRatio=2</jvm-options>

<jvm-options>-XX:MaxPermSize=128m</jvm-options>
<jvm-options>-XX:PermSize=128m</jvm-options>
<jvm-options>-Dcom.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace=false</jvm-options>
</java-config>
<thread-pools>
<thread-pool idle-thread-timeout-in-seconds="120" max-thread-pool-size="200" min-thread-pool-size="0" num-work-queues="1" thread-pool-id="thread-pool-1"/>
</thread-pools>
<management-rules enabled="true">
</management-rules>
</config>

</configs>
<servers>
<server config-ref="server-config" lb-weight="100" name="server">
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="adminapp" virtual-servers="__asadmin"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="admingui" virtual-servers="__asadmin"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="JBIFramework"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="WSTXServices"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="WSTCPConnectorLCModule"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="MEjbApp" virtual-servers="server"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__ejb_container_timer_app" virtual-servers="server"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__JWSappclients" virtual-servers="server"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="portletdriver" virtual-servers="server"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="cam"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="camBpelPlugin"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="aspects"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_PinChange_SA-CMS_PinChange_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_CardHolder_SA-CMS_CardHolder_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="MSG_SA-MSG_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_Custom_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_CATSA_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="LST_SA-LST_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_Card_SA-CMS_Card_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_Print_SA-CMS_Print_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_AuditTrail_SA-CMS_AuditLog_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_CATSA_SA-CMS_CATSA_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="ConfigurationManagerSA-ConfigurationManagerEJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_SA-CMS_EJB"/>
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="CMS_TIMER_EA"/>
<resource-ref enabled="true" ref="jdbc/__TimerPool"/>
<resource-ref enabled="true" ref="jdbc/__CallFlowPool"/>
<resource-ref enabled="true" ref="jdbc/__defaultDS"/>
<resource-ref enabled="true" ref="jdbc/__default"/>
<resource-ref enabled="true" ref="jdbc/__workflow"/>
<resource-ref enabled="true" ref="jdbc/iepseDerbyNonXA"/>
<resource-ref enabled="true" ref="jdbc/iepseDerbyXA"/>
<resource-ref enabled="true" ref="jdbc/SQLExpress"/>
<resource-ref enabled="true" ref="ConfigurationManagerEncryptionPassword"/>
<resource-ref enabled="true" ref="ConfigurationManagerEncryptionSalt"/>
<resource-ref enabled="true" ref="ConfigurationManagerFileLocation"/>
<resource-ref enabled="true" ref="jms/CMSTopicFactory"/>
<resource-ref enabled="true" ref="jms/cmsTopic"/>
<resource-ref enabled="true" ref="jdbc/MasterDB"/>
<resource-ref enabled="true" ref="jdbc/CMSAudit"/>
<resource-ref enabled="true" ref="jdbc/CIDDB"/>
<resource-ref enabled="true" ref="jdbc/RADDB"/>
<resource-ref enabled="true" ref="jdbc/sample"/>
</server>
</servers>
<property name="administrative.domain.name" value="domain1"/>
</domain>

Gavin Ross-2 wrote:

Please supply a copy of your domain.xml file. There may be a conflict in
your glassfish setup as I am running glassfish very well with upto 8
connection pools in a production environment without any issues.

Gavin Ross
Preferred Partner : The Bluebox
Cell: 0837038110
Email: gavin@bluebox.co.za

-----Original Message-----
From: jsexton0 [mailto:jsexton0@gmail.com]
Sent: 04 May 2009 05:40 PM
To: nbentpack@netbeans.org
Subject: Re: [entpack] Derby Error Starting Glassfish

Hello -

I seem to have reached the inescapable conclusion that Derby can not handle
supporting the EJB timer service in Glassfish after the application reaches
a certain point. And the only (drastic) choice is to reconfigure Glassfish
with a different database.

I only have one timer in my application, but a have been steadily adding SAs
and I have 3 or 4 DB connection pools, so I guess one of those pushes it
over the edge and prevents a valid start up?

It's hard to believe that something has not been overlooked here, it really
just doesn't work? Simple as that? Anyone else want to make a suggestion?

Thanks - here is the startup exception again, just in case.

JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
problems running JDOQL query with params [server, 0]
com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
JDBC SQLException while executing the SQL statement: SQL statement<select
distinct t0."TIMERID", t0."CREATIONTIMERAW", t0."LASTEXPIRATIONRAW",
t0."CONTAINERID", t0."OWNERID", t0."STATE", t0."PKHASHCODE",
t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from "EJB__TIMER__TBL" t0
where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and t0."STATE" = CAST (? AS
INTEGER)> with input values:java.lang.String:server, java.lang.Integer:0.
Please examine the SQLException for more information.
NestedException: java.sql.SQLTransactionRollbackException: A lock could not
be obtained within the time requested
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlExce
ption(SQLStoreManager.java:645)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQ
LStoreManager.java:479)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLSto
reManager.java:376)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.ret
rieve(PersistenceManagerImpl.java:1118)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(Query
Impl.java:689)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArra
y(QueryImpl.java:607)
at
com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersB
yOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
at
com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServ
er(TimerBean.java:709)
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
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecu
rityManager.java:1067)
at
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
at
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.ja
va:2895)
at
com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvo
cationHandler.java:242)
at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
at
com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:49
1)
at
com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactor
yImpl.java:364)
at
com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.
java:348)
at
com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:5
26)
at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
NestedStackTrace:
java.sql.SQLTransactionRollbackException: A lock could not be obtained
within the time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknow
n
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at
org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at
org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
at
com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(Result
Desc.java:490)
at
com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.g
etResult(SelectQueryPlan.java:1576)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQ
LStoreManager.java:477)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLSto
reManager.java:376)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.ret
rieve(PersistenceManagerImpl.java:1118)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(Query
Impl.java:689)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArra
y(QueryImpl.java:607)
at
com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersB
yOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
at
com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServ
er(TimerBean.java:709)
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
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecu
rityManager.java:1067)
at
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
at
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.ja
va:2895)
at
com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvo
cationHandler.java:242)
at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
at
com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:49
1)
at
com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactor
yImpl.java:364)
at
com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.
java:348)
at
com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:5
26)
at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
Caused by: java.sql.SQLException: A lock could not be obtained within the
time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossD
RDA(Unknown
Source)
... 38 more

--
View this message in context:
http://www.nabble.com/Derby-Error-Starting-Glassfish-tp23334048p23370987.htm
l
Sent from the NetBeans - EntPack mailing list archive at Nabble.com.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.287 / Virus Database: 270.12.15/2093 - Release Date: 05/02/09
14:23:00

RE: Derby Error Starting Glassfish

2009-05-04T10:25:35Z

Hello again...

I got connected using newer scripts in /javadb/bin rather than /frameworks/NewtworkServer/bin.
It's a little show to connect, and "show tables" seems to hang - with Glassfish not running.

I get "no suitable driver" on the connect command. What am I missing there?

This does in fact come up if I undeploy a few things, startup Glassfish, and re-deploy after it has finished it's start process. But if, and only if, my full application is loaded when Glassfish start, then the EJB timer service fails to start due to the time-out selecting from Derby.

Thanks

Manfred Riem wrote:

Hi there,

Have you tried executing the query against that database
yourself?

Manfred

> Hello -
>
> I seem to have reached the inescapable conclusion that Derby can not handle
> supporting the EJB timer service in Glassfish after the application reaches
> a certain point. And the only (drastic) choice is to reconfigure Glassfish
> with a different database.
>
> I only have one timer in my application, but a have been steadily adding SAs
> and I have 3 or 4 DB connection pools, so I guess one of those pushes it
> over the edge and prevents a valid start up?
>
> It's hard to believe that something has not been overlooked here, it really
> just doesn't work? Simple as that? Anyone else want to make a suggestion?
>
> Thanks - here is the startup exception again, just in case.
>
> JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
> problems running JDOQL query with params [server, 0]
> com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
> JDBC SQLException while executing the SQL statement:
> SQL statement<select distinct t0."TIMERID", t0."CREATIONTIMERAW",
> t0."LASTEXPIRATIONRAW", t0."CONTAINERID", t0."OWNERID", t0."STATE",
> t0."PKHASHCODE", t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from
> "EJB__TIMER__TBL" t0 where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and
> t0."STATE" = CAST (? AS INTEGER)> with input values:java.lang.String:server,
> java.lang.Integer:0.
> Please examine the SQLException for more information.
> NestedException: java.sql.SQLTransactionRollbackException: A lock could not
> be obtained within the time requested
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlException(SQLStoreManager.java:645)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:479)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> NestedStackTrace:
> java.sql.SQLTransactionRollbackException: A lock could not be obtained
> within the time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(ResultDesc.java:490)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.getResult(SelectQueryPlan.java:1576)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:477)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> Caused by: java.sql.SQLException: A lock could not be obtained within the
> time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 38 more

RE: Derby Error Starting Glassfish

2009-05-04T10:16:42Z

Please supply a copy of your domain.xml file. There may be a conflict in
your glassfish setup as I am running glassfish very well with upto 8
connection pools in a production environment without any issues.

Gavin Ross
Preferred Partner : The Bluebox
Cell: 0837038110
Email: gavin@...

-----Original Message-----
From: jsexton0 [mailto:jsexton0@...]
Sent: 04 May 2009 05:40 PM
To: nbentpack@...
Subject: Re: [entpack] Derby Error Starting Glassfish

Hello -

I seem to have reached the inescapable conclusion that Derby can not handle
supporting the EJB timer service in Glassfish after the application reaches
a certain point. And the only (drastic) choice is to reconfigure Glassfish
with a different database.

I only have one timer in my application, but a have been steadily adding SAs
and I have 3 or 4 DB connection pools, so I guess one of those pushes it
over the edge and prevents a valid start up?

It's hard to believe that something has not been overlooked here, it really
just doesn't work? Simple as that? Anyone else want to make a suggestion?

Thanks - here is the startup exception again, just in case.

JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
problems running JDOQL query with params [server, 0]
com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
JDBC SQLException while executing the SQL statement: SQL statement<select
distinct t0."TIMERID", t0."CREATIONTIMERAW", t0."LASTEXPIRATIONRAW",
t0."CONTAINERID", t0."OWNERID", t0."STATE", t0."PKHASHCODE",
t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from "EJB__TIMER__TBL" t0
where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and t0."STATE" = CAST (? AS
INTEGER)> with input values:java.lang.String:server, java.lang.Integer:0.
Please examine the SQLException for more information.
NestedException: java.sql.SQLTransactionRollbackException: A lock could not
be obtained within the time requested
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlExce
ption(SQLStoreManager.java:645)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQ
LStoreManager.java:479)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLSto
reManager.java:376)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.ret
rieve(PersistenceManagerImpl.java:1118)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(Query
Impl.java:689)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArra
y(QueryImpl.java:607)
at
com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersB
yOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
at
com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServ
er(TimerBean.java:709)
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
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecu
rityManager.java:1067)
at
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
at
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.ja
va:2895)
at
com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvo
cationHandler.java:242)
at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
at
com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:49
1)
at
com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactor
yImpl.java:364)
at
com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.
java:348)
at
com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:5
26)
at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
NestedStackTrace:
java.sql.SQLTransactionRollbackException: A lock could not be obtained
within the time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknow
n
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at
org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at
org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
at
com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(Result
Desc.java:490)
at
com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.g
etResult(SelectQueryPlan.java:1576)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQ
LStoreManager.java:477)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLSto
reManager.java:376)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.ret
rieve(PersistenceManagerImpl.java:1118)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(Query
Impl.java:689)
at
com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArra
y(QueryImpl.java:607)
at
com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersB
yOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
at
com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServ
er(TimerBean.java:709)
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
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecu
rityManager.java:1067)
at
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
at
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.ja
va:2895)
at
com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvo
cationHandler.java:242)
at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
at
com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:49
1)
at
com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactor
yImpl.java:364)
at
com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.
java:348)
at
com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:5
26)
at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
Caused by: java.sql.SQLException: A lock could not be obtained within the
time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossD
RDA(Unknown
Source)
... 38 more

--
View this message in context:
http://www.nabble.com/Derby-Error-Starting-Glassfish-tp23334048p23370987.htm
l
Sent from the NetBeans - EntPack mailing list archive at Nabble.com.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.287 / Virus Database: 270.12.15/2093 - Release Date: 05/02/09
14:23:00

RE: Derby Error Starting Glassfish

2009-05-04T10:14:18Z

I get "no suitable driver" on the connect command. What am I missing there?

This does in fact come up if I undeploy a few things, startup Glassfish, and re-deploy after it has finished it's start process. But if, and only if, my full application is loaded when Glassfish start, then the EJB timer service fails to start due to the time-out selecting from Derby.

Thanks

Manfred Riem wrote:

Hi there,

Have you tried executing the query against that database
yourself?

Manfred

> Hello -
>
> I seem to have reached the inescapable conclusion that Derby can not handle
> supporting the EJB timer service in Glassfish after the application reaches
> a certain point. And the only (drastic) choice is to reconfigure Glassfish
> with a different database.
>
> I only have one timer in my application, but a have been steadily adding SAs
> and I have 3 or 4 DB connection pools, so I guess one of those pushes it
> over the edge and prevents a valid start up?
>
> It's hard to believe that something has not been overlooked here, it really
> just doesn't work? Simple as that? Anyone else want to make a suggestion?
>
> Thanks - here is the startup exception again, just in case.
>
> JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
> problems running JDOQL query with params [server, 0]
> com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
> JDBC SQLException while executing the SQL statement:
> SQL statement<select distinct t0."TIMERID", t0."CREATIONTIMERAW",
> t0."LASTEXPIRATIONRAW", t0."CONTAINERID", t0."OWNERID", t0."STATE",
> t0."PKHASHCODE", t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from
> "EJB__TIMER__TBL" t0 where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and
> t0."STATE" = CAST (? AS INTEGER)> with input values:java.lang.String:server,
> java.lang.Integer:0.
> Please examine the SQLException for more information.
> NestedException: java.sql.SQLTransactionRollbackException: A lock could not
> be obtained within the time requested
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlException(SQLStoreManager.java:645)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:479)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> NestedStackTrace:
> java.sql.SQLTransactionRollbackException: A lock could not be obtained
> within the time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(ResultDesc.java:490)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.getResult(SelectQueryPlan.java:1576)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:477)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> Caused by: java.sql.SQLException: A lock could not be obtained within the
> time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 38 more

RE: Derby Error Starting Glassfish

2009-05-04T08:41:54Z

Hi there,

Have you tried executing the query against that database
yourself?

Manfred

> Hello -
>
> I seem to have reached the inescapable conclusion that Derby can not handle
> supporting the EJB timer service in Glassfish after the application reaches
> a certain point. And the only (drastic) choice is to reconfigure Glassfish
> with a different database.
>
> I only have one timer in my application, but a have been steadily adding SAs
> and I have 3 or 4 DB connection pools, so I guess one of those pushes it
> over the edge and prevents a valid start up?
>
> It's hard to believe that something has not been overlooked here, it really
> just doesn't work? Simple as that? Anyone else want to make a suggestion?
>
> Thanks - here is the startup exception again, just in case.
>
> JDO74009: Bean 'TimerBean' method ejbSelectAllTimersByOwnerAndState:
> problems running JDOQL query with params [server, 0]
> com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a
> JDBC SQLException while executing the SQL statement:
> SQL statement<select distinct t0."TIMERID", t0."CREATIONTIMERAW",
> t0."LASTEXPIRATIONRAW", t0."CONTAINERID", t0."OWNERID", t0."STATE",
> t0."PKHASHCODE", t0."INTERVALDURATION", t0."INITIALEXPIRATIONRAW" from
> "EJB__TIMER__TBL" t0 where t0."OWNERID" = CAST (? AS VARCHAR(32672)) and
> t0."STATE" = CAST (? AS INTEGER)> with input values:java.lang.String:server,
> java.lang.Integer:0.
> Please examine the SQLException for more information.
> NestedException: java.sql.SQLTransactionRollbackException: A lock could not
> be obtained within the time requested
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOSqlException(SQLStoreManager.java:645)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:479)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> NestedStackTrace:
> java.sql.SQLTransactionRollbackException: A lock could not be obtained
> within the time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.ResultDesc.getResult(ResultDesc.java:490)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.sql.generator.SelectQueryPlan.getResult(SelectQueryPlan.java:1576)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:477)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:376)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.retrieve(PersistenceManagerImpl.java:1118)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:689)
> at
> com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:607)
> at
> com.sun.ejb.containers.TimerBean_2100919770_ConcreteImpl.ejbSelectAllTimersByOwnerAndState(TimerBean_2100919770_ConcreteImpl.java:1700)
> at
> com.sun.ejb.containers.TimerBean.ejbHomeSelectAllActiveTimersOwnedByThisServer(TimerBean.java:709)
> 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
> com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
> at
> com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
> at
> com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
> at
> com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:242)
> at $Proxy24.selectAllActiveTimersOwnedByThisServer(Unknown Source)
> at
> com.sun.ejb.containers.EJBTimerService.restoreTimers(EJBTimerService.java:491)
> at
> com.sun.ejb.containers.ContainerFactoryImpl.restoreEJBTimers(ContainerFactoryImpl.java:364)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onReady(ApplicationLifecycle.java:348)
> at
> com.sun.enterprise.server.ApplicationServer.onReady(ApplicationServer.java:526)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:413)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
> 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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> Caused by: java.sql.SQLException: A lock could not be obtained within the
> time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 38 more